diff options
Diffstat (limited to 'zarb-ml/mageia-i18n/attachments/20130404/f6dd94d9/attachment-0001.html')
| -rw-r--r-- | zarb-ml/mageia-i18n/attachments/20130404/f6dd94d9/attachment-0001.html | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/zarb-ml/mageia-i18n/attachments/20130404/f6dd94d9/attachment-0001.html b/zarb-ml/mageia-i18n/attachments/20130404/f6dd94d9/attachment-0001.html new file mode 100644 index 000000000..0d0dae695 --- /dev/null +++ b/zarb-ml/mageia-i18n/attachments/20130404/f6dd94d9/attachment-0001.html @@ -0,0 +1,33 @@ +<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/4/4 Oliver Burger <span dir="ltr"><<a href="mailto:oliver.bgr@gmail.com" target="_blank">oliver.bgr@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> +Well, it doesn't matter if the translations are in a separate<br> +repository or not and I'm not sure, what it woudl mean for the devs,<br> +to separate them.<br> +The problem with tx is - or at least was - the manual work involved<br> +upon string changes.<br> +<br> +As an example:<br> +When uploading a file into tx, it parses that file and adds the<br> +strings into the database. When the string changes in the original pot<br> +(even it's only a typo), and you reupload the pot file, tx will parse<br> +it and see a new string and one string missing and it will act<br> +accordingly:<br> +It will remove the translations for the old string from its database<br> +and it will add the new untranslated string, since it can not know,<br> +that this was only a string change.<br> +So the task for us (mostly me) was:<br> +- Tell you not to touch certain translation resources in a certain time span<br> +- Download all files from this resource from tx<br> +- merge them manually with the changed po files (it couldn't be<br> +automated, since TX also had problems fuzzying strings correctly)<br> +- reupload all files to tx and tell you to check<br> +<br> +I would rather have a solution without the need to do so....<br> +<br> +Cheers,<br> +<br> +Oliver<br> +</blockquote></div>Hi again. I think most of the problems you mentioned are past day problems.<br></div><div class="gmail_extra">-Tx can be locked for certain resources to not accept new translations. See: <a href="https://www.transifex.com/projects/p/chakra-project/language/tr/">https://www.transifex.com/projects/p/chakra-project/language/tr/</a> <br> +</div><div class="gmail_extra">Resources wtih red dot mark locked.<br><br></div><div class="gmail_extra">- As i mentioned earlier even a bash script can automate pulling from tx process on server side. İs it so hard to do? I really do not know...<br> +<br></div><div class="gmail_extra">- Merging should be done in tx. Say, use hourly cron job to pull from and push to tx. Than tx should care of translations and resources merging?<br><br></div><div class="gmail_extra">- As i mentioned earlier again, i can tell tx can automatically pull resources and transations from svn from what i read.<br> +<br></div><div class="gmail_extra">- Tx do not mess up translator information anymore. It has been fixed as i know.<br><br></div><div class="gmail_extra">- For the fuzzy strings, tx still adds them into database as suggestions and every tx translator can see and if possible use them in online translation.<br> +</div><div class="gmail_extra">My 2 cents.<br></div></div> |