O que Unicode String Inspector faz?
Unicode String Inspector permite inspecionar dados diretamente no navegador e informa com clareza o resultado e os limites. Recursos verificados: Grapheme-aware counts, Unicode code points, UTF-8 byte counts, Safe grapheme reversal.
Count the unit users actually perceive
Use graphemes for user-visible length and reversal, code points for Unicode analysis, UTF-16 units for JavaScript storage behavior, and UTF-8 bytes for transport limits.
Como usar?
- Paste any Unicode text.
- Choose Inspect, Reverse graphemes, or Split graphemes.
- Review counts and per-grapheme code points, UTF-16 units, and UTF-8 bytes.
Exemplo real de entrada e saída
Inspect a multi-code-point emoji
Entrada
👩💻Saída
Graphemes: 1
Code points: 3
UTF-16 units: 5
UTF-8 bytes: 11A visible emoji sequence can contain multiple Unicode code points joined into one grapheme cluster.
Erros comuns e correções
| Sintoma | Causa provável | Correção |
|---|---|---|
| The character count differs from string length in code. | Many runtimes expose UTF-16 code units or code points rather than grapheme clusters. | Choose the measure that matches the product requirement. |
| A reversed emoji breaks apart elsewhere. | The destination lacks equivalent grapheme segmentation or font support. | Test segmentation and rendering in the target environment. |
Important behavior of String Inspector
Limite específico desta ferramenta: Grapheme clusters, code points, UTF-16 units, and visible glyphs are different measures and can produce different counts.
Padrões e referências de implementação
- Unicode Standard Annex #29 (opens in a new tab)Defines Unicode text segmentation and grapheme-cluster boundaries.
- ECMAScript Intl.Segmenter (opens in a new tab)Defines the browser segmentation API used by the inspector.
String Inspector — FAQ
Does the String Inspector upload my input?
No. Processing runs in the current browser tab, and the page does not send tool input to a KitLumi processing endpoint.
What input does the String Inspector accept?
It accepts any Unicode text. The workspace checks the input and reports malformed or unsupported values before it produces a result.
What does the String Inspector produce?
It produces summary counts, a character table, reversed grapheme text, or one grapheme per line. Copy and download controls appear when the output format supports them.
What limitation should I know?
Grapheme clusters, code points, UTF-16 units, and visible glyphs are different measures and can produce different counts.
O que mudou?
Atualização material: String Inspector: Added Grapheme-aware counts, Unicode code points, UTF-8 byte counts, Safe grapheme reversal, responsive controls, explicit runtime disclosure, and task-specific examples and limitations.