What カ means
カ is the same katakana “ka” as カ, in a narrow compatibility form. Unicode maps it to カ for compatibility; the font determines how either character looks on screen.
This form developed through Japanese character encodings. A 7-bit JIS C 6220 prototype appeared in 1967. Its 8-bit successor, JIS X 0201, made ASCII and Japanese kana available in the same encoding. JIS X 0208 later included a separate, square form of the kana, and Shift JIS carried both sets. The earlier encoding form remains useful for compatibility and conversion.
“Halfwidth” describes a traditional display convention, not how many bytes the character must use. Encoding determines storage, while the font determines visible width.
Will カ work in a Japanese form?
Only if the field accepts half-width kana. Japanese systems have different rules: e-Gov guidance lists JIS X 0201 among accepted input characters, while a Ministry of Health style rule replaces half-width katakana with full-width forms.
If a field gives no special instruction, カ is the safer choice. Use カ when the field or data format explicitly requires the half-width form.
Technical or legacy in feel; neutral when a field explicitly requires half-width kana.
If the field gives no instruction, choose カ; カ may be rejected or changed.
Part of the collection
Who writes カ
Loading…
Don't confuse it with
1Combination ideas
1Questions people ask
1Can カ turn into mojibake in email?
It can in an older ISO-2022-JP path. RFC 1468 (1993) excludes JIS X 0201 kana from that mail encoding, so an incompatible converter may reject, replace, or transform カ. If the encoding is unknown, カ is safer.
How to type or find カ
- Also called
- 半角カナ · 半角カタカナ · hankaku kana
- Search it as
- jisx0201 · jis-kana · halfwidth · hankaku · halfwidth-kana · hankaku-kana · one-byte-kana · narrow-kana
- Shows up in
- Anything that takes text · its shape is whatever your font draws
カ\FF76Codes and encoding1 code points
A visible symbol can contain several code points. JS .length counts UTF-16 units; UTF-8 counts bytes.


