2013/6/30 Pete Travis <me(a)petetravis.com>:
Okay, I've created a project[1] and created resources by
uploading POTs
from git[2]. The translation memory experiment I had in mind didn't work
out, since it doesn't look like there were any of the strings were in
the project TM to start with, but your translations will make a good
start. At least we now have this guide set up for translation. As Nick
discovered, the source language *must* be 'en' for a project to be added
to the Fedora hub; I'll leave the test project you created for you to
delete when you're sure the POs have been salvaged.
I deleted it, thanks.
Are you sure that all .pot files have been pushed to Transifex into
the new project?
I count only 2878 strings on Tx, for 25 resources, whereas I see 88
.pot (for 6500+ strings) files in the f19 git branch.
I was thinking about an issue in the publican version I was using
(epel's version for RHEL6), but F18's publican gives the same result
;)
I'll upload the missing ones.
Jérôme, per your comments above, I've sponsored your membership
in the
docs and docs-writers FAS groups. After working with you with the
Release Notes, and observing in other areas, I have complete confidence
in both the quality of your commits and your judgement in working with
guide owners when the scope of your changes warrants it.
Thank you. As usual, with great power comes great responsibility. I
respect that and will try not to mess.
Laura, I have set up your guide for translation and invited you as a
maintainer on Transifex. I've also created the 'f19' branch of the git
repo to use for managing translations and publications for that
release. As a side bonus, translators often do a great job providing
feedback :)
I may not work directly on it, but yes, translating means reading
thoroughly a document, so the team will indeed have feedback.
Regards, thanks again for your trust,
J.
--
Jérôme Fenal