Multilanguage Functionality in 2.5

Jem_Ahmet

Does anybody tried this multilanguage stuff?
I tried to change the GLOBALLANGUAGE in a function (id5) in codeunit 1 (as described in documentation), but an error
occured saying my license does not permit to use <language code>.
Is there sth specific to use, or it is a license problem?

Luc_VanDyck

In Belgium, we are using NF BE 2.01.B now, which is also multi-language enabled. In our license NSC-license file, the following granules are included:

4,903 Application Wide - Dutch (Belgian)
4,909 Application Wide - English (United States)
4,912 Application Wide - French (Belgian)

So, you can only select a language, which is included in your license.

If you want to print documents (eg. invoices) in the customers' language, you need to have granule
4,020 Application Wide - Multiple Document Lang.


[This message has been edited by Luc Van Dyck (edited 08-12-1999).]

Otto_Dreyer

Multilanguage functionality is not generally available.

As I understand there are some beta testers in Belgium.

Luc_VanDyck

Multilanguage IS available. NF BE 2.01.B is officially released.

Dennis

Multi language functionality is avaiable. In Belgium. Nowhere else. In other countries the properties are avaiable but the licence isn't.

Dennis

Otto_Dreyer

Yes, properties are here, but thats not enough.

All messages (those currently hard-coded in MESSAGE and ERROR statements) must be reimplemented as multilanguage text constants.

Erik_P._Ernst

Wasn't this available in Canada as well?
I think I heard that both Belgium and Canada was test countries.

---

Best regards,
Erik P. Ernst

Hal

I use the multi-language function here in Belgium. That's work fine ! The hard job is the upgrade between version 2.0 and 2.01 !! Lots of translations to make : we are using 3 languages instead of one and we come from a 2.0 FR version to a 2.01 UK, so all of personnal codes in french must be translate...

I've just one problem : I can't use the function LANGUAGE in my codes ! Navision doesn't recognize this function ! Could someone help me ???

John_Tegelaar

You do use the LANGUAGE statement in combination with the CurrForm, CurrReport, etc., do you?

John

Hal

Thanks John !

I test it with CurrForm and that's OK ! The Navision's documentation explains not a lot of this function ...

For other's information, I use also GLOBALLANGUAGE. That works good. By passing in a translation table for all my "fixed" texts, i can have nice forms, all in the same language.
There is allready one little problem : what must I do with all the Navision constants like "Paiement terms" to have them in another language, depends of the choice of the user ?

Best Regards,

Hal

Dennis

I'm not sure, but shouldn't you use the ML-caption property for this kind of functionality?

---

Dennis van Es
PerCom: Research & Development BV
The Netherlands

Hal

With the ML-caption property I can translate all the captions that are viewed on forms and reports. For options-fields it is also easy by the ML-property. The difficulty is, in an end-user-multilanguage system, for the contents of fields that are standardised, like "Activity sector" for a customer ...
It's more user-friendly if the list of possible activities is in the good language for the user. For this problem, all is in order with a system of translation tables ...