
Many Myanmar newspapers exist only as scanned pages or PDF files.
A computer cannot easily read the Burmese text inside them, so this text cannot be searched or used to build Burmese AI models.
Our OCR (Optical Character Recognition) research builds a system that reads these newspaper pages and turns them into clean, accurate Burmese text.
Why this is hard
Burmese letters stack and join in complex ways. For example, the word မြန်မာ ("Myanmar") is stored as six characters. One of them (ြ) wraps around the first letter, and another (်) is a small mark at the top. An OCR tool must read every mark correctly, because one small mistake changes the word. Burmese also does not always put spaces between words.
Newspaper pages add more problems: many columns, headlines in large decorative fonts, photos, advertisements and boxes of text side by side. Very few OCR tools are trained on Burmese, and almost none on Myanmar newspapers.
How the system works
Two parts of this system are models that we fine-tuned ourselves: the layout model and the OCR engine. The sections below explain how we built them and how well they work.
Step 1: Comparing existing tools
We first tested seven existing page-layout models on real Myanmar newspaper pages, including DocLayout-YOLO [1], PP-DocLayout [4], RT-DETR [5] and DeepSeek-OCR [6]. On the same page, one model found 59 parts of the page while another found only 5. No single tool worked well enough on its own, so we decided to fine-tune our own models.
Step 2: Creating our own training data
To teach a model, we need examples with the correct answers. On nearly 500 newspaper pages, we drew a box around every part of the page (headline, body text, photo, caption, advertisement and so on), gave it a label, and marked the reading order. We always tested the models on pages from newspaper issues that they had never seen, so the scores show how they work on new pages.
Step 3: Fine-tuning the layout model
What is fine-tuning?
Fine-tuning means taking a model that has already learned from many general examples and training it a little more on our own examples. The model keeps what it already knows and learns the special features of our data. This needs much less data and time than training a new model from zero.
We started from DocLayout-YOLO [1], a model already trained on many kinds of documents such as reports and books, and trained it further on our labelled pages.
Result: the detection score rose from 49% to 91%, and the model now finds 89% of the parts of a page, up from 44%. (The detection score shows how many parts the model finds and how accurately it places the boxes. 100% is perfect.)
Example: the model finds most advertisements, photos and body text areas. Headlines are the hardest part, because their size and style change a lot from page to page.
Next version: a newer version that is better at small headlines is being tested. We will use it once it passes all our checks.
Step 4: Fine-tuning the OCR engine
Tesseract [2] is a free, open-source OCR engine. Its standard Burmese model made many mistakes on newspaper print, so we fine-tuned it with about 10,700 line images from our own pages, each paired with its correct text. We then tested it on a full newspaper issue that it had never seen.
Character errors (lower is better)
Old setup (standard model) 5.7%
Our fine-tuned model 3.4%
The character error rate is the share of characters that are wrong: 3.4% means about 3 wrong characters in every 100. Our model makes about 40% fewer mistakes. Here are three real lines from the test issue, read by the old setup and by our fine-tuned model:
Example 1: numbers read correctly
Text (mistakes in underline)
Old setup (before): ပွဲချိန် ၁၈ မိနစ်နှင့် ပွဲချိနဲ ဂု၄ မိနစ်
Fine-tuned model (after): ပွဲချိန် ၁၈ မိနစ်နှင့် ပွဲချိန် ၇၄ မိနစ်
Correct text: ပွဲချိန် ၁၈ မိနစ်နှင့် ပွဲချိန် ၇၄ မိနစ်
Meaning in English:: "in the 18th minute and the 74th minute of the match". The old setup read the number 7 (၇) as letters.
Example 2: stacked letters read correctly
Text (mistakes in underline)
Old setup (before): စတဲ့သီးနှံတွေ စိုက်ပိူူးပါတယ် စိုက်ပျိုးတဲ့
Fine-tuned model (after): စတဲ့သီးနှံတွေ စိုက်ပျိုးပါတယ် စိုက်ပျိုးတဲ့
Correct text: စတဲ့သီးနှံတွေ စိုက်ပျိုးပါတယ် စိုက်ပျိုးတဲ့
Meaning in English:: "... we grow crops such as these. The crops we grow ...". The old setup misread the word for "grow".
Example 3: much better, but not perfect
Text (mistakes in underline)
Old setup (before) : ြိုင်ပွဲ၀င်ကစားသမား 99095) ယောက်တို့ ပါဝင်
Fine-tuned model (after): ပြိုင်ပွဲဝင်ကစားသမား ၁၁၃၇၅ ယောက်တို့ ပါဝင်
Correct text: ပြိုင်ပွဲဝင်ကစားသမား ၁၃၇၅ ယောက်တို့ ပါဝင်
Meaning in English: "1,375 players took part in the competition". The fine-tuned model read the words correctly but added one extra digit to the number.
Step 5: Testing AI text correction
We also asked Gemma 4 [3], a large language model, to look at each line image and its OCR text and fix the mistakes. We compared the results with text typed by a person. Here are two real lines from this test, using the OCR from before fine-tuning:
Example 1: all mistakes fixed
OCR output (before): ညီလာခံကြီးဇါ ဆုံးဖြတ်ချက်ဖြင့် နှစ်စဉ် ဒီဧငဲဘာ ၃ ရက်နေ့ကို အပြည်ပြည်ဆိုင်ရာ မသနိစ္ဗမ်းသူများနေ့
After AI correction: ညီလာခံကြီး၏ ဆုံးဖြတ်ချက်ဖြင့် နှစ်စဉ် ဒီဇင်ဘာ ၃ ရက်နေ့ကို အပြည်ပြည်ဆိုင်ရာ မသန်စွမ်းသူများနေ့
Correct text (typed by a person) :ညီလာခံကြီး၏ ဆုံးဖြတ်ချက်ဖြင့် နှစ်စဉ် ဒီဇင်ဘာ ၃ ရက်နေ့ကို အပြည်ပြည်ဆိုင်ရာ မသန်စွမ်းသူများနေ့
Meaning in English: "By decision of the General Assembly, 3 December every year [was named] International Day of Persons with Disabilities"
Example 2: the number is fixed, but one mistake is missed
Text (mistakes in underline)
OCR output (before)
၁၉၉၂ ခုနှစ် အောက်တိုဘာ ၁၄ရက်တွင် ကျင်းပခဲ့သော (၄ဂု) ကြိမ်မြေ၁က် ကုလသမဂ္ဂကအထွေထွေ
After AI correction: ၁၉၉၂ ခုနှစ် အောက်တိုဘာ ၁၄ရက်တွင် ကျင်းပခဲ့သော (၄၇) ကြိမ်မြောက် ကုလသမဂ္ဂကအထွေထွေ
Correct text (typed by a person): ၁၉၉၂ ခုနှစ် အောက်တိုဘာ ၁၄ရက်တွင် ကျင်းပခဲ့သော (၄၇) ကြိမ်မြောက် ကုလသမဂ္ဂအထွေထွေ
Meaning in English: "... held on 14 October 1992, the 47th United Nations General [Assembly] ..."
Better overall: lines with no mistakes rose from 28% to 47%.
Not perfect: the AI sometimes added new mistakes, so people still need to review important text.
Faster with better OCR: with our fine-tuned OCR, only a few unclear lines need AI correction. On a test page, the correction time fell from tens of minutes to about 17 seconds.
Step 6: Building Version 4
Many newer newspaper PDFs already contain the real text inside the file. Reading that text directly is faster and more accurate than OCR. Our current system, Version 4, checks every page: if the PDF text is usable, it uses that text; if not, for example on a scanned page, it uses our fine-tuned OCR. It then puts headlines, author names and body text in reading order and saves them as a clean dataset.
Quality check: we compared 598 lines with text typed by a person. 572 lines matched exactly, and 99.9% of characters were correct (not counting spaces).
Key results
Finding the parts of a page (layout model)| Detection score rose from 49% to 91%. | Newspaper pages not used in training
Reading Burmese text (OCR) | Character errors fell from 5.7% to 3.4%, about 40% fewer mistakes.| A newspaper issue not used in training
AI text correction| Lines with no mistakes rose from 28% to 47%.| Checked against text typed by a person
Correction speed| Time per page fell from tens of minutes to about 17 seconds.| One test page
Final text quality (Version 4)| 99.9% of characters were correct (not counting spaces).| Checked against text typed by a person
Text extracted so far
Our system has extracted Burmese text from 787 newspaper pages across three Myanmar newspapers, about 2.8 million tokens in total. A token is a small piece of text that language models read.
Limits and what comes next
The Version 4 quality check covered pages with usable PDF text. Next, we will check scanned pages read by OCR in the same way.
The OCR engine was trained on one newspaper's print. We plan to add more newspapers and years and retrain it with more data.
Small headlines are still the hardest part for the layout model. A new version is being tested.
References
1.Zhao, Z., Kang, H., Wang, B. and He, C. (2024). DocLayout-YOLO: Enhancing Document Layout Analysis through Diverse Synthetic Data and Global-to-Local Adaptive Perception. arXiv:2410.12628. https://arxiv.org/abs/2410.12628
2.Smith, R. (2007). An Overview of the Tesseract OCR Engine. Proceedings of the Ninth International Conference on Document 3.Analysis and Recognition (ICDAR 2007), pp. 629–633. https://research.google/pubs/an-overview-of-the-tesseract-ocr-engine/
Gemma Team (2026). Gemma 4 Technical Report. arXiv:2607.02770. https://arxiv.org/abs/2607.02770
4.Sun, T., Cui, C., Du, Y. and Liu, Y. (2025). PP-DocLayout: A Unified Document Layout Detection Model to Accelerate Large-Scale Data Construction. arXiv:2503.17213. https://arxiv.org/abs/2503.17213
5.Zhao, Y., Lv, W., Xu, S., et al. (2023). DETRs Beat YOLOs on Real-time Object Detection. arXiv:2304.08069. https://arxiv.org/abs/2304.08069
6.Wei, H., Sun, Y. and Li, Y. (2025). DeepSeek-OCR: Contexts Optical Compression. arXiv:2510.18234. https://arxiv.org/abs/2510.18234