From: Dan Dennedy <dan@de...> - 2008-03-06 07:42:51
The latest commit provides a helper function
mlt_repository_languages(repository). It returns a list of 2 character
language codes as a mlt_properties in priority order (highest priority
first). You can use this to generate a yaml file name. You should
iterate over the properties list while a yaml file is not found. If
there is no match, then use "en" or an untranslated yaml file. If the
locale is "C" or "POSIX", this function already converts it to "en".
If your service is a bridge to another system (e.g. frei0r), then you
can't really do anything. Maybe the foreign system has its own i18n
and that will just seamlessly pass through. Oh, and if you translate a
metadata yaml, do not translate the key names defined in the schema!