https://jsokit.com/blog/tags/encoding/ Recent content in Encoding on JsonKit Blog Hugo en © 2025 JsonKit Sun, 10 May 2026 11:42:34 +0000 https://jsokit.com/blog/posts/url-encoding-decoded-from-percent-signs-to-encodeuricomponent/ Sun, 10 May 2026 11:42:34 +0000 https://jsokit.com/blog/posts/url-encoding-decoded-from-percent-signs-to-encodeuricomponent/ URL Encoding Decoded: From Percent Signs to encodeURIComponent Last week, I was debugging a payment callback where URL parameters were double-encoded, causing order ID parsing failures. It turned out many developers still treat URL encoding as just “throw encodeURIComponent at it.” Let me break down the actual mechanics and implementation details. The Essence: Percent-Encoding URL encoding is officially called “percent-encoding.” The rule is straightforward: non-ASCII and special characters are represented as %XX, where XX is the character’s hexadecimal ASCII value. https://jsokit.com/blog/posts/svg-optimizer-implementation-from-regex-to-performance/ Mon, 04 May 2026 11:34:21 +0000 https://jsokit.com/blog/posts/svg-optimizer-implementation-from-regex-to-performance/ SVG Optimizer Implementation: From Regex to Performance Working on an icon library project, I noticed exported SVG files were often 50KB+. After optimization, they shrank by 60%. But manually uploading and downloading files every time was tedious. So I built my own SVG optimizer. Here’s how it works. Why Are SVG Files So Large? A typical unoptimized SVG: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="24" height="24"> <! https://jsokit.com/blog/posts/morse-code-encoderdecoder-from-telegraph-to-web-audio-api/ Fri, 17 Apr 2026 12:35:40 +0000 https://jsokit.com/blog/posts/morse-code-encoderdecoder-from-telegraph-to-web-audio-api/ Morse Code Encoder/Decoder: From Telegraph to Web Audio API I recently built a Morse code tool and dove into this 180-year-old encoding system. Looks simple, but the implementation has depth. The Essence of Morse Code Morse code is the ancestor of binary encoding. Only two states: dot (short signal) and dash (long signal). Like 0 and 1 in computing. The international Morse code character map: const MORSE_MAP: Record<string, string> = { 'A': '. https://jsokit.com/blog/posts/json-to-excel-tool-implementation-from-data-transformation-to-browser-side-file-generation/ Sun, 08 Mar 2026 15:59:12 +0000 https://jsokit.com/blog/posts/json-to-excel-tool-implementation-from-data-transformation-to-browser-side-file-generation/ JSON to Excel Tool Implementation: From Data Transformation to Browser-Side File Generation Written: May 7, 2026 at 21:14 As a frontend developer, data export requirements come up frequently. Users want to export JSON data returned from APIs into Excel. The product manager says “just add a button.” Sounds simple, but when you actually implement it, you need to consider encoding issues, data type handling, and file format compatibility. Let’s talk about how JsonKit’s JSON to Excel tool works under the hood. https://jsokit.com/blog/posts/implementing-json-to-csv-conversion-from-data-structure-to-table-format/ Sat, 07 Mar 2026 16:25:43 +0000 https://jsokit.com/blog/posts/implementing-json-to-csv-conversion-from-data-structure-to-table-format/ Implementing JSON to CSV Conversion: From Data Structure to Table Format I was recently working on a data export feature that required converting API JSON responses to CSV for users to download. I thought it would be simple string concatenation, but I discovered quite a few pitfalls - quote escaping, special characters, encoding issues… So I decided to document these details. CSV Format Specification (RFC 4180) Before writing code, let’s understand the CSV rules: https://jsokit.com/blog/posts/html-entity-encoding-from-xss-prevention-to-character-escaping-implementation/ Tue, 17 Feb 2026 13:57:34 +0000 https://jsokit.com/blog/posts/html-entity-encoding-from-xss-prevention-to-character-escaping-implementation/ HTML Entity Encoding: From XSS Prevention to Character Escaping Implementation Building a content management system recently, I needed to safely display user-submitted text on pages. Direct rendering? XSS attacks await. Escape everything? Garbage output. That’s where HTML entity encoding comes in. What Are HTML Entities HTML entities represent special characters using specific character sequences. For example, < becomes <, > becomes >. These seemingly cryptic strings solve two core problems: https://jsokit.com/blog/posts/building-a-document-format-converter-from-txtmarkdownhtml-to-any-format/ Sun, 08 Feb 2026 17:58:53 +0000 https://jsokit.com/blog/posts/building-a-document-format-converter-from-txtmarkdownhtml-to-any-format/ Building a Document Format Converter: From TXT/Markdown/HTML to Any Format Every time I need to embed a Markdown document into a webpage or extract plain text from HTML, I end up installing desktop software or writing scripts. But the core logic of document format conversion isn’t that complex — browser APIs can handle most cases. Let me walk through building a pure frontend document converter. The Essence: Re-encoding Text Document format conversion sounds fancy, but it boils down to three steps: read source file → parse content structure → re-encode in target format. https://jsokit.com/blog/posts/building-a-code-sharing-tool-url-hash-storage-and-base64-encoding-techniques/ Fri, 30 Jan 2026 15:09:21 +0000 https://jsokit.com/blog/posts/building-a-code-sharing-tool-url-hash-storage-and-base64-encoding-techniques/ Building a Code Sharing Tool: URL Hash Storage and Base64 Encoding Techniques Recently, I built a code sharing tool that requires a “no backend, permanent validity” sharing mechanism. After researching several approaches, I chose URL Hash + Base64 encoding - simple and reliable. Why URL Hash Storage? Traditional code sharing tools use two approaches: Backend database storage - Store code in database, generate short links. Pros: short links. Cons: needs backend, storage cost, links can expire. https://jsokit.com/blog/posts/base64-encodingdecoding-from-btoa-to-full-unicode-support/ Sat, 24 Jan 2026 15:39:10 +0000 https://jsokit.com/blog/posts/base64-encodingdecoding-from-btoa-to-full-unicode-support/ Base64 Encoding/Decoding: From btoa to Full Unicode Support I recently worked on a project requiring safe text data transmission, and Base64 encoding was unavoidable. While I’ve used it countless times, implementing a reliable tool revealed some interesting details worth sharing. What is Base64? Simply put, Base64 is a method to represent binary data using 64 printable characters: Uppercase letters A-Z (26 characters) Lowercase letters a-z (26 characters) Digits 0-9 (10 characters) + and / (2 characters) Plus = for padding at the end. https://jsokit.com/blog/posts/the-encoding-principles-behind-barcodes-building-an-online-barcode-generator/ Sat, 24 Jan 2026 12:32:47 +0000 https://jsokit.com/blog/posts/the-encoding-principles-behind-barcodes-building-an-online-barcode-generator/ The Encoding Principles Behind Barcodes: Building an Online Barcode Generator Recently added a barcode generation feature to a project. Turns out those black-and-white stripes have some interesting encoding rules underneath. What is a Barcode? A barcode converts numbers or letters into alternating black and white stripes. When a scanner reads it, black bars absorb light while white spaces reflect it, generating electrical signals that decode back to the original content.