Skip to content

Latest commit

 

History

History
69 lines (46 loc) · 3.08 KB

README.md

File metadata and controls

69 lines (46 loc) · 3.08 KB
Raw

ExifToolGui. Create or update a translation

Preparation

  • Download and install the Better Translation Manager.

    • https://bitbucket.org/anders_melander/better-translation-manager/downloads/amTranslationManagerInstall-2.0.8628.33873.exe

  • Create a new directory for translation.

    • It should contain:

    • The 32 Bits executable. (Has to do with naming, works best when it's the same name as the .Drc file)
    • ExifToolGui.Drc
    • ExifToolGui.xlat
  • Open the .xlat file in the Better Translation Manager, and start translating
    • - Regularly save.
    - When you want to test. Click on Build. That should create a translation DLL. ExifToolGui.xxx
    If the language matches your Windows language, it will automatically be selected when you start ExifToolGui.
    You can also use a command line parameter /LANG=xxx to override the default.

    Things to keep in mind when translating

  • Verify the source and target language
    • - If not correct, you can change them.

  • At the time of writing 2 languages are working
    • - EN (English) The languge that ExifToolGui was originally developed in. This is the default, it does not need a separate module.
    - NL (Dutch) I did this translation myself to make sure it works.

    When translating you have 1 source and 1 target language. The modules supplied all have source language EN. But anyone who would prefer to have NL as source language contact me.

  • Not all text's need translating
    • - I have marked a lot of text's as 'Dont Translate'. These text's normally dont show up. But even then there are about 622 text's to translate.

  • Keep track of what's remaining
    • - When the state moves from 'pending' to 'proposed' consider it done. You can use 'accepted' if you want to review all your 'proposed' text's and mark them as OK.
    - If the text is equal in the source and target language, use right-click and set it to 'accepted'.

  • Searching
    • - The searching is really powerful.

  • Text editor
    • - Special characters.
    When you see %s, %d etc. then at runtime a value is substituted. Keep these, or the program will give an error.
    When you see an & it can define a shortcut in a menu. Likely they will need changing after translation.
    Example: &Save will underline the letter S, and make that the keyboard shortcut.
    • You can type the translation directly in the grid. But I find it clearer to keep the texteditor window open. You can access it via a small button on the right of the line.


    If you want to help translating, contact me by creating an issue on GitHub for a new language, or posting to an existing issue.

    Italian: #321 Portuguese: #318 French: #316 Spanish: #299 German: #286

    Frank