Skip to content

Transliteration & parsing

These methods convert text between scripts, detect look-alike strings, and parse locale-formatted numbers, money, and dates back into values.

Method Use it for
transliterate(text, id) Run any ICU transform (script conversion, decomposition)
romanize(text) The common "to ASCII Latin" case — slugs, search keys
confusable(a, b) Are these two strings visually confusable?
suspicious(text) Is this single string spoof-prone (mixed-script)?
parseNumber / parseMoney / parseDate / parseMoment The inverse of the formatters

These methods use ICU transforms, spoof checks, and parsers.

Transliterate & romanize

transliterate(text, id) runs any ICU transform. The id is a transform specification — a source/target pair, optionally chained with ;:

id Effect
Greek-Latin Greek script → Latin
Any-Latin any script → Latin (best-effort)
Latin-ASCII strip Latin diacritics to plain ASCII
Any-Latin; Latin-ASCII the chain most slugs want
Any-Hangul, Cyrillic-Latin, Han-Latin, … other script pairs

romanize(text) is the pre-chained common case (Any-Latin; Latin-ASCII) — to Latin, then stripped to ASCII — ideal for slugs and search keys.

An unknown transform id throws. The full list of ids available on your runtime comes from supportedValues("transliterator") — the one supportedValues key beyond the standard six.

Spoof detection

confusable(a, b) asks whether two strings are visually confusable (e.g. a Cyrillic look-alike of a Latin brand). suspicious(text) flags a single string as spoof-prone — typically because it mixes scripts that shouldn't appear together.

Backed by UTS #39

Both checks implement Unicode Technical Standard #39, Unicode Security Mechanisms — the standard that defines the confusable-character data and mixed-script detection rules — through ICU's SpoofChecker.

Use these to defend account names, domains, and brand mentions against homograph attacks — suspicious() on signup to reject mixed-script usernames, confusable() to flag a new name that mimics an existing one.

Parsing (inverse formatters)

Intl can only format, never parse — but ICU's parsers are available in the other this library. Each reads the kind of text produced by its corresponding formatter:

Parser Inverts Returns
parseNumber(text) number() a float
parseMoney(text) money() amount and currency
parseDate(text, width?) date() a native date (width defaults to short)
parseMoment(text, pattern) formatMoment() a native date from a raw pattern

A few things worth knowing:

  • The locale matters — parseNumber("1.234,56") reads 1234.56 in de but would read 1.234 in en. Parse in the same locale you formatted (or the user's input locale).
  • parseDate()'s width must match how the text was produced — a "long" string won't parse with the short skeleton. Set a timeZone modifier so the resulting moment is anchored, not shifted by the runtime zone.
  • parseMoney() returns the amount and the recognised currency as a (double, string) tuple.- Text that doesn't parse throws rather than returning 0 — so you can reliably distinguish a real "0" from unparseable input. Wrap user input in a try/catch.