Understanding the HTML Entity Encoder

The HTML Entity Encode tool is designed to parse text and convert specific reserved HTML characters and high-value Unicode characters into their corresponding decimal numeric character references. Rather than sending data to a backend server, the utility processes your input directly using client-side Alpine.js bindings and native JavaScript string manipulation methods.

For its user interface, the tool relies on Ace Editor (version 1.8.1) loaded from the Cloudflare CDN. The editor is configured with the "clouds" theme and is specifically set to ace/mode/html. This ensures that when you paste large blocks of HTML, the editor provides appropriate syntax highlighting, even before you trigger the encoding process. The interface also includes a direct-to-clipboard copy button that calls a custom window.writeClipboardText method, extracting the contents directly from the Ace Editor instance.

How the Conversion Algorithm Works

When you click the submit button, an Alpine.js convert() function is executed. This function retrieves the current value of the Ace Editor and applies a targeted Regular Expression replacement algorithm. The exact regex used by the tool is /[\u00A0-\u9999<>\&]/g.

This regular expression captures three distinct categories of characters:

• Reserved HTML Characters: The less-than sign (<), the greater-than sign (>), and the ampersand (&). Note that double and single quotes are not targeted by this specific pattern.
• Extended ASCII and Latin-1 Supplement: Starting at Unicode \u00A0 (the non-breaking space) up through the rest of the Latin-1 block, including accented characters, currency symbols, and copyright marks.
• High Unicode Characters: The match extends all the way to \u9999, which covers a massive array of symbols, Greek letters, Cyrillic scripts, and many CJK (Chinese, Japanese, Korean) Unified Ideographs.

For every character that matches this pattern, the tool executes a callback function that reads the character's decimal code point using JavaScript's charCodeAt(0) method. It then constructs a string starting with &#, followed by the decimal code point, and ending with a semicolon (;). The original text in the editor is then completely overwritten with the newly encoded string.

Concrete Worked Example

To understand exactly how this logic transforms text, consider the following HTML snippet containing standard tags, an ampersand, and an accented character:

Here is how the algorithm evaluates this specific string:

• Standard ASCII Text: The characters h, 1, C, a, f, (standard space), B, a, and r fall outside the regex pattern. Their Unicode values are below \u00A0 and they are not <, >, or &. They remain completely unchanged in the final output.
• The < and > characters: These are explicitly matched. The < resolves to decimal 60 (<) and the > resolves to decimal 62 (>).
• The accented é: This is a Latin-1 supplement character located at Unicode \u00E9. Because it falls within the \u00A0-\u9999 range, it is matched. Its decimal character code is 233, transforming it into é.
• The ampersand &: Explicitly matched by the regex, resolving to decimal 38 (&).

Notice that the standard spaces (ASCII 32) are preserved as raw spaces, while all structural HTML characters and extended characters are strictly converted to decimal numeric references.

Frequently Asked Questions

Does this tool generate named HTML entities?

No. The conversion logic exclusively generates decimal numeric character references (e.g., < instead of <). Because it utilizes the charCodeAt(0) method programmatically across a vast Unicode range, creating named entities would require a massive lookup table. The decimal approach is computationally lightweight, perfectly valid across all web browsers, and mathematically robust.

Are standard spaces encoded by the tool?

Standard space characters (ASCII 32) fall below the \u00A0 threshold in the regex pattern and are left untouched. However, non-breaking spaces (NBSP), which sit exactly at \u00A0, will be caught by the algorithm and encoded as  .

Why aren't single and double quotes encoded?

The underlying regular expression targets a specific bracketed set: [\u00A0-\u9999<>\&]. Single quotes (ASCII 39) and double quotes (ASCII 34) are standard characters below the \u00A0 cutoff and are not explicitly listed alongside the ampersand and angle brackets. Therefore, they remain unchanged. If you are placing the output of this tool directly inside an HTML attribute (like value="..."), you must handle quote escaping manually to prevent attribute injection.

How does the editor perform with extremely large files?

The tool utilizes Ace Editor, a high-performance code editor built for the web. By turning off the print margin (showPrintMargin: false) and setting the mode to HTML, the editor can comfortably handle thousands of lines of code without layout thrashing. The JavaScript string replacement function executes in a single pass using the global (g) regex flag, making the actual conversion almost instantaneous even for very large HTML documents.