Chakma Transliterator Roman to Chakma Unicode Online

What is Chakma Transliterator Roman to Chakma Unicode Online?

This Agent converts text between Romanized Chakma and Unicode Chakma (Ojhopath) script. It works from a fixed substitution table covering consonants, independent vowels, dependent vowel signs, digits and Chakma punctuation. You type or paste text, say which direction you want (or let the Agent detect it), and receive copyable Unicode output plus a short note on anything that was left unchanged.

It is a transliterator, not a translator: it maps written tokens, it does not translate meaning, fix grammar, or supply vocabulary outside the table.

Key Features

• Roman to Chakma conversion for tokens such as ka, kha, ga, aa, -i, -aau, digits 0-9 and punctuation like ?, ., ~, _, *, ** and ...
• Chakma to Roman reverse conversion using the same table inverted, so 𑄇 returns ka and 𑄶 returns 0
• Longest-match-first ordering, so multi-character tokens such as ... and ** and kha are matched before shorter keys
• Preservation of unmapped characters: Latin letters, spaces and symbols outside the table are kept as-is and listed in a note rather than silently dropped
• Direction detection with manual override: if your text contains Chakma codepoints the Agent assumes Chakma to Roman; you can always state the direction explicitly

How to Use

1. Paste or type your text and state the direction, for example: "Roman to Chakma: ka kha ga 123". If you omit the direction, the Agent infers it from the script present.
2. Read the converted text in the code block first; that block is the exact output you can copy.
3. Check the short note beneath it for any characters that were not in the mapping, then ask for a correction or a different direction if needed.

Example Use Cases

• Roman to Chakma script conversion for a name or short phrase: input "Roman to Chakma: ka kha ga" returns the three Chakma consonant characters in order.
• Chakma Unicode to Roman transliteration for reading practice: paste a line of Ojhopath text and get a Roman token string you can sound out.
• Digit and punctuation conversion for labels: convert "123?" so the digits become Chakma numerals and the question mark becomes the Chakma question mark.

Tips for Best Results

• Write dependent vowel signs with the leading hyphen exactly as in the table (for example -i, -uu, -aau); the hyphen is part of the key.
• Keep tokens separated by spaces when you want predictable matching, especially around multi-character punctuation such as ... and **.
• If a character comes back unchanged, it is outside the table; the note will tell you which ones.

FAQ

What input format does it accept?
Plain text. Roman Chakma tokens, Unicode Chakma characters, digits and punctuation are all accepted. There is no file upload and no length guarantee beyond what the chat can hold; very long passages should be sent in sections.

How accurate is the conversion?
It is exact for tokens present in the mapping table, because the substitution is deterministic and applied by a script rather than guessed. Anything outside the table is preserved and reported, so accuracy is limited by table coverage, not by interpretation.

How does this compare with some free text tools?
Some free text tools present two boxes and a Send button with an undocumented mapping. This Agent states its ordering rule, preserves unmapped characters, reports them, and supports an explicit reverse direction, all as copyable text in the conversation.

Does it translate Chakma language?
No. It transliterates script. Meaning, grammar and vocabulary are outside its scope.