Hi Gurus,

I am reading the project desc from table which is having chianese char .When I am trying to print that on report it prints some garbage values....

I am using utf8.export finction with UTF8_STD_MODE .

Any help would be helpful....

Thanks In Advance


Amol N

Hi,

You might want to look at the mb.import$() (http://www.baanboard.com/programmers_manual_baanerp_help_functions_multibyte_strings_mb_import) and mb.export$() (http://www.baanboard.com/programmers_manual_baanerp_help_functions_multibyte_strings_mb_export) functions.

I hope it helps,

- George

Hi ,

Thanks for the reply ....but the function mb.export$ is now returning "?????????" in target string .

still not worked ...Let me know if i need to provide more details

Try - utf8.import() (http://www.baanboard.com/programmers_manual_baanerp_help_functions_multibyte_strings_utf8_import)

I tried utf8.import() .it also didnot worked it is returning below format
c<<\0x8be \ 0x93c<<\0x8be .......i dont know what this means...


Any clues....

Use mb.export.raw. That solved my similair problem.

Regards,

mb.export.raw didnt worked....it is returning ???????? .

Hello gurus,
I would like to understand the meaning of mb.import$ and mb.export functions.

The help (I honestly do not understand) says something like:
"This function converts a string from the external, native character set to the TSS Encoding character set. By default, the setting of the current locale determines the native character set from which the string is converted. Code features are restored. "

What is the "the external, native character set" ? What does it mean?
What is the "TSS enconding character set"?

Why a string needs to be converted?

Thanks very much,
Luca

You do remember the old days, when we where discussing things like ANSI textcoding in windows 3.11 and ASCII coded dos-files? It's all about how to store special chars like umlaut or various accented letters in texts (or strings).

Nowadays the old way of using a codepage with 256 characters may not always be the way we can walk: there are much to many special chars used in the common languages. Today we often have to use Unicode text coding instead.

Unicode works very well, but Baan used to be different and invented its own text coding method: TSS. (Maybe Unicode is younger than Baan TSS. I don't know.)

The "TSS encoding carater set" is the way LN encodes texts internally. Technically it uses its multybyte strings (mb strings) to store the characters.

The "external, native character set" is the coding standard used by the OS LN is running at.

LN will not autoconvert its TSS multibyte strings when writing mb strings into a file. You need to do this yourself by using mb.export$() to transform the mb string into the valid character set of the OS you're using.
Mb.export$() will convert the mb string into the codepage coding used by your OS. This will create a "classical" 256byte coded textfile, when written into a file. If you don't convert your Date prior to saving it into a file, the file will be coded in the TSS coding standard and no other program will now how to decode its special chars...

You can also create UTF8-Files by using utf8.export() instead of mb.export$(). There's also an uni.export() function to create UTF-16 encoded strings, but that never worked for me (it simply created an empty string on our LN 10.2.1 system; maybe I'm still missing something when using uni.export(); I'm still exploring those conversions, too).

The import-functions can be used, when reading files into LN. They will create an TSS encodes mb string (AFAIK; still did not used them as of today).

Hope this helps...

Luca,

Refer to the following PDF for more information -
Infor Enterprise Server Technical Manual
Release: Infor Enterprise Server 10.4
Publication Date: December 11, 2014
Document Code: U8172N US

Chapter 10: Multibyte Management...........................................................................121
General..................................................................................................................................................121
TSS........................................................................................................................................................121
Unicode support.....................................................................................................................................122
Legacy TSS versus UTF-T.................................................................................................................123
Legacy TSS in the old and in the new situation.................................................................................125
Explicitly mentioned unchanged things..............................................................................................126
Font selection in BW when using UTF-T/Unicode.................................................................................126
To use multibyte character sets.............................................................................................................127
To print multibyte characters..............................................................................................................127
Utilities...................................................................................................................................................128
tsscvt..................................................................................................................................................128
tssinfo.................................................................................................................................................129