What I think I said is that it *currently* takes a lot of time to set up. As
we do not have development time to spare, and I am overbooked, I will not be
able to have it set up or set it up myself. However, we have a bunch of open
staff positions and I'd be happy to set someone up with a shell account at twn
and do some tutoring, the that another volunteer can make things in order.
Some shell knowledge and php skills are important, because I'd like to see
solutions that scale and work properly.
The twn approach scales, but work at the backend needs to be done to set it up
properly. I'm certain that multiple translators editing files and committing
them does not scale.
From: John Reese [mailto:jreese@...]
Sent: Friday, November 27, 2009 6:37 PM
To: developer discussions
Subject: Re: [mantisbt-dev] Plugins translations
Jeferson Oliveira wrote:
> I started to translate the Source Control and WebSVN plugin strings.
> Will the strings be added to the main mantis language file or other
> translate projects will be created in translatewiki.net for each
AFAIK, Siebrand has mentioned that translatewiki is not easy to set up
individual translation sets for each plugin, so it will likely have to be
maintained the old fashioned way. =\
> Also, currently the language files of the Source plugin are not in
> UTF-8 format and this should be the format for compatibility with the
> main language files.
Considering that I have no clue a) why a plaintext english strings file should
be in UTF-8, or b) how I would go about specifically generating a UTF-8
plaintext file, a patch that I can apply directly to Git is probably the best
> If someone could point me to right direction so I can send my
> contributions I would appreciate.
My bugtracker is located at http://leetcode.net/mantis -- I would be more than
happy to accept bug reports or patches against the source integration plugins