What ト means
It is “to” in Japanese katakana, shown in a narrow legacy form.
In a Japanese word or name, ト contributes the syllable /to/; it has no standalone idea. Its ordinary fullwidth counterpart is ト. Katakana also writes foreign-origin words, some proper names, slang, and onomatopoeia, so the surrounding word—not the width—determines the message.
Katakana grew from abbreviated Chinese-character strokes used as notes between lines to record Japanese readings of Chinese sentences. Buddhist scholars were using it this way in the early ninth century. Its forms coexisted with Man’yōgana, an older way of writing Japanese sounds with Chinese characters, and with hiragana; katakana became more standardized by the twelfth century. ト is a much later computer compatibility form paired with ト, made for one-byte and legacy character systems rather than a new pronunciation.
Use ト for ordinary Japanese; keep ト for legacy constraints
ト and ト represent the same syllable in different compatibility forms. NFKC and NFKD normalization can fold the width distinction for matching; NFC preserves it. Use compatibility normalization only when losing width information is acceptable. “Halfwidth” is a legacy layout term, not a promise that every font draws the glyph at exactly half the pixels; font and layout affect its visible width.
Use ト when a receiving field or preserved source calls for halfwidth kana. For new Japanese prose or a field that requests fullwidth katakana, use ト. Fullwidth kana is the safer default for ordinary text; single-byte halfwidth kana mainly serves legacy compatibility.
Technical and legacy-looking: it signals a width or encoding constraint, not extra emphasis.
If a field expects fullwidth katakana, use ト; ト can remain a different string even when the sound is identical.
Don't confuse it with
1Questions people ask
2Will NFKC turn ト into ト?
Yes. NFKC compatibility-normalizes the narrow form to its fullwidth counterpart, which can help matching but removes the width distinction.
Can I use ト in a Japanese name field?
Only if the field allows halfwidth kana. The pronunciation stays the same, but software can distinguish the two forms, so follow the field’s width rule.
How to type ト
ト\FF84Codes and encoding1 code points
A visible symbol can contain several code points. JS .length counts UTF-16 units; UTF-8 counts bytes.
