Trouver un outil

↑↓ parcourir Enter ouvrir

Recherchez par tâche si vous ne connaissez pas le nom exact.

Unicode String Inspector

Traitement local

Unicode String Inspector permet de inspecter des données dans le navigateur et présente clairement le résultat et ses limites. Cette page contient un exemple réel d’entrée et de sortie, les limites d’implémentation et les sources primaires de cet outil.

Vérifié · Mis à jour · Gratuit · Sans compte

String Inspection Workspace
Input0 characters
Output
Files and text stay in this browser tab.

Que fait Unicode String Inspector ?

Unicode String Inspector permet de inspecter des données dans le navigateur et présente clairement le résultat et ses limites. Fonctions vérifiées : 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.

Comment l’utiliser ?

  1. Paste any Unicode text.
  2. Choose Inspect, Reverse graphemes, or Split graphemes.
  3. Review counts and per-grapheme code points, UTF-16 units, and UTF-8 bytes.

Exemple réel d’entrée et de sortie

Inspect a multi-code-point emoji

Entrée

👩‍💻

Sortie

Graphemes: 1
Code points: 3
UTF-16 units: 5
UTF-8 bytes: 11

A visible emoji sequence can contain multiple Unicode code points joined into one grapheme cluster.

Erreurs fréquentes et corrections

SymptômeCause probableCorrection
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 propre à cet outil : Grapheme clusters, code points, UTF-16 units, and visible glyphs are different measures and can produce different counts.

Normes et références d’implémentation

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.

Quelles modifications ?

Mise à jour substantielle : 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.

Qui maintient cet outil ?

KL
KitLumi EngineeringKitLumi Engineering maintient le comportement, les tests, les exemples et les informations de confidentialité.