help us translate addons - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: Translations and Language Files (/forumdisplay.php?fid=90)
+--- Thread: help us translate addons (/showthread.php?tid=72837)
- parad - 2011-02-10 21:23
spiff Wrote:we will use the same lang code as the one you have for your xbmc language, if it doesn't exist we fall back to english.
I've 3 spanish languages: Spanish, Spanish (Mexico), Spanish(Argentina) (I only need the one for Argentina but keep the others for help me with translation and because i don't want to delete anything from the original installation).
The three languages have the "sp" lang code. And my translation for the scraper has a lang="sp" description, but when i open xbmc and look for the scraper info, it appears in english.
What i've to do to see the info in spanish?
- parad - 2011-02-13 01:19
Anyone can help me with this?
- spiff - 2011-02-15 12:16
vanilla Spanish has lang code es. unfortunately so does mexico and likely argentina. we need to expand it to use 3 letter langcodes to distinguish.
- parad - 2011-02-16 05:26
Thanks for your answer.
Then i suppose that the better solution by now is keep only the spanish translation (with "Spanish" as name and "es" as lang)
I will try this and see if the info is in spanish.
- MaDDoGo - 2011-02-16 21:37
Why don't you support extended language tags (es_ES, es_AR, etc...)?
Isn't possible to make a field in the language strings to name the sublanguages?
Maybe in langinfo.xml make a field like <id> to force a language tag. Maybe then add the Language String (Español (España)) and rename the language folder to es_ES.
Will That change slowdown the program so much?
That is only a suggestion, and if I'll know C++ I'll try to do it
- spiff - 2011-02-16 23:07
actually it's just a todo, we have the info now (didnt when i added the localization). see the locale stuff in LangInfo.cpp / langinfo.xml
- MaDDoGo - 2011-02-17 00:06
I looked at this and I think this would read the information from langinfo.xml:
Quote: const TiXmlNode *pLocale = pRootElement->FirstChild("locale");
And would read this:
Sorry if it's not the place but I don't know how to do it better.
Then in the options, maybe you can adapt the addon's way of reading tags (but instead of Addons name you read locale's name) using the es_ES file scheme.