nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Encodings and their supported languages

GOMATHY

Hi,

We have a requirement of supporting different country sites with different languages. The UTF-8 encoding does not support all languages.So we tried customizing the iwpt_encoding.ipl with different encoding standards according to the languages.The pages are with .asp extension.
But for few languages the encodings are not supported in Teamsite.So If anybody have worked with similar requirement , please suggest me on this.

Teamsite version 5.5.2

Thanks
Gomathy

Find more posts tagged with

Comments

ISCBorisB

The UTF-8 encoding does not support all languages...

UTF-8 includes even Babylonian Cuneiform encoding. If you have more recent Language in mind,
I (and probably the Unicode Consortium, too) would like to know what this Language is

nipper

First, good luck with 5.5.2, that was EOL (end of life) YEARS ago.

So unless you plan to upgrade, it is highly unlikely you will be able to get any help.

As to UTF-8 etc, I am goign through the same issue (with 6.7.1). We support the western European languages (FR, DE, ES, IT, etc) plus Japanese. We are also looking to Korean, which *should* work with UTF-8. From what I have read, some Chinese can work with UTF-8 but the full character suite requires UTF-16.

Before you do anything, you MUST upgrade, and at this late inthe game it will be tough.

Andy

topn_bottomn_problem.zip

ISCBorisB

First, good luck with 5.5.2, that was EOL (end of life) YEARS ago.

So unless you plan to upgrade, it is highly unlikely you will be able to get any help.

As to UTF-8 etc, I am goign through the same issue (with 6.7.1). We support the western European languages (FR, DE, ES, IT, etc) plus Japanese. We are also looking to Korean, which *should* work with UTF-8. From what I have read, some Chinese can work with UTF-8 but the full character suite requires UTF-16.

Before you do anything, you MUST upgrade, and at this late inthe game it will be tough.

Andy

UTF-16 is 2-bytes character encoding (thus 16) + certain 4-bytes subset of so called "surrogates".
UTF-8 is a variable-length ( 1 to 6 bytes) character encoding, it covers many orders of magnitude
more symbols than UTF-16, UTF-32 or any other Unicode flavor known to man.

Take a look at UNICODE.ORG, Chinese, Japanese and Korean for some discussion

GOMATHY

Hi,

During the preview ,I could find the languages with their characters but once i generate i am getting some junk characters with some english alphabets.And also,when i View Source for the previewed pages i get junk characters and not language's characters.For languages like Japanese,Korean,Arabic etc i can't preview the files using proper encoding set in iwpt_encoding.ipl.

Please suggest me , if something should be done when generating the page, so that i could get the language's characters instead of junk characters.

Thanks
Gomathy

ISCBorisB

Hi,

During the preview ,I could find the languages with their characters but once i generate i am getting some junk characters with some english alphabets.And also,when i View Source for the previewed pages i get junk characters and not language's characters.For languages like Japanese,Korean,Arabic etc i can't preview the files using proper encoding set in iwpt_encoding.ipl.

Please suggest me , if something should be done when generating the page, so that i could get the language's characters instead of junk characters.

Thanks
Gomathy

If you need help with it, attach (do NOT copy/paste!) generated code that gives you troubles and perhaps
screen-shot fragment showing the problem manifestation.

There can be numerous reasons for "garbage" symbols effect. Common problems are declared/real encoding
discrepancies, indiscriminate use of MS Office Copy/Paste and the like.

cesarecastro

We have a global deployment of Teamsite. We support many languages in our Teamsite forms from English to Korean (Chinese too). So far we have not encountered any issues with encoding that we have not been able to resolved. We deploy to File systems (Windows and Linux) and databases (Oracle and MS SQL). Here are a couple of things to keep in mind while you are setting up your architecture.

1. Before you do anything upgrade to a supported version of Teamsite and OpenDeploy.
2. All your encoding should be UTF-8 (declare your encoding at the very first line of a file when ever possible)
3. When a file is created make sure that it is saved as UTF-8

It is that simple. I am curious to know the languages do you have that are not supported by UTF-8.