Replies: 1 comment
-
|
@milotype, we initially populated our ISO 639-3 translations using existing data where possible (most significantly, the open-licensed language data at lexvo.org) -- I'm not sure to what extent this overlaps with the work done in the weblate project you mentioned here (which I see also has a Git repo at https://salsa.debian.org/iso-codes-team/iso-codes.git which may be useful for reference). We'll have to find time to do some analysis to figure out whether one data source is better than the other, or whether we need a workflow that merges data together from multiple sources. An an ideal world, it would of course be best to just have a single source of truth for this, as it would make things significantly easier to manage -- but in my experience, it's usually not that simple. :-) In any case, thanks for pointing this out, and of course, please feel no obligation to invest time in re-translating things in our project if that data is available somewhere else. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Please inspect if it's possible to use the translations of
ISO639-3language codes from ISO 639-3 at the Hosted Weblate translation platform (and implement those translations into the VuFind strings at the Lokalise platform), so translators don't have to translate 6628 strings.Beta Was this translation helpful? Give feedback.
All reactions