Maconomy Online Translationfile Validation

This tool validates and stamps translation files.
If you expirence issues whith this tool please reach out to Maconomy DevOps using Teams

Follow the step-by-step guide below. Please note that only a zipped
translation file is accepted in step 8.

The translation file will only be stamped if the validation does not encounter any errors


1: Select Maconomy version
Select the Maconomy version the translation file should be used with. If the service pack/patch level in question is not available, select the newest version that is closest your version.

Maconomy 2.1 = 16.0, 2.2 = 17.0, 2.3 = 19.0, 2.4 = 20.0, 2.5 = 21.0
2: Select user language
Select the target language of the translation file. For 16.0 and later versions, use the language_COUNTRY options, for previous versions use the COUNTRY options e.g. en_US or US respectively.

3: Select character set
Select the character set table used on the Maconomy server. Standard is western character set until version 15.0. For version 16.0 and above, only 'Unicode' is allowed.

4: Select encoding
Select the encoding used in the translation file. This may be a specific character set or a general encoding.

5: Select solution
If the translation file is a solution file, choose your solution. Otherwise select 'No Solution'.

6: Custom solution
If the translation file is a custom made file you can write a three letter abbreviation here. This will result in a translation file named with this abbreviation. If this is not a custom file leave the field empty.

7: Complete dictionary
Check this box if the translation file is supposed to be complete. This should not be checked in the case of solution files.

8: Choose file
Only a zip file is accepted, and only one file may be in the zip file.

9: Convert to Unix format
Check this box if the resulting translation file should be in unix textfile format. Default is PC format.

10: Do extra Quality check
Check this box to perform an extra quality assurance of the translation file. Extra QA log files will be added to the zip file.

Important! Issues detected during the QA do not influence the validation and stamping of the translation file. However, issues detected during the QA may be due to wrong or missing translation.

Some issues are corrected automatically. The corrections are made in a copy of the translation file, which has added "._new.txt" to the file name.

11: Upload file


Maconomy Online Translationfile Validation, v. 0.15.3 (05-10-2018)
Documents

Here are some document which can help you working with dictionaries / translationfiles (also available on the Localisation Centre on M-Sync):

  • Getting Started With Localization
  • Fixing Typical Errors And Warnings In Translation Files
  • Dictionary Format And Notation
  • One Page Dictionary Guide
  • SolutionDictionary tool

    • News & Updates
    2021-09-24 Validation of field references

    Validation of field references has been introduced. Strings may reference internal field names e.g. ^{JobNumber} i.e. a caret and an expression in curly brackets. These should not be translated.
    A new version of the Solution Dictionary tool respecting this can be downloaded from the link above.

    2018-10-05

    Corrected issue causing incomplete validation reports and possibly hiding errors.

    2018-08-27

    New tool for creating custom/solution dictionaries. See the System Administrator Guide for instructions.

    2016-03-01 (v. 0.15.0)

    Changed defaults for language and character set

    2015-03-05 (v. 0.15.0)

    Support for custom dictionaries for solution languages
    It is now possible to select both a custom and standard solution. Doing this will include the selected solution dictionary (which will also include the standard dictionary). This means that the custom dictionary does not need to include solution terms.
    Updates to the solution dictionaries when installing a service pack will automatically be reflected in the application
    NOTE: The Workspace Client will support this from 2.0sp9, 2.1.6 and 2.2.1

    2015-02-15 (v. 0.15.0)

    Added option for UTF-8 encoding

    2014-03-03 (v. 0.14.0)

    Added new language codes for 16.0
    The new language codes conform to the format language_COUNTRY[_DIALECT] e.g. en_GB or en_US_MCS

    2013-10-07 (v. 0.13.0)

    Support for Maconomy 2.1 (16.0)
    Note: The only character set valid for 2.1 is Unicode

    2013-02-13 (v. 0.12.0)

    Automatic translations
    Many of the new terms for the Workspace Client can be created automatically with a few prerequisites:

    • Translate the gender term: |Gender|{gender}
    • Translate a few generic, gender dependent terms:
      • |Add ^1|
      • |Create ^1|
      • |Delete ^1|
      • |Insert ^1|
      • |Move ^1 down|
      • |Move ^1 up|
      • |New ^1|
      • |Print ^1|
      • |Save ^1|
    E.g. |New ^1| |Neuer ^1|Neue ^1|Neues ^1|
    Validate the dictionary with 'Do extra Quality check' marked. The zip file will include a new _Suggested.txt file with possible translations for missing terms. Verify the suggestions, add them to the dictionary and make a new validation.
    Many but not all terms like 'Gender{Entity}' will be automatically translated. The rest of these gender entries should be translated to allow translation of more terms using the generic terms above.

    2013-02-13 (v. 0.12.0)

    Workspace Client terms added
    New gender specifications are needed. The dictionary should have a line like e.g. 

    |Gender|{gender}	|M|F|N|
    to indicate that the target language have the genders (M)asculine, (F)eminine and (N)eutral or a line like
    |Gender|{gender}	|N|
    to indicate that the target language has only one gender etc.
    New translations like
    Gender{A/P Entry}	N
    would indicate that A/P Entry is of Neutral gender.

    2012-11-27 (v. 0.11.4)

    New step: Encoding
    Encoding is the character encoding used when saving the dictionary file as opposed to the character set used on the server.
    Currently only single-byte character sets are supported.
    Encoding can be specified by selecting an encoding below or directly in the dictionary:
    ##encoding = ISO-8859-1

    2012-11-27 (v. 0.11.4)

    CPA solution added

    2008-02-26 (v. 0.11.2)

    Another check on gender related issues added. One new error message has been introduced to the log. It is:

    1. Error: Empty entry in Java gender list
    The document about fixing typical errors is updated with the new issue.

    2008-02-15 (v. 0.11.0)

    Due to some support cases we have added some extra checks on gender related issues. One new error and one new warning has been introduced to the log. They are:

    1. Warning: Gender marker missing
    2. Error: Translated as genderlist but is not a genderlist
    The document about fixing typical errors is updated with these new issues.

    Improvements
    The Missing Terms Warnings have been removed from the log file to make it easier to locate other issues.

    Also the online log has been improved with colors so it should be easier to get a quick view of any issues.