To put your mind at ease a little:
The translation editor makes a backup up everything. Even if
someone accidentally or intentionally erased all of the
translations, we could revert back to the previous state
instantly, and change the password.
I see the translation editor as a place to make minor
changes, not a place to write brand-new translations.
When the developers add a new phrase to the website, it
should be much faster and easier for the translators to
update their languages.
Finally, I don't intend to make the translation editor
available to lots of people; ideally just 1-2 people
per language. So I'm not worried about people making
Mostly I'm just trying to make sure that I and the other
developers aren't spending all of our time coordinating
translations instead of focusing on improving the product.
I'm totally happy to upload and integrate some new files
when somebody completes an entirely new language or a large
number of new files. But imagine in six months - we may
have 12 languages, and that means that every change to
the web page would require us to manually upload 12 new
translated pages! Ack! So that's what the translation
editor should help to solve.
> Hi Dominic...
> Dominic wrote:
> > Thanks for doing such a great job with the translations!
> Thanks for appreciating the value of our work.
> About the new Translation Editor:
> The first moment I started using the editor I felt it great. Friendly,
> comfortable, simple, and flexible. that instant I though what you surely
> mean when you refer to make it bigger: to use something similar for
> paragraphs. Just form with a TextArea for each paragraph.
> I see a couple of issues I think you should take into account:
> * The translation is something that takes it's time to be done. I
> don't know if this new way you are thinking to implement will need the
> translator to be Online all the time he/she is translating the
> paragraphs. That will mean on dial-up connections, big telephone bills.
> * And by the other hand, I see security issues: (bad intentions or
> just confussion or mistakes)
> - Evil hands (for any reason that could be imagined) could make
> disasters on the hard work of good translators (more if this application
> is going to be automatic).
> - Someone could change things that he/she thinks are a better
> translation without noticing that some word is there because it is on
> the manual too and in the program, and it was discussed with other
> translators to use that particular word to have an homogeneous
> translation between the Manual, the Program, and the Website.
> - Other translators with less knowledge of technical words could
> ruin the work of the translator before them that really knew what he/she
> was doing, when they decide to edit an already translated paragraph.
> - And there could be mistakes without bad intentions. For example
> if the languages are all together with the same password like they are
> right now someone could use the wrong link to the laguage and end
> translating to the wrong language.
> What I am most affraid of, are less skilled translators editing right
> translated paragraphs, or great skilled translators editing paragraphs
> in the best possible way but without the participation with the other
> translators to know why some words and phrases have been translated the
> way they have. And don't discard jealousy, and problems because of
> issues between translators of the same language (i.e.: "I wanted to
> translate this or that but you ended doing it first and did it all wrong").
> In short, I did really like the application, but some things I think
> should be taken in account. (If there were no evil intentions how much
> easy it would be to develop anything. But in this case there could be
> mistakes too, without bad intentions).
> best regards Dominic.
> Ezequiel Plaza
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.362 / Virus Database: 199 - Release Date: 7/05/02