Page encoding / charset / special chars / NON-ASCII chars

Whenever special characters are used in our environment, the data is stored incorrect ...
® gets converted to Â®
and other special chars gets converted to other special chars ... the strange thing is that some inputText fields in some pages work just fine ..chars dont get converted and it happend in some other many pages ...not sure whats going on ..I tried to change the charset or the pageEncoding of the pages or even manually using the setPageEncoding in the reequest and in the response ..with no luck ...when I print the request params ..the values are converted, so ma not sure at what stage the string get converted and how to prevent it ...
Charset of the jsp-page is UTF-8. Need help here please.
Thanks.

You must verify that all resources are in UTF-8. There are a couple of places you have to check:
Compiler encoding
Embedded OC4J JSP Compiler options
Project settings
After that it worked for me.
Timo

Similar Messages

How Aperture encodes non-ascii chars

It looks like Aperture uses a way of encode chars as UTF that seem to be bit unusual, many application (especially web apps) expects another way of encoding Unicode chars. The end result is that non-ascii chars comes out really strange.
When I use applescript to read the IPTC info I need to do something like this before using the data:
set c_title to normalize unicode p_title without decomposition
Is there some way of telling Aperture to do this automatically when exporting photos?
(sorry about the bad use of Unicode terminology but I don't know the area very well)

I've spent quite a bit of time on this topic - I'm the author of Phoshare http://code.google.com/p/phoshare/, an open-source tool to export images and metadata from iPhoto and Aperture. Storing non-ASCII characters in image metadata is a messy business. If you want to get a taste of it, have a look at the Exiftool FAQ at http://www.sno.phy.queensu.ca/~phil/exiftool/faq.html#Q10 . A quote: "Most textual information in EXIF is stored in ASCII format, ... However *it is not uncommon for applications to write UTF‑8 or other encodings where ASCII is expected*". This leads to all sorts of problems, because the reader will have to make assumptions about the encoding used by the writer.
In the case of Aperture, I have found that it writes metadata encoded in a way consistent with what most other applications and on-line services expect. Most of the encoding problems I've debugged where caused by bad input data. E.g. the characters were encoded improperly to begin with, but in a way that they still display as expected in some places (like Aperture). Can you try erasing some of the meta data in Aperture, and retype them from scratch (e.g. not copy-paste, which would paste the same stuff right back). Also make sure that you force-updated the preview images, so that the new meta data get written into the files.

Java 5, Linux, 64-bit: Non-ASCII chars over socket

Hi,
I am having issues with reading non-ASCII chars from a socket. I send a mixed message, with the first part in ASCII and the last bit in non-ASCII. There are no issues with reading the non-ASCII characters on Windows. However, when I try running the server on Linux. The following is a message sample:
Start message<CRLF>
фвафывафвыафыв<CRLF>
The second part (which is encoded in either Windows-1250 or KOI8-R), comes out as 3F (when you look at the bytes) on Linux.
Any suggestions?
Thanks,
Max

You must be using Readers and Writers, and you need to make sure you specify the same charsets when constructing them. Don't leave this to the default, as this seems to vary across platforms and definitely has varied across releases.

Folders that having non-ascii chars are not displaying on MAC using JFileChooser

On MAC OS X 10.8.2, I have latest Java 1.7.25 installed. When I run my simple java program which allows me to browse the files and folders of my native file system using JFileChooser, It does not show the folders that having non-ascii char in there name. According this link, this bug had been reported for Java 7 update 6. It was fixed in 7 Update 10. But I am getting this issue in Java 1.7.21 and Java 1.7.25.
Sample Code-
{code}
public class Encoding {
public static void main(String[] arg) {
try {
//NOTE : Here at desktop there is a folder DKF}æßj having spacial char in its name. That is not showing in file chooser as well as while is trying to read for FILE type, it is not identify by Dir as well as File - getting File Not Found Exception
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
} catch (IllegalAccessException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (UnsupportedLookAndFeelException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (ClassNotFoundException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (InstantiationException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
JFileChooser chooser = new JFileChooser(".");
chooser.showOpenDialog(null);
{code}

Hi,
Did you try this link - osx - File.list() retrieves file names with NON-ASCII characters incorrectly on Mac OS X when using Java 7 from Oracle -…
set the LANG environment variable. It's a GUI application that I want to deploy as an Mac OS X application, and doing so, the LSEnvironment setting
<key>LSEnvironment</key> <dict> <key>LANG</key> <string>en_US.UTF-8</string> </dict>

UploadedFile and filenames with non-ascii chars

Hi
I'm using an UploadedFile object in my web app, and all works fine. However, when I try to upload a file, with a filename containing non-ascii chars (e.g. Spanish), I see that the getBytes method returns an empty byte array, the filename is not stored correctly (the non-ascii chars are lost, replaced by another representation), and that the content-type is application/octet-stream instead of image/png as supposed to be.
If I rename that same file to have only ascii chars - everything is back to normal.
How can I upload files with non-ascii chars in their name?

Hi, back! Spent a few hours experimenting and found
that everything is working great (including the creation
of international non-ASCII foldernames) when I used
utf-8 encoding in the sieve filters rules for the
the match strings and the folder names... at least
so far so good... for your ref and sorry for bothering.

FILE_DATASTORE and non-ASCII chars

I have created an interMedia Text index
with the FILE_DATASTORE option, so that
interMedia treats table entries as
filenames and indexes the corresponding
file on the servers's filesystem.
But whenever the filename contains characters
which are not part of the US7ASCII charset (like dv| _), the file is not found. But both Oracle and the operating system support these characters.
The Oracle instance uses UTF8 as internal
characterset. The client which stores
the filenames in the table uses the
WE8ISO8859P1 charset. The values in the
database table are stored and shown correctly
when viewed with Oracle or Java client
programs.
So where does the charset conversion fail ?
The names are stored correctly, they can be
read correctly by clients, but the indexer
seems to use a wrong charset to translate
the filenames stored in the database into
filenames of the operating system.
Do I have to apply some additonal configurations to my indexer ?
Greetings,
Michael Skusa
null

I bump Dr. Chucks thread for a similiar problem with non-ascii chars.
The chars show up but the sorting is a bit off.
Example: A, Å, B, ... Z
Should be: A, B, ... Z, Å, Ä, Ö
In Swedish Å (the letter Aring;) is one of the last letters and should not be placed after A despite being similiar.
Any ideas?

IPhone: sectionIndexTitlesForTableView and non-ASCII chars

You specify an array of strings for your section titles in your implementation of UITableViewDataSource method sectionIndexTitlesForTableView. However, it seems like if you have a string with non-ASCII characters, it is left blank (for example the Korean string "누리마루"). Anybody else encounter this issue?

I bump Dr. Chucks thread for a similiar problem with non-ascii chars.
The chars show up but the sorting is a bit off.
Example: A, Å, B, ... Z
Should be: A, B, ... Z, Å, Ä, Ö
In Swedish Å (the letter Aring;) is one of the last letters and should not be placed after A despite being similiar.
Any ideas?

Non-ASCII chars in applets?

hi,
Spent 4 hours to find a way to use non-ASCII chars in applets (buttons, textareas), but didn't make it.
Simply saying
TextFieldObj.setText("\uxxxx");
//or any equivalent obj. Ex. of \uxxxx: \u015F
doesn't work. I even went into Graphics.paint() example, but it too can paint only ASCII chars.
My hunch is that it is smt. about Character.Subset but i still can't figure out how to do it.
Please SOS,
Reshat.

Hi,
I just managed to get Buttons to show Greek characters, so it appears that static buttons are fine.
However, i still face the same problem for TextField's:
TextFields work fine for IE, but in NN they sometimes convert into ASCII and sometimes give ? The same in HotJava.
So there are 2 questions in my head:
1. why can't NN use the fonts used by IE to display Non-ASCII chars?
2. What is the safest font to use for Non-ASCII chars, to cover the widest possible audience.
P.S. Java solves most cross-platform-browser problems, but the font issue still seems to be dependent on a user and his/her browser. It appears Java is not font-independent in non-ASCII context. If so, it would be nice to develop a plug-in to make sure that if the user doesn't have the font, then a Java-standardized Unicode-based font is used. Otherwise, non-ASCII world is still w/o a real Java.)
Thank you for your feedback,
Reshat.

Can Java be started in a directory that contains non ascii char

I installed a product developed using Java in a folder whose name contains non-ascii chars, such as Japanese chars or german chars.
This will cause error said: unable initialise java virtual machine, error code -1
Some one said Java doesn't like being started in a directory that contains non ascii characters. There appears to be no way of passing it unicode parameters.
Is there anyone once hit the similiar issue or know the root cause of such problem?
Thanks

Yes you can use your web start application console. To enter data which is required for your application it is better idea to use java application which runs in console mode althou you may try to run console of windows and then read data from its input stream.

Does Java 5 accept non-ascii chars as identifiers?

I am surprised to find out that Java 5.0 accept non-ascii chars as identifiers.
Is it true that Java 5 really accept non-ascii chars?
Thanks.

Here is the code:
public class non��name {
private static void ��(){
    System.out.println("this is called from a function with a chinese name!");
    int ��1 = 1, ��2 = 2;
    System.out.println("��1 = " + ��1 + ", ��2=" + ��2 + ", �� = " + (��1+��2));
public static void main(String[] args) {
    ��();
}

GSSName is corrupted for non ascii chars

Hi,
I have a setup where a web application is deployed to use SPNEGO for user authentication ( using kerberos V ) and authorization.
We have several users with non english characters in the user ID and even though kerberos authentication succeeds for such users ( KDC / Active Directory is returning valid kerberos ticket which the client embeds in the SPNEGO token). Hoowever, on passing the SPNEGO token to GSS API and extracting the user name from GSS API returns incorrect user name. All non ascii characters in the user name are replaced with some junk byte sequences.
We use JGSS API (with JRE 1.4.08) for extracting the SPNEGO token and create a GSS secruity context object. Later, the GSS Name is extracted from the GSS context object.
Currently I am tesitng the SPNEGo authentication for a user with user ID 123<sp char> . The <sp char> 's unicode value is FE and UTF-8 encoded byte sequence is C3 BE. However, if I invoke 'export' method of the GSSName object and examine the returned byte sequence, instead of C3 BE, the byte sequence EF BF BD EF BF BD is present. The byte sequence for other english characters are proper.
Is this a defect in GSS-API ? Or am I not using GSS properly?
Do I need to have any special setup / configuration for using JGSS with kerberos V for users with non ascii characters in the user ID?
Please advise.
Regards,
Jayaram.
Message was edited by:
s_jayaram_s

I understand that this is an older thread.
We have spent lot of time on the internet to find out any possible workarounds or permanent solutions to enable Multi-Byte character support for username / password / SPN with Kerberos and Java . But no luck so far :(
Are there any new updates on this i18n issue ?
Thanks,
Venkatesh

Can ims5.2p1 do sieve filter searches with non-ASCII chars?

Particularly, is it possible with the
Subject header line, which is
=?xxx?Q?xxxxx?= or =?xxx?B?xxxxx?= encoded
Resolved the fileinto foldername part, but
now found that seems like ims's sieve filter
cannot do non-ASCII matches... Thanks.

Hi, back! Spent a few hours experimenting and found
that everything is working great (including the creation
of international non-ASCII foldernames) when I used
utf-8 encoding in the sieve filters rules for the
the match strings and the folder names... at least
so far so good... for your ref and sorry for bothering.

Non ascii characters are padding without reason

Hi all,
here is my issue :
I have description field in my jsp page, when user enters some non ASCII characters as shown below :
This is user had entered the input string is :
"Hello Ã?Â?Ã?Â?Ã?Â?Ã?Â Hello" (without quotes)
When he edits for the first time without change anything in the the string and save, then it became :
"Hello Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã? Hello" (without quotes)
Then again one more time, it became :
"Hello Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â?Ã?Â? Hello" (without quotes)
Like wise it is getting increased its size. I'm saving the data to Oracle 10g database from jsp.
Please suggest what to do to rectify the problem.
Thanks & regards,
Achchayya

But I didnt changed anything from server.xml except two changes
1) from : <?xml version='1.0' encoding='iso-8851-1'?>
    to : <?xml version='1.0' encoding='UTF-8'?>
2)
from : <Connector port="8888" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
to : <Connector port="8888" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443"
               URIEncoding="UTF-8"/>here is my JSP :
<%@ page pageEncoding="UTF-8" %>
<html>
<head>
<title>The servlet example </title>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body>
<h1>A simple web application</h1>
<form method="POST" action="HelloWorld">
<label for="name">Enter your name </label>
<input type="text" id="name" name="name"/><br><br>
<input type="submit" value="Submit Form"/>
<input type="reset" value="Reset Form"/>
</form>
</body>
</html>Servlet Code :
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class HelloWorld extends HttpServlet {
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
* Get the value of form parameter
     System.out.println("response char set "+response.getCharacterEncoding());
     System.out.println("request char set "+request.getCharacterEncoding());
response.setCharacterEncoding("UTF-8");
String name = request.getParameter("name");
String welcomeMessage = "Welcome "+name;
System.out.println("Name : "+name);
* Set the content type(MIME Type) of the response.
response.setContentType("text/html");
PrintWriter out = response.getWriter();
* Write the HTML to the response
out.println("<html>");
out.println("<head>");
out.println("<title> A very simple servlet example</title>");
out.println("</head>");
out.println("<body>");
out.println("<h1>"+welcomeMessage+"</h1>");
out.println("</body>");
out.println("</html>");
out.close();
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
     response.setCharacterEncoding("UTF-8");
     doPost(request, response);
} web.xml :
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4"
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<servlet>
<servlet-name>HelloWorld</servlet-name>
<servlet-class>HelloWorld</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>HelloWorld</servlet-name>
<url-pattern>/HelloWorld</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>
HelloWorld.html
</welcome-file>
</welcome-file-list>
<context-param>
     <param-name>PARAMETER_ENCODING</param-name>
     <param-value>UTF-8</param-value>
</context-param>
</web-app>please have a look at my files and suggest me BalusC.
Thanks for your patience.
regards,
Achchayya
Edited by: achayya on Oct 16, 2009 7:26 AM

File upload with non-ascii name

I'm designing a system that includes file-uploads. My problem is that any non-ascii chars in the filename are encoded strangely when saved. ä is encoded to å etc.
I use Tomcat with the -Dfile.encoding="UTF-8" in the Catalina file. I get the same result despite method; my own implementation, apache commons or Javazoom's uploadBean. All the JSP charset parameters are set.
Any ideas?

Hi amitads,
I'm sure u've used Java enough. Also, u must have learned about the \ (backslash) escape character ?
So, if u want to include a string like a single quote, u can write \' and for a double quote u can write \".
Try this ... I'm sure it will help.
Keep me posted.
Cheers !!
Sherbir.

URGENT!! Drill Down Error with Character Set non-ascii on Discoverer Viewer

Hi,
We have an error in a Drill down. It comes up when the Discoverer Viewer tries to process data that contains special character (non-ascii) in a query's filter. The same report that does not perform well with special characters, does perform well if the data dont contains special characters, so it seems to be an issue processing non-ascii chars in this Discoverer Viewer instance.
Ex. FIELD_NAME = 'Ã¶ÜÃ¦Ã¤é (This filter is contained in a query that this getting an error msg="We're sorry, the server encountered an unexpected condition" ).
It might be possible that there are some problems with the Discoverer charset ?
We will appreciate any suggestion about this respect.
Regrads,
Seba.

Sure,
This is the hole sql command that get an error in a drill down action process
SELECT NVL (sf_dw_people_skills.major_name, 'No Major'),
sf_dw_people_skills.minor_name, sf_dw_people_skills.skill_name,
sf_dw_people_skills.skill_level,
sf_dw_people_all_rel_v.supervisor_name,
sf_dw_people_all_rel_v.person_name, sf_dw_people_all_rel_v.LOCATION,
sf_dw_people_all_rel_v.supervisor_dir_name, COUNT (1)
FROM olnreport2.sf_dw_people_all_rel sf_dw_people_all_rel,
olnreport2.sf_dw_people_skills sf_dw_people_skills,
olnreport2.sf_dw_people_all_rel_v sf_dw_people_all_rel_v,
olnreport2.sf_dw_competences_rel sf_dw_competences_rel
WHERE ( (sf_dw_people_all_rel.person_id = sf_dw_people_skills.person_id
AND (sf_dw_people_all_rel_v.person_id =
sf_dw_people_skills.person_id
AND (sf_dw_competences_rel.skill_id = sf_dw_people_skills.skill_id
AND (sf_dw_people_all_rel_v.supervisor_id =
sf_dw_people_all_rel.supervisor_id
AND (sf_dw_people_all_rel_v.supervisor_name = 'Kunz, Jürgen Mr') /*When I replace the charset 'ü' by u, it´s work ok*/
AND (sf_dw_people_skills.minor_name = 'HRMS')
AND (sf_dw_people_skills.skill_name = 'HR Intelligence')
AND ( sf_dw_competences_rel.competence_type = :"competence_type"
AND sf_dw_competences_rel.competence_id IN ((:"competence_id"))
AND (sf_dw_people_all_rel.supervisor_id IN ((:"Manager")))
AND ((( :"resource_manager" <> -1
AND olnreport2.do_val_person_job_prod
('RESOURCE_MANAGER_VIEW',
sf_dw_people_skills.person_id,
sf_dw_people_skills.job_code,
sf_dw_people_skills.product_code,
:"resource_manager"
) = 'Y'
OR :"resource_manager" = -1
GROUP BY NVL (sf_dw_people_skills.major_name, 'No Major'),
sf_dw_people_skills.minor_name,
sf_dw_people_skills.skill_name,
sf_dw_people_skills.skill_level,
sf_dw_people_all_rel_v.supervisor_name,
sf_dw_people_all_rel_v.person_name,
sf_dw_people_all_rel_v.LOCATION,
sf_dw_people_all_rel_v.supervisor_dir_name;
Regards,
Seba.

Page encoding / charset / special chars / NON-ASCII chars

Similar Messages

Maybe you are looking for