Hi again
Thank you intrigeri for the info.
El 27/03/14 19:26, intrigeri escribió:
> In case nobody replies here, you might want to get in touch with the
> people doing Spanish translation on Transifex. If needed, I can easily
> generate a list of email addresses.
I'll join the team in Transifex and I can send a message from there.
>> If there is other workflow or procedure already set up, please let me know.
> Until now, we only take Git pull requests for the website, for various
> reasons including:
Oh, sorry, I jumped into the Translate website section and skipped the
Git part :)
No problem about using Git. I'm not an expert, but it shouldn't be a
blocker.
I said I prefer to translate the website because I prefer to deal with
xhtml or wml files than with PO files :)
But I know Poedit more or less, so it shouldn't be a problem either.
Regards
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
>
> - Git branches allow translators to work on new stuff separately
> from what's already published, when we are preparing a release and
> issueing a call for translations; note that generally, new and
> fuzzy strings are spread over dozens of files in this case, so I'm
> not sure if a per-file, purely email-based workflow would work;
>
> - Git gives us the "what version was translated" information for
> free, and allows to handle more nicely the case when the English
> text has changed in the meantime.
>
> If the Git requirement is a blocker, and you prefer using another
> workflow, at least this needs to be taken into account (e.g. take note
> of what commit a PO file was at when you start working on it, and make
> it explicit what branch you're working on).
>
> E.g. another team wanted to have one team member as the Git person,
> who acts as the interface between developers (Git) and whatever
> workflow and toolkit the rest of the team uses. I'm not sure this
> happened in practice, but this would certainly work, given one
> dedicated person who is at ease with Git.
>
> Regards,
>
