Apologies if this is the wrong forum for this question --
please point
me as gently as you can in the right direction.
Suppose I wanted to make use of additional language/script
codes for
content (not portal translations, just items and fields),
for example:
* 3-letter codes, following ISO639-2, for registered
languages not
covered in the 2-letter codes registered for ISO639-1 (e.g.,
"grc" for
Ancient Greek).
* lang codes plus script subtags, following ISO15924 and
assembled in
accordance with
http://www.inter-locale.com/ID/draft-ietf-ltru-re
gistry-14.html (e.g.,
"grc-Latn" for ancient Greek transliterated with
Roman characters)
I seem to be able to accomplish both simply by adding to the
appropriate
dictionaries in Plone Language Tool's
availablelanguages.py.
Is this best practice? If not, what is?
Are there hidden gotchas? I.e., dependencies I should also
deal with?
Is there a ticket (or interest in creating one) for adding
either of
these classes of codes to the out-of-the-box version? Or
does the
shipped list coordinate with available translations?
Many thanks,
Tom
--
Tom Elliott, Ph.D.
Director, Pleiades Project
Ancient World Mapping Center
University of North Carolina at Chapel Hill
http://www.unc.
edu/awmc/pleiades.html
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-i18n mailing list
Plone-i18n lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n
|