Bug 730237
Summary: | RFE: As a gettext-based project maintainer I don't want to have to worry about locale mapping when importing a package to Zanata | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Akira TAGOH <tagoh> |
Component: | Component-UI | Assignee: | Ding-Yi Chen <dchen> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ding-Yi Chen <dchen> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | pnemade, sflaniga, sshedmak, zanata-bugs |
Target Milestone: | --- | Keywords: | Improvement, UserStory |
Target Release: | 1.6.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 1.6.1-SNAPSHOT (20120606-0019) | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-07-03 05:27:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 729522 | ||
Bug Blocks: |
Description
Akira TAGOH
2011-08-12 09:22:32 UTC
If I understand correctly, this is about a mismatch between the server-side locales (eu, bn-BD, es-ES, etc) and the client-side .po files (eu_ES, bn, es, etc). At present, the only mechanism for handling this mismatch is to edit zanata.xml on the client to provide mappings, eg: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <config xmlns="http://zanata.org/namespace/config/"> <url>http://localhost:8080/zanata/</url> <project>sample-project</project> <project-version>1.1</project-version> <locales> <locale map-from="eu_ES">eu</locale> <locale map-from="bn">bn-BD</locale> <locale map-from="es">es-ES</locale> <locale map-from="de">de-DE</locale> <locale map-from="sr">sr-Cyrl</locale> <locale map-from="zh_TW">zh-Hant-TW</locale> <locale map-from="zh_CN">zh-Hans-CN</locale> <locale map-from="ta">ta-IN</locale> <locale map-from="pt">pt-PT</locale> <locale map-from="sr@latin">sr-Latn</locale> </locales> </config> This works, but it is fairly painful, considering it may have to be done once for each project. (It would probably help if we at least provided some sample mappings as a comment when generating zanata.xml) We should consider overhauling the way we map client-side locales to server-side locales, perhaps by moving it to the server, or possibly we could do away with mapping and implement some sort of intelligent locale grouping instead. Such a grouping would need to handle language teams and also translation statistics. That's just a couple of ideas, we should consider a lot more. And we should try to find an easier way to reduce the problem in the meantime. Assigning to Scrum product owner for prioritisation. One of the intermediate goal can be: Zanata clients output the locale that the server currently support. Such as: zanata locale Returns: eu bn-BD es-ES de-DE zh-Hant-TW zh-Hans-CN From here, scripting monkeys like us can workout the generation of zanata.xml. Assigned to Runa for prioritization. BTW, I have made a set of utilities, zanata-util, which address some thing like this. Specifically, use following command to generate zanata.xml you want. zanata_zanata_xml_make -m -p gettext <ZanataServerUrl> <ProjectId> <VersionId> zanata-util has passed package review, and is now in test repositories for rawhide, f17, f16, el6 and el5. VERIFIED with Zanata version 1.6.1-SNAPSHOT (20120606-0019) and as well as zanata-util-0.2.7 I still have these issues with older version which is actually deployed. Hope to see new version in use as early as possible. |