New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arabic Naming: Numbers #77
Comments
* origin/improve-conflict-checking: Fix Zanabazar conflict and clean up the range. #65 Add farsi names for EXTENDED ARABIC-INDIC DIGIT <n>. Fixes #77 This undoes the greek suffix changes as they were happening in too many places. Need to look at this problem separately. Remove range-wide prefix for phonetic extensions. Output banner to svg as well fixes #70 This fixes #68 "schwa", #74 "armenian", #72 "rupee", #73 "fractions", #71 "dingbats", This fixes #68 "schwa", #74 "armenian", #72 "rupee", #73 "fractions", #71 "dingbats", This fixes a problem with analysing conflicting names. A glyphname object checks with scriptConflictNames before outputting its name. If its name is listed it will add the prefix. However, when *making* the conflicts list it should *not* check otherwise the results are skewed. # Conflicts: # Lib/glyphNameFormatter/data/conflict.txt # Lib/glyphNameFormatter/data/scriptConflictNames.py # Lib/glyphNameFormatter/names/glyphNamesToUnicode.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicodeAndCategories.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicodeAndCategories_experimental.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicode_AGDonly_colon_prefixed.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicode_AGDonly_colon_suffixed.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicode_AGDonly_hyphen_prefixed.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicode_AGDonly_hyphen_suffixed.txt # Lib/glyphNameFormatter/names/glyphNamesToUnicode_experimental.txt # Lib/glyphNameFormatter/rangeProcessors/arabic.py
|
I agree with Khaled. These so-called Arabic and Persian digits perfectly fit in the generally well-understood decimal system, and are not only used by the Arabic and Persian languages. |
I see |
There is a different between a specific language’s words for cardinal numbers and a script’s set of digit symbols. In principle all numeral characters (especially decimal digits) in Unicode, of any scripts, are named with a single terminology because it’s the most comprehensible way to name them when working in such a multilingual, multiscript scope. Letters tend to get native names because different scripts’ letters tend form distinct systems on their own (and when they do follow an underlying system, such as Sanskrit phonology, Unicode does try to align to that)—but decimal digits are just plain, decimal digits. They’re named using English cardinal number words not because “they're named according to the most common language used with that script which is English”, but because they’re named language-independent, and English happens to be the working language of Unicode. I can see a specific need of introducing localized glyph names for users who are not comfortable with the English terms used in glyph names, but this doesn’t quite feel like this general-purpose project’s responsibility…(?) (I know I might be talking too much about Unicode now, and this project is not meant to blindly reflect whatever there is in Unicode.) |
I think naming glyphs is tricky. It tends to become personal and the reason I suggested this was that I explicitly wanted to differentiate Arabic script numbers from Latin. It makes sense to follow Unicode. No arguments there ( ͡° ͜ʖ ͡°)! |
Ok. I like the idea of localized names, but had not really thought about the consequences. |
Arabic numbers could have transliteration names for their glyph names. I can't transliterate the Arabic figures but for Persian, it could go like this:
۰۱۲۳۴۵۶۷۸۹
sefr yek do seh chahar panj shish haft hasht noh
Maybe @khaledhosny would like to suggest transliterated Arabic names for the Arabic figures?
The text was updated successfully, but these errors were encountered: