German translation files for Objects in Attain?

QuongElvisQuongElvis Member Posts: 22
edited 2003-09-05 in Navision Attain
Hi Forum,

is there a txt file to translate the objects, field names and variables
into german avaiable anywhere?


Carsten

:shock:

Comments

  • eromeineromein Member Posts: 589
    downlaod section
    "Real programmers don't comment their code.
    If it was hard to write, it should be hard to understand."
  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    Have a look at the Languages Modules for Attain 3.60: http://www.mibuso.com/downloads.asp?cat ... ttain360lm
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • QuongElvisQuongElvis Member Posts: 22
    Thanks for your abswers

    that is not what iam looking for. I need a textfile to import in the object designer under extrs-translate. I want to translate the fieldnames, objectnames and variables in the cal environment so i don't have to know the english field-names.

    Carsten
  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    The names of the objects and fields in a table are ALWAYS in English (starting from Attain 3.10 I guess).
    When you import a language module, you add multi-language captions to the objects, so you can run Navision in another language.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • QuongElvisQuongElvis Member Posts: 22
    Yes the Objects are in english. But there is a Way to translate them with Navisions localization Workbench. The Application side is already in german so i don't need the language module.
    I can't imagine that there still is no translation out.
    Attain supports the translation in the object-designer under extras-translate (not language module). WIth an existing translation-file it would be possible to translate the objects and variable names in code with 2 mouseclicks. So i still hope that Navision lets the choice to the programmer if he wants to work with english variables or use the german version as in Financials before, Technically this is full supported, i only need a translated file.
    I still see no need to code with english fieldnames and variables in local german attain projects. Work can be much faster done if i can use german names than before in financials. The only missing link to get happy is that translated file, it needs to much time (much to much) to make an own translation.

    Carsten

    p.s. : i would be glad for comments of other programmers to see if i am the only one who doesn't want to use english fieldnames etc.
  • eromeineromein Member Posts: 589
    As always the French and you Germans want everything in there own language (no offence).

    I’m not quite sure what Navision’s policy is on language for Germany and France. I’ve heared that especially for these two countries the database is going to be translated again. All the other countries in the whole wide world will be working with the English code base version of Navision.

    If you want your database to be German code based, you have to contact your HQ in Germany or translate it yourselves. If you ask me, you’re better of learning English, in fact it toke me only a few months to learn most English the (Navision) terminology.
    "Real programmers don't comment their code.
    If it was hard to write, it should be hard to understand."
  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    In Belgium, we where one of the first (together with Canada) to have a multi-language Navision application available. This was introduced in Navision Financials 2.01!

    So we now are already used to have all objects available in English. And this is the way to go, because when you work together with other partners, or you have to develop a multi-country solution, it is so much easier to communicate.

    I can't imagine you want to translate everything back to a language other than English.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • KowaKowa Member Posts: 924
    edited 2003-09-05
    Hi Carsten,

    I've spent the last months translating old 2.6 Applications into 3.7 Code.
    It is hard work to switch but after some time you will get used to it.

    Since all NSC developments are analysed by Navison Headquarters and, quite often, are integrated into the next standard release, I see no chances of a survival/revival of the german field names. It makes it simpler for them to adapt these developments than in the past.

    Don't forget the advantages: If you are familiar with the english code base
    you can travel all over the world and work on any Navison Attain system, provided you find someone to translate the captions for you... :)

    Kowa
    Kai Kowalewski
  • QuongElvisQuongElvis Member Posts: 22
    small world :)

    of course you are right about the advantages.
    But i still don't see them for local german installations.
    i wOuld only need the translated textfile and the translation of the standard back to english (if needed) would even be reversible with 2 mouseclicks.

    But i see most programmers have accepted this standard so i have to accept it. :twisted:

    Carsten
  • StephenGStephenG Member Posts: 99
    Hi all

    Just a quick comment, when we say all Core/Base coding has to be in English, you must remember that it is the U.S. English.

    Even us English have to watch out for the differences between Our language and the the US version of our language ie Cheque = Check , Colour = Color...

    PS at one time in our history the national language here was French.
    Answer the question and wait for the answer.
Sign In or Register to comment.