On Fri, Mar 4, 2011 at 8:47 AM, Jiri Moskovcak <jmoskovc@xxxxxxxxxx> wrote: > When I was migrating ABRT to transifex.net I hit a problem with tx push, > so to ease the life of others who may hit the same problem here is my story: > > 1. created the project > 2. created the resource by uploading the abrt.pot > 3. outsource the project to Fedora Project > 4. try to $ tx push -t > 5. got "unauthorized" error with correct user/login in .transifexrc > > - as it turned out you have to push the translation files *before* you > outsource the project, because once you do it, you have to be a member > of that team to add translation, which I think is wrong and the owner of > the project should always have the permission to add (push) translations > (even the button "Add Translation" in webui dissapears once you > outsource the project) A fix is on the way for our weekly Tx updates. Until then, please use the above workaround (push translations before outsourcing access). Instructions on wiki were updated with this tip. Thanks for reporting. -d > On 03/03/2011 04:46 PM, Jared K. Smith wrote: >> Quick Summary >> --- >> The Fedora translation workflow has changed. ÂIf you are a developer >> of a package being translated by the Fedora Translation (L10n) >> Project, you must change your workflow slightly if you want translated >> strings to appear in your software package. Tools and assistance are >> available to make this workflow as simple as possible for developers. >> Read below for details. >> >> Details >> --- >> Over the past couple of weeks, we've made some improvements and >> infrastructure changes to the Fedora translation system. ÂWe've moved >> from a self-hosted version 0.7 instance of the Transifex software to a >> hosted version of the 1.1-dev version at Transifex.net. The upgrade >> from version 0.7 to version 1.0 (and beyond) introduces a number of >> important changes for developers and packagers. ÂPlease pay close >> attention to this email, particularly if your software package uses >> translations provided by the Fedora Translation team. ÂWhile the >> changes aren't terribly complicated, they do have a bigger impact on >> the developer than they do on the translation team. >> >> The most visible change is that Transifexâs native integration with >> source code management systems has been replaced by a mechanism for >> automatic updates. ÂTransifex now watches an HTTP view of a repository >> for change notifications. ÂIn addition, there is now a more secure >> command-line tool for project maintainers and translators. ÂThis new >> command-line tool has been packaged for Fedora in the >> "transifex-client" package. ÂIt is currently available in Rawhide >> (pre-F16), and in the "updates-testing" repositories for Fedora 13, >> 14, and 15, and EPEL 5 and 6. >> >> Here's the new workflow: >> >> This series of steps only needs to be run once for a project. >> * The developer installs the "transifex-client" package: >>  Âyum --enablerepo=updates-testing install transifex-client >> * The developer runs the "tx init" command in the top level folder of >> the project. >> * The developer runs the "tx set" command according  to the >> transifex-client user guide found at: >> http://help.transifex.net/user-guide/client/client-0.4.html. ÂThis >> creates a small config file, .tx/config, which can be committed in the >> repository for re-use, if desired. >> >> This series of steps are run on as as-needed basis: >> * The developer updates and commits his or her POT file to the >> project's repository at string-freeze time or as needed. >> * Transifex watches an HTTP link to that POT file and auto-updates its >> English strings regularly, *OR* the developer can also push the POT >> file to Transifex (either manually or as part of a >>  Âbuild script) by using the "tx push" command. >> * Translators work inside Transifex. ÂTranslated strings are stored >> inside of Transifex, and are *not* pushed automatically to the >> developer's repo. >> * Before rolling a release, the developer runs 'tx pull' (either >> manually or from a build script) to fetch the latest translation files >> from Transifex. Translation files do not need to live in >>  Âthe repo, although the developer may commit and store copies if desired. >> >> For more details on the features of the new version of Transifex and >> more help on using the transifex client, please refer to either >> http://help.transifex.net/user-guide/one-dot-zero.html or the >> Fedora-specific wiki page at >> https://fedoraproject.org/wiki/FAQ_on_migration_to_transifex.net. If >> you have technical questions, feel free to ask questions in the >> #fedora-l10n or #transifex IRC channels or on the devel mailing list. >> >> -- >> Jared Smith >> Fedora Project Leader >> _______________________________________________ >> devel-announce mailing list >> devel-announce@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/devel-announce > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > -- Dimitris Glezos Transifex: The Multilingual Publishing Revolution http://www.transifex.net/ -- http://www.indifex.com/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
