File size: 45,855 Bytes
f9bc0c1 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 | % Options for packages loaded elsewhere
\PassOptionsToPackage{unicode}{hyperref}
\PassOptionsToPackage{hyphens}{url}
\documentclass[
10pt,
]{article}
\usepackage{xcolor}
\usepackage[margin=0.75in]{geometry}
\usepackage{amsmath,amssymb}
\setcounter{secnumdepth}{-\maxdimen} % remove section numbering
\usepackage{iftex}
\ifPDFTeX
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{textcomp} % provide euro and other symbols
\else % if luatex or xetex
\usepackage{unicode-math} % this also loads fontspec
\defaultfontfeatures{Scale=MatchLowercase}
\defaultfontfeatures[\rmfamily]{Ligatures=TeX,Scale=1}
\fi
\usepackage{lmodern}
\ifPDFTeX\else
% xetex/luatex font selection
\fi
% Use upquote if available, for straight quotes in verbatim environments
\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
\IfFileExists{microtype.sty}{% use microtype if available
\usepackage[]{microtype}
\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
}{}
\makeatletter
\@ifundefined{KOMAClassName}{% if non-KOMA class
\IfFileExists{parskip.sty}{%
\usepackage{parskip}
}{% else
\setlength{\parindent}{0pt}
\setlength{\parskip}{6pt plus 2pt minus 1pt}}
}{% if KOMA class
\KOMAoptions{parskip=half}}
\makeatother
\usepackage{longtable,booktabs,array}
\usepackage{calc} % for calculating minipage widths
% Correct order of tables after \paragraph or \subparagraph
\usepackage{etoolbox}
\makeatletter
\patchcmd\longtable{\par}{\if@noskipsec\mbox{}\fi\par}{}{}
\makeatother
% Allow footnotes in longtable head/foot
\IfFileExists{footnotehyper.sty}{\usepackage{footnotehyper}}{\usepackage{footnote}}
\makesavenoteenv{longtable}
\usepackage{graphicx}
\makeatletter
\newsavebox\pandoc@box
\newcommand*\pandocbounded[1]{% scales image to fit in text height/width
\sbox\pandoc@box{#1}%
\Gscale@div\@tempa{\textheight}{\dimexpr\ht\pandoc@box+\dp\pandoc@box\relax}%
\Gscale@div\@tempb{\linewidth}{\wd\pandoc@box}%
\ifdim\@tempb\p@<\@tempa\p@\let\@tempa\@tempb\fi% select the smaller of both
\ifdim\@tempa\p@<\p@\scalebox{\@tempa}{\usebox\pandoc@box}%
\else\usebox{\pandoc@box}%
\fi%
}
% Set default figure placement to htbp
\def\fps@figure{htbp}
\makeatother
% definitions for citeproc citations
\NewDocumentCommand\citeproctext{}{}
\NewDocumentCommand\citeproc{mm}{%
\begingroup\def\citeproctext{#2}\cite{#1}\endgroup}
\makeatletter
% allow citations to break across lines
\let\@cite@ofmt\@firstofone
% avoid brackets around text for \cite:
\def\@biblabel#1{}
\def\@cite#1#2{{#1\if@tempswa , #2\fi}}
\makeatother
\newlength{\cslhangindent}
\setlength{\cslhangindent}{1.5em}
\newlength{\csllabelwidth}
\setlength{\csllabelwidth}{3em}
\newenvironment{CSLReferences}[2] % #1 hanging-indent, #2 entry-spacing
{\begin{list}{}{%
\setlength{\itemindent}{0pt}
\setlength{\leftmargin}{0pt}
\setlength{\parsep}{0pt}
% turn on hanging indent if param 1 is 1
\ifodd #1
\setlength{\leftmargin}{\cslhangindent}
\setlength{\itemindent}{-1\cslhangindent}
\fi
% set entry spacing
\setlength{\itemsep}{#2\baselineskip}}}
{\end{list}}
\usepackage{calc}
\newcommand{\CSLBlock}[1]{\hfill\break\parbox[t]{\linewidth}{\strut\ignorespaces#1\strut}}
\newcommand{\CSLLeftMargin}[1]{\parbox[t]{\csllabelwidth}{\strut#1\strut}}
\newcommand{\CSLRightInline}[1]{\parbox[t]{\linewidth - \csllabelwidth}{\strut#1\strut}}
\newcommand{\CSLIndent}[1]{\hspace{\cslhangindent}#1}
\setlength{\emergencystretch}{3em} % prevent overfull lines
\providecommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
\usepackage{multicol}
\usepackage{bookmark}
\IfFileExists{xurl.sty}{\usepackage{xurl}}{} % add URL line breaks if available
\urlstyle{same}
\hypersetup{
hidelinks,
pdfcreator={LaTeX via pandoc}}
\author{}
\date{}
\begin{document}
\section{LimbuOCR: An End-to-End Page-to-Book OCR System for Limbu, and
a Pipeline Toward the Nepal Language
Pack}\label{limbuocr-an-end-to-end-page-to-book-ocr-system-for-limbu-and-a-pipeline-toward-the-nepal-language-pack}
\textbf{Ashish Thapa} Ampixa Labs \texttt{ashish@ampixa.com}
\begin{multicols}{2}
\subsection{Abstract}\label{abstract}
Nepal's languages are written in more than a dozen scripts (Limbu in
Sirijonga, Newar in Prachalit, Santali in Ol Chiki, among others), yet
almost none has optical character recognition good enough to turn a
scanned newspaper or book into editable text, so their printed record
stays trapped in page images. The obstacles are concrete: tiny training
corpora, legacy fonts that store the wrong bytes, no rights-cleared
benchmarks, and multi-column pages that defeat naive reading-order
recovery. \textbf{LimbuOCR} is a deployed system that begins to close
that gap for Limbu. It turns a scanned page, image batch, or PDF into
Unicode text with page and line structure, reading order, and crops that
lead back to every prediction; a script router and a 50-language
registry extend the same path to further recognizers as their data and
rights mature.
The Sirijonga recognizer is trained from 4,872 real-print line pairs
across 16 newspaper editions, each crop and label taken from the same
PDF and split by publication date. On the held-out silver test it
reaches 0.474\% codepoint character error rate (CER), 0.979\% grapheme
CER, and 85.92\% exact-line accuracy; on complete held-out pages the
full pipeline reaches 2.575\% page CER with 96.85\% line-detection F1.
Beyond Limbu, the same source-pairing workflow has produced real-print
silver labels for Newar, Tirhuta, Ol Chiki, Sunuwar, Kirat Rai, and
Gurung Khema (in several cases the first such data of any scale), staged
training sets, a working Newar diagnostic recognizer, and two
mechanism-level negative results that redirected those routes. These are
engineering baselines against machine-converted text, not human-graded
accuracy: native review, a wider independent page set, and genuine
Devanagari-written Limbu evaluation remain open.
\subsection{1. Introduction}\label{introduction}
Someone should be able to hand LimbuOCR a scanned book, photographed
pages, or a PDF and receive editable Unicode text---and, when the system
is unsure, find the source line and correct it without reconstructing
the OCR run. That requires more than low error on pre-cropped lines: the
output must keep page boundaries, reading order, line boxes, crops,
confidence, script decisions, and source identity, with weak detections
visible for review. LimbuOCR covers that path today: it detects lines,
routes Sirijonga and Devanagari crops, restores reading order, writes
editable and structured outputs, and ties reviewer decisions to source
crops. One data-side technique needs separating from the runtime: some
newspaper PDFs draw Sirijonga with Namdhinggo legacy fonts whose stored
codes can be mapped to Unicode and aligned with pixels from the same
page. That is how scarce real-print training pairs were constructed; the
deployed recognizer itself reads pixels, never a PDF text layer.
Concretely, this paper contributes: (1) an operational page-to-book
Limbu OCR prototype; (2) a provenance-preserving real-print data
path---4,872 line pairs from 16 same-PDF sources under a date-grouped,
leakage-filtered split; (3) date-disjoint line and page diagnostics for
the ft-v2 recognizer, including the demonstration that page CER is
meaningful only under a declared serialization (the same predictions
score 41.34\% or 4.329\% depending on the reading-order contract); (4) a
tested boundary for two-writing-system support, built on a source-pixel
audit that rejected a mislabeled Devanagari result; and (5) the same
pipeline executed across the Nepal language pack, yielding per-script
real-print data, one diagnostic second-language recognizer, and two
root-caused negative results, each reported with its review status
(Section 10). The measured subject remains Limbu.
\subsection{2. Limbu OCR as a System
Problem}\label{limbu-ocr-as-a-system-problem}
Project sources use both Limbu and Yakthung for the language, and both
Sirijonga and Devanagari for its written form; Unicode assigns the Limbu
script U+1900--U+194F (Unicode Consortium 2025a). An OCR record
therefore needs three separate fields: the \textbf{language}, the
\textbf{visual writing system} on the page, and the
\textbf{transcription encoding} of the output. A Sirijonga page paired
with a Devanagari transcription is a valid cross-script transcription
task, but it says nothing about recognizing Devanagari glyphs, and it
changes the dictionary, recognition head, fonts, and error analysis. A
page may also look like Sirijonga while its text layer stores Latin or
private codes rendered through an embedded font: a known font map
converts those codes into useful silver labels, but the visible script
is unchanged and the model still reads pixels.
We describe support in four levels---runtime (a model loads),
operational (the workflow emits reviewable artifacts), measured (quality
is evaluated on relevant real pixels), and claim-grade (frozen,
rights-cleared, human-reviewed evaluation). Sirijonga is measured on
date-disjoint silver diagnostics; the Devanagari route is merely
operational; neither is claim-grade. Throughout, machine-converted
silver is scored without being called ground truth, and source grouping,
leakage checks, normalization, and reading order are part of the metric
definition.
\subsection{3. Related Work}\label{related-work}
LimbuOCR builds on PaddleOCR's PP-OCR family of deployable detectors and
recognizers (Li et al. 2022; Cui et al. 2025); the measured recognizer
is the PP-OCRv5 mobile model (PPLCNetV3 backbone, SVTR neck, CTC/NRTR
heads), with Tesseract as the classical single-engine reference point
(Smith 2007). CTC removes character-level alignment (Graves et al. 2006)
but not layout, which is why line CER, detection F1, matched-line
recognition, and full-page CER stay separate here. For low-resource
scripts, fonts, standardized text, rights, and representative evaluation
constrain progress at least as much as model size (Agarwal and
Anastasopoulos 2024), and synthetic rendering broadens coverage without
establishing real-page performance (Sharma et al. 2024)---consistent
with our ablations (Section 8.1). We report NFC codepoint and
extended-grapheme CER (Unicode Consortium 2025b), treat datasets and
models as documented evidence objects (Gebru et al. 2021; Mitchell et
al. 2019), and follow the human-in-the-loop platform tradition of
Transkribus (Mühlberger et al. 2019) and postediting research (Poncelas
et al. 2020). Community-centered work on Yakthung digital heritage
frames script support as community-controlled tooling (Limbu 2024); we
found no peer-reviewed public Sirijonga page-to-book benchmark with
comparable reporting, so ft-v2 is described as an internal silver
baseline without a priority claim.
\subsection{4. The LimbuOCR Platform}\label{the-limbuocr-platform}
LimbuOCR separates model development from book processing. The offline
path turns audited sources and accepted corrections into datasets,
models, and evaluation records; the runtime path turns page pixels into
editable text and review tasks; human decisions, attached to their
crops, connect the two.
\end{multicols}
\begin{figure}
\centering
\includegraphics[width=0.88\linewidth,height=\textheight,keepaspectratio]{figures/system-architecture.png}
\caption{LimbuOCR system architecture. The upper path constructs and
validates evidence and model bundles; the lower path performs
page-to-book OCR. Review decisions remain attached to source crops and
can feed later audited training exports.}
\end{figure}
\begin{multicols}{2}
The runtime accepts a line crop, a full page, an ordered image set, or a
PDF rendered at a recorded resolution; capture tooling can deskew and
perspective-correct photographs while retaining raw and prepared image
hashes. PaddleOCR detects text on the full page, and each polygon
becomes a crop with page-relative geometry. The crop is the smallest
reviewable evidence unit: its record links source page, prepared page,
detector box, image, recognizer output, and final book line, so a missed
line or wrong character can be traced to the stage that produced it.
Recognition may be fixed to Sirijonga or Devanagari or chosen per crop;
the application bundles \texttt{limbu-sirijonga-ft-v2} (measured here)
and \texttt{deva-v2}, a generic Devanagari recognizer that supplies a
runtime route without any Limbu-specific accuracy result. Detected
regions are assembled by row or column---the six-column newspaper test
uses deterministic column-major order, recorded with every output and
score---and the book path writes \texttt{book.txt}, \texttt{book.json},
annotated pages, crops, Markdown projections, and scorer-compatible
document JSON. Weak lines, empty detections, suspected furniture, mixed
scripts, and suspicious vertical gaps enter review queues; corrections
fail closed against source and crop identity, and only explicitly
accepted text can reach a training export.
The same components are parameterized beyond Limbu. A shared
Unicode-block table identifies scripts, and a configuration-driven book
runner resolves each language's detector, recognizers, converters, and
writing-system profiles from a 50-language pipeline registry.
Registration does not grant permission to run: every recognizer is
marked \texttt{champion}, \texttt{diagnostic-only}, \texttt{blocked}, or
\texttt{failed-fit}, and an execution allowlist decides which statuses
may enter the production path, so a withdrawn or legally blocked model
stays visible but will not execute. Section 10 gives the evidence behind
those statuses.
\subsection{5. Building Real-Print Sirijonga
Evidence}\label{building-real-print-sirijonga-evidence}
\subsubsection{5.1 Source pairing and legacy-font
recovery}\label{source-pairing-and-legacy-font-recovery}
The real-print material comes from Limbu pages in the \emph{Naya Nepal}
supplement of Gorkhapatra epaper PDFs. Both sides of every pair come
from the same full PDF: we render the page image and extract the text
layer from that same page, which prevents pairing a thumbnail with
article text that was never laid out in it. Each retained row records
the PDF and its hash, page number, rendered page, line geometry, raw
codes, converted text, and crop. We manually checked the test page dated
2082-08-12: a six-column Sirijonga newspaper page whose rendered-image
SHA-256 is recorded in the source-verification report. Publisher pixels
are not reproduced here; the current owner determination covers derived
counts and metrics, while redistribution awaits a formal license
statement.
The pages display Sirijonga through Namdhinggo-family fonts, but their
text layers are not Unicode Limbu. During extraction we group PDF spans
into lines and convert the stored codes with \texttt{Limbu.map}, so the
Unicode label and its image crop trace back to one PDF layout object.
The pairing scales, but it is not gold ground truth: font maps can be
wrong, spans can arrive out of order or vanish, and grouping and
normalization can introduce errors. Every row is marked
\texttt{pdf\_text\_layer\_silver} and excluded from claim-grade
evidence.
\subsubsection{5.2 Grouped splitting and leakage
control}\label{grouped-splitting-and-leakage-control}
The rebuilt collection contains 4,872 line pairs from 16 publication
dates. Every line from a date stays in one split: after sorting the
dates, indices congruent to 2 modulo 5 form the test split (2082-03-24,
2082-08-12, 2082-12-25), indices congruent to 0 form development, and
the rest form training. Removing the 38 normalized labels that repeat
across split boundaries leaves 4,834 lines: 2,711 training (nine dates),
1,221 development (four dates), and 902 test (three dates). Date
grouping stops same-edition leakage and label filtering catches repeated
boilerplate; near-duplicate phrases and shared page templates may
remain.
\subsubsection{5.3 Training mixture}\label{training-mixture}
The ft-v2 training bundle has 46,753 training rows and 1,221 development
rows: 25,065 synthetic examples plus eight passes over the 2,711
real-print lines. Another 3,090 referenced synthetic images were lost in
a storage failure and excluded rather than regenerated under the old
names. Replay changes optimization weight, not sample independence.
Training used an NVIDIA L4 for 40 epochs (about 8.5 GPU-hours),
selecting epoch 39 on development; the bundle, YAML, log, checkpoint,
export, predictions, and scores survive, and building this paper checks
them without rerunning training.
\subsection{6. Model and Evaluation
Method}\label{model-and-evaluation-method}
The recognizer is initialized from PaddleOCR's pretrained PP-OCRv5
mobile checkpoint: PPLCNetV3 backbone at scale 0.95, SVTR neck, CTC/NRTR
heads, 48-by-320 inputs, at most 128 characters, trained 40 epochs with
Adam, a cosine schedule from \(10^{-4}\), one warm-up epoch, and batches
of 64. The output dictionary remains the working
\texttt{limbu-sirijonga-v2.txt}. The comparator is the preceding
real-heavy Sirijonga export; both models run through one local CPU
inference and scoring path on the same 902 images. ft-v2 never sees its
test dates during training or selection; the older model's history
cannot be isolated to the same standard, so this is an engineering
before/after comparison, not a controlled leaderboard.
Strings are normalized to NFC with whitespace preserved. CER is
Levenshtein distance divided by reference length, micro-averaged over
codepoints and over extended grapheme clusters; exact-line accuracy
counts predictions matching the entire normalized reference. A page run
starts from the complete rendered image: the detector proposes regions,
the recognizer reads each crop, low-value outputs are filtered, boxes
are ordered column-major, and a one-to-one matcher pairs predictions
with references at IoU of at least 0.5. We report detection
precision/recall/F1, CER over the fully assembled page text, CER and
exact accuracy over matched lines, and missed and unmatched counts.
The 16-page regression set catches deployment regressions, but 13 of its
dates occur in ft-v2 training or development, so we also rescore the
exported documents for the three line-test dates (907 reference lines,
date-disjoint from selection). We do not present page results as
accuracy claims: there is no human review, only three independent pages
against the project's minimum of 30, no permission yet to redistribute
pixels, and no complete multi-domain leakage audit. They are reported as
reproducible diagnostics.
\subsection{7. Results}\label{results}
\subsubsection{7.1 Date-disjoint line
recognition}\label{date-disjoint-line-recognition}
\end{multicols}
\begin{longtable}[]{@{}
>{\raggedright\arraybackslash}p{(\linewidth - 8\tabcolsep) * \real{0.1579}}
>{\raggedleft\arraybackslash}p{(\linewidth - 8\tabcolsep) * \real{0.2105}}
>{\raggedleft\arraybackslash}p{(\linewidth - 8\tabcolsep) * \real{0.2105}}
>{\raggedleft\arraybackslash}p{(\linewidth - 8\tabcolsep) * \real{0.2105}}
>{\raggedleft\arraybackslash}p{(\linewidth - 8\tabcolsep) * \real{0.2105}}@{}}
\toprule\noalign{}
\begin{minipage}[b]{\linewidth}\raggedright
Recognizer
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Lines
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Codepoint CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Grapheme CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Exact-line accuracy
\end{minipage} \\
\midrule\noalign{}
\endhead
\bottomrule\noalign{}
\endlastfoot
Previous real-heavy export & 902 & 1.379\% & 2.840\% & 63.75\% \\
ft-v2 & 902 & \textbf{0.474\%} & \textbf{0.979\%} & \textbf{85.92\%} \\
\end{longtable}
\begin{multicols}{2}
The 902 test lines contain 34,814 codepoints and 16,760 grapheme
clusters. ft-v2 cuts codepoint CER by 65.625\% and grapheme CER by
65.55\%; exact-line accuracy gains 22.17 percentage points. This
measures agreement with the same-PDF silver layer, not with a fluent
transcription. Same-source pairing with date grouping, real-line replay,
and a fixed dictionary yields a useful internal baseline where
transcription is scarce; only native review can say how much residual
error---or apparent agreement---belongs to the silver labels.
\subsubsection{7.2 Non-oracle pages on the held-out
dates}\label{non-oracle-pages-on-the-held-out-dates}
\end{multicols}
\begin{longtable}[]{@{}
>{\raggedright\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.0968}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}
>{\raggedleft\arraybackslash}p{(\linewidth - 14\tabcolsep) * \real{0.1290}}@{}}
\toprule\noalign{}
\begin{minipage}[b]{\linewidth}\raggedright
System
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Pages
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Ref./pred./matched lines
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Detection F1
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Page cp CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Page grapheme CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Matched cp CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Exact matched lines
\end{minipage} \\
\midrule\noalign{}
\endhead
\bottomrule\noalign{}
\endlastfoot
Previous recognizer & 3 & 907 / 903 / 877 & 96.91\% & 3.957\% & 6.280\%
& 2.569\% & 45.95\% \\
ft-v2 & 3 & 907 / 904 / 877 & 96.85\% & \textbf{2.575\%} &
\textbf{3.361\%} & \textbf{1.012\%} & \textbf{76.17\%} \\
\end{longtable}
\begin{multicols}{2}
The detector is fixed; most improvement is recognition. ft-v2 reduces
assembled-page codepoint error by 34.94\% and grapheme error by 46.49\%
relative; exact accuracy on the 877 matched lines rises 30.22 points.
The run still misses 30 reference lines and leaves 27 predictions
unmatched, so these numbers include detection and assembly, not oracle
crops.
\subsubsection{7.3 Sixteen-page regression
check}\label{sixteen-page-regression-check}
\end{multicols}
\begin{longtable}[]{@{}
>{\raggedright\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1111}}
>{\raggedleft\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1481}}
>{\raggedleft\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1481}}
>{\raggedleft\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1481}}
>{\raggedleft\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1481}}
>{\raggedleft\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1481}}
>{\raggedleft\arraybackslash}p{(\linewidth - 12\tabcolsep) * \real{0.1481}}@{}}
\toprule\noalign{}
\begin{minipage}[b]{\linewidth}\raggedright
System
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Pages
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Page cp CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Page grapheme CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Detection F1
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Matched cp CER
\end{minipage} & \begin{minipage}[b]{\linewidth}\raggedleft
Exact matched lines
\end{minipage} \\
\midrule\noalign{}
\endhead
\bottomrule\noalign{}
\endlastfoot
Previous recognizer, shared column-major & 16 & 4.329\% & 6.714\% &
96.57\% & 2.657\% & 43.40\% \\
ft-v2, shared column-major & 16 & \textbf{2.722\%} & \textbf{3.468\%} &
96.50\% & \textbf{0.898\%} & \textbf{79.27\%} \\
\end{longtable}
\begin{multicols}{2}
Most of these dates occur in training or development, so this table is
an acceptance check for the bundled model, not an estimate on unseen
books.
\subsection{8. Lessons from the
Experiments}\label{lessons-from-the-experiments}
\subsubsection{8.1 Real-domain weighting beats indiscriminate
synthesis}\label{real-domain-weighting-beats-indiscriminate-synthesis}
Synthetic data supplied script and glyph coverage, but more of it did
not consistently help: one targeted synthetic/Unicode expansion worsened
the frozen real-print score, and expanding the dictionary during a warm
start replaced part of the recognition head and failed outright. ft-v2
worked after we kept the output space fixed and gave the aligned
real-print lines much more replay weight. Synthesis should be treated as
controlled coverage, ablated against a fixed real-domain test.
\subsubsection{8.2 Page CER is defined by its serialization
contract}\label{page-cer-is-defined-by-its-serialization-contract}
Full-page CER compares two long strings, so it measures sequence as much
as text, and the serialization rule is part of the metric definition. On
the 16-page set, the same recognizer output scores 41.34\% codepoint CER
when reference and prediction are linearized under different
rules---alongside 4,895 reference lines, 4,839 predictions, 4,700
geometric matches, 96.57\% detection F1, and only 2.66\% CER on matched
lines. Applying one explicit column-major linearization to both sides
resolves the contradiction: 4.329\% codepoint and 6.714\% grapheme CER
over the identical predictions, with no model retrained and no
recognized text altered. The mechanism is simple: on a six-column page,
small vertical offsets make a global y-sort weave columns together, and
edit distance counts the moved blocks as character errors. The
catastrophic-looking number was mainly an inconsistent sequence
definition; the remaining error belongs to recognition, missing and
extra lines, crop quality, and layout generalization. Every page score
now records its linearization, and the 41.34\% and 4.329\% figures must
never be read as two OCR systems.
\subsubsection{8.3 A target string does not identify the visual writing
system}\label{a-target-string-does-not-identify-the-visual-writing-system}
An early curriculum pack was labeled Devanagari-written Limbu because
its JSON references contain Devanagari Unicode. The PDF pixels, on
reinspection, show Sirijonga glyphs: the fonts include
\texttt{YakthungBold} and \texttt{NamdhinggoSILL}, and raw extraction
yields ASCII-like legacy codes. On the inspected page the 14-line
reference has 408 Devanagari-block codepoints and no Limbu-block
codepoints while the page itself is visibly Sirijonga---so the real task
is Sirijonga pixels to Devanagari transcription, not Devanagari OCR. A
surviving 31-crop diagnostic is therefore evidence about cross-script
transcription, and its lost scoring bundle is a second reason to exclude
it from the verified tables. Operationally: manifests store
\texttt{language}, \texttt{visual\_script}, \texttt{source\_encoding},
and \texttt{transcription\_encoding} separately, \texttt{deva-v2} is
called a generic runtime route, and a Limbu-specific Devanagari result
will require visibly Devanagari pixels containing Limbu.
\subsubsection{8.4 Review burden is the next system
metric}\label{review-burden-is-the-next-system-metric}
None of the recognition scores says how long a book takes to correct.
Low average CER can coexist with missing headings, confidently wrong
lines, or an interface that forces the editor back to the source page
for every error. The needed study measures lines routed to review,
missing and extra lines, correction time per page and per thousand
characters, accuracy after bounded review, and the share of a book
needing resegmentation---review burden, rather than CER alone, decides
production usefulness.
\subsection{9. What Is Implemented}\label{what-is-implemented}
The repository contains a compact application (Line OCR, Paddle Page
OCR, and Paddle Book OCR, plus image-line fallbacks and diagnostic
probes) and the larger experiment workflow: capture manifests, page and
book outputs with source and crop hashes, triage and review queues,
fail-closed correction application, and reviewed-only training export. A
private CPU service runs the same application; superseded models and a
failed-fit manuscript-Newa export remain in the bundle with model cards
so their history stays inspectable. Model cards bind inference artifacts
and dictionaries by SHA-256, and the paper build verifies those
artifacts and code paths statically. What is \emph{not} yet
demonstrated: a complete human-reviewed book, a correction-time study,
and any Limbu-specific Devanagari validation.
\subsection{10. The Language Pack in
Pipeline}\label{the-language-pack-in-pipeline}
Sections 5--8 report Limbu experiments. Here we record what the same
workflow produced on the rest of the Nepal language pack: locate a
source document, classify its text layer (Unicode, legacy glyph
substitution, transcription, or none), build an explicit converter where
the font is understood, pair text with pixels from the same PDF object,
and check provenance and split leakage before staging a training set.
Training and quality claims wait for rights and native-label review;
most entries below have not cleared those gates.
\end{multicols}
\begin{figure}
\centering
\includegraphics[width=0.88\linewidth,height=\textheight,keepaspectratio]{figures/language-pack-status.png}
\caption{Real-print and silver line substrate per script, with pipeline
status. Counts are read from the recorded pack artifacts at figure-build
time. All rows are mechanical silver or diagnostic substrate, not
human-reviewed ground truth.}
\end{figure}
\begin{multicols}{2}
\subsubsection{10.1 Substrate at scale}\label{substrate-at-scale}
Gorkhapatra's \emph{Naya Nepal} archive rotates pages for more than
fifty languages. Applying the Limbu same-page rule at two depths
retained \textbf{515,586} converted silver lines (monthly backfill,
March 2024--July 2025) and \textbf{306,971} lines (per-language rebuild)
across the 50-language registry; the collections overlap and are not
deduplicated, so their sum is not a corpus size. These labels identify
pages, not necessarily each line's language---Nepali furniture appears
on language pages---so line-level language identification must precede
per-language training. Gorkhapatra is Nepal's state-owned national
daily; an owner determination (2026-07-22) permits the derived counts
and metrics here, while page and crop redistribution awaits a formal
license statement.
\subsubsection{10.2 Newar, the second
language}\label{newar-the-second-language}
Newar (Nepal Bhasa) was chosen second because its Devanagari route could
exercise the full Limbu workflow quickly. A publication-date split
produced 4,096 training, 1,528 development, and 1,139 test lines; after
a storage failure, the recovered labels lack the row-level provenance to
reconstruct that isolation. On the frozen test, generic \texttt{deva-v2}
(never trained on Newar) records 6.223\% codepoint CER; warm-started
\texttt{newar-ft-v1} records \textbf{4.655\%} codepoint CER, 9.569\%
grapheme CER, and 24.50\% exact-line accuracy. The Limbu page path gives
19.92\% page codepoint CER, 91.16\% detection F1, and 9.05\%
matched-line codepoint CER on 19 pages, pointing toward recognition and
crop-domain error rather than reading order---though the evidence is too
compromised for a firm attribution. A later check found label whitespace
artifacts, 18 exact and 575 substring-level cross-split matches, missing
provenance, and an open rights review, so the pack is not used for
claims. The useful result is procedural: the shared path produced a
working second-language diagnostic within days, and the review then
stopped it from becoming an accuracy claim.
\subsubsection{10.3 Scripts with staged training, pending
review}\label{scripts-with-staged-training-pending-review}
Four other scripts have real-print material and staged training sets but
no training run; archives are hash-pinned, development splits follow
issue or page boundaries, and train/development intersections are zero.
\textbf{Tirhuta.} The Maithili e-zine \emph{Videha} publishes a parallel
Tirhuta edition (archived issues carry uploader-applied CC BY-SA 4.0
statements, recorded per issue), but its PDFs use legacy
glyph-substitution fonts. Recovering that mapping, including a 149-entry
conjunct extension, yielded \textbf{10,696} clean real lines---to our
knowledge the first real-print Tirhuta OCR substrate at this scale. The
staged split has 9,765 training and 844 development rows with a complete
issue held out, plus a 48,960-image synthetic pretraining pack in an
openly licensed font. No model is trained yet.
\textbf{Ol Chiki.} A magazine evaluation pack retains \textbf{772} clean
lines (of 895 candidates; a dark-pixel guard removed 123 blank renders).
The synthetic-trained v2 recognizer scores \textbf{8.26\%} codepoint CER
and 20.34\% exact-line accuracy on it, but we withdrew that model from
claim use after finding its training fonts came from the evaluation
edition. A public-source-only v3 training set (5,307 images: 242 real
train, 5,000 synthetic, 65 real development) awaits native review.
Santali OCR exists elsewhere; this is pack coverage, not a first-ever
claim.
\textbf{Sunuwar and Kirat Rai.} Government-hosted Sikkim Herald editions
yielded \textbf{9,743} clean Sunuwar/Jenticha and \textbf{3,699} Kirat
Rai lines through converters grounded in the relevant encoding proposals
with no unresolved units. The splits (8,422/514 and 2,865/193) remain
unused while legal review determines whether the State Portal permission
covers model training.
\subsubsection{10.4 Negative results that redirected
routes}\label{negative-results-that-redirected-routes}
The Lepcha converter returned no lines from 18 Sikkim Herald editions
because the article bodies are raster images with no live text
layer---no font converter can ever recover them. The Lepcha path now
starts from synthesis, anchored by a \textbf{132}-crop machine-labelled
diagnostic that is explicitly ineligible for claims. The manuscript-Newa
recognizer failed even on its training data for a structural reason: its
mobile backbone pools every sequence to 40 CTC timesteps while 95.7\% of
manuscript lines exceed 40 characters, and CTC cannot emit more labels
than timesteps, so no amount of data could fit. A T=200 configuration
passes shape and loss checks, and a leakage-filtered 1,961-row training
set with a sealed 635-line holdout awaits an approved run. Both failures
identify a mechanism and changed the next experiment.
\subsubsection{10.5 Source-first discipline for the hardest
scripts}\label{source-first-discipline-for-the-hardest-scripts}
For Gurung Khema and native-script Newar, work stops at the source
stage. Official Sikkim Herald Gurung Editions contain running Gurung
Khema print, overturning our earlier belief that only synthetic material
existed; a proposal-grounded converter can mechanically convert
\textbf{749} of 759 candidate lines, but none is used pending
provenance, native pixel-label review, and split checks. Newar itself is
modeled as four writing-system profiles (Prachalit, Bhujimol, Ranjana,
Devanagari): Bhujimol has no distinct Unicode encoding and Ranjana
remains unencoded, so neither can reuse the Prachalit route without an
explicit transcription policy. Bhujimol and Ranjana manuscript groups
were catalogued and acquired only from institutional archives with
explicit reuse statements, with every image hashed; there are still no
reviewed labels, models, or metrics. In this registry, ``supported'' can
mean only that input and output semantics are defined.
\subsubsection{10.6 What the pipeline does not
claim}\label{what-the-pipeline-does-not-claim}
No result in this section is claim-grade. The intended near-term system
has one Sirijonga recognizer, one shared Devanagari recognizer, and
per-script experts added only after rights-cleared, natively reviewed
evaluation exists. What exists today is the auditable
substrate---sources, converters, staged training sets, diagnostics, and
explicit refusals to run unreviewed models---and each remaining model
still has to earn its place per language, script, and domain slice.
\subsection{11. Research Agenda}\label{research-agenda}
The next work closes specific gaps, in dependency order. \textbf{First,
human-grounded Sirijonga evaluation}: fluent readers correct the three
date-separated line and page sets (keeping silver and corrected text,
with recorded disagreements), then the benchmark grows to at least 30
independent pages across newspapers and books, split by source; scoring
the same predictions against silver and corrected references will show
how much text-layer noise helps or hurts. \textbf{Second, genuine
Devanagari-written Limbu}: candidate pages must visibly use Devanagari,
contain Limbu, and carry references aligned to those pixels;
\texttt{deva-v2} becomes the baseline and routing is tested only after
both scripts have relevant page evidence. \textbf{Third, book and
phone-capture robustness}: skew, curvature, uneven light, damaged print,
varied fonts, and changing layouts, scored jointly with capture
preparation, on at least one complete work. \textbf{Fourth,
human-centered evaluation}: raw and post-review CER, missed and falsely
confident lines, share of lines routed to review, correction time per
page and per thousand characters, and reviewer agreement---queue
policies compared at fixed final quality, with accepted corrections
entering versioned training packs only after checks. \textbf{Fifth,
structure and fallback}: tables, figures, and captions with
structure-aware references; any large document model used for hard
regions must report trigger rate, latency, and measured gain.
\textbf{Sixth, gated transfer across the pack}: resolve the Sikkim
Herald legal question, obtain native review per staged set, then run the
approved chains (Tirhuta pretrain and fine-tune, Ol Chiki v3, Newa
T=200) against frozen, edition-disjoint tests---one language, script,
and domain slice at a time. This paper makes no claim-grade accuracy
statement for any language, including Limbu.
\subsection{12. Limitations and Rights}\label{limitations-and-rights}
\textbf{References and scope.} The largest numerical limitation is
reference quality: converted text layers carry encoding, ordering,
grouping, and normalization errors, and a model trained on one publisher
may learn its typography and PDF artifacts. Three held-out pages cannot
represent other books, publishers, fonts, periods, or cameras. The
previous deployment is an operational comparator, not a baseline suite;
external comparisons should wait for a frozen, human-reviewed image set.
Only Sirijonga has a surviving Limbu-specific result---the presence of a
Devanagari model is not evidence about Devanagari-written Limbu. Pack
numbers add script-specific caveats: many silver lines are
page-attributed rather than language-verified, the Newar pack has
cross-split leakage and missing provenance, the Ol Chiki diagnostic was
withdrawn over font overlap with its evaluation edition, and a pre-crash
per-language Devanagari scorecard lost its backing artifacts and is
omitted.
\textbf{Rights.} An owner determination (2026-07-22) for Gorkhapatra,
Nepal's state-owned national daily, permits the derived counts and
metrics reported here but not redistribution of pages or crops; the
paper uses artifact-derived diagrams only. Sikkim Herald training sets
remain unused while the State Portal permission is reviewed for training
use; only the Videha Tirhuta source has recorded per-issue CC BY-SA 4.0
statements. Any later release must state precisely which material its
rights basis covers.
\textbf{Community validation and reproducibility.} Metrics cannot settle
linguistic correctness, preferred script names, or community acceptance;
fluent Limbu readers need a standing role in benchmark review, error
taxonomy, and release decisions, with their corrections kept visible.
The paper build regenerates figures and checks source counts, splits,
metrics, model hashes, and runtime paths against local artifacts; it
does not repeat the L4 training run, whose bundle, checkpoint,
predictions, and scores remain available for inspection.
\subsection{13. Conclusion}\label{conclusion}
LimbuOCR is an operational research platform that turns page images and
PDFs into editable, structured, reviewable Limbu text. The measured
Sirijonga route records 0.474\% codepoint CER, 0.979\% grapheme CER, and
85.92\% exact-line accuracy on a three-date silver test, and 2.575\%
codepoint CER with 96.85\% detection F1 from complete pages. The same
source and release workflow has produced large silver collections,
converters, staged training sets, a Newar diagnostic, and two useful
negative results across the Nepal language pack. Those artifacts mark a
starting point: Sirijonga labels need native validation,
Devanagari-written Limbu needs verified pages of its own, and every
other language remains behind its rights and review gates. The
serialization correction and the withdrawn curriculum result show why
these boundaries belong in the method, and the next meaningful measure
is review burden on a complete book.
\phantomsection\label{refs}
\begin{CSLReferences}{1}{0}
\bibitem[\citeproctext]{ref-agarwal2024survey}
Agarwal, Milind, and Antonios Anastasopoulos. 2024. {``A Concise Survey
of {OCR} for Low-Resource Languages.''} In \emph{Proceedings of the 4th
Workshop on Natural Language Processing for Indigenous Languages of the
Americas}, 88--102. Association for Computational Linguistics.
\url{https://doi.org/10.18653/v1/2024.americasnlp-1.10}.
\bibitem[\citeproctext]{ref-cui2025paddleocr3}
Cui, Cheng, Ting Sun, Manhui Lin, Tingquan Gao, Yubo Zhang, Jiaxuan Liu,
Xueqing Wang, et al. 2025. {``{PaddleOCR 3.0} Technical Report.''}
\emph{arXiv Preprint arXiv:2507.05595}.
\url{https://arxiv.org/abs/2507.05595}.
\bibitem[\citeproctext]{ref-gebru2021datasheets}
Gebru, Timnit, Jamie Morgenstern, Briana Vecchione, Jennifer Wortman
Vaughan, Hanna Wallach, Hal Daumé III, and Kate Crawford. 2021.
{``Datasheets for Datasets.''} \emph{Communications of the ACM} 64 (12):
86--92. \url{https://doi.org/10.1145/3458723}.
\bibitem[\citeproctext]{ref-graves2006ctc}
Graves, Alex, Santiago Fernández, Faustino Gomez, and Jürgen
Schmidhuber. 2006. {``Connectionist Temporal Classification: Labelling
Unsegmented Sequence Data with Recurrent Neural Networks.''} In
\emph{Proceedings of the 23rd International Conference on Machine
Learning}, 369--76. Association for Computing Machinery.
\url{https://doi.org/10.1145/1143844.1143891}.
\bibitem[\citeproctext]{ref-li2022ppocrv3}
Li, Chenxia, Weiwei Liu, Ruoyu Guo, Xiaoting Yin, Kaitao Jiang, Yongkun
Du, Yuning Du, et al. 2022. {``{PP-OCRv3}: More Attempts for the
Improvement of Ultra Lightweight OCR System.''} \emph{arXiv Preprint
arXiv:2206.03001}. \url{https://arxiv.org/abs/2206.03001}.
\bibitem[\citeproctext]{ref-limbu2024heritage}
Limbu, Sumi. 2024. {``Linguistic Heritage in Digital Landscape: A
Collective Memory of Indigenous Script.''} Master of Design thesis,
University of Arkansas. \url{https://scholarworks.uark.edu/etd/5325/}.
\bibitem[\citeproctext]{ref-mitchell2019modelcards}
Mitchell, Margaret, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy
Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, and
Timnit Gebru. 2019. {``Model Cards for Model Reporting.''} In
\emph{Proceedings of the Conference on Fairness, Accountability, and
Transparency}, 220--29. Association for Computing Machinery.
\url{https://doi.org/10.1145/3287560.3287596}.
\bibitem[\citeproctext]{ref-muehlberger2019transkribus}
Mühlberger, Günter, Louise Seaward, Melissa Terras, Sofia Ares Oliveira,
Vicente Bosch, Maximilian Bryan, Sebastian Colutto, et al. 2019.
{``Transforming Scholarship in the Archives Through Handwritten Text
Recognition: Transkribus as a Case Study.''} \emph{Journal of
Documentation} 75 (5): 954--76.
\url{https://doi.org/10.1108/JD-07-2018-0114}.
\bibitem[\citeproctext]{ref-poncelas2020postediting}
Poncelas, Alberto, Mohammad Aboomar, Jan Buts, James Hadley, and Andy
Way. 2020. {``A Tool for Facilitating {OCR} Postediting in Historical
Documents.''} In \emph{Proceedings of LT4HALA 2020 -- 1st Workshop on
Language Technologies for Historical and Ancient Languages}, 47--51.
European Language Resources Association (ELRA).
\url{https://aclanthology.org/2020.lt4hala-1.7/}.
\bibitem[\citeproctext]{ref-sharma2024voltage}
Sharma, Prawaal, Poonam Goyal, Vidisha Sharma, and Navneet Goyal. 2024.
{``{VOLTAGE}: A Versatile Contrastive Learning Based {OCR} Methodology
for Ultra Low-Resource Scripts Through Auto Glyph Feature Extraction.''}
In \emph{Proceedings of the 18th Conference of the European Chapter of
the Association for Computational Linguistics}, 881--99. Association for
Computational Linguistics.
\url{https://doi.org/10.18653/v1/2024.eacl-long.53}.
\bibitem[\citeproctext]{ref-smith2007tesseract}
Smith, Ray. 2007. {``An Overview of the Tesseract OCR Engine.''} In
\emph{Proceedings of the Ninth International Conference on Document
Analysis and Recognition}, 629--33. IEEE Computer Society.
\url{https://research.google/pubs/an-overview-of-the-tesseract-ocr-engine/}.
\bibitem[\citeproctext]{ref-unicode17limbu}
Unicode Consortium. 2025a. {``The Unicode Standard, Version 17.0:
Chapter 13, Limbu.''} Unicode Standard.
\url{https://www.unicode.org/versions/Unicode17.0.0/core-spec/chapter-13/}.
\bibitem[\citeproctext]{ref-uax29}
---------. 2025b. {``Unicode Text Segmentation.''} Unicode Standard
Annex \#29. \url{https://www.unicode.org/reports/tr29/}.
\end{CSLReferences}
\end{multicols}
\end{document}
|