Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Transformation of korean and other languages goes wrong

Transformation of korean and other languages goes wrong

2003-01-08       - By Katz Guy

Hi all;
I have a problem and hope you can help
I am using the latest xalan and xerces
I am using xsl java extension to call the java reosurce bundle.
I have a problem when reading 'exotic languages strings' like korean and
thai. After the transformation to an html doc I get strange symbols instead
of the word I wanted.
If I don’t use transformation and print the string to the browser straight
from a servlet than everthing is fine.

Can anyone think of a reason why I have this?

If I take the properties file and run the 'native2ascii' jave tool on it
than the sxl transformation works fine. Is this a solution? (this tool
transforms a readable text to non readable one)

Thanks in advance


_______________________
Guy Katz
Comverse
guy.katz@(protected)
+972 3 7663686


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1255">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>Transformation of korean and other languages goes wrong</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">Hi all;</FONT>
<BR><FONT SIZE=2 FACE="Arial">I have a problem and hope you can help</FONT>
<BR><FONT SIZE=2 FACE="Arial">I am using the latest xalan and xerces</FONT>
<BR><FONT SIZE=2 FACE="Arial">I am using xsl java extension to call the java
reosurce bundle.</FONT>
<BR><FONT SIZE=2 FACE="Arial">I have a problem when reading 'exotic languages
strings' like korean and thai. After the transformation to an html doc I get
strange symbols instead of the word I wanted.</FONT></P>

<P><FONT SIZE=2 FACE="Arial">If I don’t use transformation and print the string
to the browser straight from a servlet than everthing is fine.</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Can anyone think of a reason why I have this?<
/FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">If I take the properties file and run the
'native2ascii' jave tool on it than the sxl transformation works fine. Is this a
solution? (this tool transforms a readable text to non readable one)</FONT></P>

<P><FONT SIZE=2 FACE="Arial">Thanks in advance</FONT>
</P>
<BR>

<P><B><FONT SIZE=2 FACE="Arial">_______________________</FONT></B>
<BR><B><FONT SIZE=2 FACE="Arial">Guy Katz</FONT></B>
<BR><B><FONT SIZE=2 FACE="Arial">Comverse</FONT></B>
<BR><B><FONT SIZE=2 FACE="Arial">guy.katz@(protected)</FONT></B>
<BR><B><FONT SIZE=2 FACE="Arial">+972 3 7663686</FONT></B>
</P>

</BODY>
</HTML>