Thanks for the heads up! I've tried following your instructions, but after editing the .tx/config file, the translation isn't being updated with the remote short-named version.
Here's what my .tx/config file looks like:
[main]
host = https://www.transifex.net
lang_map = nl: nl-NL
[fedora-readme-live-images.Article_Info]
file_filter = <lang>/Article_Info.po
source_file = pot/Article_Info.pot
source_lang = en
lang_map = nl: nl-NL
[fedora-readme-live-images.Author_Group]
file_filter = <lang>/Author_Group.po
source_file = pot/Author_Group.pot
source_lang = en
lang_map = nl: nl-NL
[fedora-readme-live-images.Fedora_Live_Images]
file_filter = <lang>/Fedora_Live_Images.po
source_file = pot/Fedora_Live_Images.pot
source_lang = en
lang_map = nl: nl-NL
[fedora-readme-live-images.Revision_History]
file_filter = <lang>/Revision_History.po
source_file = pot/Revision_History.pot
source_lang = en
lang_map = nl: nl-NL
However, when I run 'tx pull -r fedora-readme-live-images.Fedora_Live_Images -l nl-NL', tx pulls the remote nl-NL Fedora_Live_Images.po file instead of the nl one. I know the remote nl file is more up-to-date than the remote nl-NL one, but the changes aren't being pulled to the local repo.
What am I doing wrong? I am hesitant to run 'tx push' as I don't want to overwrite the more recent translation with the old one I have locally.
Thanks!
Nathan
On Mon, 2011-06-20 at 23:15 +0300, Dimitris Glezos wrote:
A few months ago, some of the Fedora teams were duplicated to support Publican's language format (eg. nl and nl-NL). This support has been available in the Transifex Client for many weeks now, and Publican projects can simply configure their Tx client to easily map the Fedora Team languages to their dash format (ie. convert nl → nl-NL) without requiring to have a duplicated team. This configuration is stored in the ``.tx/config`` file, so it's going to be available for all users of the git repos. http://lists.fedoraproject.org/pipermail/docs/2011-May/013337.html http://help.transifex.net/user-guide/client/devel.html#customizing-the-language-mappings We will proceed in removing all the duplicated teams soon and only keep the ones the L10n team uses. For example, remove nl_NL and only keep nl (merge the first members into the latter and remove team). The following languages will be RENAMED (two-letter teams do not exist): - zh_CN → zh - lt_LT → lt - es_ES → es - vi_VN → vi The following teams will be REMOVED (two-letter teams already exist): - cz_CZ - it_IT - jp_JP - lv_LV - fa_IR - ta_IN - uk_UA The Docs Project owners can follow something like the following: 1. tx pull --translations (remote nl_NL → local nl_NL) 2. <edit .tx/config file to add mappings> 3. tx push --translations (local nl_NL → remote nl) 4. # tx pull --translations #remote nl → local nl-NL) Step #1 can only happen before we remove/rename the teams. If there is a time constraint, or we are missing something, please let us know. -d -- Dimitris Glezos Transifex: The Multilingual Publishing Revolution http://www.transifex.net/ -- http://www.indifex.com/
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
