Incorrect printing of Unicode characters

C5180 prints some unicode chars (0x2283 and 0x25A1) as if combined with a carriage return.
On screen the line looks fine, but on my printer they are printed at the beginning of that (current) line.
I use them in a Java program and don't see where the error lies: Windows 7, Java 7 or HP. (3 changes in one)

Hi,
It is a printer issue. The printer needs to be configured to support the Chinese chanracter set.
Normally when we are able to view the chinese characters properly in the print preview but not properly displayed on the output it is surely a printer problem.
This kind of problem we faced many times.
Thanks
Ram

Similar Messages

QRcode printing with unicode characters

Hi,
We're trying to print out QRcode in smartforms by referencing below link with output device ZBWIPP and device type ZBWIPPQR.
http://www.rjruss.info/2010/09/how-to-printpdf-qr-codes-in-standard.html
Meanwhile, we need to print out trad. Chinese in same smartform.
Seems that QRcode and trad. Chinese are in different character set.
Would there be any device type which supports QRcode and unicode ?
or any revision requires for ZBWIPPQR device type?
Please help.
Thank you.

Hello Nieves,
Just came aware of your question and see its been a while so you may have moved on.
However I created the post you refer to.
Also I posted the following SCN blog post that covers using a Japanese Device type to allow Kanji with the QRcode.
The SAP note referenced in the blog also has Chinese device types so could be adapted. The device types do come with some limitations so may not be suitable in all cases.
If you still have the requirement have a read of my SCN blog and happy to help further if required.
Cheers
Robert
Barcodes in SAP with the Barcode Writer in Pure Postscript update

Printing unicode characters in Java - help

Hi there,
I want to print out unicode characters through java programming language in windows system. For example, I want to print Devanagari characters. I found out that '\u0900' to '\u0975' represent devanagari characters. So I tried following,
out = new PrintStream(System.out, true, "UTF-8");
out.println('\u0911');
but they print characters like �� and not the actual devanagari characters. Just to be more clear, devanagari script is used by Hindi, Nepali and similar languages.
If you knew about it and could give any suggestions, that would be very helpful.
Thanks in advance!

priyankabhar wrote:
I am not sure, it is just a windows system and I am trying to print to the command line. Please suggest me how I can find out if my console supports it.Use the CHCP command to find out what code page your console uses. And as already suggested, Google is a good resource if you don't know what a "code page" is.

Printing Unicode characters

Hi all,
I am trying to print certain unicode characters to a file using this code:
import java.io.*;
public class Unicode{
     public static void main(String args[]) throws IOException{
          char[] c = new char[1];
          char ch= '\u0ce6'; //starting character
          File f = new File("c:\\UC.txt");
          BufferedWriter bf = new BufferedWriter(new FileWriter(f));
          while( ch < '\u0cef'){
               c[0] = ch++;
               bf.write(c, 0, 1);//write the character to a file
          bf.flush();
}All I can see in the file is '?????????'. I tried printing it to file as command prompt also showed the same thing. How can I see the Unicode characters of different languages? Do I need to set any char encoding using System properties?
Thank you very much.

Sigh there is no such thing as plain text.
You create a file with the platform encoding (read the API docu of the FileWriter). That platform encoding is probably not even able to represent all unicode characters (it's likely to be ISO-8859-1 or one of it's variants).
Then you open that file without specifying the character set (it's guessed, possibly wrong) and you don't see the expected output.
Read http://www.joelonsoftware.com/articles/Unicode.html for an introduction into the beautiful world of unicode.

Scanning files for non-unicode characters.

Question: I have a web application that allows users to take data, enter it into a webapp, and generate an xml file on the servers filesystem containing the entered data. The code to this application cannot be altered (outside vendor). I have a second webapp, written by yours truly, that has to parse through these xml files to build a dataset used elsewhere.
Unfortunately I'm having a serious problem. Many of the web applications users are apparently cutting and pasting their information from other sources (frequently MS Word) and in the process are embedding non-unicode characters in the XML files. When my application attempts to open these files (using DocumentBuilder), I get a SAXParseException "Document root element is missing".
I'm sure others have run into this sort of thing, so I'm trying to figure out the best way to tackle this problem. Obviously I'm going to have to start pre-scanning the files for invalid characters, but finding an efficient method for doing so has proven to be a challenge. I can load the file into a String array and search it character per character, but that is both extremely slow (we're talking thousands of LONG XML files), and would require that I predefine the invalid characters (so anything new would slip through).
I'm hoping there's a faster, easier way to do this that I'm just not familiar with or have found elsewhere.

require that I predefine the invalid charactersThis isn't hard to do and it isn't subject to change. The XML recommendation tells you here exactly what characters are valid in XML documents.
However if your problems extend to the sort of case where users paste code including the "&" character into a text node without escaping it properly, or they drop in MS Word "smart quotes" in the incorrect encoding, then I think you'll just have to face up to the fact that allowing naive users to generate uncontrolled wannabe-XML documents is not really a viable idea.

Is there a list of Unicode characters that can be used in Acrobat bookmarks?

I can add Greek characters to Acrobat bookmarks using hexadecimal strings. For example, to print a lower case gamma symbol I use <FEFF03B3>. FEFF is the required Unicode flag and 03B3 is the Unicode code for gamma. This works fine. However, there are no Unicode entries for greek characters in the PDF 32000-1:2008 PDF Specification manual. Table D.2 - PDFDocEncoding Character Set on page 656 lists Unicode characters and these also work when added to bookmarks but no Greek codes are in this table. Since I can sucessfully use Greek Unicode characters in the range of 0x0391 - 0x03CE and these characters are not listed in the PDF manual I am assuming there are additional Unicode character that will work in bookmarks. Therefore, I am looking for a complete list of Unicode characters that can be used in Acrobat's bookmarks. Does such a list exist?

Thank you for the response.
I'm sorry to hear there is no list available. I'm building the Acrobat bookmarks automatically. The input data contains entity codings (for example, a lower case Greek gamma is coded as γ) and I was hoping to be able to just pass these through with an automatic conversion to a hexadecimal string (for example <FEFF03B3>). If I had a list of valid Unicode characters, that will display in an Acrobat bookmark, I could validate each entity before the conversion and catch the ones that won't display correctly. I know these types of characters are out there because I have already come across them. For example, a superscript 5 (0x2075) displays fine in MSWord but shows as a white box in a bookmark. Now I'll need to proof the output PDFs and look for white boxes in the bookmarks so that I can build my list of unicode characters that do not work in Acrobat bookmarks.
Again, thanks for your help.

Preview and Printing of Chinese Characters in Smartform

Hi everyone!
I have a development that needs to output in Smartform a combination of Chinese and English characters, on an English Logon,
When I debug the form, the Chinese characters are shown in the debug screen, but when it is previewed or printed, it shows garbage. Can anyone help me with this?
Thanks a lot! Points for any helpful answer!

Hi
check this OSS Note
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Regards
Anji

Direct Execution of query having Unicode Characters

Direct Execution of query having Unicode Characters
Hi All,
In my application I am firing a Select Query having Unicode characters in Where Clause under condition like '%%'
to Oracle 10g DB from a Interface written in VC6.0...
Application funcationality is working fine for ANSI characters and getting the result of Select properly.
But in case of Unicode Characters in VC it says 'No Data Found'.
I know where the exact problem is in my code. But not getting the exact solution for resolving my issue...
Here with I am adding my code snippet with the comments of what i understand and what i want to understand...
DBPROCESS Structure used in the functions,_
typedef struct
HENV hEnv;
HDBC hDbc;
HSTMT hStmt;
char CmdBuff[[8192]];
char RpcParamName[[255]];
SQLINTEGER SpRetVal;
SQLINTEGER ColIndPtr[[255]];
SQLINTEGER ParamIndPtr[[255]];
SQLPOINTER pOutputParam;
SQLUSMALLINT CurrentParamNo;
SQLUSMALLINT OutputParamNo;
SQLUSMALLINT InputParamCtr;
SQLINTEGER BatchStmtNo;
SQLINTEGER CmdBuffLen;
short CurrentStmtType;
SQLRETURN LastStmtRetcode;
SQLCHAR SqlState[[10]];
int ShowDebug;
SQLCHAR* ParameterValuePtr;
int ColumnSize;
DBTYPE DatabaseType;
DRVTYPE OdbcDriverType;
BLOCKBIND *ptrBlockBind;
} DBPROCESS;
BOOL CDynamicPickList::GetResultSet(DBPROCESS *pDBProc, bstrt& pQuery, short pNumOdbcBindParams, COdbcBindParameter pOdbcBindParams[], CQueryResultSet& pQueryResultSet)
     int               lRetVal,
                    lNumRows;
     bstrt               lResultSet;
     wchar_t               lColName[[256]];
     SQLUINTEGER          lColSize;
     SQLSMALLINT          lColNameLen,
                    lColDataType,
                    lColNullable,
                    lColDecDigits,
                    lNumResultCols;
     wchar_t               lResultRow[[32]][[256]];
OdbcCmdW(pDBProc, (wchar_t *)pQuery); *//Query is perfectly fine till this point all the Unicode Characters are preserved...*
     if ( OdbcSqlExec(pDBProc) != SUCCEED )
          LogAppError(L"Error In Executing Query %s", (wchar_t *)pQuery);
          return FALSE;
Function OdbcCmdW_
//From this point have no idea what is exactly happening to the Unicode Characters...
//Actually i have try printing the query that gets stored in CmdBuff... it show junk for Unicode Characters...
//CmdBuff is the Char type Variable and hence must be showing junk for Unicode data
//I have also try printing the HexaDecimal of the query... I m not getting the proper output... But till i Understand, I think the HexaDecimal Value is perfect & preserved
//After the execution of this function the call goes to OdbcSqlExec where actual execution of qurey takes place on DB
SQLRETURN OdbcCmdW( DBPROCESS p_ptr_dbproc, WCHAR      p_sql_command )
     char *p_sql_commandMBCS;
     int l_ret_val;
     int l_size = wcslen(p_sql_command);
     int l_org_length,
l_newcmd_length;
p_sql_commandMBCS = (char *)calloc(sizeof(char) * MAX_CMD_BUFF,1);
l_ret_val = WideCharToMultiByte(
                    CP_UTF8,
                    NULL,                         // performance and mapping flags
                    p_sql_command,          // wide-character string
                    -1,                         // number of chars in string
                    (LPSTR)p_sql_commandMBCS,// buffer for new string
                    MAX_CMD_BUFF,                    // size of buffer
                    NULL, // default for unmappable chars
                    NULL // set when default char used
l_org_length = p_ptr_dbproc->CmdBuffLen;
l_newcmd_length = strlen(p_sql_commandMBCS);
p_ptr_dbproc->CmdBuff[[l_org_length]] = '\0';
if( l_org_length )
l_org_length++;
if( (l_org_length + l_newcmd_length) >= MAX_CMD_BUFF )
if( l_org_length == 0 )
OdbcReuseStmtHandle( p_ptr_dbproc );
else
strcat(p_ptr_dbproc->CmdBuff, " ");
     l_org_length +=2;
strcat(p_ptr_dbproc->CmdBuff, p_sql_commandMBCS);
p_ptr_dbproc->CmdBuffLen = l_org_length + l_newcmd_length;
if (p_sql_commandMBCS != NULL)
     free(p_sql_commandMBCS);
return( SUCCEED );
Function OdbcSqlExec_
//SQLExecDirect Requires data of Unsigned Char type. Thus the above process is valid...
//But i am not getting what is the exact problem...
SQLRETURN OdbcSqlExec( DBPROCESS *p_ptr_dbproc )
SQLRETURN l_ret_val;
SQLINTEGER l_db_error_code=0;
     int     i,l_occur = 1;
     char     *token_list[[50]][[2]] =
{     /*"to_date(","convert(datetime,",
                                   "'yyyy-mm-dd hh24:mi:ss'","1",*/
                                   "nvl","isnull" ,
                                   "to_number(","convert(int,",
                                   /*"to_char(","convert(char,",*/
                                   /*"'yyyymmdd'","112",
                                   "'hh24miss'","108",*/
                                   "sysdate",     "getdate()",
                                   "format_date", "dbo.format_date",
                                   "format_amount", "dbo.format_amount",
                                   "to_char","dbo.to_char",
                                   "to_date", "dbo.to_date",
                                   "unique","distinct",
                                   "\0","\0"};
char          *l_qry_lwr;
l_qry_lwr = (char *)calloc(sizeof(char) * (MAX_CMD_BUFF), 1);
l_ret_val = SQLExecDirect( p_ptr_dbproc->hStmt,
(SQLCHAR *)p_ptr_dbproc->CmdBuff,
SQL_NTS );
switch( l_ret_val )
case SQL_SUCCESS :
case SQL_NO_DATA :
ClearCmdBuff( p_ptr_dbproc );
p_ptr_dbproc->LastStmtRetcode = l_ret_val;
if (l_qry_lwr != NULL)
     free(l_qry_lwr);
return( SUCCEED );
case SQL_NEED_DATA :
case SQL_ERROR :
case SQL_SUCCESS_WITH_INFO :
case SQL_STILL_EXECUTING :
case SQL_INVALID_HANDLE :
I do not see much issue in the code... The process flow is quite valid...
But now i am not getting whether,
1) storing the string in CmdBuff is creating issue
2) SQLExecDirect si creating an issue(and some other function can be used here)...
3) Odbc Driver creating an issue and want some Client Setting to be done(though i have tried doing some permutation combination)...
Any kind of help would be appreciated,
Thanks & Regards,
Pratik
Edited by: prats on Feb 27, 2009 12:57 PM

Hey Sergiusz,
You were bang on target...
Though it took some time for me to resolve the issue...
to use SQLExecDirectW I need my query in SQLWCHAR *, which is stored in char * in my case...
So i converted the incoming query using MultibyteToWideChar Conversion with CodePage as CP_UTF8 and
then passed it on to SQLExecDirectW...
It solved my problem
Thanks,
Pratik...
Edited by: prats on Mar 3, 2009 2:41 PM

[SOLVED] Conky Not Displaying Unicode Characters Correctly

I have some music that requires unicode characters in order to be displayed properly. The artist name is Röyksopp, but it is displayed like this:
http://i.imgur.com/rRBDxZn.png
Does anyone know how to either make it display correctly (Röyksopp), or at least remove the umlauts to make it almost correct(Royksopp)? I've set the locale, so it displays correctly in both i3bar and urxvt, but it had no effect on conky.
EDIT: Here is my conkyrc.
Last edited by ProfessorProcrastinator (2014-05-14 22:50:16)

x33a wrote:Try a different font.
I know that this font works because I tried it in urxvt and it displayed correctly.
Also, I tried "override_utf8_locale yes" and it still was incorrect.

FOI Servlet non-unicode characters cannot be processed

Hello,
I'm using Oracle MapViewer 10.1.3.1 quickstart kit to test some map features
my database is in CL8MSWIN1251 charset
I made a simple map application to display some data using JavaScript API
when I define a theme based FOI layer in the map and the predefined theme has some non-Unicode characters in the labeling or in hidden info fields I get the folowing error:
Cannot process the following response from FOI server:
{"foiarray":[{"id":"AAARiqAAEAAAzFgAAA","name":"\u422\u414","gtype":"2001","imgurl":"http://localhost:8888/mapviewer/images/foi/p_16_13_MVDEMO_M.IMAGE131_BW.png","x":"50.0","y":"50.0","width":"16","height":"13","attrs":["987654321","100"]}],"attrnames":["BBB","Osn"]}
As you can see "\u422\u414" shoud be "\u0422\u0414" otherwise JavaScript cannot display characters in the right way. I think FOIServlet is the problem here.
Anyone has the same problems or has a solution for this problem pls

require that I predefine the invalid charactersThis isn't hard to do and it isn't subject to change. The XML recommendation tells you here exactly what characters are valid in XML documents.
However if your problems extend to the sort of case where users paste code including the "&" character into a text node without escaping it properly, or they drop in MS Word "smart quotes" in the incorrect encoding, then I think you'll just have to face up to the fact that allowing naive users to generate uncontrolled wannabe-XML documents is not really a viable idea.

Terminal.app and the European Unicode characters?

Does anyone have the unicode characters working properly in Terminal.app?
If I try to write in GNU nano 1.2.4 for instance "örrör" it translates into:
(one empty line)
örr
ör
which isn't certainly right. This is especially awkward when editing an unicode text file where the text then easily becomes more or less garbled. Usually more.
It doesn't seem to make any difference whether or not I use the Finnish extended (unicode) keyboard layout or the conventional one in nano. If the Terminal.app window preferences are set as UTF-8, it says:
?rr
?r
which looks even more garbled.
In plain bash the characters print like this:
å = \345
ä = \344
ö = \366
so my mighty apple translates the example string "örrör" as "\366rr\366r".
Any ideas, anyone?
PowerBook G4 @ 1.5 GHz Mac OS X (10.4.4) 1.25 GB DDR SDRAM
Debian Sarge 3.1 as a slave fetchmail server.

Hi solarflare,
   My first (and essentially only) language is English as well. However enough folks have asked that I have experimented with multibyte characters. There are so many apps and options involved, it's difficult to get consistent results. However, I'll recount as many settings as I can recall.
   To begin with, you are right about the LC settings. It helps many apps to have:
export LCALL=enUS.UTF-8
export LANG=en_US.UTF-8
set in your shell startup scripts. Then the system should be set to produce unicode when you type. In the "Input Menu" tab of the "International" pane of "System Preferences", you should select a unicode keyboard layout, such as U.S. Extended.
   To configure the Terminal, you need to open the "Terminal Inspector" by selecting "Window Settings..." in the "Terminal" menu. To type many multibyte characters, you need the option key. To use it, you must have the "Use option key as meta key" checkbox unchecked, although I find the meta key too important in UNIX to leave that unchecked. In the dropdown menu in the "Display" pane of the "Terminal Inspector", you should set the "Character Set Encoding" to "Unicode (UTF-8)". In the "Emulation" pane of the same window, you must uncheck the "Escape non-ASCII characters" checkbox. That is important as I've read that it is checked by default and that can produce some pretty strange results.
   Now it's helpful to use a very modern shell. For instance, the latest beta version of zsh-4.3 has the best unicode support of all versions of zsh. After you've chosen a good shell, you're at the mercy of the application that you're using. As I gather you've noticed, vim has excellent unicode support and picks up on the LC settings. I have no idea about nano but it is meant to be a minimal text editor.
   I know that my settings allow me to type extended characters and the "Character Palette" lets me insert more. As far as other command line utilities go, the best you can do is to choose well and keep your apps as up-to-date as possible. Fink or Darwin Ports can often help in that regard.
Gary
~~~~
   This generation doesn't have emotional baggage.
   We have emotional moving vans.
         -- Bruce Feirstein

Printing non-latin characters

If I wanted to print unicode characters in JSP, for example, arabic or japanese, what's the best way to go through with this?
I tired the
<%@ page contentType="text/html; charset=Windows-1256" %>but it won't work
I tried this:
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">but wasn't any better
what else can I do? Is there any specification I should look up first?

Here you are ..
<%@ page contentType="text/html; charset=UTF-8"
%>
that doesn't work either,,,
The input comes from a textArea, it is then stored into a mysql database and then displayed on the browser. Weird thing is it works on my localhost but not on the server i'm uploading the war file!!!

Java PrintService printing Chinese/Japanese characters output is garbled.

Hi Java Gurus,
I have been spending the whole day trying to make our text printing application able to print non-western Characters (e.g. Chinese and Japanese) as part of our requirements. But I am constantly getting garbled output when I print a UTF-8 formatted text file containing Chinese characters. I've been trying to switch the DocFlavor types (e.g. byte array in UTF 8, input stream auto sense, UT8-8, etc) but I couldn't simply make it work.
Here is our test method:
     public void testPrintText(String fileName) throws Exception {
          FileInputStream textStream = new FileInputStream(fileName);
          File file = new File(fileName);
          String fileContent = FileUtils.readFileToString(file);
          DocFlavor flavor = DocFlavor.BYTE_ARRAY.TEXT_PLAIN_UTF_8;
          //DocFlavor flavor = DocFlavor.READER.TEXT_PLAIN;
          InputStreamReader isr = new InputStreamReader(textStream, "utf-8");
          DocAttributeSet das = new HashDocAttributeSet();
          //System.out.println("host encoding: " + flavor.hostEncoding);
          Doc mydoc = new SimpleDoc(fileContent.getBytes("utf-8"), flavor, das);
          //Doc mydoc = new SimpleDoc(textStream, flavor, das);
          PrintRequestAttributeSet pas = new HashPrintRequestAttributeSet();
          pas.add(new PrinterName("\\\\fsinec\\Canon iR5055 PCL6", null));
          PrintService[] services = PrintServiceLookup.lookupPrintServices(flavor, pas);
          PrintService defaultService = PrintServiceLookup.lookupDefaultPrintService();
          System.out.println("DEBUG: " + defaultService.getClass().getName());
          if(services.length == 0) {
               if(defaultService == null) {
                    //no printer found
               } else {
                    //print using default
                    DocPrintJob job = defaultService.createPrintJob();
                    job.print(mydoc, pas);
          } else {
               //built in UI for printing you may not use this
               PrintRequestAttributeSet attSet = new HashPrintRequestAttributeSet();
               for(int ctr=0; ctr<services.length; ctr++) {
                    PrintService printService = services[ctr];
                    System.out.println("COTS DEBUG: " + defaultService.getClass().getName());
               //attSet.add();
               PrintService service = null;
               if(services.length == 1) {
                    //assume that there is no other printer with the name \\\\fsinec\\Canon iR5055 PCL6
                    //resulting to fetch the printer services to only one (1) element.
                    service = services[0];
               /* open a dialog box
               * PrintService service =
                    ServiceUI.printDialog(null, 200, 200, services, defaultService, flavor, attSet);*/
               if (service != null) {
                    DocPrintJob job = service.createPrintJob();
                    job.print(mydoc, attSet);
Please help me on this.
Thanks.

This could be of different reeasons...
1) Make sure your printer is uni-code enabled.
2) Make sure, your unicode enabled printer is configured in SAP.
3) make sure, your printer device is supported by SAP. (You can find list of SAP recommended printers in www.service.sap.com)
4) Check whether the correct device type is used for printing chinese and japanese characters.
5) Check code pages.
6) Make sure you use Cyrillic font family, for printing chinese and Japanese characters.
Regards,
SaiRam

How to display unicode characters

hi
How could we save, display, write or read Unicode characters.

Thanks a lot. I fully understand what you have said.
My test is running under Traditional Chinese "Big5" Windows XP system.
Chinese "Big5" font can display on a Console window. I can even input Chinese into the console window.
Or, in another word, I can TYPE a text file which contains "Big5" Chinese characters and show from the Console window. I assume this will prove that the Console window do know how to handle Chinese characters.
Now, my test is trying to CONVERT a Unicode string into a Chinese character string expecting the resulting Chinese string can be output into the Console window and let the XP Console window to handle the Chinese character display.
My main concerned question is "How can I CONVERT a Unicode string into a Big5 Chinese character string?"
String tstr = new String("\u39321\u28207","big5");
It seems this statement is INCORRECT, isn't it?

Printing of german characters

Hello Friends,
I am new to SDN and would like to know something. I want to print special german characters via SAP like 2 dots on alphabet A and O. How can I get those printed on the document. Currently these special characters are not printed but a blank space is printed instead. Can someone help?
Regards,
Atul Lotlikar.

Hello Friends,
This is about a non-unicode system where I see that the european characters like the german umlauts ( ä, ö, ü ) are not printed. What could be the solution? Implementing a new codepage like ISO 8859-2 or can it be done with the existing codepage 1100? Can someone help me on this?
Regards,
Atul Lotlikar.

Incorrect printing of Unicode characters

Similar Messages

Maybe you are looking for