#define TXT_NviewMenu_ShowGPS_GeoHack        "Open GPS location in GeoHack"
#define TXT_NviewMenu_XnViewMP               "Discover XnViewMP Project..."
#define TXT_TemplateMenu_Color_label_Number  "Colour label number"
#define TXT_Option_Has_ICC_Profile           "Has ICC profile"
#define TXT_Option_Lossless_Backup           "For lossless operation, make a backup"
#define TXT_String_Rotation_Bits_Problem     "The picture will be converted in 8 bits per component\nDo you want to continue?"
#define TXT_String_Err_Bad_Format            "Format of the file <%s> could not be determined\n\nFor display of less common format, the following option is available: \n    Options>General>[x]Display all image file types"
#define TXT_String_Open_Output_Folder_XnView  "Open output folder in XnView"
#define TXT_String_Open_Output_Folder_Windows "Open output folder in Windows"
#define TXT_String_Slideshow_Recurse_Folder   "Do you want to add this folder recursively?"
170=JPEG lossless operation will modify original file(s), and may remove some unused pixels (width and height must be multiple of 8 pixels)!\nDo you want to continue?
171=The picture will be converted in 8 bits per component\nDo you want to continue?
172=This file contains more than one page/image, so it's not possible to rotate it.
173=This file uses a nonwritable format, so it's not possible to rotate it.
- "Do you want to add this folder recursively?" -> "Do you want to add this folder and all its subfolders?"
- "Show GPS" -> "Show GPS data" / "Show GPS position" ?
- "Edit GPS" -> "Edit GPS data"
- "Show recursive" -> "Show recursively"
- "Deskew auto." -> "Automatic De-skew"
- "Show infos" -> "Show info" / "Show information"
- "... nonwritable ..." --> "non-writable"
Other suggestions? Could native speakers please check?
Don't really know what does it means? After some testing I think that this shows file size in automatic unitx (b, B, KB, MB and so on) - is it correct?
It would be clearer and more intuitive IMO.
"INI used" it's not very intuitive, what about >> "Options file location (or path)"?
Some strings of the ShellExtension can be found in XnView (xnview_xx.h or string_xx.h), already. A similar or close wording should be used.
Good questions, I'll have to look were the strings are used myself. Perhaps someone can point us in the right direction.
Skiff wrote: #define TXT_TemplateMenu_Size_Auto	"Size auto"
+1 to all your suggestions.
Both XnView and ShellExtension should use the same wording (see my previous post).
- "Rotate based on EXIF value".
- "Keep date/time for saving"
Either XnView or ShellExt should be modified.
Currently, in Options > Image View > Image View it says "Zoom step" and values are "Default", "Fixed step", and "Relative step".
I think the English should be changed to just "Default", "Fixed", and "Relative". Consequently, the narrow label "Zoom step" should be wider and the combobox with values more narrow.
What's the difference between De-Skew and De-Skew auto?
Auto is used in many other programs, so perhaps it might be used, but together with Bytes/KB/MB/GB.
The Save as TGA window will appear. Make sure you uncheck the “RLE compression” and “Original at bottom left” options. Click on the “OK” button to continue.
Adobe (TechNote #312831: [url=http://www.lochnessproductions.com/shows/you_make.html]Numbered Sequence Files in Premiere 4.x Feature Summary[/url]) wrote: NOTE: By default, Premiere 4.2 for Windows writes header information in Targa files so the image's data flows from the top of the image to the bottom. To make Targa files compatible with applications that read the image's data from the bottom upward, you can set a switch in the Premiere Initialization (Prem32.ini) file.
Muska and Lipman (Beginning OpenGL Game Programming: Chapter 6 – [url=http://www.opengl-doc.com/Muska.and.Lipman-Beginning.Ope/pg_0167.htm]Bitmaps and Images with OpenGL[/url]) wrote: Finally, the imageDesc field is a byte whose bits specify the number of attribute bits per pixel and the order in which pixel data is transferred from a file to the screen. For our purposes, we are interested in bits 4 and 5, which tell us how the image data needs to be rendered to the screen. Because we are using OpenGL and glDrawPixels(), we need to make sure the image data is stored in memory “upside-down.” Given the possible values for bits 4 and 5 in Table 6.5, this means that you need to make sure the image origin is located at the bottom left. Some image tools like to save the Targa with the origin at the top left, which means you need to flip the Targa image data vertically to get a proper rendering with glDrawPixels().
@XnTriq: Thanks for great explanation for "bottom up" - for polish it would be "render image from bottom to up" (almost literally translated).
Hmm.. I know it's a bit longer, but for me this would be the best.
"Color label number" >> "Color label - number" or "Color label (number only)"
"Rating number" >> "Rating - number" or "Rating (number only)"
Currently it's not clear it's the short version of rating. Moreover, if both options are used, it's not clear which one is rating, so perhaps, if possible symbols might be used: star for rating and another symbol - circle(?) for colour label, for example: 5* 3●... With the star symbol it would be also clearer the higher number means better rating.