Also some other Tulu websites exhibit these digits, including in public
signages:

https://www.easytulu.com/p/tulu-lipi-alphabets.html

Also why this proposal for these numerals was still not considered?

https://www.unicode.org/L2/L2025/25020-tulu-tigalari-numerals.pdf
(here the additional decimal digits, and numerals ten and one hundred, were
proposed in a contiguous range 113F0-113FB instead of using the Kannada and
Telugu blocks layout)


Le mar. 2 juin 2026 à 11:30, Philippe Verdy <[email protected]> a écrit :

> Is there a reason for not encoding these Tulu-Tigalari digits (0 to 9) and
> numerals (10, 100) ?
>
> Suggested code points in the Tulu-Tigalari block (U+11380-113FF, allocated
> in Unicode 16.0).
>
> (1)  Using the same layout as in the Kannada block (U+0C80-0CFF) or the
> Telugu block (0C00-0C7F) for their decimal digits:
>
> 113E6...113EF: TULU-TIGALARI DIGIT ZERO...NINE
>
> (I'm not sure if we can give them the "decimal digit" character property:
> digit zero is apparently a later addition, when traditional numerals used
> specific multipliers for tens and hundreds, however the existence of zero
> is documented and visible in existing modern usage, and the two other
> numerals may be used in legacy numerals for integers 1 to 999,999)
>
> (2) Using additional numerals with the same layout as in the Telugu block
> (0C00-0C7F) for its additional fraction digits:
>
> 113F8: TULU-TIGALARI NUMERAL TEN
> 113F9: TULU-TIGALARI NUMERAL ONE HUNDRED
>
> Some images are listed in Wikimedia Commons (including an example in
> modern usage for a wedding invitation in Tulu, printed in the Kannada and
> Tulu-Tigalari script), and a few alphabet charts including these numerals:
>
> https://commons.wikimedia.org/wiki/Category:Tulu-Tigalari_numerals
>
> One convincing point is that this appears in a *printed* document
> (intended for some sizable audience in the Tulu community and families),
> and that there may already existing fonts for them (even if they don't use
> Unicode mappings), and not just a personal creation.
>
>

Reply via email to