<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 13.01.2014 02:36, Lunar wrote:<br>
<span style="white-space: pre;">> Frithjof:<br>
>> Unfortunately I don't think that Transifex helps much
here: When you<br>
>> are translating a complete web page, you need a lot more
context than<br>
>> when translating isolated strings in a program.<br>
><br>
> My opinion on this:<br>
><br>
> The current community of people working on translating Tor
software is<br>
> on Transifex. The tool is already working for them. I suggest
we try to<br>
> push website translations and see what they think. If the
translators<br>
> are unhappy with Transifex to work on web pages, then we can
try<br>
> different things to see what they would like. But let's focus
on people<br>
> here, tools should come after.</span><br>
<br>
you're probably right. go the familiar route and only change if the
pain points are real (and not only imaginary).<br>
<br>
if transifex is open to add (small) features for website
translations, that of course would be ideal.<br>
<br>
the main problem is the lost context when you're filtering over
untranslated strings.<br>
e.g. you select a paragraph/string but have no (easy) way to get to
the next or previous paragraphs (assuming they already have been
translated).<br>
that IMHO is a *real* pain in the ass. but then you probably could
just keep a browser with the real website open and get the context
from there.<br>
<br>
<br>
will the transifex integration be handled by the software guys? (as
in: the same people who did the integration to translate tor itself)<br>
or is there need for any help?<br>
<br>
<span style="white-space: pre;">><br>
><br>
> The other thing is that I think we should have a staging
environment<br>
> where translators can review their translation on a copy of
the website<br>
> right after pushing a change.</span><br>
<br>
maybe a point to raise with the back-end/cms guys: the build-times
for the site-generator shouldn't get out of hand.<br>
<br>
<span style="white-space: pre;">> This would make them able to
verify their<br>
> translation in the best context possible.<br>
><br>
> Setting up a staging environement is tracked in<br>
> <a class="moz-txt-link-rfc2396E" href="https://bugs.torproject.org/10597"><https://bugs.torproject.org/10597></a>.<br>
><br>
> Also, it's probably worthwhile to mention that translations
*will* have<br>
> to be manually reviewed before being merged in the official
website<br>
> to prevent attacks based on malicious code.</span><br>
<br>
<br>
</body>
</html>