XML Parsers which supports Thai Characters

Hi,
I want to know which XML Parser supports Thai characters or "MS874" encoding ?
I want the name of jar file.
Thanks
Paresh

won't utf-16 support Thai characters?

Similar Messages

Thai characters to PDF using smart forms

Hi All,
I have created a smartform which displays order details. The address contains thai characters. While viewing the preview, the characters are displayed correctly.
The OTF form of this print is converted into PDF using the function module CONVERT_OTF and sent as mail attachment.
The issue is in the PDF attachment, thai characters are converted to junk characters. Can anyone suggest how to overcome this?
FYI, for displaying thai characters, chinese font THANGSAN is used.
Thanks & regards,
Juli.

Hi,
There is no command like this. If you use device type PDFUC or SWINCF to create the spool before converting via RSTXPDFT4, then the PDF conversion will be unicode. See SAP note #999712. But you still need to upload true type fonts to support the Thai characters, this time via report RSTXPDF2UC as per note 999712 and the attached guide. The Adobe fonts don't support Thai so it is needed to embed Angsana new true type font into the PDF file to support Thai characters.
Regards,
Aidan

Does Adove FrameMaker 7.0 support Thai language?

Hello,
after creating a sample document with some Thai text, I save it as MIF 7.0 . There is a prompt saying that saving in this format will cause loss of information related to new features. Then, after reopening the file in FrameMaker instead of Thai characters i get question marks.
I'm using Adobe FrameMaker v10 , Thai Kedmanee keyboards, my text is written using font that supports Thai characters (Angsana New) .
So, ladies and gentlemen - is there anything i can do with this or FrameMaker 7.0 just does not support Thai language?
Thanks in advance,
Chris

Your Angsana New is likely a Unicode font. When you type Thai characters in it, what goes into the document is 3-byte UTF8 from the U+0E00 codepoint block. These are completely different binary values vs. the 8-bit code page 874 legacy encoding for Thai overlay fonts, and may not even have the same ordering of glyphs in the block.
You're going to need a legacy 8-bit Thai font, possibly Angsana code page 874, and you'll need to know the mapping. On Windows, you'll might even have to type them as Alt sequences, based on the {128-255 decimal?) values of the code points. Alternatively, Windows will have a keyboard mapping for code page 874.
ISO/IEC 8859-11:2001, code page 874 is apparently not the same as TIS-620, if that matters.
Now entering the Unicode parking lot.
Do not back up.
Severe text damage may result.

Xml parsers supported by JAXP1.1

I'd like to know the xml parsers and their versions supported by JAXP1.1. although crimson.jar is the default parser provided, but i want to use a different parser. I need the answers urgently,
Thanks.

Actually, your question should be the other way around. The parsers I use (besides Crimson) are Xerces (apache) and XML4J (ibm). I know these support JAXP1.1.
For more info I refer you to the Web Developers Virtual Library, which maintains a list of available XML parsers at: http://wdvl.com/Software/XML/parsers.html
Go from there to see if they support JAXP.
Good luck.

Javax.xml.parsers.DocumentBuilder to skip invalid XML characters?

Hi,
I convert XML files into flat files. In doing so I call the API DocumentBuilder.parse(File f). If the XML file f contains an invalid XML character, the API throws a SAXException.
My question is: while I know that certain invalid XML chars are not part of the data and therefore can be safely ignored in the conversion, is there a way to tell the API to skip those chars?

Nope. Compliant XML parsers are required to parse the XML as it is and not to "repair" it in any way. Your best option is not to have badly-formed XML in the first place, so if you are the one generating the XML, you should fix that process. But if you have bozo customers generating it, and you can't make them do it right, then pre-process the XML to drop the bad characters.

Problems displaying Thai characters in FTE components on Mac

I had originally posted a question here: http://forums.adobe.com/message/4027591, but was told that this is more of a flash runtime issue.
I am running into issues displaying Thai characters in Flex components that make use of the Flash Text Engine (FTE), specifically on Mac OSX 10.6.8 Snow Leopard.
Here's a blurb of my compiler font managers in flex-config.xml:
<flex-config>
        <target-player>10.2.0</target-player>
        
        <swf-version>11</swf-version>
        <compiler>
          
          <locale>
              <locale-element>en_US</locale-element>
          </locale>
          <fonts>
              
              
              <managers>
                  <manager-class>flash.fonts.JREFontManager</manager-class>
                  <manager-class>flash.fonts.BatikFontManager</manager-class>
                  <manager-class>flash.fonts.AFEFontManager</manager-class>
                  <manager-class>flash.fonts.CFFFontManager</manager-class>
              </managers>
                
            </fonts>
        </compiler>
    </flex-config>
...and another from flash-unicode-table.xml:
<language-range>
    <lang>Thai</lang>
    <range>U+0E01-0E5B</range>
</language-range>
My flex application originally had the following defined in its stylesheet:
    Application {
        fontSize: 12px;
        fontFamily: Arial;
        font-sharpness:0;
        font-anti-alias-type:advanced;
Thai characters render correctly in mx components such as TextField so far. However, FTE components such as TextLine show those crappy-looking boxes as a substitution. My initial guess was that somehow one of the compiler font managers declared in flex-config.xml was not finding the right system font to fallback to for Thai characters. So, I ensured the system font was installed by going to System Preferences > Language and Text > Edit List. Then I changed fontFamily to Arial, Ayuthaya. Still was seeing the boxes of evil.
Next I figured that perhaps the Arial font might be assigning a box for each unicode value corresponding to a Thai character. So it was effectively overriding the Ayuthaya system font. So I changed fontFamily once more to just Ayuthaya and this worked with one issue - Ayuthaya looks inherently different from Arial for non-thai characters.
Here's my question - is there a less invasive way to support Thai in FTE components such that the appearance of the text is closer to the Arial font? I would rather not embed a font because I'm constrained on SWF size.
Oh and I'm using flash player 10.3 right now.

OK, I asked the FTE team and got this reply: "Lucida Grande is CTS's fallback font for Thai. This font on OS 10.7 and 10.6 are not supporting Thai anymore. The version on 10.5 was supporting it." This means that it's our bug that we keep using Lucida Grande as fallback font even Apple dropped support Thai script with that font after 10.6. Unfortunately this bug was deferred from current development release (11.2) because of time constraint. If this support is critical for your business, can you open a bug in our public bugbase and ask as many vote as possible? In this way I may be able to convince internal team to fix this bug in next release.
Thank you for your feedback!
Hitomi

Problems displaying Thai characters in Flex FTE components on Mac

I am running into issues displaying Thai characters in Flex components that make use of the Flash Text Engine (FTE), specifically on Mac OSX 10.6.8 Snow Leopard.
Here's a blurb of my compiler font managers in flex-config.xml:
    <flex-config>
        <target-player>10.2.0</target-player>
        
        <swf-version>11</swf-version>
        <compiler>
          
          <locale>
              <locale-element>en_US</locale-element>
          </locale>
          <fonts>
              
              
              <managers>
                  <manager-class>flash.fonts.JREFontManager</manager-class>
                  <manager-class>flash.fonts.BatikFontManager</manager-class>
                  <manager-class>flash.fonts.AFEFontManager</manager-class>
                  <manager-class>flash.fonts.CFFFontManager</manager-class>
              </managers>
                
            </fonts>
        </compiler>
    </flex-config>
...and another from flash-unicode-table.xml:
    <language-range>
        <lang>Thai</lang>
        <range>U+0E01-0E5B</range>
    </language-range>
My flex application originally had the following defined in its stylesheet:
    Application {
        fontSize: 12px;
        fontFamily: Arial;
        font-sharpness:0;
        font-anti-alias-type:advanced;
Thai characters render correctly in mx components such as TextField so far. However, FTE components such as TextLine show those crappy-looking boxes as a substitution. My initial guess was that somehow one of the compiler font managers declared in flex-config.xml was not finding the right system font to fallback to for Thai characters. So, I ensured the system font was installed by going to System Preferences > Language and Text > Edit List. Then I changed fontFamily to Arial, Ayuthaya. Still was seeing the boxes of evil.
Next I figured that perhaps the Arial font might be assigning a box for each unicode value corresponding to a Thai character. So it was effectively overriding the Ayuthaya system font. So I changed fontFamily once more to just Ayuthaya and this worked with one issue - Ayuthaya looks inherently different from Arial for non-thai characters.
Here's my question - is there a less invasive way to support Thai in FTE components such that the appearance of the text is closer to the Arial font? I would rather not embed a font because I'm constrained on SWF size.

If you don't set fontFamily, what it will be? For such a question, you need turn to Flash runtime guys for help. I think you can find them on http://forums.adobe.com/community/flashplayer?view=overview

Java.lang.NullPointerException javax.xml.parsers.DocumentBuilder.parse

Hi all,
i have a problem by solving an error in my code. The Code is mainly from Ian Darwin.
The code i am running works with j2sdk1.4.2_04. But now i have to bring it to work with jdk1.6.0_13.
The code parses xml documents. With small xml documents the code works. With large xml documents i get the following error while running the produced class file.
Exception in thread "main" java.lang.NullPointerException
at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.setChunkIndex(DeferredDocumentImpl.java:1944)
at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.appendChild(DeferredDocumentImpl.java:644)
at com.sun.org.apache.xerces.internal.parsers.AbstractDOMParser.characters(AbstractDOMParser.java:1191)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.characters(XMLDTDValidator.java:862)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:463)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:208)
at XParse.parse(XParse.java:38)
at XParse$JFileChooserrv.<init>(XParse.java:119)
at XParse.main(XParse.java:213)
I know what a java.lang.NullPointerException mens. But i don't know where i have to look for. Specially i don't know what or where "com.sun.org.apache...." is.
Is there a package that a have to add to the environment? Can some one tell my where i can find this package?
I wrote the code for some years ago, 2006 or so. With the knew jdk1.6.0_13 some thinks chance in the environment. Couldn't find what exactly.
The code has only 215 lines, but some how i can't add it to this Message, because Maximum allowed is only 7500.
Is there an other Forum, which may is better for my question?

Here is the code:
import java.io.*;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.xml.sax.*;
import javax.swing.*;
import java.awt.event.*;
import java.io.*;
import java.util.*;
import javax.swing.*;
import java.awt.Container;
import javax.swing.JTextArea;
* This code is mainly from @author Ian Darwin, [email protected]
public class XParse {
     /** Convert the file */
     public static void parse(File file, boolean validate) {
          try {
               System.err.println("");
               String fileName = file.getAbsolutePath();
               System.err.println("Parsing " + fileName + "...");
               // Make the document a URL so relative DTD works.
               //String uri = new File(fileName).getAbsolutePath();
               //System.err.println(uri);
               DocumentBuilderFactory f = DocumentBuilderFactory.newInstance();
               if (validate)
               f.setValidating(true);
               DocumentBuilder p = f.newDocumentBuilder();
               p.setErrorHandler(new MyErrorHandler(System.err));
               //XmlDocument doc = XmlDocument.createXMLDocument(file);
               boolean vaild = p.isValidating();
               if (vaild) {
                    System.out.println("yes parsing");
                    Document doc = p.parse(file); // <<<< ERROR
               System.out.println("Parsed OK");
          } catch (SAXParseException ex) {
               System.err.println("+================================+");
               System.err.println("|       *SAX Parse Error*        |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
               System.err.println("At line " + ex.getLineNumber());
               System.err.println("+================================+");
          } /**catch (RuntimeException ex) {
               System.err.println("+================================+");
               System.err.println("|       *SAX Parse Error*        |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
               //System.err.println("At line " + ex.getLineNumber());
               //System.err.println("At line " + ex.getMessage());
               System.err.println("+================================+");
          }**/ catch (SAXException ex) {
               System.err.println("+================================+");
               System.err.println("|          *SAX Error*           |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
               System.err.println("+================================+");
          /*}} catch (SAXNotRecognizedException ex) {
               System.err.println(" no SAX");*/
          } catch (ParserConfigurationException ex) {
               System.err.println(" ???");
           } catch (IOException ex) {
               System.err.println("+================================+");
               System.err.println("|           *XML Error*          |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
private static class JFileChooserrv {
     JFileChooserrv(JFrame f, boolean vverabreiten) {
          String openfile;
          String verror;
          boolean validate = true;
          final JFrame frame = f;
          String vFilename = "Z:\\Boorberg\\parsen_vista\\daten";
          //String vFilename = "C:\\";
          File vFile = new File(vFilename);
          final JFileChooser chooser = new JFileChooser(vFile);
          JFileFilter filter = new JFileFilter();
          filter.addType("xml");
          filter.addType("sgml");
          filter.addType("html");
          filter.addType("java");
          filter.setDescription("strukturfiles");
          chooser.addChoosableFileFilter(filter);
          boolean vjeas = true;
          chooser.setMultiSelectionEnabled(vjeas);
          int returnVal = chooser.showOpenDialog(frame);
          if (returnVal == JFileChooser.APPROVE_OPTION) {
               //Array filearry[] = chooser.getSelectedFiles();
               //if (vFile = chooser.getSelectedFiles()) {
               //File file[] = chooser.getSelectedFiles();
               File vfile[] = chooser.getSelectedFiles();
               //String openfile = new String();
               int vlenght = vfile.length;
               if (vlenght>1) {
                    int x=0;
                    while (x< vlenght) {
                              parse(vfile[x], validate);
                              x = x +1;
               if (vlenght<=1) {
                    File v2file = chooser.getSelectedFile();
                         parse(v2file, validate);
          } else {
               System.out.println("You did not choose a filesystem           object.");
     System.exit(0);
private static class JFileFilter extends javax.swing.filechooser.FileFilter {
     protected String description, vnew;
     protected ArrayList<String> exts = new ArrayList<String>();
     protected boolean vtrue;
     public void addType(String s) {
          exts.add(s);
     /** Return true if the given file is accepted by this filter. */
     public boolean accept(File f) {
          // Little trick: if you don't do this, only directory names
          // ending in one of the extentions appear in the window.
          if (f.isDirectory()) {
               return true;
          } else if (f.isFile()) {
               Iterator it = exts.iterator();
               while (it.hasNext()) {
                    if (f.getName().endsWith((String)it.next()))
                         return true;
          // A file that didn't match, or a weirdo (e.g. UNIX device file?).
          return false;
     /** Set the printable description of this filter. */
     public void setDescription(String s) {
          description = s;
     /** Return the printable description of this filter. */
     public String getDescription() {
          return description;
private static class MyErrorHandler implements ErrorHandler {
        // Error handler output goes here
        private PrintStream out;
        MyErrorHandler(PrintStream out) {
            this.out = out;
         * Returns a string describing parse exception details
        private String getParseExceptionInfo(SAXParseException spe) {
            String systemId = spe.getSystemId();
            if (systemId == null) {
                systemId = "null";
            String info = "URI=" + systemId +
                " Line=" + spe.getLineNumber() +
                ": " + spe.getMessage();
            return info;
        // The following methods are standard SAX ErrorHandler methods.
        // See SAX documentation for more info.
        public void warning(SAXParseException spe) throws SAXException {
               //System.exit(0);
            //out.println("Warning: " + getParseExceptionInfo(spe));
        public void error(SAXParseException spe) throws SAXException {
               //System.exit(0);
            String message = "Error: " + getParseExceptionInfo(spe);
            throw new SAXException(message);
        public void fatalError(SAXParseException spe) throws SAXException {
               //System.exit(0);
            String message = "Fatal Error: " + getParseExceptionInfo(spe);
            throw new SAXException(message);
     public static void main(String[] av) {
          JFrame vframe = new JFrame("chose files to pars");
          boolean vverabreiten = true;
          boolean validate = true;
          JFileChooserrv vdateienwaehlen = new JFileChooserrv(vframe, vverabreiten);
}The Stack Trace i posted in the last Message. But i couldn't read it, i am not a programmer.

Experiences with Adobe XPAAJ, XML Parsers, OC4J /AS 10.1.2,10.1.3 and DB10g

Over the past couple of weeks we have been working on a solution which uses the newly available adobe XPAAJ api's (XML/PDF Access API for Java) for Java.
The client has a legacy requirement to where users are issued with a pdf form which they complete, save and upload to the server via a JSP. A neat bit of Java code utilizing the XPAAJ API's then strips out the form entered data and spits out XML. This is then parsed and inserted into relational tables within the schema.
Our solution needs to be deployed to an Oracle stack. However we ran into a number of problems when deploying the solution to AS 10.1.2. The adobe API's are not compatible with the Oracle XML Parsers. When extracting the form data, no error is reported and the code which performs the xml parsing just fails. Very nasty.
The main problem has been that Oracle XDK libraries have been hard-coded into the classpath of the container using the referential JAR file Class-Path mechanism. Altering this has required the use of the JRE extension library mechanism, or altering the boot classpath of the JVM when it is launched to load the alternative XML parser implementation instead. While this works, it has been an unsupported operation since the effect of this change is not limited to a specific application – it’s effect are felt across the entire container and this may lead to unpredictable results at runtime.
~http://www.oracle.com/technology/tech/java/oc4j/10131/how_to/how-to-swapxmlparser/doc/readme.html
We did look at a number of other solutions including embedding the java classes I'd written into the database. After loading the apache Xerces api's into our schema we hit upon the same problem. It seems that the same thing happens in the database and the Oracle XML parser is used by default.. Please see SR Number : 6153038.994 on Metalink.
If you can upgrade to AS 10.1.3 then you can follow the excellent how to at:http://www.oracle.com/technology/tech/java/oc4j/10131/how_to/how-to-swapxmlparser/doc/readme.html . Demo code can be found at: http://www.oracle.com/technology/tech/java/oc4j/10131/how_to/how-to-swapxmlparser/how-to-swapxmlparser.zip
The how-to details how to swap xml parsers within the application server.
Other possible solutions that are also available include:
- Shelling out to the OS from the DB or Apps Server, You can then execute the app as a command line app with a custom classpath. Very bad architecture design.
- Setting up an RMI client / server application where client is the db or apps server. You can find examples of this on the web. google 'Simple RMI example'.
- Bootstrapping the XML parser in AS 10.1.2 (unsupported).
I hope people have found this informative. It might save someone a lot of time.
Message was edited by:
Kris Jones

"When I was installing SOA 10.1.3.1.0 on oracle 10.2.0.1 and it was giving error that it needs minimum 10.2.0.3, just wondering 10.1.2.0.2 + SOA =will this work?"
so you talk about the db version. SOA 10.1.3.x runs on 10.2.0.1 and above (I ran for the longest time on XE) and if I remember correctly that's a warning, and not a hard prereq.
Regarding Appserver versions - soa 10.1.3 runs on AS 10.1.3 only

Weblogic 12g Server - EAR with WAR - how can I have different XML parsers

Hi All,
I have a requirement where I need to have two different XML parsers in the same enterprise application.
By backend Spring container require a XML parser and my JSP code which has XSLT logic require another XML parser.
If I specify -D System property then it is applied to the whole Enterprise application. Instead I want a way to specify different XML parsers one for Spring backend container and the other for JSP pages.
I am deploying my application in Weblogic and it is an EAR file.
Thanks in Advance,
Kishore Veleti A.V.K.

check this one.
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl

Thai characters not displaying correctly within App

Hi everyone,
I have a Adobe Flex Mobile app displays Thai text, however this is not displaying correctly. While developing the App on my Windows machine and testing using the Adobe Flash Builder mobile emulator, the font/characters look correct.
However when running the app on either the MAC Adobe Flash Builder emulator, the iPhone simulator or on an actual iPhone, the font/characters are incorrect.
First I thought that it was maybe an encoding issue (I am using locale properties files to replace text), so followed instructions at this website Flash Builder, Flex language bundles showing strange symbols. Not utf8 encoded.Sefol however this did not solve the issue.
Looking more closely at the text rendered, it looks as though all of the characters for each word are actually being rendered, but they are just being rendered in correctly. Where as if it was a encoding issue then it would be missing characters completely.
So if you look at the first character, in the correct version it is built up of 3 components. If you look at the second image, you can see that these three components are present but just not all appearing within one character.
Is this a font issue? or is it actually an encoding/rendering issue?
My code for testing this is just a simple label tag
<s:Label text="ชื่อผู้ใช้" fontFamily="Arial" fontSize="12" />
Many thanks.

Ok so after doing a bit more of an investigation into the Font being the issue and not the encoding type, it seems as though if I use a specific font which I know has the Thai characters, then they are displayed correctly.
I have embedded the font into the App using the code:
[Embed(source="../assets/Kinnari.ttf", mimeType="application/x-font", embedAsCFF="true", fontFamily="ThaiFont")]
private var ThaiFont:Class;
Then on my UI I have added the font:
<s:Label text="ชื่อผู้ใช้" fontFamily="Arial" fontSize="12" fontFamily="ThaiFont" />
I was able to find this font at a Hawaiian Educational website! Thai fonts :: Thai Language Program, University of Hawai'i, Manoa
Thanks @tooMuchTrouble for your help.

How to read a file which content hindi characters.....

I m reading a text file which content hindi characters.... but m nt getting the right result. It shows garbage instead of hindi characters.
plz somebody help me....:(

You posted this in the XML forum. Is this an XML file you are asking about?
And we need definitions for some of the terms you used in your original post. You said "it shows garbage". We need to know:
1. What is the "it" there?
2. How does it "show" something?
3. What does the "garbage" look like.
In future you will find you get better answers if you write better questions.

IPad is slow in processing Thai characters

Hi
I'm Thai and I use my iPad a lot for reading and writing. The iPad slowness has been an issue for me for so long. At first, I thought it was some apps that heavily use resources of my iPad, so I tried closing all inactive apps or restarting which doesn't help. The problem occurs only occasionally, so I decided to be patient and live with it. However, lately I found that this slowness seems to related with processing or displaying a lot of Thai characters.
The first app that the behavior is obvious is iBooks. It takes a good amount of time (minutes) to load a Thai book with about 200 pages, and many seconds just to flip a page. I have another English book that longer than thousand pages and it opens almost instantly without waiting for flipping through pages.
Safari is the other app that shows the same behavior. It takes a lot of patience to read a page with a lot of Thai characters. It freezes and unresponsive when I scroll down the page or click the link so many times. I even used to think that my iPad really freezes, but it will come back if I just wait long enough. Never had this happened on English pages.
The last app that I found this occurs noticeably and I just tested it intentionally today is DayOne, a journal app. My journal writing (in Thai) became painful that I needed to switch to use my macbook instead because of typing lag. I used to blame the bluetooth keyboard and the app itself. Today I copied a pretty long English article into my journal entry and then continued to write after it. The lag was minimal and didn't affect my writing, so I switched to Thai. After only 5-6 lines, the typing lag came back to the point that I can't continue. I tried deleting only the Thai part and the problem solved!
This is very strange to me and please correct me if you think I reach a wrong conclusion, but this is what I've observed. If I remember correctly this issue has been occurring after upgrading to iOS 7, and it is an iPhone issue as well. It's just not obvious because I don't read and write this much on iPhone. If anybody have seen this and know the solution or have any suggestions please let me know. Thank you in advance.
SC

The only things you can do on an iOS device are to restart apps as suggested by Lance or reset the device:
Otherwise let Apple know the details of the problem via
http://www.apple.com/feedback

Problem when printing Thai Characters in Smartform

Hi All,
When printing thai characters in smartform it takes more spaces between characters than required. I tried all possible font to adjust the character spacing.
Can anyone help me out.
Thanks,
Khushboo Dand

Dear Khushboo, Jag
I have observed that tThe tiny boxes that are appearing in the Smartform text element is only occuring when you are printing a variable whose content is thai and nothing else with that. by nothing else i mean no THAI hardcoded text.
if you try and check you will observe that when you try to print something like this in your Text element
with your paragraph format alright/ output device and device type everythng in place
eg:
ของผู้มีเงินได้ &G_VAR& -
is printing alright : content of G_VAR is thai characters
but if you are printing just the variable
eg:
&G_VAR& --- it will print boxes
to overcome this after trying no.of checks / online helps / settings etc etc which , ofcourse, did not help
I did a lil bit trick with the system
You can create a character format in your smartstyle with FONT : THANGSAN and maintain the COLOR as white
now go to your text element key in a THAI character at the start or end of you variable and assign your new character format to that character. and Eureka! it will work
eg: <CF> ข </> &G_VAR& - --- seen in your change editor
where CF is the new "colorless" character format I have asked you to create.
Thanks and Regards,
Charu.
Edited by: Charu Borkar on Aug 3, 2011 00.14 am

LSMW upload of Thai characters uploaded incorrectly as '#####'

Hello,
Im using LSMW to upload data in Thai language. However the Thai characters are uploaded as ####.
I uploaded using LSMW to upload customer master as follows
-     file uploaded is a tab delimitted (.txt) unicode file
-     SAP gui character set is set to Thai TIS620
-     I logon in language EN using codepage 1100
-     SAP release is 620 for SAP ABAP & BASIS and release 470 for SAP APPL
Logging onto SAP using codepage 8600(Thai codepage) did not make any difference.
Doing all of the above with SAP gui character set Simplified Chinese GB2312, I was able to upload chinese characters into SAP succesfully
Just wondering if any special Thai codepage, character set, technical settings is required as part of Thai installation(I'm not a Basis expert).
Has anyone sucessfully uploaded Thai characters into your SAP system?
Thanks for any tips and informations.
Best regards, Yong Yong

Hi Yong,
I need some help in upload some data using LSMW. I am uploading some customer data which is mainatined in Spanish. Could you please tell me about the settings that i have to take care off before the upload?
my email address is [email protected]

XML Parsers which supports Thai Characters

Similar Messages

Maybe you are looking for