iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Chrome extension can convert Hanifi Rohingya text on a webpage into Rohingyalish—the Latin-script form of the same language—so readers do not have to copy text into a converter and paste it back. The core design is to detect Hanifi characters by their Unicode code points, transform eligible page text nodes, and let the reader restore the original. This is transliteration, not translation: the writing system changes, but the language and meaning are not translated.
What the extension should do
Hanifi Rohingya is an alphabetic, right-to-left script in Unicode’s U+10D00–U+10D3F range. Rohingya is also written in Myanmar, Arabic, and Latin scripts. The Unicode Consortium estimates approximately one million Rohingya speakers and describes Hanifi Rohingya as “an alphabetic script written from right to left” in Unicode 18.0, Chapter 16.
For a reader-facing extension, the useful outcome is a clear “Convert this page” action and a matching way to “Show original.” The extension listing describes these controls, although its current publication status should be checked rather than assumed. Chrome Web Store search results and the author’s September 27, 2026 article do not establish a settled listing status.
Detect Hanifi text, not just the page language
Do not rely solely on the page’s lang attribute or on its chosen font. The extension author reports that Hanifi text is often not marked correctly on webpages. Instead, inspect text for characters in the Hanifi Rohingya block, U+10D00 through U+10D3F. This also lets a page containing multiple scripts be handled selectively rather than treated as entirely Rohingya.
The author’s implementation splits text into Hanifi runs, converts those runs, and passes other scripts and punctuation through unchanged. That behavior is the author’s implementation description, not an independent test of every mixed-script case. See the RohingyaLanguage.org implementation article.
Choose how the extension gets page access
Chrome content scripts can inspect and modify a page’s DOM while running in an isolated world. Chrome supports declaring content scripts statically or dynamically, as well as injecting them programmatically. For a reader-triggered conversion, programmatic injection with activeTab and the scripting permission is a narrow option: the user invokes the extension on the current tab, rather than granting continuing access to every site. Chrome documents the approach in its Scripting API and activeTab guide.
Rank #2
If the extension offers an “always convert this website” setting, it needs permission to access that site. Chrome’s permissions documentation recommends optional permissions when they fit the design, so users can grant host access at runtime instead of receiving broader access by default.
Transform text without taking over the page
Work with text nodes
Change existing text-node data rather than replacing an element’s innerHTML. Replacing markup can remove event listeners or interfere with framework-managed page state. The implementation article recommends recording both the original text and the exact converted value written by the extension. When restoring, replace the text only if it still matches the extension’s recorded output; if the page changed it in the meantime, do not overwrite that newer content.
Skip active and code-oriented regions
Leave text alone where changing it could disrupt typing, editing, or code. The author’s implementation skips scripts, styles, inputs, textareas, contenteditable regions, elements with role="textbox", code blocks, and common code editors. This is especially important for a reversible reading aid: converting text under a cursor or inside an editor could alter what a user is composing.
Handle pages that update after loading
Modern pages may add or replace content after the initial document scan. The author describes using a MutationObserver to process added or changed nodes rather than repeatedly rescanning the entire page. The article reports approximately 12 ms work slices and a conversion of a 5,000-paragraph page in around 0.4 seconds with zero long tasks. Those are the author’s reported test conditions, not a general Chrome-extension performance guarantee.
Rank #4
Make conversion reversible and understandable
Expose conversion as an explicit reader action, and provide “Show original” so the user can return to the source text. A conversion toggle should also account for content that changes while conversion is active: restore only text that still equals the extension’s own written value, then process later mutations according to the selected mode. The author describes this record-and-check approach as a way to avoid overwriting page changes.
Recommended Free Tools
Explain that the result is approximate. The author reports a round-trip consistency check over 9,200 distinct dictionary words, with 187 entries failing to round-trip. The article attributes discrepancies to spelling conventions, including ts, sh, and ng/ny versus ñg/ñy. This is a dictionary-specific consistency result, not a human-rated accuracy score or evidence that a given percentage of webpages will be correct. Fluent Rohingya readers still need to review the output.
The same article describes 15,926 lexicon rows built from 6,510 English dictionary entries. It says generated Hanifi entries were not individually reviewed, so those entries should be described as converter-consistent rather than verified spellings.
Separate extension output from source-page font problems
If Hanifi characters on the original webpage appear as boxes or question marks, the source device may not have a font that covers the Hanifi Rohingya block. The language reference identifies Noto Sans Hanifi Rohingya as a free font. This is a source-page display issue: the extension’s Latin-script output does not itself require that font. See the reference’s explanation of Hanifi Rohingya script and display.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
