Front-end applications such as Xiphos display localized language names as branches in the module manager.
However, not all third party created modules stick to the CrossWire developers' guideline to use the two letter language code, when both two letter and three letter codes are defined in ISO-639. Example: One of the modules from the http://www.wordofgod.in/ Word of God team in India is the Tamil Bible. ISO-639-1 code for Tamil is "ta" ISO-639-2 code for Tamil is "tam" ISO-639-3 code for Tamil is "tam" The language code in tamil.conf is "tam". This causes Xiphos to display it as an English language name "Tamil" rather than a localized one, "தமிழ்". Should Xiphos be made sufficiently versatile to cope with such third party deviations from our guidelines? Or should we suggest to brother Yesudas Solomon to change the conf file to use the two letter code? A similar situation appertains for the Hindi, Telugu and Kannada Bible modules available from the same website. David H. -- View this message in context: http://n4.nabble.com/Localised-language-names-for-third-party-modules-tp976968p976968.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
