On 06/29/2013 01:09 PM, Jérôme Fenal wrote: > 2013/6/29 Jérôme Fenal <jfenal@xxxxxxxxx>: >> 2013/6/29 Pete Travis <me@xxxxxxxxxxxxxx>: >>> On 06/29/2013 09:58 AM, Jérôme Fenal wrote: >>>> 2013/6/25 Jérôme Fenal <jfenal@xxxxxxxxx>: >>>>> 2013/6/25 Eric H. Christensen <sparks@xxxxxxxxxxxxxxxxx>: >>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>> Hash: SHA512 >>>>>> >>>>>> On Tue, Jun 25, 2013 at 07:15:20PM +0200, Jérôme Fenal wrote: >>>>>>> 2013/6/25 Eric H. Christensen <sparks@xxxxxxxxxxxxxxxxx>: >>>>>>>> On Tue, Jun 25, 2013 at 04:54:34PM +0200, Jérôme Fenal wrote: >>>>>>>>> Le 25/06/2013 15:34, Eric H. Christensen a écrit : >>>>>>>>>> On Tue, Jun 25, 2013 at 03:15:51PM +0200, Jérôme Fenal wrote: >>>>>>>>>>> I've tried to setup my own translation project >>>>>>>>>>> (freeipa-management-guide) for the FreeIPA management guide on >>>>>>>>>>> Transifex, and it worked nicely. I'll remove it if needed, as it >>>>>>>>>>> seems it's not easy to change the hierarchy to another hub. The >>>>>>>>>>> Fedora hub may have to create the project envelope here. >>>>>>>>>> ... >>>>>>>>>>> My proposal : - I can destroy my own project, as it would be nice >>>>>>>>>>> to have it under the Fedora umbrella in Transifex, >>>>>>>>>> You shouldn't need to destroy your own project. It can be added to >>>>>>>>>> the Fedora umbrella without too much trouble. In Tx, Manage->Access >>>>>>>>>> Control and then select "Fedora Project" on the "Outsource access >>>>>>>>>> to:" field. Someone with Tx rights will need to accept the project >>>>>>>>>> but that should be it. I've done that with a couple of other >>>>>>>>>> projects. >>>>>>>>> Tried that, but I only see beatport & Test_project in the combo box. >>>>>>>> Hmmm... >>>>>>>> >>>>>>>>> So I added you as a co-maintainer, in case you can manage to do >>>>>>>>> something here ;) >>>>>>>> I've asked Nick to add it to the Fedora Project portion of Tx. >>>> Hi all, >>>> >>>> Nick did remove last night my FreeIPA Management Guide project in >>>> Transifex, and recreated it (empty, but I had backups of my >>>> translations). >>>> >>>> I populated the guide again on Transifex, and is ready to accept >>>> translations for all languages supported by Fedora translations. >>>> >>>> @Martin: as I'm currently reading it thoroughly while translating it >>>> into French, how would you like me to get the fixes I could make? >>>> The easiest for me would be to have a direct commit access to the git >>>> repo, but you may want to review the fixes. >>>> The main one is the extensive use of &IPAA; & &IPAB; entities (resp. >>>> "a IPA" and "A IPA"), which make it a real pain to translate (I need >>>> to revert both to &IPA; and add the article, which is will for sure be >>>> forgotten in translations). >>>> >>>> Or I could commit that to my github repo, and see later how we proceed. >>>> >>>> Let me know, regards, >>>> >>>> J. >>> Did you notice if Transifex's Translation Memory retained any of the >>> translated strings? I'm always curious about the scope the TM will >>> apply to. >> Well, I didn't check that, as I pushed my saved translations just >> after creating the resources. > Thinking of it, I suppose I could drop all the resources completely, > recreate them without pushing my translations and check from there. > I believe it would here because I would not drop the project completely. > > To be in the exact same conditions, you could check out my test > project for the new Virt deploy&admin guide I created, drop it, and > recreate it under Fedora's hood. I could then recreate the resources, > and check here. > > Because I believe (from my memories of translating Transifex strings) > that a translation memory is not share between projects. It would work > within Fedora, but maybe not between two different projects (mine & > Fedora). > > Want to try? ;) > > J. > 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. 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. 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 :) [1] https://www.transifex.com/projects/p/fedora-virt-deploy-and-admin/ [2] https://git.fedorahosted.org/cgit/docs/virtualization-deployment-and-administration-guide.git/ -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize@xxxxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
