Text that looks identical on screen is not always represented identically in memory or in a URL. Unicode normalization and percent-encoding solve different problems, and confusing them can create subtle bugs in search, comparison, storage and web requests.
One visible character can have different code points
Some accented characters can be represented as a single precomposed code point or as a base character followed by a combining mark. They may look the same while their underlying sequences differ. The Unicode Normalizer lets you apply NFC, NFD, NFKC or NFKD and inspect the resulting code points.
Use NFC when you want canonical composition, or NFD when decomposed representation is useful for analysis. NFKC and NFKD also apply compatibility mappings, so they can change distinctions that matter in some contexts. Normalization should be a deliberate choice, not an automatic cleanup step for every string.
URL components are not complete URLs
A URL contains structural characters such as slashes, question marks and ampersands. When encoding a single query value, use component encoding so reserved characters inside that value do not accidentally become URL structure. The URL Codec offers separate operations for components and complete URIs.
Inspect text before transforming it
Text Fingerprint reports character counts and UTF-8 size, while Text & Base64 Toolkit handles common text and Base64 conversions. These checks can help distinguish character-count problems from byte-length or encoding problems.
Use the right transformation
Normalization changes the representation of Unicode text. URL encoding makes data safe to place in a URL component. Neither operation encrypts information or makes sensitive data secret.
Try the gioyous.it browser tools for these small developer tasks. Most utilities run locally in your browser, and each page explains when an external service is involved.
What do you want to say about this?