 |
 |
 |
|
|
|
|
Suggestions
 How to translate / localise TuxGuitar
|
|
| Author |
Message |
|
Samuel Murray (samuel[at]translate.org.za)
|
|
Post:
Feb 25th 2008 at 8:40 AM |
|
|
G'day everyone
I lead a volunteer translation project to translate opensource software into various languages, and TuxGuitar looks like a likely candidate for translation. I see you're using Java .properties files, which we can handle.
I'm just not sure about certain procedures about translating TuxGuitar -- could someone please let me know?
* Are languages assigned to a single translator or translation team, or do you simply take the latest translation from whoever submits it?
* Do you have a system to deal with conflicting translations, or do you simply trust the last or the previous translator?
* The messages.po file I got from the source code seemed to have been in a Windows encoding -- is this normal, or is that just beacuse I got it from my Windows installation?
I look forward to your responses. Should I contact the developer(s) directly?
|
|
| Back to Top |
| |
|
Julian
|
|
Post:
Feb 25th 2008 at 9:29 AM |
|
|
Hello,
We don't have a translation system.
we only receibe mails from who want translate the app, and he became a translator.
but, the translation "must" not exist on CVS version. (if exists, and you want fix any bug, just contact the translator.)
don't worry about the encoding problem, i can fix that.
the strange chars must be converted to unicode UTF-8.
On CVS version, there is a single perl script todo that.
TuxGuitar/share/lang/touft.pl
you can excec:
./toutf.pl orig_file > new_file
well, that's if you have GNU/Linux. ( i'm not sure what about that script on other OS )
You can contact me ( from contact link ).
NOTE: TuxGuitar-1.0 is very near to release. so if you want make a translation, please make one based on CVS version.
so i'll can include that file on the next release.
Bye.
|
|
| Back to Top |
| |
Post Reply
|
|
 |
|
 |
|
