Dynamics NAV + ADCS + VT220 (not VT100)? Use multynational?

RedFoxUARedFoxUA Member Posts: 21
Dynamics NAV + ADCS + VT220 (and other - not VT100, because this type don't allow use no-English language)? ](*,)
How use multynational language system, for example vt-utf8 or other?
Regards,
Yuriy Golyachuk, NAV Solutions Specialist & Developer
Skype: RedFoxUA

Comments

  • MissesMagicMissesMagic Member Posts: 39
    Hello RedFoxUA,

    first a correction:
    Are you sure, that you cannot use other languages than english with VT100? What do you mean exactly?

    If you want to show table-data in output you just have to write some code to fill in fields from a ML-Text.

    Only fixed text-constants (i.e. selection-lists) you can not switch language.
    Please define your problems more detailed.
  • RedFoxUARedFoxUA Member Posts: 21
    All terminals with English code-page work EASY!!
    About your questions:
    - {that you cannot use other languages than english with VT100? What do you mean exactly?}
    Yes. When I write Russian text (character-code ACSII more than 127) in field Text table 7701 (NAV 4.0 SP1) non-English symbol - on terminals I receive only "???". I know what VT100 (1977 year) use 7-bit key for coding keyboard, but now 2006. And Microsoft don't good doing, supporting ony old standart.. But it is they decision!!
    I know what make my application for Navision for CE5.0 is not hard, but I don't want make it...

    - {If you want to show table-data in output you just have to write some code to fill in fields from a ML-Text}

    What mean "write some code to fill"? and "ML-Text"?
    What is you mean "fixed text-constants"?
    Regards,
    Yuriy Golyachuk, NAV Solutions Specialist & Developer
    Skype: RedFoxUA
  • jorgecphjorgecph Member Posts: 26
    Which version of ADCS are you using? I know of a customer running ADCS in Russian, and as long as the codepages match, it should run fine with VT100.
    _________________
    “This posting is provided "AS IS" with no warranties, and confers no rights.”
  • RedFoxUARedFoxUA Member Posts: 21
    I run VT100 with Dynamics NAV 4.0 SP1 (NAV SP2 not work with ADCS - have some problem with XML-path). English-version work very good and i can change anything (without assistance connect several type of terminals for stockman). But Russian - .. :cry:
    Also I know what for Navision 3.60 Microsoft send some changes, but it is old version.

    Are you may send me Russian contact-info?
    Regards,
    Yuriy Golyachuk, NAV Solutions Specialist & Developer
    Skype: RedFoxUA
  • cmarthalercmarthaler Member Posts: 2
    I've got the same problem. In german texts, the chars äöü are written as ? on mobile device. How can I change this?
  • MissesMagicMissesMagic Member Posts: 39
    cmarthaler wrote:
    german texts, the chars äöü are written as ? on mobile device. How can I change this?

    hello cmarthaler,
    I had the same problem in 4.00 SP1.
    There exists a version that solves this problem (ask MS to deliver it to you, I don´t know where I have it - I will look for it), but this causes a "no go anymore" in my DB, so I let it out and use like ae as most as you can!

    Greets MM
  • cmarthalercmarthaler Member Posts: 2
    Thank you for your reply. Unfortunately I can't use just ae, oe and ue because some äöü are stored in the data themselves.

    I'll check partnersource again for some kind of patch.

    Have a nice day!
  • KowaKowa Member Posts: 923
    We also have problems with displaying non-englisch characters (äöüß) with a VT100 4.0 SP3 ADCS. I can't find any patch for this on partnersource. Any suggestions welcome :)
    Kai Kowalewski
  • jorgecphjorgecph Member Posts: 26
    For SP3, you need to use version 4.0.3.24080. Also, if you are testing with HyperTerminal, you need also to change the font that you are using to a valid one for the characters you are trying. In the case of German>(äöüß), try "Courier New".

    Hope it helps.
    _________________
    “This posting is provided "AS IS" with no warranties, and confers no rights.”
  • KowaKowa Member Posts: 923
    jorgecph wrote:
    For SP3, you need to use version 4.0.3.24080. Also, if you are testing with HyperTerminal, you need also to change the font that you are using to a valid one for the characters you are trying. In the case of German>(äöüß), try "Courier New".
    Thanks for the answer, but our NAS Version is already 4.0.3.24080. If I change the font for the HyperTerminal, it does change the character, but still doesn't display the right one. With "Courier New" I get an "R" for "ä" instead of "?" which is shown when the selected font is "Terminal". When the HyperTerminal is set to "Import Data as 7-Bit Ascii" the "R", which should be an "ä" is changed into a "d". :)
    Kai Kowalewski
Sign In or Register to comment.