Localization for numerical digits in the UI ?

[GoogleCodeExporter]

Refer to discussion in the Go Bible Forum
http://jolon.org/vanillaforum/comments.php?DiscussionID=389&page=1#Item_1

Original issue reported on code.google.com by DFH...@gmail.com on 26 Nov 2007 at 7:41

[GoogleCodeExporter]

The recent appearance of the Hindi Mobile Bible led me to consider that there 
is an
overlooked aspect of the Go Bible user interface. Namely, the numerical digits 
0 - 9
that are used for chapter and verse references. In the Devanagari script in 
which
Hindi and Nepali are written, the numerical digits are written as follows:
०
१
२
३
४
५
६
७
८
९

These are Unicode characters U-966 to U-96F.

Several other languages have different representations for the numerical 
digits. It
should therefore be considered to implement in the UI, the substitution of the 
normal
Western numerical characters by a different group of Unicode characters for 
those
languages that require this.

Original comment by DFH...@gmail.com on 29 Mar 2008 at 1:19

• Changed state: Accepted

[GoogleCodeExporter]

The Khmer language also uses special glyphs for numbers.

Original comment by DFH...@gmail.com on 9 Apr 2008 at 12:20

[GoogleCodeExporter]

Light hearted comment:

A pedant might wish to see chapter and verse numbers for the Latin Vulgate 
rendered 
as Roman numerals, n'est-ce pas?

Even in English literature, scripture references cited up to the 19th century 
often 
used digits for the chapter numbers, and lowercase Roman numerals for the 
verses.

eg.  Rom. 10.x [or such like] (rather than Rom. 10:10)

Earlier times used Roman numerals for both chapter and verse.

eg.  Rom. X(x)

LOL.

Original comment by DFH...@gmail.com on 9 Apr 2008 at 12:26

[GoogleCodeExporter]

also there are Arabic Numerals (The Arabic-Indic). it will be nice to have it
http://en.wikipedia.org/wiki/Arabic_numerals

Original comment by Arabic.G...@gmail.com on 27 Apr 2008 at 10:30

[GoogleCodeExporter]

Arabic numerals are the Unicode range U+0660 to U+0669.

٠١٢٣٤٥٦٧٨٩

This too would be a nice to have.

Original comment by DFH...@gmail.com on 15 Nov 2008 at 1:28

[GoogleCodeExporter]

Here is a very useful link that tabulates the numerical digits in Unicode for 
various language scripts.

http://www.code2000.net/numbersutf.htm

Original comment by DFH...@gmail.com on 23 Feb 2009 at 9:07

[GoogleCodeExporter]

This would not necessarily require any extra items in the UI translation.

The digits could be defined by a single optional item in Go Bible Creator.

Digits: Arabic
would set ٠١٢٣٤٥٦٧٨٩

Digits: Devanagari
would set ०१२३४५६७८९

etc.

NB. GoBibleCore would need to be significantly altered.

Original comment by DFH...@gmail.com on 11 Nov 2009 at 8:27

[GoogleCodeExporter]

I think we should take this issue forward sometime, especially as it would be 
quite
easy to test. For example, if the Unicode digits to be used were defined by an
optional item in the collections text file, one could build even the English 
KJV with
Devanagari digits! This means you don't need to have (say) a Hindi Bible in USFM
format in order to test the feature.

Original comment by DFH...@gmail.com on 9 Dec 2009 at 1:55

[GoogleCodeExporter]

Changed summary.

Original comment by DFH...@gmail.com on 7 Apr 2010 at 11:14

• Changed title: Localization for numerical digits in the UI ?

[GoogleCodeExporter]

Or we could do it like one of the SWORD front-ends.

The optional new keyword in the collections text file would be 

0123456789: 

The default would be what we have at present.

To set Devanagari, the line would become
0123456789: ०१२३४५६७८९

To set Arabic, the line would become
0123456789: ٠١٢٣٤٥٦٧٨٩

If the programmed parameter was not 10 unique characters, an error message 
should be generated, and the Go Bible would revert to default.

Original comment by DFH...@gmail.com on 9 Oct 2010 at 2:40

[GoogleCodeExporter]

This has been addressed in symscroll branch.

Add the following line to ui.properties:

UI-Digits: ٠١٢٣٤٥٦٧٨٩

OR

UI-Digits: 0123456789

OR

UI-Digits: JABCDEFGHI (for testing)

Limitations: Currently, there is no error message. GoBible will not check for 
uniqueness of characters. If there are less than 10 characters, it will revert 
to default.

Original comment by daniel.s...@gmail.com on 10 Oct 2010 at 8:40

[GoogleCodeExporter]

Does this require any change to GoBibleCreator?
i.e. Apart from the obvious addition of the same UI item?

btw. What happens if there are more than 10 characters specified?

Original comment by DFH...@gmail.com on 10 Oct 2010 at 9:32

• Changed state: Started

[GoogleCodeExporter]

The localised digits are looked up based on string offset.

In pseudo-code: "٠١٢٣٤٥٦٧٨٩".charAt( digit ).

In short, if there are more than 10 characters, the extra characters will be 
ignored (since no digits are larger than 9). It currently checks for less than 
10 characters, because that condition would most certainly throw a 
StringIndexOutOfBoundsException, which is much less prettier.

Original comment by daniel.s...@gmail.com on 10 Oct 2010 at 9:39

[GoogleCodeExporter]

See http://crosswire.org/wiki/Projects:Go_Bible/SymScroll#Other_numeral_systems

Original comment by DFH...@gmail.com on 15 Apr 2011 at 3:29

[GoogleCodeExporter]

Original comment by DFH...@gmail.com on 15 Apr 2011 at 3:29

• Changed state: Fixed

[GoogleCodeExporter]

Also fixed in GoBibleCreator v2.4.2 and GoBibleCore v2.4.2 to be released 
presently.

Original comment by DFH...@gmail.com on 3 Dec 2011 at 1:44