Hide Forgot
Description of problem: When browsing the documentation in Spanish, referring to the language code 'es-ES' where the code should be 'es' for Spanish (Castillan) How reproducible: Enter to the site http://docs.fedoraproject.org/, navigate Spanish Docs. Actual results: Navigate docs in spanish, references to 'es-ES' code language Expected results: Navigate docs in spanish, references to 'es' code language
Are you saying that we should ignore all of es_AR, es_BO, es_CL, es_CO, es_CR, es_DO, es_EC, es_GT, es_HN, es_MX, es_NI, es_PA, es_PE, es_PR, es_PY, es_SV, es_US, es_UY, and es_VE?
Yes, exactly, there is only a translation team to Spanish, seeking to unify all regionalization in Spanish as neutral as possible to avoid overhead of translation. Spanish in Latin America and Spain is very similia in all countries, being able to fully understand the linguistic variations from one country to another without problems. Thus instead of having many Spanish translation team, we only have a single Spanish translation team with the code 'es' regarding Spanish (Castillan)
Something about this topic? Many manuals into Spanish (Castillan), 'es', now are completely translated but aren´t available to users because this bug in http://docs.fedoraproject.org
From what little I understand, the language code shows up as "es-ES" because Publican (the tool used to create HTML and PDF and ePub versions of the documentation) uses the IETF BCP47 standard for language codes. You can read more about it at http://jfearn.fedorapeople.org/en-US/Publican/2.7/html/Users_Guide/appe-Users_Guide-Language_codes.html and http://tools.ietf.org/html/bcp47.
Transifex has a language map option now, this could be linked. See[1] for ex. Today I can see some guide available in Spanish, is it fixed? Could you point us to some guide not available but translated? Or could we close this? [1] http://git.fedorahosted.org/git/?p=docs/user-guide.git;a=blob;f=.tx/config;h=7cb3fc1db8813d26cfcb5363e2d5390163b432bd;hb=f16
We're using a language map with transifex as noted in Comment 5, and the language codes used are as expected, as noted in Comment 4. Beyond that, using 'es-ES' instead of a more broad 'es' allows us to scale if interest develops in other dialects. If there are guides with available but unpublished translations, please open a new bug against that guide or mail the docs list, as is the SOP.