Converting XML to Spreadsheet - Problem with Accented Characters

I have a program that uses an external program to gathers user account information from Active Directory. The external program is .Net, and I execute it from my Java app, which then collects the XML output and saves it in a String variable. So far so good.
Next it parses the XML and retrieves the values for each field for each user 'record' and stores these values in a String member inside of a class I created called "User".
At the end of the process, the User class data is written to a file in XML format. Still, so far so good. However, using a text editor, any user names that have accented characters in them have an extra space character after the accented character. E.g. accented "e" becomes "e ". At least that is how it appears in the Textpad editor app that I use.
Next I have a class called "XMLToExcel", that creates a spreadsheet using Apache's POI library, reads in the XML records , and writes the values for each field into a cell. Here the name with an accented character gives the message "[Fatal Error] <file name>:2617:23: Invalid byte 1 of 1-byte UTF-8 sequence."
I'm not sure what I can to do fix this, or even where to fix it. I wouldn't mind losing the accented characted and replacing it with an un-accented one.
Any ideas? I can provide code snippets if that would help.
-John Gooch

The text looks the same in Notepad and Textpad. However, I manually added the "encoding" tag with the value of "ISO-8859-1", and the converter no longer complains about invalid characters.
I added the encoding tag to my application's output file, so the converter should not complain about it on the next run. Unfortunately, the names have been fixed in Active Directory ( the special character was there by mistake ), so I cannot do a live test to be sure that it is fix.
Thanks for the help, Duke points incoming!

Similar Messages

WE + CE cause problem with accented characters

While creating a CFF font which contains the WE as well as the CE character set, it causes problems with most of Adobe programs (Photoshop 7, Illustrator 10, Photoshop Elements 2.0) under Mac OS X. Problem: the accented characters get replaced by Helvetica (Photoshop) or Myriad (Illustrator). Only InDesign treats it right.
I tested under Mac OS X 10.2 as well as 10.3; no difference. I tested on 'old machines', but fresh machines as well (machines which didn't have the fonts installed before); no difference. All the same problem.
Deleting the CE characters solves the problem, but yeah, I want to create a CFF font which contains both character sets.
Generating the font in FontLab or FDK doesn't make any difference.
So, what's the solution? Sounds like a mystery.
Bas

Two comments:
OpenType/CFF fonts should work to some degree on versions of Mac OS from 8.x on. "Some degree" means that pre-Mac OSX, you need ATM for them to work, and you only get the Roman char set. On Mac OSX, Unicode savvy apps will give you access to the entire charset, but at the moment only Adobe apps support any OpenType features.
About your problem with CE charset: this is a known problem, and is still a mystery. Adam Twardoch has reported the same problem and has supplied some test fonts. I have spent over a day looking over the fonts, and looking into old code, and can't find any problem in the font data. Investigating further is likely to be a several day effort, and will happen, but not soon.

File XML Content Conversion: Problem with special characters

Hello,
in a file sender cc content conversion is used to transform a flat structure to XML. What we experiencecd is that the message mapping failed due to a character that was not allowed in XML:
I was assuming that the file content conversion just creates XML messages with allowed characters. Is there any way to configure content conversion to remove control characters which are not allowed in XML? Unfortunately the sender system cannot be modified.
Thank you.

Hi Florian,
Please use this UDF to remove special characters which prevent XML messages to form properly.
public static String removeSpecialChar(String s)
 try
 s=s.replaceAll("&","& amp ;");
 s=s.replaceAll("<" , " & lt ;");
 s=s.replaceAll(">", "& gt ;");
 s=s.replaceAll("'", "& apos ;");
 s=s.replaceAll("\"", "& quot ;");
 catch(Exception e)
 e.printStackTrace();
 return s;
Please remove spaces between characters within double quotes. I have added them because otherwise you can't see this code properly. Please check this below link , please replace the characters with proper values as the display is causing a problem here
http://support.microsoft.com/kb/316063
regards
Anupam
Edited by: anupamsap on Jul 7, 2011 4:22 PM
Edited by: anupamsap on Jul 7, 2011 4:23 PM

Problems with Accented Characters after migrating to UTF8

Hi,
I am puzzled about the following problem.
We have recently changed the database character set from US7ASCII to UTF8 for the internationalization
purpose. We ran the Character set scanner utility and it did report that some data may pose problems.
We followed the the below mentioned process to convert into UTF8 -
1) alter database character set utf8
2) alter database national character set utf8.
Now we find some problem while working with the old data in our application which is java based.
We are getting the following error "java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv".
We further analyzed our data and found some interesting things :
e.g.
DB - UTF8.
NL_LANG also set to UTF8.
Select name from t1 where name like 'Gen%';
NAME
Genhve
But when we find out the length of the same data it show like this
NAME          LENGTH(NAME)          VSIZE(NAME)
Genhve 4 6
My question is why is it showing length as 4 only and when we try to use a substr function
its extracting like the following :-
select name,substr(name,4,1) from t1 where name like 'Gen%';
NAME               SUB
Genhve          hve
We have execute the above queries on US7ASCII DB and it is working fine, length it shows 6
and using SUBSTR it extracts just 'h' as well.
I also used dump function on the UTF8 Db for the above query,,this is the result :-
select name,length(name),vsize(name),dump(name) from t1 where name like 'Gen%';
NAME          LENGTH(NAME)          VSIZE(NAME)               DUMP(NAME)
Genhve 4 6               Typ=1 Len=6: 71,101,110,232,118,101
I checked a lot with the data and it seems 'h' (accented e) is posing the problem.
I want to know where is the problem and how to overcome this.
Regards
Siba

We ran the Character set scanner utility and it did report that some data may pose problems. Did you check out the documentation with the scanner ? It explains why and how to deal with problem data.
The problems are :-
1. You had invalid data inside your original US7ASCII database . h is not a valid 7 bit ASCII character. All the invalid US7ASCII characters, ( ie. all those that will be lost after doing ALTER DATABASE CHARACTER SET ) would have been flagged by the scanner.
2. All non 7 bit ASCII characters need to be converted to their UTF8 counterpart values, and typically these characters will have size expansions too. for example ,from 1 byte to 2 bytes.
3. ALTER DATABASE CHARACTER SET UTF8 changes the character set tag in the database header only. No data conversions are performed to your existing data .
Hi,
I am puzzled about the following problem.
We have recently changed the database character set from US7ASCII to UTF8 for the internationalization
purpose. We ran the Character set scanner utility and it did report that some data may pose problems.
We followed the the below mentioned process to convert into UTF8 -
1) alter database character set utf8
2) alter database national character set utf8.
Now we find some problem while working with the old data in our application which is java based.
We are getting the following error "java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv".
We further analyzed our data and found some interesting things :
e.g.
DB - UTF8.
NL_LANG also set to UTF8.
Select name from t1 where name like 'Gen%';
NAME
Genhve
But when we find out the length of the same data it show like this
NAME          LENGTH(NAME)          VSIZE(NAME)
Genhve 4 6
My question is why is it showing length as 4 only and when we try to use a substr function
its extracting like the following :-
select name,substr(name,4,1) from t1 where name like 'Gen%';
NAME               SUB
Genhve          hve
We have execute the above queries on US7ASCII DB and it is working fine, length it shows 6
and using SUBSTR it extracts just 'h' as well.
I also used dump function on the UTF8 Db for the above query,,this is the result :-
select name,length(name),vsize(name),dump(name) from t1 where name like 'Gen%';
NAME          LENGTH(NAME)          VSIZE(NAME)               DUMP(NAME)
Genhve 4 6               Typ=1 Len=6: 71,101,110,232,118,101
I checked a lot with the data and it seems 'h' (accented e) is posing the problem.
I want to know where is the problem and how to overcome this.
Regards
Siba

XML to PCL: Problem with special characters, entity referenceses, etc.

I (an XML beginner) am trying to produce PCL (escape sequences, you know) documents from XML using the PL/SQL parser and I'm having the following problems:
1. I need the escape character either in the XSL file, or in the XML, but this results in the error:
Error occurred while parsing: Invalid char in text.
2. I also need the character &. I tried to use the entity reference for & but the result was that it's converted to ampersand-#-38; (without the hyphens, of course) in the parsed file.
3. I have to use characters from the German alphabet (umlauts) but it seems that I'm not the only one who doesn't like them! I tried changing the encoding (ISO-8859-1 or -2) in my XSL file but the error is always:
Error occurred while parsing: 6-byte UTF8 encoding not supported.
How can I get all these characters in the result file?
Thanks for any info on the subject!

I am having this same trouble. I want to have an XML document that has ISO-8859-1 encoding that contains an (ampersand)amp; character entity. When I apply XSL to this, I want the (ampersand)amp; entity to remain intact. Instead it is converted to (ampersand)#38; Please let me know if you find an answer to this problem. [email protected]
<BLOCKQUOTE>quote:<HR>Originally posted by Penn ([email protected]):
I (an XML beginner) am trying to produce PCL (escape sequences, you know) documents from XML using the PL/SQL parser and I'm having the following problems:
1. I need the escape character either in the XSL file, or in the XML, but this results in the error:
Error occurred while parsing: Invalid char in text.
2. I also need the character &. I tried to use the entity reference for & but the result was that it's converted to ampersand-#-38; (without the hyphens, of course) in the parsed file.
3. I have to use characters from the German alphabet (umlauts) but it seems that I'm not the only one who doesn't like them! I tried changing the encoding (ISO-8859-1 or -2) in my XSL file but the error is always:
Error occurred while parsing: 6-byte UTF8 encoding not supported.
How can I get all these characters in the result file?
Thanks for any info on the subject!<HR></BLOCKQUOTE>
null

Problem with base64 encoding an xml file with accented characters

Oracle 10.2.0.1.0 Enterprise Edition running under windows 2003 server
DB Characterset UTF-8
I have a routine which takes an xml file and base64 encodes it, and the base64encoded text is stored in a clob column of a table.
The xml file is stored in UTF-8 format.
The routine works correctly, except when there are accented characters.
I am using dbms_lob.loadclobfrom file to load the file.
DBMS_LOB.OPEN(src_clob, DBMS_LOB.LOB_READONLY);
 DBMS_LOB.LoadCLOBFromFile(
 DEST_LOB => dest_clob
 , SRC_BFILE => src_clob
 , AMOUNT => DBMS_LOB.GETLENGTH(src_clob)
 , DEST_OFFSET => dst_offset
 , SRC_OFFSET => src_offset
 , BFILE_CSID =>dbms_lob.default_csid
 , LANG_CONTEXT => lang_ctx
 , WARNING => warning
 DBMS_LOB.CLOSE(src_clob);base 64 encoded xml with accented character -- incorrect
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxncDpBcHBs
aWNhdGlvblByb2ZpbGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
L1hNTFNjaGVtYS1pbnN0YW5jZSINCiAgICB4c2k6c2NoZW1hTG9jYXRpb249Imh0
dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2Zp
bGVzLzEuMS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9z
eXN0ZW1zLXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAu
QXBwbGljYXRpb25Qcm9maWxlLnhzZCINCiAgICB4bWxuczpncD0iaHR0cDovL25h
bWVzcGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4x
LjAiDQogICAgVW5pcXVlSUQ9Ik1FIiBQcm9maWxlVmVyc2lvbj0iMS4xLjAiIEVy
cmF0YVZlcnNpb249IjAiPg0KICAgIDxncDpEZXNjcmlwdGlvbj5Gb3J1bSBUZXN0
PC9ncDpEZXNjcmlwdGlvbj4NCiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iw6Fj
Y2VudCIgRXh0ZXJuYWw9InRydWUiIFR5cGU9IkJ5dGVTdHJpbmciIEVuY29kaW5n
PSJIRVgiIEZpeGVkTGVuZ3RoPSJmYWxzZSIgTGVuZ3RoPSIxNiIgUmVhZFdyaXRl
PSJ0cnVlIiBVcGRhdGU9InRydWUiIE9wdGlvbmFsPSJ0cnVlIiAvPiAgICANCjwv
Z3A6QXBwbGljYXRpb25Qcm9maWxlPg0Kbase 64 encoded xml without accented character -- correct
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxncDpBcHBs
aWNhdGlvblByb2ZpbGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
L1hNTFNjaGVtYS1pbnN0YW5jZSINCiAgICB4c2k6c2NoZW1hTG9jYXRpb249Imh0
dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2Zp
bGVzLzEuMS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9z
eXN0ZW1zLXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAu
QXBwbGljYXRpb25Qcm9maWxlLnhzZCINCiAgICB4bWxuczpncD0iaHR0cDovL25h
bWVzcGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4x
LjAiDQogICAgVW5pcXVlSUQ9Ik1FIiBQcm9maWxlVmVyc2lvbj0iMS4xLjAiIEVy
cmF0YVZlcnNpb249IjAiPg0KICAgIDxncDpEZXNjcmlwdGlvbj5Gb3J1bSBUZXN0
PC9ncDpEZXNjcmlwdGlvbj4NCiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iYWNj
ZW50IiBFeHRlcm5hbD0idHJ1ZSIgVHlwZT0iQnl0ZVN0cmluZyIgRW5jb2Rpbmc9
IkhFWCIgRml4ZWRMZW5ndGg9ImZhbHNlIiBMZW5ndGg9IjE2IiBSZWFkV3JpdGU9
InRydWUiIFVwZGF0ZT0idHJ1ZSIgT3B0aW9uYWw9InRydWUiIC8+ICAgIA0KPC9n
cDpBcHBsaWNhdGlvblByb2ZpbGU+DQo=the xml file in use is
<?xml version="1.0" encoding="UTF-8"?>
<gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
 xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
 UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
 <gp:Description>Forum Test</gp:Description>
 <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />
</gp:ApplicationProfile>The file is being loaded from a windows xp professional 32 bit system.
If I just convert the xml text of the file using
select utl_raw.cast_to_varchar2(
utl_encode.base64_encode(
utl_raw.cast_to_raw(
'<?xml version="1.0" encoding="UTF-8"?>
<gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
 xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
 UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
 <gp:Description>Forum Test</gp:Description>
 <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />
</gp:applicationprofile>'
))) from dual;I get the following
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPGdwOkFwcGxp
Y2F0aW9uUHJvZmlsZSB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEv
WE1MU2NoZW1hLWluc3RhbmNlIgogICAgeHNpOnNjaGVtYUxvY2F0aW9uPSJodHRw
Oi8vbmFtZXNwYWNlcy5nbG9iYWxwbGF0Zm9ybS5vcmcvc3lzdGVtcy1wcm9maWxl
cy8xLjEuMCBodHRwOi8vbmFtZXNwYWNlcy5nbG9iYWxwbGF0Zm9ybS5vcmcvc3lz
dGVtcy1wcm9maWxlcy8xLjEuMC9HUC5zeXN0ZW1zLnByb2ZpbGVzLjEuMS4wLkFw
cGxpY2F0aW9uUHJvZmlsZS54c2QiCiAgICB4bWxuczpncD0iaHR0cDovL25hbWVz
cGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4xLjAi
CiAgICBVbmlxdWVJRD0iTUUiIFByb2ZpbGVWZXJzaW9uPSIxLjEuMCIgRXJyYXRh
VmVyc2lvbj0iMCI+CiAgICA8Z3A6RGVzY3JpcHRpb24+Rm9ydW0gVGVzdDwvZ3A6
RGVzY3JpcHRpb24+CiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iw6FjY2VudCIg
RXh0ZXJuYWw9InRydWUiIFR5cGU9IkJ5dGVTdHJpbmciIEVuY29kaW5nPSJIRVgi
IEZpeGVkTGVuZ3RoPSJmYWxzZSIgTGVuZ3RoPSIxNiIgUmVhZFdyaXRlPSJ0cnVl
IiBVcGRhdGU9InRydWUiIE9wdGlvbmFsPSJ0cnVlIiAvPiAgICAKPC9ncDphcHBs
aWNhdGlvbnByb2ZpbGU+Edited by: Keith Jamieson on Jul 13, 2012 9:59 AM
added code tag for last base64 encoded object

Not sure if utl_i18n is already there in version prior to 11.2.0.2.
But on above mentioned version I can do the simplified method
SQL> SELECT utl_i18n.raw_to_char (
 utl_encode.base64_encode (
 xmltype (
 '<?xml version="1.0" encoding="UTF-8"?>
<gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
 xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
 UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
 <gp:Description>Forum Test</gp:Description>
 <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />
</gp:ApplicationProfile>').getblobval (
 NLS_CHARSET_ID ('utf8'))),
 'utf8')
 x
FROM DUAL
X
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPGdwOkFwcGxp
Y2F0aW9uUHJvZmlsZSB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEv
WE1MU2NoZW1hLWluc3RhbmNlIiB4c2k6c2NoZW1hTG9jYXRpb249Imh0dHA6Ly9u
YW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2ZpbGVzLzEu
MS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1z
LXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAuQXBwbGlj
YXRpb25Qcm9maWxlLnhzZCIgeG1sbnM6Z3A9Imh0dHA6Ly9uYW1lc3BhY2VzLmds
b2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2ZpbGVzLzEuMS4wIiBVbmlxdWVJ
RD0iTUUiIFByb2ZpbGVWZXJzaW9uPSIxLjEuMCIgRXJyYXRhVmVyc2lvbj0iMCI+
CiAgPGdwOkRlc2NyaXB0aW9uPkZvcnVtIFRlc3Q8L2dwOkRlc2NyaXB0aW9uPgog
IDxncDpEYXRhRWxlbWVudCBOYW1lPSLDoWNjZW50IiBFeHRlcm5hbD0idHJ1ZSIg
VHlwZT0iQnl0ZVN0cmluZyIgRW5jb2Rpbmc9IkhFWCIgRml4ZWRMZW5ndGg9ImZh
bHNlIiBMZW5ndGg9IjE2IiBSZWFkV3JpdGU9InRydWUiIFVwZGF0ZT0idHJ1ZSIg
T3B0aW9uYWw9InRydWUiLz4KPC9ncDpBcHBsaWNhdGlvblByb2ZpbGU+Cg==
1 row selected.which encodes and decodes properly on my system even with accented characters.

How to load CSV with accented characters?

Hi,
I have a database instance with NLS_CHARACTERSET = 'AL32UTF'. I upload a csv file with APEX into WW_FLOW_FILES table and then parse it with dbms_lob.instr. The problem that I am facing is that if I save the CSV file in UTF8, then this works fine, if I save it in any other encoding then it's displaying 'funny' characters when I try to parse it and display the parsing result and the source data contains some accented characters, like, á, é, ő etc,
I am not sure if this is an APEX issue or I rather be turning to NLS forum. TIA.
Tamas
Edited by: Tamas Szecsy on Jan 30, 2011 6:34 PM

Did you every find a resolution to this issue on importing with accented characters?

Problems with special characters like "u00F6" "u00E4" "u00FC"

Hi,
we currently face some major problems with special characters like "ö" "ä" "ü". First I thought it is a SP02 specific problem but it still doesn't work with SP03.
When I start an import the import manager shows correct converted value. "ö"s "ä"s "ü"s are displayed correctly. But after I've done the import I look into the Data manager and I see instead of these characters charcaters like "̈". (note: the character should show a little square box - but the forum cannot desplay it)
How can I solve this problem?
Regards
Nico

Hi Nico
Just try it out the following steps, hope it solves ur issue.
To set one or more values back to their original values:
1. In the Import Manager Source Values grid, select the values that you want to set back to their original values.
2. Right-click on one of the values and choose Set to Original Value from the context menu, or choose Values > Apply Value Conversion Filter > Set to Original Value from the main menu.
3. MDME sets each value back to its original value, which appears in black in the Source Values grid.
NOTE : You can use the Set to Original Value filter only at the value-level and not at the field level.
thanks
Alexander

Problems with special characters in InputStream or XPath

Hello everyone,
I am having problems with special characters such as ", ', - and so on, everything becomes ? (questionmark). (Not with special nordic characthers (å,æ,ø) though.)
The encoding of the XML is UTF-8, and the server that holds the webservice is setting encoding to UTF-8 also, so no conflict there.
What I have done is something like this:
{code}
String url = "http://www.formula1.com/rss/news/latest.rss"; // This is not the feed I use, it is a custom XML document
InputSource is = new InputSource(url);
DocumentBuilderFactory fct = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = fct.newDocumentBuilder();
Document doc = builder.parse(is);
Element rootElement = doc.getDocumentElement();
XPathFactory factory = XPathFactory.newInstance();
XPath xPath = factory.newXPath();
out.print(xPath.evaluate("/rss/channel/title", rootElement)); // The xml is not a RSS feed, this is just an example.
{code}
Please let me know what I am doing wrong, or give me a hint of how to solve this in another way.
Best regards,
G.Hansen
Edited by: G.Hansen on Mar 24, 2009 2:39 AM

Hello, thanks for you reply. I had to rewrite your code a little, and I think that your code would not really compile, if you tried yourself :-)
I ended up with something like this:
our environment is running in 1.4 mode, so I could not use the for-each loop :-(
public String printEntities(String s) {
 char[] sArray = s.toCharArray();
 StringBuffer sb = new StringBuffer();
 for (int i = 0; i < sArray.length; i++) {
 if (sArray[i] > 256)
 sb.append("&#x" + Integer.toHexString(sArray) + ";");
 } else
 sb.append(sArray[i]);
 return sb.toString();

How to send Oracle rowid to servlet? | Problem with national characters.

There is same possibility how to send rowid to servlet?
I have now definition like this:
<af:image source="/imageservlet?Par1=#{bindings.Col1.inputValue}"/>
But If column contents national characters, servlet methods obtained changed these characters.
My idea is to use not primary key for row, but use oracle rowid. It is simply possible?
Use something like this:
<af:image source="/imageservlet?Rowid=#{bindings.Rowid}"/
Or Do you have ideas how to solve problem with national characters ?
Thanks
FiL

Hi,
Although your workaround works.
I think this is a simple encoding problem.
I simply need to make sure all parameters and pages are encoded with a char set which contains the national characters you mentioned.
This is a bit dependent on the exact technology your using, but most can be done via the web.xml:
<jsp-config>
 <jsp-property-group>
 <url-pattern>*.jsp</url-pattern>
 <page-encoding>UTF-8</page-encoding>
 </jsp-property-group>
</jsp-config> This forces all JSP pages to be encoded in UTF-8
Adding the following parameter sometimes helps as well, although I think this one is a bit dated:
You said your using a servlet so your servlet needs a similar block for its pattern
<context-param>
 <param-name>PARAMETER_ENCODING</param-name>
 <param-value>UTF-8</param-value>
</context-param>If you want to be 100% sure the encoding is set right make sure thepages contain:
<%@ page contentType="text/html;charset=utf-8"%>Or depending on your view technology the syntax can be a bit different
-Anton

Problem with national characters on windows client

Hello there,
I'am having problem with national characters on windows client.
All national data stored in NVARCHAR2 colums, applications (.net) works fine,
but in sqlplus:
select city from test_table;
- everything ok, sqlplus shows national characters
select dump(N'<national symbols>') from dual
- returns
Typ=96 Len=12: 0,191,0,191,0,191,0,191,0,191,0,191
select * from test_table where city = N'<national symbols> '
- always returns nothing
As i understand the problem in
sql query text (and national literals) convertion
to servers "WE8ISO8859P1" encoding, Is it possible
to solve the issue?
Thanks in advance
PS.
Console in right mode (chcp=1251)
sqlplus shows russian messages well
Server (oracle 9 on solaris):
select * from nls_database_parameters
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_SAVED_NCHAR_CS WE8ISO8859P1
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8ISO8859P1
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZH:TZM
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZH:TZM
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_RDBMS_VERSION 9.2.0.6.0
Client (windows server 2003, oracle client 10):
NLS_LANG = RUSSIAN_CIS.CL8MSWIN1251

N'<national symbols>', being part of an SQL statement, will be converted to the database character set (WE8ISO8859P1) before being parsed. Only if the client and the database are both 10.2 or higher, the client can encode the literal appropriately so that it survives this conversion.
In earlier versions, you can do the encoding yourself. Instead of the N'<national symbols>' literal use the UNISTR function: UNISTR('\xxxx\yyyy\zzzz'), where U+xxxx, U+yyyy, U+zzzz are Unicode code points of your national characters.
-- Sergiusz

Problem with accent in Title

Hi there,
I'am using Adobe Captivate 6 on a mac, in French.
On each slide I have a Title (area defined in my main slide).
In the Title area, I cannot type accent such ü ö, but é à are working. In other text areas, is it working.
What could I do ? Is it a bug ?
Many thanks for your Help

Yes I tried with antother fonts such as Arial Times New Roman, it is the same.
I experience this also with other placeholders not only title ones, BUT... I found a partial issue.
When I am typing the wanting caracter such as "ü" in the search filed, and then Copy/Paste in my Title Placeholder it works.
I realy think is it a bug.
Regards
tchiboo
Le 30 sept. 2012 à 13:38, Lilybiri <[email protected]> a écrit :
Re: Problem with accent in Title
created by Lilybiri in Adobe Captivate - View the full discussion
Cannot help you, just hope someone of the staff pops in. It seems a bit strange however that this issue is only with the Title placeholders... the Spanish users had similar issues all the time. Did you try to change the font?
Lilybiri
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4738287#4738287
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4738287#4738287
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4738287#4738287. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Captivate by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Urgent:BiG Problem with accents.

Hi,
I have a problem with accents in IPlanet 4.0 sp4.
I have a form in a html page and a servlet that takes the words that i
put in the form.
The problem is if i put accents in the word iplanet don' t serve the
correct caracters..
Please i need help...
Manu

Try this
http://www.dhakamobile.com/nokia-fourth-generation-dct-4/9423-nokia-n97-hard-reset-keys.html
Good Luck
If I have helped at all, a click on the White Star is always appreciated :
you can also help others by marking 'accept as solution'

Application Hudba (Music) problem with Czech characters

Hello,
I have problem with Czech characters for Music files copied into application "Hudba" all Czech letters (š,č,ť...etc.) are translated into Japonies letters (which I could not read at all). Could someone help please.
Thanks

You might to consider contacting the app developers http://talk.sonymobile.com/t5/Music/Walkman-Beta-Test/m-p/953659#U953659

Problems with special characters with XML/PDF printing

Hi,
Our setup:
Apex Listener 2.0.5
Oracle DB 11G
Weblogic
Apex 4.2.2
Various recent major browsers
We used this blog post so we could do some PDF printing with APEX Listener:
http://marcsewtz.blogspot.be/2013/04/pdf-printing-with-oracle-application.html
The problem is special characters. For example the "&" sign comes out as "%26amp;" when we export an XML.
Could anyone provide some insights of what we can do to fix this?
Regards,
Joni

This is a known bug.
https://support.oracle.com/epmos/faces/BugDisplay?_afrLoop=957905848396285&id=18282188&_afrWindowMode=0&_adf.ctrl-state=168vq5zhn3_233
The bug 18282188 has been fixed in Apex 4.2.5 version.
Upgrade the Apex version to 4.2.5 when it is available.

Converting XML to Spreadsheet - Problem with Accented Characters

Similar Messages

Maybe you are looking for