Referring to http://www.crosswire.org/wiki/DevTools:confFiles the only language related element is lang itself.
This means that when a front-end encounters a new module for which it cannot yet provide a look-up for the localized language name, it will show Unknown as the name of the language. That's what Xiphos does, for example. As a fall-back position, might it be sensible to allow the conf file to optionally include the localized language name in addition to the lang element? This would be processed as follows: If the lang identifier can be looked up, use the look-up value. If not, then if the conf file includes the localized language name, use that. Then if not either, fall back to using unknown, as at present. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Localized-language-names-a-suggestion-tp3094297p3094297.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
