Generating ASCX for Korean Language using XSL PT do not encode in UTF-8

Hi,

Enviornment Details :

TS 7.3

Presentation Template : XSL Template

DCR Type : XML

I am generating footer.ascx file using the footer.xml and footer.xsl via formpublisher. The footer.xml has Korean Language contents, the file get generated successfully but when I preview the index.aspx which includes the footer.ascx the all Korean characters renders as junk characters.

I have set the encoding to UTF-8 in the footer.xsl, as shown below :

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xalan" version="1.0" extension-element-prefixes="redirect"
xmlns:redirect="org.apache.xalan.xslt.extensions.Redirect" exclude-result-prefixes="xalan">

<xslutput method="xml" encoding="UTF-8" indent="yes" xalan:indent-amount="2"/>
<xsl:template match="/">
<div id="footer">
		<div id="footerNav">
			--- some logic----
                 </div>
</div>
</xsl:template>
</xsl:stylesheet>

Although if I open the file in the editor, the Korean characters seems perfectly fine, I believe it is the browser which is not able to render them properly.

One thing to note is that if I edit the footer.ascx in an notepad++ and encode to UTF-8 and save it, then the index.aspx renders the charcaters fine on the browser.

It seems like , the footer.ascx is not getting encoded to UTF-8 while XSL transformation .

Any pointers which can help !

Thanks

Find more posts tagged with

Comments

kissthedevil

@info_seek,

It might be something related to the meta tags in the head section which might be telling something different to the browser and the browser might be using that. (meta content="text/html; charset=UTF-8" http-equiv="content-type">)

Does this issue occur in all the browsers? Or is it specific to a browser?

Regards,

KTD

________________________________________________

If at first you don’t succeed, call it version 1.0

info_seek

Thanks KTD.

Yes, the issue is occuring on all browsers, the head tag of the aspx file has meta element defined as shown below :

<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <head>
  <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
  <title> some text in korean title>
  <meta name="keywords" content="some text in korean ">
  <meta name="description" content="some text in korean ">
  <meta property="og:title" content="">
  <meta property="og:type" content="">
  <meta property="og:url" content="">
  <meta property="og:image" content="">
  <meta property="og:site_name" content="">
  <meta property="og:description" content="">

-thanks

info_seek

Thanks KTD.

Yes, the issue is occuring on all browsers, the head tag of the aspx file has meta element defined as shown below :

<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <head>
  <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
  <title> some text in korean title>
  <meta name="keywords" content="some text in korean ">
  <meta name="description" content="some text in korean ">
  <meta property="og:title" content="">
  <meta property="og:type" content="">
  <meta property="og:url" content="">
  <meta property="og:image" content="">
  <meta property="og:site_name" content="">
  <meta property="og:description" content="">

-thanks

kissthedevil wrote:
@info_seek,

It might be something related to the meta tags in the head section which might be telling something different to the browser and the browser might be using that. (meta content="text/html; charset=UTF-8" http-equiv="content-type">)

Does this issue occur in all the browsers? Or is it specific to a browser?

Regards,
KTD
________________________________________________

If at first you don’t succeed, call it version 1.0

kissthedevil

@info_seek,

Did you individually try and preview the footer.ascx? Might give an idea on what exactly is happening. You can also try changing the output method to "html". This might be an issue with the processing engine. Did you try using the local NetBeans/Eclipse transformation to test the scriplet locally?

________________________________________________
If at first you don’t succeed, call it version 1.0

info_seek

kissthedevil wrote:
@info_seek,

Did you individually try and preview the footer.ascx? Might give an idea on what exactly is happening. You can also try changing the output method to "html". This might be an issue with the processing engine. Did you try using the local NetBeans/Eclipse transformation to test the scriplet locally?

________________________________________________
If at first you don’t succeed, call it version 1.0

Yes, I tried preview the footer.ascx individually and get the same junk characters, when I change the output to HTML and generates the footer.html it works for me , because at that time browser do the trick of rendering the characters properly.

I tried with individual generation using eclipse and java transformation , for html page generation it works but for aspx or ascx page - the same problem.

What I have figured out that we want the footer.ascx to generated as encoded to utf-8 with BOM, because if the BOM characters are present in the file then it is working fine ,,,,and somehow the formpublisher engine is not generating the ascx encoded to utf-8 with bom when I use the xsl as presentation template. On the other hand if I use the perl based template then it works fine for the same DCR. It generates the footer.ascx encoded in utf-8 with BOM hence it works everywhere.

I have raised the ticket to Support and they come back saying that they don't have solution to this right now, and will check with others if they have this issue with them in past.

XSLT 2.0 has the solution to it, but TS 7.3 supports xslt 1.0 only Smiley Sad

So, Now I am trying to build a custom page generation module using xsl and java so that we can integrate it with Generate functionality.....as java may help us here.

Thanks for all the pointers..

Will post once done with the solution.

-PP

On the