Subject | Re: [ib-support] language selection |
---|---|
Author | Helen Borrie |
Post date | 2003-03-07T12:55:30Z |
At 04:39 AM 7/03/2003 -0800, Ray Holme wrote:
higher than ascii 126. The problems come when you try to query them - you
will get transliteration errors.
Take Arno's advice. Choose the character set that maps correctly for your
input and output requirements.
mapping of ascii codes to character images. The code-to-image mapping can
vary from charset to charset.
heLen
>Unless I missed something Dutch (like German and/orIt's true, using NONE will let you *store* any characters, including those
>French) has just a few extra characters and you can
>use the extended Ascii characters to represent them.
>Using "none" will let you do this.
higher than ascii 126. The problems come when you try to query them - you
will get transliteration errors.
Take Arno's advice. Choose the character set that maps correctly for your
input and output requirements.
>The extendedDon't mess with extended characters in a database. There is no standard
>character set however will allow things to sort
>correctly (extended Ascii values are all after "z").
>Some extended character sets will use 2-byte encoding,
>which will use double the space for all text. I
>suspect Dutch would notm but am not sure.
mapping of ascii codes to character images. The code-to-image mapping can
vary from charset to charset.
heLen