Open ibo-o opened 4 months ago
Those last set of numbers are commonly used by Persian and Urdu readers can be named like these:
۰ perzero U+06F0
۱ perone U+06F1
۲ pertwo U+06F2
۳ perthree U+06F3
۴ perfour U+06F4
۵ perfive U+06F5
۶ persix U+06F6
۷ perseven U+06F7
۸ pereight U+06F8
۹ pernine U+06F9
Or they can be prefixed with far
instead of per
. G app uses a different scheme one-ar
for Arabic ones and oneFarsi-ar
for Persian ones.
The proposal is to rename the ar*
glyphs to per*
, and then use the ar
names for the missing values. Is that correct, @typoman? @typemytype
٠ arzero U+0660 (was: missing )
١ arone U+0661 (was: missing )
٢ artwo U+0662 (was: missing )
٣ arthree U+0663 (was: missing )
٤ arfour U+0664 (was: missing )
٥ arfive U+0665 (was: missing )
٦ arsix U+0666 (was: missing )
٧ arseven U+0667 (was: missing )
٨ areight U+0668 (was: missing )
٩ arnine U+0669 (was: missing )
۰ perzero U+06F0 (was: ٠ arzero )
۱ perone U+06F1 (was: ١ arone )
۲ pertwo U+06F2 (was: ٢ artwo )
۳ perthree U+06F3 (was: ٣ arthree )
۴ perfour U+06F4 (was: ٤ arfour )
۵ perfive U+06F5 (was: ٥ arfive )
۶ persix U+06F6 (was: ٦ arsix )
۷ perseven U+06F7 (was: ٧ arseven )
۸ pereight U+06F8 (was: ٨ areight )
۹ pernine U+06F9 (was: ٩ arnine )```
I'm not sure, but it might not be a good idea to disconnect the Farsi numbers from the Arabic script. Finding a similar solution what G app has might be more informative.
Something like this:
۰ arPerzero U+06F0
۱ arPerone U+06F1
۲ arPertwo U+06F2
۳ arPerthree U+06F3
۴ arPerfour U+06F4
۵ arPerfive U+06F5
۶ arPersix U+06F6
۷ arPerseven U+06F7
۸ arPereight U+06F8
۹ arPernine U+06F9
Ok. What are the arguments for "Persian" over "Farsi"?
I do need to think about the repercussions of the re-assigning of the name arzero
from U+06F0 to U+0660
Arabic-Indic Digits don't exist in the GlyphBrowser. (These digits you can access via Arabic Keyboard)
Only extended Arabic-Indic Digits are available in the list. (These digits you can access via Persian Keyboard)