1.90 English Translation / List of new strings

[helmut]

I'm afraid that lose seems to be correct, after looking through some dictionarys. Spontaniously I'd choose loose aswell, but I stand corrected.

Sometimes I am at a loss with English and would be lost without the help of you native speakers.

[helmut]

In the new Paint tool there is:

In the context menu (right mouse click), there is "Move on front" and "Move on back" for bringing objects to front or to back. I think it should say "Move to front" and "Move to back", instead.

@Pierre: Could you please post the complete list of English strings of the Paint tool (with #defines), here?

[Clo]

—> helmut

• Hi!

@Pierre: Could you please post the complete list of English strings of the Paint tool (with #defines), here?

• As an aside :
- I've reported somewhere that an English section is missing in the <Paint.lng> file,
this could be very useful for all translators.
- All small similar *.lng files I know are built in that way (when there is a single file with sections)
• With text-files, the *.h files are no longer needed to translate…

• Just my 0.02 €…

G.
Claude
Clo

[Troken]

Sometimes I am at a loss with English and would be lost without the help of you native speakers.

He he, nice one.

[helmut]

For some reason I haven't seen your suggestions, before.

- "For Copy/Move use companion file (.xmp/.thm)"
I think a clearer phrase should be found.

How about “Include companion file (.xmp/.thm) when copying/moving images”...

Sounds clear and English to me.

- "Follow orientation (switch W/H)"
"Follow" sounds wrong to me. And "Swap" instead of "switch")

... and “Swap W/H according to orientation”?

Again, simple and clear. Good!

Shouldn't it be “Multi-page files” instead of “Multi-pages files” (#define TXT_Print_Multi_Page), and “Use estimated quality if possible” instead of “Use estimate quality if possible” (#define TXT_Option_Use_Estimate_Load_Quality)?

Yes.

I also found a few minor inconsistencies in the usage of uppercase/lowercase and latin-derived spellings:

• #define TXT_Efx_Select_All ....... "Select All" » "Select all"
  #define TXT_Efx_Unselect_All ... "Unselect All" » "Unselect all"

• #define TXT_String_Infos_Dpi ... "Dpi" » "DPI"
  #define TXT_String_Print_DPI ... "Single - DPI"

• #define

Agreed.

TXT_String_Infos_Color_Model ... "Colour Model" » "Color model"
#define TXT_Color_mode ......................... "Color mode"[/list]

• #define TXT_BrowseMenu_Favorites ... "Favourites" » "Favorites"
  #define TXT_String_New_Favorite ....... "New favorite"

Partly agreed: "Favourite" and "colour" are British English and we have decided to "speak" BE, so we should all change this to "Favourite" and "colour".

Exchangeable image file format (official abbreviation Exif, not EXIF) [...]

"Exif" is a bit of a surprise for me. XnView should follow the standard so this should be changed.

I agree to remove all the above inconsistency. Any native speaker who vetoes?

[SeaMaiden]

I am a Native American English speaker.

Code: Select all

"Multi-pages files"

change to "Multi-page files"

Code: Select all

"Combine new && current values"

"&Yes"

"&No" 

Does the extra "&" need to be in the first one? Does the "&" need to be in the last two? Maybe this is a matter of coding rather than a typo.

Code: Select all

"Dpi"

change to "DPI"

Code: Select all

"%dbits, %.3lfKhz, %s"

Not sure what to make of this. Maybe insert spaces if possible, unless that would mess up the code.

Code: Select all

#define TXT_String_Tooltips_Text                  "<Filename>, <Size> bytes, <Modified>||<Format>||<Width>x<Height>, <BPP> bits" // Be carefull, don't change text between <>!!! 

The word "careful" is misspelled.

Code: Select all

"Tagged files will be used instead of selected files. \nDo you want to continue with tagged files?"

I guess the "\n" won't show up as text?

Code: Select all

"This file use a non writable format, so it's not possible to rotate it."

change to "This file uses a nonwritable format, so it's not possible to rotate it."

Code: Select all

"Every picture pair gets a computed value,\n if this value is greater than the tolerance,\n then the pair is considered as similar."

Again, I hope the "\n" will not show as text. These should be 2 sentences.

"Every picture pair gets a computed value.\n If this value is greater than the tolerance,\n then the pair is considered as similar."

Code: Select all

"Previous/next frame"

change to "Previous/Next frame"

Code: Select all

"Move on front"
"Move on back"

change to "Move to front" and "Move to back"

[Clo]

Hi !

• PM …^

KRT
Claude
Clo

[helmut]

I am a Native American English speaker.

Good to see you back in the forum, J..

There are some special characters used in the language files:
& - next character is a mnemonic (key combination with Alt key)
\n - line break
\t - separator between menu item and short cut
%s, %d - place holders for dynamic text

All your suggestions sound good and reasonable to me. Thank you!