It would be sensible for modules to be grouped by language using the language
names looked up from the langage code with reference to the entries in the file
locales.d
I wonder why that method isn’t already used by the Bishop app ?
Aside: When PocketSword is next updated, it ought to be compile
Dear Steve,
You are right that the Bishop app definitely needs help in making it
easy to find a specific Bible translation in a very long list of Bible
translations. The fact that the languages are NOT in alphabetical order
is not helpful. They are actually ordered by module name, so Tandroy
Sorry to have use the list for this, but:
David Haslam:
We appear to have lost email contact. I have had no replies from you. I
checked my server and things *look* ok in the mail logs.
Tom
--
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
_
The Turkish translation of OT and NT are as follows:
OT = Eski Antlaşma
NT = Yeni Antlaşma
David
--
View this message in context:
http://n4.nabble.com/lost-books-testaments-when-in-Turkish-locale-tp1592460p1593198.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
_
Karl,
I have not looked at any source code, but one feature of the Turkish
alphabet is the existence of both dotted and dotless letter I, each with
both lower and upper case characters.
If any locale-sensitive code snippet uses a case conversion, based on the
usual assumption that uppercase("i")
I'm looking at a Xiphos bug report which notes that, when operating in
Turkish locale (LC_ALL=tr_TR LANG=tr), the Old Testament appears to be
simply missing, no matter the Bible module in use. I can reproduce the
bad effect.
Picking on a perfectly ordinary 2-testament Bible module (my NET), I try
