I've run into a problem this morning with i18n in Zope3, and I'm not
exactly sure what the appropriate approach is.  We have a set of South
African translations, paticularly Zulu (zu) and Sotho (st) that are
getting picked up correctly.  Upon some inspection it appears that the
i18n negotiator is skipping over them, with an exception such as:

The desired locale is not available.

Upon inspection I can confirm that the locales which are not working
are those without .xml files in the data directory.  So a few

* Is there an external source for those .xml files, or do we create
them ourselves?
* Translation seems to work OK (in the case of Zulu, not Sotho) from
ZPT, but not from Python; does this sound sane, or perhaps I'm missing


Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to