ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) - Printable Version
-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4)
+---- Forum: Translation (/forumdisplay.php?fid=24)
+----- Thread: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) (/showthread.php?tid=25594)
ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-21-2004 at 03:13 PM
This post is a reminder of some (minor and major) faults (most technicaly) currently in the latest translations.
So, this is a "must read" for all the translators out there!!!
This concearns the translations for:
Afrikaans, Arabic, Bahasa Indonesia, Bosanski, Català, Chinese Simplified, Chinese Traditional, Dansk, Deutsch, Español (España), Español (Latino), Eesti, Français, Galego, Greek, Hebrew, Italiano, Japanese, Korean, Magyar, Norsk (Bokmål), Português, Suomi, Svenska, Thai, Valencià
UPDATE 3 (may 25th): I checked all the languages again. Check yours for the updated list.
UPDATE 2: I had a very very quick look in some menu's in Messenger Plus! and discovered that some lines are too long in some languages. So do check your translation in Messenger Plus itself!
(current languages checked for this: Afrikaans, Arabic, Bosanski, Deutsch (translator notified), Bahasa Indonesia (translator notified), Français, Italiano, Norsk (Bokmål))
UPDATE 1: I also checked for double spaces in the middle or at the end of textlines. So recheck the list please...
Note that there may be faults that I've missed. I only checked the translations roughly and quickly.
Note that I didn't checked spelling, nor grammar, nor other language rules. I also didn't check for the consequent use of titles, names, etc... And I didn't check for ampersand collisions/missing...
Afrikaans (Lang_Afrikaans.ini)
Incomplete translations:
[Commands]ErrorStartVideo is used for both the videochat as for the audiochat. (see DefaultLg.dat) So, check out your translation for them.
Double keys, delete one of them:
[Dialog.PersoStatus]OkButton
[Dialog.PersoStatus]CancelButton
[Dialog.PersoStatus]PeronaliseButton
[Dialog.PersoStatus]CloseButton
[Dialog.PersoStatus]NameSuffixLabel
[Dialog.PersoStatus]AutoCloseMessageOS
[Dialog.PersoStatus]AutoCloseMessageMS
Obsolete keys, delete them:
[Dialog.PersoStatus]Tooltip4
[Dialog.PersoStatus]ConfigButton
[Dialog.PersoStatus]PreDefinedHeader
[IMWindowMenu]AddContact
[IMWindowMenu]QuickTexts
[PrefDlg.EventLogging]WindowMaxLine
[PrefDlg.MsgQuickTexts]Label2
[PrefDlg.NotifOpt]Text2
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Dialog.EncryptionPassword]TextEncryption
[PrefDlg.NotifDefaults]Text3
Too long textlines:
(it could be that there are more, I've only found these after a very quick look thru some menu's within Plus!)
[PrefDlg.CustomNames]Text1
[PrefDlg.CmdTags]Text2
[PrefDlg.Logging]TimeStampCheck
[PrefDlg.NotifOpt]Text1
[PrefDlg.POP3Email]Text1
[Dialog.NotifConfig]TopLabel
[Dialog.PersoStatus]InfoFrame
Arabic (Lang_Arabic.ini)
Obsolete keys, delete them:
[IMWindowMenu]AddContact
[IMWindowMenu]QuickTexts
[Dialog.PersoStatus]PreDefinedHeader
[PrefDlg.EventLogging]WindowMaxLine
[PrefDlg.MsgQuickTexts]Label2
[PrefDlg.NotifOpt]Text2
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Launcher]MinReq
[SoundCommands]Doh
[IMWindowMenu]CurrentIP
[Dialog.UpdateNotif]DisableUpdate
[Dialog.PersoStatus]Tooltip2
[PrefDlg.Archiving]Text1
[PrefDlg.CustomNames]Text1
[Dialog.QuickIconCustom]TopLbl
[PrefDlg.Plugins]ChangeMsg
[Dialog.Quotes]TimeMaxHour
Too long textlines:
I've seen some textlines, menu's and buttons that are half-truncated!
Check out:
* [PrefDlg.CmdTags]Text2 <= missing ")"
* Sometimes there is "<word><space>," and sometimes just "<word>,"
* Sometimes there is "<word><space>.." and sometimes just "<word>.."
* Sometimes there is "<word><space>:" and sometimes just "<word>:"
* Sometimes there is "..." and sometimes "...."
etc... but these are very small minor things
Bahasa Indonesia (Lang_Bahasa (Indonesia).ini)
Checked with updated version from the translator, everything seems ok...
Bosanski (Lang_Bosnian.ini)
Are these correct?:
[FileInfo]CurrentLanguageA=Bosnian
CurrentLanguageA should contain the name of your language in your own language (not in English), but in the limited normal character set.
So this must be changed to CurrentLanguageA=Bosanski also.
If the languagename can't be represented with the normal character set then and only then, the English translation must be used. While CurrentLanguageM should contain the name of your language in your own language (not in English), but in the character set of your own language. (see TranslationGuidelines.doc for more details)
for example:
CurrentLanguageA=Francais
CurrentLanguageM=Français
not
CurrentLanguageA=French
CurrentLanguageM=Français
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Dialog.ContactManager]DeleteConfirmTitle
[Dialog.PersoStatus]AutoCloseMessageMS
[Dialog.PersoStatus]Tooltip2
[PrefDlg.BossProtectIcon]Text2
[Dialog.BasicLogViewer]BadEncryptionPwd
[PrefDlg.LocalSettings]TitleSub
[PrefDlg.LocalSettings]UnicodeLog
[PrefDlg.CtcListGenOptions]Text1
[PrefDlg.CtcListGenOptions]Text2
[PrefDlg.Archiving]Text3
[Dialog.Quotes]Label2
[PrefDlg.Plugins]EnableCheck
[ArgumentBrowser]ArgStatusNameTag
[PrefDlg.WordFilter]DuplMsg
Too long textlines:
Did a quick view, nothing seems too long at first sight...
Català (Lang_Catala.ini)
Checked with new version, everything seems ok...
Chinese Simplified (Lang_Chinese Simplified.ini)
Checked with version from Plus! 3.00.92, everything seems ok...
Chinese Traditional (Lang_Chinese Traditional.ini)
Checked with version from Plus! 3.00.92, everything seems ok...
Dansk (Lang_Danish.ini)
Very minor thing:
Almost all lines in the translation ends with a space. Although this is not a real fault, it isn't needed...
Deutsch (Lang_Deutsch.ini)
Checked with new version, everything seems ok...
Español (Espana) (Lang_Espanol (Espana).ini)
Checked with version from Plus! 3.00.92, very small error found, fixed is confirmed...
Español (Latino) (Lang_Espanol (Latino).ini)
Obsolete keys, delete them:
[IMWindowMenu]AddContact
[IMWindowMenu]QuickTexts
[Dialog.PersoStatus]PreDefinedHeader
[PrefDlg.EventLogging]WindowMaxLine
[PrefDlg.MsgQuickTexts]Label2
[PrefDlg.NotifOpt]Text2
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Install]Screen3_Text
Eesti (Lang_Estonian.ini)
Forgotten/incomplete translations:
For the sound-command "Come On!" there is no translation given, see http://shoutbox.menthix.net/showthread.php?tid=26127 for the fix.
Are these correct?:
[FileInfo]CurrentLanguageA=Estonian
CurrentLanguageA should contain the name of your language in your own language (not in English), but in the limited normal character set.
So this should be changed to CurrentLanguageA=Eesti.
If the languagename can't be represented with the normal character set then and only then, the English translation must be used. While CurrentLanguageM should contain the name of your language in your own language (not in English), but in the character set of your own language. (see TranslationGuidelines.doc for more details)
for example:
CurrentLanguageA=Francais
CurrentLanguageM=Français
not
CurrentLanguageA=French
CurrentLanguageM=Français
Check out:
* Sometimes "<word><space>:" is used, sometimes just "<word>:"
* [IMWindowMenu]SBeRightBack <= only ".." instead of "..."
* [Dialog.UpdateNotif]CancelButton <= only ".." instead of "..."
Français (Lang_Francais.ini)
Checked with version from Plus! 3.00.92, everything seems ok...
Galego (Lang_Galego.ini)
Incomplete translations:
[Commands]ErrorStartVideo is used for both the videochat as for the audiochat. (see DefaultLg.dat) So, check out your translation for them.
Obsolete keys, delete them:
[IMWindowMenu]AddContact
[IMWindowMenu]QuickTexts
[Dialog.PersoStatus]PreDefinedHeader
[PrefDlg.EventLogging]WindowMaxLine
[PrefDlg.MsgQuickTexts]Label2
[PrefDlg.NotifOpt]Text2
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Dialog.About]Text1
[Dialog.PersoStatus]Text1
[Dialog.ImpExport]ExportRadio
[PrefDlg.Passwords]Text1
[Dialog.PrefLock]Text1
Greek (Lang_Greek.ini)
This language file is a real mess. It's still full of original English parts!!! Delete all these as your translated parts will not be read out because the English parts come first.
Obsolete keys, delete them:
[PrefDlg.MsgQuickTexts]Label2
[PrefDlg.NotifOpt]Text2
Missing keys:
[Launcher]MsgRunning
[Notifications]SchedulerLast
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[MainMenu]LockMessenger
[MainMenu]Help
[PrefDlg.MsgQuickTexts]Text1
[CommandBrowser]HelpInfo
[CommandBrowser]HelpConfig
Hebrew (Lang_Hebrew.ini)
Checked with version from Plus! 3.00.92, everything seems ok...
Italiano (Lang_Italiano.ini)
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Commands]ErrorStartVideo
[IMWindowMenu]MyEmail
Check out:
[Install]FileCopyError => double ":"
Japanese (Lang_Japanese.ini)
Checked with version from Plus! 3.00.92, everything seems ok...
Korean (Lang_Korean.ini)
Checked with new version...
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[PrefDlg.Archiving]Text3
Magyar (Lang_Magyar.ini)
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Share]Message2
Norsk (Bokmål) (Lang_Norsk (Bokmal).ini)
Checked with new version (rev:2.6), everything seems ok...
Português (Lang_Portugues.ini)
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Install]MessengerRestart
[Dialog.Recovery]Text1
[PrefDlg.CtcListGenOptions]Text2
Check out:
* [PrefDlg.POP3Email]Label1 <= There is a space before ":", dunno if this is intentional...
Suomi (Lang_Finnish (Suomi).ini)
Are these correct?:
[FileInfo]CurrentLanguageA=Finnish (Suomi)
[FileInfo]CurrentLanguageM=Finnish (Suomi)
CurrentLanguageA should contain the name of your language in your own language (not in English), but in the limited normal character set.
So, these must be:
[FileInfo]CurrentLanguageA=Suomi
[FileInfo]CurrentLanguageM=Suomi
If the languagename can't be represented with the normal character set then and only then, the English translation must be used. While CurrentLanguageM should contain the name of your language in your own language (not in English), but in the character set of your own language. (see TranslationGuidelines.doc for more details)
for example:
CurrentLanguageA=Francais
CurrentLanguageM=Français
not
CurrentLanguageA=French
CurrentLanguageM=Français
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Dialog.CompatInfo]Text1
[QuickText.Defaults]Def3Text
Svenska (Lang_Svenska.ini)
Checked with new version (.92f), everything seems ok...
Thai (Lang_Thai.ini)
Obsolete keys, delete them:
[Dialog.PersoStatus]PreDefinedHeader
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Dialog.About]TranslationAuthors
[Dialog.RenameContact]EnableQuestion
Valencià (Lang_Valencian.ini)
Are these correct?:
[FileInfo]CurrentLanguageA=Valencian
CurrentLanguageA should contain the name of your language in your own language (not in English), but in the limited normal character set.
So this must be CurrentLanguageA=Valencia
If the languagename can't be represented with the normal character set then and only then, the English translation must be used. While CurrentLanguageM should contain the name of your language in your own language (not in English), but in the character set of your own language. (see TranslationGuidelines.doc for more details)
for example:
CurrentLanguageA=Francais
CurrentLanguageM=Français
not
CurrentLanguageA=French
CurrentLanguageM=Français
Obsolete keys, delete them:
[IMWindowMenu]QuickTexts
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Install]Screen2_NoAdmin
[Dialog.About]Text1
[PrefDlg.Archiving]Text1
[PrefDlg.SndConfig]Mpeg1Radio
[PrefDlg.SndConfig]Mpeg2Radio
[PrefDlg.MsgQuickTexts]MessageTip
[Dialog.Quotes]Text1
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by Mnjul on 05-21-2004 at 03:17 PM
quote:
Originally posted by CookieRevised
Chinese Traditional (Lang_Chinese Traditional.ini)
Double keys, delete one of them:
[IMWindowMenu]SendPlugin
Obsolete keys:
[PrefDlg.IMGenOptions]ChangeSecurityMsgCheck
[PrefDlg.LogChangePassword]OldPwd
Changes made. Thanks a million
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by user17033 on 05-21-2004 at 03:32 PM
quote:
Originally posted by CookieRevised
Deutsch (Lang_Deutsch.ini)
Are these correct?:
[FileInfo]CurrentLanguageA=German
CurrentLanguageA should contain the name of your language in your own language (not in English), but in the limited normal character set.
If the languagename can't be represented with the normal character set then and only then, the English translation must be used. While CurrentLanguageM should contain the name of your language in your own language (not in English), but in the character set of your own language. (see TranslationGuidelines.doc for more details)
for example:
CurrentLanguageA=Francais
CurrentLanguageM=Français
not
CurrentLanguageA=French
CurrentLanguageM=Français
i mailed patchou because of this, you can read the reason why i did it in my quote below
quote:
Originally written by me
i wrote "German" in CurrentLanguageA and "Deutsch" (=the translation) in
CurrentLanguageM because i think it's easier to search for your own language
in a list if you see that all languagenames are written in english.
Otherwise you don't know if you have to search German under "G" or "D".
Please tell me if you don't want the english name in CurrentLanguageA
quote:
Originally written by Patchou
[...] However, if you want to change the name in CurrentLanguageA, I'm
fine with it [...]
edit » to explain why i did this change: the setup's language autoselection for german did not work correct and you had to search "german / deutsch" manually. patchou fixed it for mp!3 and now it isn't really important what CurrentLanguageA's value is...
I can change it back to "deutsch" if you want me to...
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by CookieRevised on 05-21-2004 at 03:39 PM
Well, I followed the guidelines...
But actually I agree with your reasoning. But I also agree that you must see the language in your own language....
This is something where a clear line should be drawn. Either everybody puts English languagesnames, or either nobody does...
Cause with the current implementation, I still don't know when I need to search for the English one or the Native one... (Examples: Japanese/Francais, German/Nederlands, Korean/Espanol, etc....)
So:
quote:True, but the fact is, not all languages are written in English....
because i think it's easier to search for your own language
in a list if you see that all languagenames are written in english.
Conclussion: Patchou should make a clear decission in how we must write it and stick to that...
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by KeyStorm on 05-21-2004 at 03:44 PM
Thanks a lot for your revision 
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by user17033 on 05-21-2004 at 03:47 PM
i know that not all languages are written in english and i think you are right that patchou should make a clear decission...
as you can see i edited my post above to explain why i changed it.
i will change it back to "deutsch" and remove the "FileNameOverride" (i did not think about it again after patchou fixed the language autoselect problem)
edit » changed:
code:
[FileInfo]
OriginalFormat=ANSI
CodePage=1252
CompatibilityLevel=3087
CurrentLanguageA=Deutsch
CurrentLanguageM=Deutsch
RightToLeft=0
LangIdentifier=7
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by Leif on 05-21-2004 at 05:21 PM
1. "Incomplete translations:
[Commands]ErrorStartVideo is used for both the videochat as for the audiochat. (see DefaultLg.dat) So, check out your translation for them."
DefaultLg.dat
ErrorStartVideo=Sorry, couldn't start a video/audio conference with user "%s".
Swedish:
ErrorStartVideo=Kunde inte starta en röst-/videokonversation med "%s".
Is this not OK? Or perhaps you didn't check my latest translation (May 20).
2. "Faulty use of the ampersand "&":
In [Dialog.Preferences] (the Preferences window), Patchou asked NOT to put '&'-shortcuts on buttons. (see DefaultLg.dat)"
No ampersands on buttons?? I don't get this! What about these, taken from DefaultLg.dat?
OkButton=&OK
CancelButton=&Cancel
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by CookieRevised on 05-21-2004 at 05:49 PM
quote:I checked the files that were in the latest beta/RC => 3.00.92
Originally posted by Leif
Swedish:
ErrorStartVideo=Kunde inte starta en röst-/videokonversation med "%s".
Is this not OK? Or perhaps you didn't check my latest translation (May 20).
There it is:
ErrorStartVideo=Kunde inte starta en videokonferens med "%s".
So if this is fixed then
quote:This goes for [Dialog.Preferences] only! Not for all other buttons. Every button in the section [Dialog.Preferences] must not have a ampersand. See the comments in defaultLg.dat:
Originally posted by Leif
In [Dialog.Preferences] (the Preferences window), Patchou asked NOT to put '&'-shortcuts on buttons. (see DefaultLg.dat)"
No ampersands on buttons?? I don't get this! What about these, taken from DefaultLg.dat?
OkButton=&OK
CancelButton=&Cancel
quote:
from defaultLg.dat
;Preferences window. Do not put '&' shortcuts on buttons
[Dialog.Preferences]
....
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by Choli on 05-21-2004 at 05:49 PM
well posted cookie
quote:yay!!! spanish_spain isn't in the list
Originally posted by CookieRevised
This concearns the translations for:
Afrikaans, Arabic, Bahasa Indonesia, Bosanski, Català, Chinese Simplified, Chinese Traditional, Dansk, Deutsch, Español (Latino), Eesti, Galego, Greek, Hebrew, Italiano, Japanese, Korean, Magyar, Norsk (Bokmål), Português, Suomi, Svenska, Valencià
quote:All the menus, checkboxes, radio buttons and buttons * must have the &.
Originally posted by Leif
No ampersands on buttons??
* Note: this applies to all buttons except for the OK, Cancel and Apply that are at the bottom right of the preferences. Those buttons must not have any &.
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations) by CookieRevised on 05-21-2004 at 05:52 PM
quote:and Default and Backup button
Originally posted by Choli
quote:All the menus, checkboxes, radio buttons and buttons * must have the &.
Originally posted by Leif
No ampersands on buttons??
* Note: this applies to all buttons except for the OK, Cancel and Apply that are at the bottom right of the preferences. Those buttons must not have any &.
(as far as I'm concearned)RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-21-2004 at 06:08 PM
quote:they aren't buttons, but "links"
Originally posted by CookieRevised
and Default and Backup button (as far as I'm concearned)
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-21-2004 at 06:48 PM
Checked for double spaces also... recheck the list for your language
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-21-2004 at 06:50 PM
The reason for the ampersands is to make it easier for e.g. disabled people who are unable to use the mouse. And it also makes handling Windows much quicker for us "normal" people who prefer the keyboard to the mouse.
I have some questions...
1. Why must those buttons not have ampersands?
2. Why are there ampersands on OK and Cancel buttons elsewhere? This is not normal in Windows! There is no need for that because OK = Enter and Cancel = Esc.
3. Apply normally has an ampersand in Windows. Why not here in Messenger Plus!?
4. Default and Backup buttons? Can't find them! Where?
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-21-2004 at 06:50 PM
quote:minor bug, but fixed for the next version
Originally posted by CookieRevised
Español (Espana) (Lang_Espanol (Espana).ini)
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[Dialog.UpdateNotif]DisableUpdate
thanks cookie
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Mike on 05-21-2004 at 06:52 PM
So does anyone know what happened with the greek translation?
Its not that i care because i dont use the greek translation...
But i want to know if our greek translators read this...
RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-21-2004 at 06:53 PM
quote:Good point! Did that a week ago! Found two instances!
Originally posted by CookieRevised
Checked for double spaces also... recheck the list for your language
But there still are lots of them in other translations. I had a sneak peak!
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-21-2004 at 07:03 PM
quote:1) Because those button are used in every window of the preferences. And thus if you used ampersands there, you can't use them anymore in any other possible subwindow of the preferences
Originally posted by Leif
The reason for the ampersands is to make it easier for e.g. disabled people who are unable to use the mouse. And it also makes handling Windows much quicker for us "normal" people who prefer the keyboard to the mouse.
I have some questions...
1. Why must those buttons not have ampersands?
2. Why are there ampersands on OK and Cancel buttons elsewhere? This is not normal in Windows! There is no need for that because OK = Enter and Cancel = Esc.
3. Apply normally has an ampersand in Windows. Why not here in Messenger Plus!?
4. Default and Backup buttons? Can't find them! Where?
2) Don't fully understand your questions there, what OK and Cancel buttons? There are many... Besides, like you explained yourself, ampersand are used by disabled people for example (if that answers this question)
3) Same reason as question 1
4) Nah... error from my part, they are links, but the keys are called "xxxButton"...
quote:Hu? Dunno... Why? What do you mean? Greek is one of the languages that has the least "errors"...
Originally posted by Mike2
So does anyone know what happened with the greek translation? Its not that i care because i dont use the greek translation... But i want to know if our greek translators read this...
(PS: this thread isn't meant to talk about such things, so please don't )
RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-21-2004 at 07:34 PM
quote:1. Of course I can't use ampersands on the same letters elsewhere. But as a translator it is my job to check these things.
Originally posted by CookieRevised
quote:1) Because those button are used in every window of the preferences. And thus if you used ampersands there, you can't use them anymore in any other possible subwindow of the preferences
Originally posted by Leif
The reason for the ampersands is to make it easier for e.g. disabled people who are unable to use the mouse. And it also makes handling Windows much quicker for us "normal" people who prefer the keyboard to the mouse.
I have some questions...
1. Why must those buttons not have ampersands?
2. Why are there ampersands on OK and Cancel buttons elsewhere? This is not normal in Windows! There is no need for that because OK = Enter and Cancel = Esc.
3. Apply normally has an ampersand in Windows. Why not here in Messenger Plus!?
4. Default and Backup buttons? Can't find them! Where?
2) Don't fully understand your questions there, what OK and Cancel buttons? There are many... Besides, like you explained yourself, ampersand are used by disabled people for example (if that answers this question)
3) Same reason as question 1
2. In Messenger Plus! there are ampersands on all OK and Cancel buttons (except for the Preferences window). There is NO NEED for ampersands on these buttons (probably that is the reason why there are no ampersands on them in Windows). No need for accelerators on these two buttons as Enter and Esc work OK here. No need to tab to those buttons either. Using tab is the only way to get to those keys with no ampersands on them (but this does NOT apply to OK and Cancel as stated earlier).
3. Same argument as # 1
Conclusion:
A. Get rid of the ampersands on all OK and Cancel buttons. No need for them and it is not normal to have them in Windows, since you can use Enter and Esc.
B. Put an ampersand on the Apply button (but make sure that you don't use the same letter elsewhere in Preferences, of course).
These simple steps will make it easier for disabled people and furthermore it will conform to normal Windows "behaviour". Two birds, one stone.
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Patchou on 05-21-2004 at 07:40 PM
Note about CurrentLanguageA. As specified in the translation guidelnes document, you have to write the name of your language, as said in your language, without any special punctuation. The only exception is when your file is distributed in Unicode and your language name cannot be written with the european alphabet. Then, you have to write the name of your language in english.
Example: for French, write Francais
for Japanese write Japanese
CurrentLanguageM must always contain the name of your language, as said in your language, with all the characters of your language
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by nus on 05-21-2004 at 07:48 PM
Thanks CookieRevised;
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Apatik on 05-21-2004 at 09:41 PM
i was happy not seeing the french file in your list lol, but it was before your edit ^^ anyway, i fixed it but i didn't received any new beta, i'm still with 3.00.91
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-21-2004 at 10:36 PM
quote:that's right. Translators have only received .91 and they won't get any other more until the release day. However beta testers have received .92
Originally posted by Apatik
but i didn't received any new beta, i'm still with 3.00.91
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-22-2004 at 05:21 AM
At some requests I rechecked some updated language files that I recieved, they pasted those "tests" that I did for this thread (which aren't realy tests, just a comparison with defaultLg.dat and the translation with Choli's Translator). But when I had a quickview with them in Messenger Plus!, I discovered that there are still translations with too long lines.
So, please check your translation for too long lines by actually browsing thru every possible menu/dialog/etc...!!!
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-24-2004 at 07:40 PM
Update (especialy for Greek language):
Please check your language for leftover chunks of the original English file!
PS: Maybe I have no right in saying this, but I'm personaly very ashamed that some translations are included in Plus!. They are simple not worth the be put in IMO. I know I also left some small mistakes into the Dutch one, but that's nothing compared to what a mess some languages realy are...
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-24-2004 at 08:01 PM
quote:I haven't tested all translations as hard as Cookie has, but if what he has been saying these days is true (and I belive on him that it is) I agree with him. Several translations aren't good enough...
Originally posted by CookieRevised
PS: Maybe I have no right in saying this, but I'm personaly very ashamed that some translations are included in Plus!. They are simple not worth the be put in IMO. I know I also left some small mistakes into the Dutch one, but that's nothing compared to what a mess some languages realy are...
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Chrono on 05-24-2004 at 08:08 PM
i agree too... 
RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by user17033 on 05-24-2004 at 10:21 PM
quote:
Originally posted by CookieRevised
They are simple not worth the be put in IMO.
hi cookie,
how do you decide what language is worth?
did you find not translated strings or do you conclude from the errors the user are posting here?
anyway, i hope you don't mean the german translation
but please let us know what we can improve if you include our translation into your statement!
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-24-2004 at 10:25 PM
Obviously, he does NOT mean the German translation. It's splendid! I only found some minor mistakes in it. The biggest one is this:
CheckPlusButton=Auf &Plus! prüfen
ProfileButton=&Profil anzeigen
Both on buttons in the same window. Not very nice!
Edit:
Just found &Weiter (on a button) and &Wortfilter exportieren
Must say that the German translation is the best I've seen so far! Apart from the Swedish one, of course!
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-24-2004 at 10:33 PM
quote:i think he bases in
Originally posted by gooofi
how do you decide what language is worth?
quote:
• Important: one mistake is human but multiple errors due to improper testing will result in the translation for a given language to be completely suspended. You have to understand that Messenger Plus! is being translated in a lot of languages and problems that can be detected easily can only mean that the translation itself suffers from a lack of work. Again, keep in mind that tens of thousands of people will use your translation and all of them will be expecting professional results.
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by user17033 on 05-24-2004 at 10:39 PM
@Leif
and i thought PlusChecker should find the double ampersands 
thanks for reporting
edit » btw: are all of you checking other languages? i'm a little bit shocked how many translators are checking the german translation 
RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-24-2004 at 10:50 PM
quote:
Originally posted by gooofi
@Leif
and i thought PlusChecker should find the double ampersands
thanks for reporting
edit » btw: are all of you checking other languages? i'm a little bit shocked how many translators are checking the german translation
Using PlusChecker I was told of four "collisions". But it missed the &P and &P!
You should be glad, not shocked!
No-one bothers about the Swedish one...
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by user17033 on 05-24-2004 at 10:56 PM
lol, be happy that i can't understand swedish... 
but i watched a swedish movie one hour ago - it was translated into german, but i didn't check the movie for missing ampersands
edit » I mailed Patchou the updated translation - thank you for your help Leif
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-25-2004 at 12:36 AM
I rechecked all the translations again and updated the list...
Note about "MsgPlus Hotkey Checker" to check for collisions with ampersands. I hate to say it, sorry Shunter, but do NOT trust the result of that program! Currently the routine for checking ampersands is very dodgy and very buggy. It will miss many ampersand and on the other hand it will give many false warnings...
read about it here: http://shoutbox.menthix.net/showthread.php?tid=25313
RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-25-2004 at 04:00 AM
quote:Could you post a copy on the forum as well? Preferably under Translations | German translation.
Originally posted by gooofi
edit » I mailed Patchou the updated translation
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by ben_b on 05-25-2004 at 05:01 AM
Korean file fixed and sent to Patchou.
RE: RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by user17033 on 05-25-2004 at 08:10 AM
quote:
Originally posted by Leif
Could you post a copy on the forum as well? Preferably under Translations | German translation.
Done
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Apatik on 05-25-2004 at 05:15 PM
quote:er.. I know and i did it intentionally, but if you want me to delete those spaces I can do it..
Français (Lang_Francais.ini)
Check out:
* Sometimes "<word><space>:" is used, sometimes just "<word>:"
RE: RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-25-2004 at 05:32 PM
quote:
Originally posted by Apatik
quote:er.. I know and i did it intentionally, but if you want me to delete those spaces I can do it..
Français (Lang_Francais.ini)
Check out:
* Sometimes "<word><space>:" is used, sometimes just "<word>:"
Ne le fais pas !
This is what I've been taught. Doesn't this rule apply any longer?
"In French, a space is required both before and after all two- (or more) part punctuation marks and symbols, including : ; « » ! ? % $ # etc."
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-25-2004 at 05:35 PM
quote:
Originally posted by ben_b
Korean file fixed and sent to Patchou.
but:
quote:So I take it that's intentional then?
Originally posted by CookieRevised
Double spaces detected in or at the end of:
(=<space><space> instead of <space>. Note: this may be intentional or maybe not, so this is just reminder.)
[PrefDlg.Archiving]Text3
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Apatik on 05-25-2004 at 06:08 PM
quote:
Originally posted by Leif
Ne le fais pas !
This is what I've been taught. Doesn't this rule apply any longer?
"In French, a space is required both before and after all two- (or more) part punctuation marks and symbols, including : ; « » ! ? % $ # etc."
I put a space before the ":" almost everytime (i know that rule
), but not after words such "Note:" or "Warning:" because i thought it was nicer without spaces
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by ZrednaZ on 05-25-2004 at 06:58 PM
quote:Hmm...!
Originally posted by CookieRevised
Dansk (Lang_Danish.ini)
Faulty use of the ampersand "&":
In [Dialog.Preferences]ApplyButton (the Preferences window), Patchou asked NOT to put '&'-shortcuts on buttons. (see DefaultLg.dat)
Very minor thing:
Almost all lines in the translation ends with a space. Although this is not a real fault, it isn't needed...
I was told that it was alright to use an ampersand on the apply button.
Besides, when I submitted my file to Patchou I included this:
"...And in regards to [Dialog.Preferences], I've left things as they were. E.g.
no ampersands on OK and Cancel, only Apply. I've been told that it's alright
to have an ampersand on Apply. If you disagree, feel free to remove it (or
notify me about it) before the final release."
This means that Patchou must have been OK with it since he accepted the file and didn't change a thing.
In regards to the space af each line thing... I'll be glad to remove 'em if someone tells me how. But isn't it a bit late for that? I mean the program's been released already.
//Zred
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-25-2004 at 07:10 PM
about puting a space or not before ":" : well, it really doesn't matter very much... what is really important is that the whole transaltion keeps the same look. if you decide to put a space always except for one word sentences, that's right. The important thing is keep some guidelines with all the translation. It has to be coherent (or how you write it)
quote:
Originally posted by ZrednaZ
But isn't it a bit late for that? I mean the program's been released already.
TRANSLATORS: Patchou is going to release a new version of Plus! (3.01) soon, so I'd suggest you to correct all mistakes of your translations. I think he'll accept the changes.
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-25-2004 at 07:45 PM
quote:As far as I know Patchou doesn't change anything in the translations, even if there are errors in it.
Originally posted by ZrednaZ
I was told that it was alright to use an ampersand on the apply button. Besides, when I submitted my file to Patchou I included this:
"...And in regards to [Dialog.Preferences], I've left things as they were. E.g. no ampersands on OK and Cancel, only Apply. I've been told that it's alright to have an ampersand on Apply. If you disagree, feel free to remove it (or notify me about it) before the final release."
This means that Patchou must have been OK with it since he accepted the file and didn't change a thing.
Anyways, I once asked this also to Patchou (for the translation of 2.xx), back then he told me to follow the guidelines/comments in the INI file. So I did. I realy like a clear decission on this from Patchou. It's either allowed, or it isn't (If it isn't, I don't argue with that, it's Patchou's program, not mine!!!!). But saying: "itsn't allowed, but if you feel like it then do it" isn't exactly a clear rule if you ask me.....
But other then that, there are only a few translations which brake the rule asked in the INI ("No ampersand on buttons in this section"). This means that all the others, do follow the rule, regardless of how it might be in Windows or etc... etc... .....
quote:With notepad?
Originally posted by ZrednaZ
In regards to the space af each line thing... I'll be glad to remove 'em if someone tells me how.
Blah... I know it will take too long... Well, here is a trick, open up your translation in Word and replace "<space>^p" with "^p"
(note "^p" is the code for "new paragraph in Word) If you aren't certain on how to do this exactly, I'm glad to do it for you if you like
send me a PM)...
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by user17033 on 05-25-2004 at 07:46 PM
quote:
Originally posted by Choli
TRANSLATORS: Patchou is going to release a new version of Plus! (3.01) soon, so I'd suggest you to correct all mistakes of your translations. I think he'll accept the changes.
thank you for the information - file sent to patchou
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by CookieRevised on 05-25-2004 at 08:21 PM
Urgh... I realy need to stop doing this 
... I found a mistake in English translation file. This means that many translations are proberly suffering from this.
Note: this is a very minor thing!
Original:
[Dialog.ContactSelector]
PersoStatNoContactMsg=..........will be sent.\n(if you don't, this option serves no purpose really :).
Comments:
Patchou started the sentence with "(" and ended with ".". But ":)" is meant as a smiley (I assume). So the punctuation is wrong I think. It should either be:
(if you don't, this option serves no purpose really :))
or
If you don't, this option serves no purpose really :).
or (thanks Leif)
If you don't, this option serves no purpose really. :)
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by user17033 on 05-25-2004 at 08:28 PM
@CookieRevised
not wrong in my translation
* user17033 is a striver
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Leif on 05-25-2004 at 08:30 PM
or
If you don't, this option serves no purpose really.
RE: ALL TRANSLATORS READ THIS ASAP (faults in current translations for msgplus 3) by Choli on 05-25-2004 at 08:35 PM
quote:strictly speaking you're right, but people (as good example s patchou himself) use to write "(bla bla bla :)" meaning "(bla bla bla :))" because the ")" is for both finish the "( and complet the smilie
Originally posted by CookieRevised
Patchou started the sentence with "(" and ended with ".". But "" is meant as a smiley (I assume). So the punctuation is wrong. It should either be:
quote:also, the "i" of the "if" should be upper cased.
will be sent.\n(if you don't,
I've just checked the spanish translation: lol, look:
Debe seleccionar al menos un contacto al que enviar el mensaje.\n(Si no, esta opción sirve de poco :P ).
we didn't do that on pourpose
