Loading Profile...
CHAMP
Translation queries
G'day guys,
Recently discovered translate.songbirdnest.com and thought I'd fix up a few mistakes in en-gb. However, I have since noticed a few things:
1) MANY original en-us statements have typos, spelling mistakes and grammatical errors (I have seen a few instances of "transfered"). Is there any way I can fix these? Is there an easy way, or do I need to edit the raw DTD file and submit it as a patch to bugzilla?
2) In fact, I even noticed 1 which I would consider a blocker for 1.3. "Do not manage music into your watch folder directory if you are also using Watch Folders" is very visible in the prefpane, yet makes absolutely NO sense.
3) Many old translations don't match the en-us version. I suspect that the strings in the en-us have changed since they were originally posted (and the en-gb translations aren't automatically dropped when a change has been made to the US). Should I change strings to match the en-us string ALWAYS (I mean where the statement differs)?
I'd like to see en-gb become good enough for the en-gb version to be offered alongside the US version on the website before 1.4.
Recently discovered translate.songbirdnest.com and thought I'd fix up a few mistakes in en-gb. However, I have since noticed a few things:
1) MANY original en-us statements have typos, spelling mistakes and grammatical errors (I have seen a few instances of "transfered"). Is there any way I can fix these? Is there an easy way, or do I need to edit the raw DTD file and submit it as a patch to bugzilla?
2) In fact, I even noticed 1 which I would consider a blocker for 1.3. "Do not manage music into your watch folder directory if you are also using Watch Folders" is very visible in the prefpane, yet makes absolutely NO sense.
3) Many old translations don't match the en-us version. I suspect that the strings in the en-us have changed since they were originally posted (and the en-gb translations aren't automatically dropped when a change has been made to the US). Should I change strings to match the en-us string ALWAYS (I mean where the statement differs)?
I'd like to see en-gb become good enough for the en-gb version to be offered alongside the US version on the website before 1.4.
I’m excited
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?Hey Andrew,
I know you sent question 2 direct to me and Ali but I also passed this thread on to Georges so hopefully he can address your questions or point us in the right direction.
I’m thankful
-
Inappropriate?Andrew,
Thanks for being so thorough. If you have caught simple typos, etc. in the original english, I'd suggest to simply file a bug and we should be able to correct it. If the change are more involved, attaching a patch for the DTD file would make it easier.
Regarding tracking the translations, we do update en-us from time to time, so yes, it's a good idea to match them.
The company and 1 other person say
this answers the question
-
Inappropriate?Is there any chance in the future that translate.songbirdnest.com could mark translations where the en-us statement has changed? Otherwise, the translations will NEVER be on par with the originals.
EMPLOYEE
EMPLOYEE
