RE: [WDSCI-L] Strange characters/Unicode

["Dupuis Vincent" <vdupuis@xxxxxxxxxxxxxx>]

Hello,

Nice joke! :D 
sorry but I don't have any other idea to correct your first problem!

For the second problem, I found the following document in the help area of WDSC.
My search words were "encoding utf-8".
Here is the result (I have highlighted the most important sentence) : 

Configuring application servers for UTF-8 encoding
To use multiple language encoding support in the administrative console, you 
must configure an application server with UTF-8 encoding enabled.
Steps for this task

Create an application server or use an existing application server. 
On the Application Server page, click on the name of the server you want 
enabled for UTF-8. 
On the settings page for the selected application server, click Process 
Definition. 
On the Process Definition page, click Java Virtual Machine. 
___________________________________________________________________________________________________
On the Java Virtual Machine page, specify -Dclient.encoding.override=UTF-8 for 
Generic JVM Arguments and click OK. 
___________________________________________________________________________________________________
Click Save on the console taskbar. 
Restart the application server. 
Note that the autoRequestEncoding option does not work with UTF-8 encoding 
enabled. The default behavior for WebSphere Application Server is, first, to 
check if charset is set on content type header. If it is, then the product uses 
content type header for character encoding; if it is not, then the product uses 
character encoding set on server using the system property 
default.client.encoding. If charset is not present and the system property is 
not set, then the product uses ISO-8859-1. Enabling autoRequestEncoding on a 
Web module changes the default behavior: if charset it not present on an 
incoming request header, the product checks the Accept-Language header of the 
incoming request and does encoding using the first language found in that 
header. If there is no charset on content type header and no Accept language 
header, then the product uses character encoding set on server using the system 
property default.client.encoding. As with the default behavior, if charset is 
not present and the system property is not set, then the product uses 
ISO-8859-1.


-----Message d'origine-----
De : wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]De la part de Paul Nicolay
Envoyé : mardi 7 décembre 2004 11:16
À : wdsci-l@xxxxxxxxxxxx
Objet : Re: [WDSCI-L] Strange characters/Unicode


Hi,

No problem... my French is probably worse ;-)  Anyway, I now changed the
script combobox to 'Turkisch' (the sample it shows looks good)... but the
characters are still printed as '-???-' when doing

s = new String("-" +  "\u011F" + "\u0131" + "\u015F" + "-");
System.out.println(s);

As far as the application server is concerned, it's still Tomcat and the
JSP pages include <meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />.  The servlet itself does not do any output itself, only
fills some beans, stores them in the request/session and forwards to the
JSP page (which uses the beans to output the actual data).

Kind regards,
Paul


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On
Behalf Of Dupuis Vincent
Sent: maandag 6 december 2004 17:32
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] Strange characters/Unicode


1/ My english is so awfull...
I mean fonts by polices!

2/ No, I don't think so!
We had some trouble editing and printing some russian characters in JSP.
You should have <META http-equiv="Content-Type" content="text/html;
charset=UTF-8"> in the header of your JSP. What are the version and
release
of your WAS?


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) mailing 
list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.