 Joined: 20/03/2011(UTC) Posts: 1,660 Location: Paris, France
|
OK Tom , I’ll take a crack at it … While I know absolutely nothing about the CS2, I do know about putting texts to form … I also count on your known perseverance to report these bugs to Märklin, this foremost, concerning all their manuals in general, is making my clock tick atm … ! So here’s my two cents worth : Originally Posted by: H0  Here's one dialogue to get started0. (Dialog #1)
How about this text:
"Not a valid locomotive address.
The address range for this protocol is 1 through 255."
Or is "Invalid locomotive address." better? <-- Better
Maybe a native English speaker can make a better suggestion.
Here's the original dialogue from CS2 3.5.6: --- Originally Posted by: H0 Now here comes Dialogue #2:
There should be no fullstops after "Delay" because it's no abbreviation. <-- Agreed, “full stops” are called “periods” … these are accurately used for abbreviations, such as “Max.” and “Min.” speeds …
I didn't spot other errors (but maybe a native speaker will).
--- Originally Posted by: H0 Here comes Dialogue #3:
Funny thing about this dialogue: there are two keys each for colon and semi-colon.
There's a backtick ("`") but the forward version ("´") is missing - is this a problem? <-- Yep, see qwerty below …
Are the symbols that are missing and which a native speaker would need? <-- If you look at a “normal” qwerty keyboard, the colon and semi-colon are correct, on the same key after L ... but the comma and dot (or period) after M are wrong … should include “<” and “>”, yep, also, “Shift” key took a hike before Z to the left, and “?” became a “2” after dot to the right, and Capslock went underground … , how about just: “Märklin, please check qwerty layout” … ^^ ?: http://education.davidsp...9/9b/Keyboard_qwerty.jpg--- Originally Posted by: H0 Here comes Dialogue #4: First, I would write: “These are not standard CVs; you are in the mfx Configuration Space” … instead of “These are not normal CVs; this is the Mfx Configuration Space”. It's probably the only time where they write "Mfx" with an upper case letter. <-- Don’t know this protocol, but consistency is paramount for best comprehension in any prompt text … if “mfx” everywhere else, then it’s no good here …I would write "CVs" without apostrophe (but I know that "CV's" is acceptable usage). Which way is better in your opinion? <-- Either / or really, just makes sense that if the CS2 screen is short on space “CVs” is fine, it’s netspeak even … ^^Nice warning about reading the decoder manual - it's a pity that Märklin locos do not include useful decoder manuals.   --- Originally Posted by: H0 Now for Dialogue #5:
The word "Information" does not fit ("Info" could be used instead) <-- Agreed
and "Motor/Licht" was not translated ("Motor/Lights" will probably do). <-- Agreed
Is "Direction Inversion" OK? Or maybe "Reversion of Direction"? "Reversion of Directions"? <-- I would write: “Reverse direction”
--- Originally Posted by: H0 Here comes Dialogue #6:
"Addresss" is a simple typo. <-- Yep
And some more German terms here.
- Folge aus : Output ?
- ¾ adr: ¾ Address? No idea here…
- Halb stufen: Half increment
- erlaubt: Allowed
- MM2 aktive Funktionen : Active functions
--- Originally Posted by: H0 Dialogue #7:
Only two entries - and nothing was translated. <-- Not much to say here …
"Speicher" probably should be "Memory".
"ABV" should be "ABD" (at least they use ABD on the function mapping screen).
"Geschw." => "Speed".
"Richtung" => "Direction".
"Funktion" is left as an exercise to the reader ... (Function ?) --- Originally Posted by: H0 Dialogue #8:
Right below "Duration Function" they introduced "memory function". Why no upper-case letters here? <-- Wrong if isn’t consistent with rest of prompts … !
The abbreviations "Switc...Range" and "Runni...ounds" look a bit odd. <-- if their limit is 13 characters, then “Switch Range” and “Running Sound” should be OK …
--- Originally Posted by: H0 Dialogue #9: How about using "shall" and "would" (instead of "should" and "will")? <-- “Shall” is closely associated with the Bible, and therefore kind of harsh for model trains  , so I would suggest this wording in “contemporary” netspeak: "Reset locomotive to factory defaults? The locomotive will register itself again automatically." (The word “then” is not necessary … ^^)Maybe native speakers can make a much better suggestion. --- Originally Posted by: H0 Dialogue #10:
My proposal for this message:
"The version information could not be read from the decoder.
Try again?" <-- No idea here, but sounds good …
--- Originally Posted by: H0 Dialogue #11:
Two typos in the title. <-- Yep …
--- Originally Posted by: H0 Dialogue #12:
Assuming that "Decoder type" is correct then it should be "Coding switch". <-- Again, consistency in the text is paramount, so for prompt titles I’d put caps everywhere: “Decoder Type”, “Coding Switch”, etc …
Should "Accessory state" be written in two words? <-- Yep, “Accessory State” even, with caps … --- Originally Posted by: H0 Dialogue #13:
Title: "Configure New" or "Configure New Locomotive". <-- “Configure New Loco” (OK, if character space is a problem …)
"New locomotive" should be lower case IMHO. <-- Caps for prompt titles IMHO, so “New Loco – From Database”
"manual" should be "manually". <-- Dito: “New Loco – Manual Config”
"M.U. Set" should be "M. U. set" IMHO. <-- Not an issue IMHO
"Manualy" should be "Manually" (typo, yep) and "mfx-Loco" should be "mfx locomotive".<-- Not an issue IMHO
--- Originally Posted by: H0 Dialogue #14:
I think it should be "stick", "status" and "device" (all lower case) and "Device ID" instead of "Device-ID".
Do the native English speakers agree? <-- Nope, not an issue, on the contrary caps are better for prompts IMHO … --- Originally Posted by: H0 Dialogue #15:
Text not properly right aligned. <-- I’d say not properly left aligned, like all other interface windows ... again, consistency first !
And again too many upper case letters IMHO. <-- Again, caps are good for prompt titles IMHO … ^^
Hope that helps Tom ^^, French texts next … Y  Hmm, looks like that arrow motif before each comment dun work so well here : <-- |
|
 3 users liked this useful post by Yumgui
|
|
