CMD outputs in chinese characters

All my CMD outputs are in chinese characters like "net share > svrshareinfo.txt
I dont have a clue why this is happening but I need a solution fast so I cant turn in my output captures for my windows server 2012 r2 class quickly.

Hi,
Please check the language for non-Unicode programs.
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Fax output - Chinese characters are garbled

Hello,
We are using fax output for two forms ( One smartform and the othe sap script). Both the form outputs are thorugh the same fax device. For the smartform output there are no issues and the output is as expected but for the sap script output the chinese characters are garbled. Instead of the chinese characters i get output like _____ _______>,<%,,<< etc.
Interestingly, if i have a look at the print preview or take print out there is no issue and the characters are as expected. The issue arises only during fax.
Can someone help pls?
Thanks,
Venkat

HI friend,
I found few same post in SDN which are related to this Chinese characters in SAP Scripts.
Please see this link and find is the problem is same as yours if so make use of it.
Link: [Output of Sapscript in Chinese language|Output of Sapscript in Chinese language;
Link: [Problem displaying Chinese Characters|Problem displaying Chinese Characters in SAP script form WESCHEINVERS1;
I think these will be helpful please revert back to me after going through the links.
Thanks,
Sri Hari

Chinese Characters in Discoverer Plus

Hi,
I am having the problem of outputting chinese characters in Discoverer Plus on the client browser. The chinese characters are represented by "box" when they are outputted to Discoverer plus. The chinese characters can be shown with the Report Builder. My database is running on UTF8 characterset.
I have done some configurations to output the chinese characters to the Report Builder. Besides, the chinese characters can be shown in the PDF reports generated from the Report Server. The configurations that I have done is to modify some of the files in ORACLE_HOME/bin/ and ORACLE_HOME/guicommon9/tk90/admin/.
How do I ouput the chinese characters in Discoverer Plus?
Thank you.
Cheers,
Joey

i have installed sqlplus and oracle db in the same PC under chinese win xp.
i found that if you spool the output to a text file, and type in dos-prompt, it still cannot display the chinese character properly. but if you open the text file by notepad, bingo, you can the chinese character.
i think that it is because dos-prompt application is non-unicode application. so it could not display unicode character properly.
as a result, if you want to display unicode character in non-unicode application (run sqlplus under dos-prompt), you have to set the NLS_LANG environment variable which match the character set of non-unicode application which your operating system assigned. in my case, it should be Big5. then oracle would do the conversion for you automatically, i.e. from unicode in DB to Big5 in client.
I either set the NLS_LANG environment variable in one of the 2 ways:
NLS_LANG=american_america.zht16big5 or
NLS_LANG=american_america.zht16hkscs
Regards,
KH

PO Print Output- Doesn't print Chinese characters

Hi,
There is customized t-code ZME9F similar to ME9F with an added feature of e-mail to vendor.
When we process PO through ZME9F, the PO converted to PDF is not printing the chinese characters.when 'Display message' is clicked also it is fine.The print preview of the PO is fine.
Can you please let me know what is the reason for not printing chinese characters in the conversion of PDF?
Thanks in Advance,
Sowmya

Hi Soumya,
Please check note 903157.
Also the notes 812821, 83502, 776507 are helpful.
Thanks,
Ashwini.

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

How can I force text in a table to wrap at the margin? Chinese characters result in wide tables.

Hello all ye RoboHelpers out there.
Background:
We're using RH 9 (latest patch) on Windows 7 machine.
We document in English and then the RH project gets localized into many diff languages and we use that to generate CHM, and Printed outputs.
The Problem:
In the Chinese language, in printed output, the right border of most tables exeeds well beyond the margin.
Here's what the localized table looks like in the RH editor:
By comparison, here's the equivalent English topic prior to localization:
Our CHM output is fine. In fact, here's what the Chinese looks like in when output to a browser or previewed and I drag the right side to
a narrower width. Notice that the table text appropriately wraps to remain within the window's size:
But here's what it looks like when I generate it in Word's printed output:
Notice the location of the margin at 6.5 inches. It should be wrapping at the margin. And something is weird with the left cell how it's getting pushed so far to the right.
The actual table width ends up around 11 inches! I had some tables last time I did this that were as far out as 18 inches but looked perfectly fine in English!
We use Across Systems for our localization tool, and I've verified that our translators are not messing with the table properties at all; only the text is exposed. One interesting difference I've noticed from other languages, is that Chinese characters do not contain a true space or period characters when we get them back from localization. This makes sentences essentially a really long string of unbroken characters, and I suspect this somehow pushes the generated tables to wide extremes in printed output.
What I've Tried:
I've tried to change the table properties in Word to auto fit the size of the window.
I've tried setting the width in RH to a specific size and regenerating. Still doesn't help.
I've added in space character and doing that does cause lines to wrap in some cases, but not in all. But I shouldn't have to do this.
I've tried to create a VBA macro in Word to size the tables, but couldn't get it to work.
What I need:
I need to somehow globally force all the tables' text strings to wrap once they reaches the right margin no mater what, even if the line does not contain space characters. Is there a setting I'm missing somewhere, either on the RH side or the Word side that can do this for these long strings of characters?
I really hope someone else has figured out how to deal with this because last time I did this, I had to go through approximately 500 tables and manually do a very convoluted workaround dragging the table handle in Print layout mode back to the right margin to get the table to wrap appropriately. It was a major pain in neck!
Many thanks in a advance for any ideas you might have.

I wonder the Format Tables macros on my site could be adapted?
http://www.grainge.org/pages/authoring/word/word_macros.htm
If not, I have used Macro Express to format tables in Rh. No reason it could not be used in Word.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Issue Regarding Chinese characters In Smart Form Print preview..

Hi All,
I am working on a smart form development for chinese users. The requirement is the user will login using English & when the delivery will be issued for output, a check will be done on the country of user. If that comes as china then the international version (C) maintained for that customer will come as output.
Now the problem is even if I login using EN or ZH the below issue I am facing always.
In the database I can view the details in chinese properly by logging in as ZH. During debugging also i checked the data from table ADRC & MAKT is coming in chinese properly. But when i gave the values to be output in SmartForm, it is showing the characters like how it will look if I login using EN & view the table contents.
When i view the data by changing character set as Simplified Chinese then in table i can see chinese texts properly. But when the same data goes to print preview it shows the chinese characters like as it would appear when character set is Unicode or West European..
Please help..
Thanks in advance.
Edited by: malayanayak123 on Jun 1, 2011 5:48 AM

Dear,
print preview and physical printout are two different things.
PrintPreview:
The data stream will be sent to the frontend and rendered with windows-fonts etc (for backend prints a simulation).
Printout:
Frontend: You need a printer, that maps the character, you have to use SAPWIN or SAPWINCF when using cascading fonts. The rendering will be done in the windows spooler.
Backend: Your printer needs also a mapping (look like something with UTF8). Also the printer needs the fonts installed because the rendering will be done in the printer!
If you use the pdf-printer in SAP, you need to upload all necessary fonts (TTF) for the pdf-composer. Also you need a unicode pdf printer for that.
Regards,
Christian

Cannot Store Chinese Characters In Oracle 9.2.0.7 Database

Hi,
I'm having trouble localizing my Oracle 9.2.0.7 / ASP web application for our Chinese-speaking users.
My Oracle 9.2.0.7 Database has NLS_NCHAR_CHARACTERSET set to AL16UTF16.
I've set up a test table thus:
CREATE TABLE "TBL_TEST_CH"
field1                          NVARCHAR2(40),
field2                          NVARCHAR2(40)
I have the Chinese character set installed on my database / web server (same box), as well as a test client machine. I can see Chinese characters in my web browser, and can enter them in a test ASP page I've set up. When I execute an insert statement via ADO, the insert statement seems to work, but the result is that the data seems to be stored as upside-down question marks.
I thought perhaps the data was being somehow scrambled between the web app and the database, so I set up an external table import the Chinese data from a Unicode text file:
CREATE TABLE kenny.ch_import
     FIELD1          NVARCHAR2(255),
     FIELD2          NVARCHAR2(255)
     ORGANIZATION EXTERNAL (TYPE oracle_loader
     DEFAULT DIRECTORY ext_dat_dir
     ACCESS PARAMETERS
     (RECORDS DELIMITED BY ":"
     FIELDS TERMINATED BY "~"
     missing field values are null)
     LOCATION (ext_dat_dir:'test_ch.txt'))
     reject limit unlimited
However, when I query the data in the external table using my web application, it comes back with garbage like "ÿþ1" and the like.
To attempt to determine if the database is capable of storing the Chinese characters, I've performed the following test:
1) I insert a Chinese character in an NVARCHAR2 field in my table by using the UNISTR function thus:
insert into tbl_test_ch (field1) values (unistr('\3E00'))
2) I interrogated the value using the dump function thus:
select dump(field1, 1016) FROM tbl_test_ch
I'm struggling to understand the output. Obviously the character set being used is "AL16UTF16" (which I would expect to be able to store Chinese characters), but the return_format argument I've provided to the function (1016) should return the hexadecimal code point of the character that's being stored. I would expect this to be the same as I inserted ("3E00"), but I'm getting the following output:
DUMP(FIELD1,1016)
Typ=1 Len=2 CharacterSet=AL16UTF16: 3e,0
I'd really appreciate any suggestions on what I could do next to determine exactly where the problem lies. I've not been able to convince myself that the database is correctly storing the Chinese character data, but I appreciate equally that the problem could lie elsewhere.
Thanks in advance,
Kenny McEwan.

Thanks, Serguisz.
My technology stack is as follows:
ASP 3.0 web application, running on IIS6.
On the web servier, I have MDAC 2.8 SP2 on Windows Server 2003 SP1.
On the Oracle database server, I have Windows Server 2003 SP1.
My Oracle database version is 9.2.0.7.
The client I've been using in this investigation is Internet Explorer 6.0.2900.
It does look like you're right about characters coming from the application are being corrupted. To support this, I tried to insert the chinese character 博 as well as the Unihan character 中 from a web page in my application. I then used the dump function to interrogate the contents of the field I input to thus:
select dump(field1, 1016) FROM tbl_test_ch
DUMP(FIELD1,1016)
Typ=1 Len=2 CharacterSet=AL16UTF16: 0,bf
Typ=1 Len=2 CharacterSet=AL16UTF16: 0,bf
Both characters seem to have suffered the same corruption.
The problem seems to happen in the other direction as well - even after verifying that the character detailed in the previous post was stored correctly, it is still displayed by my web app as an upside down question mark.
Do you have any suggestions on how to proceed?
Best regards,
Kenny.

How to use a select statement with chinese characters?

I am currently developing a java servlet<using tomcat 4.x> which allows me to use select statement to retrieve results from the Microsoft SQL Server 2000 database. I am using a simple form to get the parameter for querying. The main problem i'm facing is that there are chinese information in the SQL database, but i can't retrieve it through the sql statement with the chinese characters input<thru the form with the help of NJ STAR>in the WHERE condition. When i execute the statement, it returns me no results even though the rows are present in the database.
Does anyone have the solution to using chinese words in the WHERE clause of the select statement to retrieve results with columns which contains chinese characters? Please help me. Thanks everyone. :)
PS: when i cut and paste those characters in the sql database and paste onto java.. it is ??? in questionmarks.. but when i paste them into excel 2000.. its shown as chinese chars again..
please heelppp~~

Greetings,
PS: when i cut and paste those characters in thesql
database and paste onto java.. it is ??? in
questionmarks.. but when i paste them into excelThis is why the SELECT is not returning any results.
You need to set the character encoding set on your
statement and parameters for the characters to be
properly translated. Refer to the charsetName
parameter in the String class constructor in your API
docs and also to
$JDK_DOCS/guide/intl/encoding.doc.html in your JDK
documentation.
2000.. its shown as chinese chars again..Because Office programs are performing the same kind
of character translation with the appropriate MS APIs.
please heelppp~~Regards,
Tony "Vee Schade" Cookis it possible for you to show me some coding examples? i don't really understand what is to be done in order to set the char set and what does it really do.. tried reading up but still dun understand.. :(
pardon my shallow knowledge of java..
ok..
The thing is when i used an insert statement with chinese characters of GBK format hardcoded into the java servlet and then i use the insert statement to insert the chars into the database, it cannot be seen as a chinese word when i off the NJStar. and then it can be searched out with my current form of servlet.. below is my coding of the servlet..
note: i've set my html file to charset = GBK
//prototype of Search engine...
//workable for GBK input and output...
import java.io.*;
import java.io.OutputStream;
import java.io.IOException;
import javax.servlet.http.*;
import javax.servlet.ServletException;
import java.util.*;
import java.sql.*;
import java.nio.charset.Charset;
public class SearchBeta extends HttpServlet {
     private Vector musicDetails = new Vector();
     private String query = "";
     public void service (HttpServletRequest req, HttpServletResponse res) throws IOException, ServletException, UnsupportedEncodingException {
          query = req.getParameter ("T1");
          System.out.println("before:"+query);
          String type = req.getParameter ("D1");//type
          query = req.getParameter ("T1");
          //query = "��";
          System.out.println("after:"+query);
          getResults(type,query);
          System.out.println("locale = :"+req.getLocale());
          res.setContentType ("text/html;charset=GBK");
          PrintWriter out = res.getWriter();
          out.println("<html>");
          out.println("<head>");
          out.println("<body bgcolor = \"black\">");
          out.println("<font face = \"comic sans ms\" color=\"Cornsilk\">");
          if (query.length()==0)
               out.println ("Please key in your search query.");
          else if (musicDetails.size()==0)
               out.println ("Sorry, no results matching your search can be found.");
          else {
               out.println("<center>");
               out.println("<table cellspacing = \"50\">");
               int i = 0;
               //Display the details of the music
               while (i<musicDetails.size()) {
                    Results details = (Results)musicDetails.get(i);
                    String dbArtist = "";
                    String dbAlbum = "";
                    String dbTitle = "";
                    String dbCompany = "";
                    dbAlbum = details.getAlbum();
                    dbTitle = details.getTitle();
                    dbCompany = details.getCompany();
                    dbArtist = details.getArtist();
                    try{
                         dbAlbum = new String(dbAlbum.getBytes("ISO-8859-1"),"GBK");
                         dbTitle = new String(dbTitle.getBytes("ISO-8859-1"),"GBK");
                         dbCompany = new String(dbCompany.getBytes("ISO-8859-1"),"GBK");
                         dbArtist = new String(dbArtist.getBytes("ISO-8859-1"),"GBK");//correct translation.
                    catch(UnsupportedEncodingException e){
                         System.out.print(e);
                         e.printStackTrace();
                    String dbImage_loc = details.getImage();
                    out.println("<tr>");
                         out.println("<td><table>");
                              out.println("<img src=C:\\Program Files\\Apache Group\\Tomcat 4.1\\webapps\\examples\\ThumbNails\\"+dbImage_loc+">");
                         out.println("<tr>");
                              out.println("<th><font color=\"violet\"> Artist: </font></th>");
                              out.println("<td><font color=\"Cornsilk\">"+dbArtist+"</font></td>");
                         out.println("</tr>");
                         out.println("<tr>");
                              out.println("<th><font color=\"violet\"> Title: </font></th>");
                              out.println("<td><font color=\"Cornsilk\">"+dbTitle+"</font></td>");
                         out.println("</tr>");
                         out.println("<tr>");
                              out.println("<th><font color=\"violet\"> Company: </font></th>");
                              out.println("<td><font color=\"Cornsilk\">"+dbCompany+"</font></td>");
                         out.println("</tr>");
                         System.out.println("album: "+ dbAlbum);
                         out.println("<tr>");
                              out.println("<th><font color=\"violet\"> Album: </font></th>");
                              out.println("<td><font color=\"Cornsilk\">"+dbAlbum+"</font></td>");
                         out.println("</tr>");
                         System.out.println("company: "+ dbCompany);
                         out.println("</table></td>");
                    out.println("</tr>");
                    i++;
               out.println("</table>");
               out.println("</center>");
          out.println("</font>");
          out.println("</body>");
          out.println("</head>");
          out.println("</html>");
          out.close();
          //to remove all the elements from the Vector
          musicDetails.removeAllElements();
     //get Searched Music Details and store in Results object which is stored in musicDetails vector
     public void getResults (String type, String searchQuery) {
          try {
               Class.forName ("com.microsoft.jdbc.sqlserver.SQLServerDriver");
               Connection con = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=music","sa","kokkeng");
               Statement stmt = con.createStatement();
               String query = "SELECT * FROM MusicDetails WHERE "+type+" = '"+searchQuery+"'";
               ResultSet rs = stmt.executeQuery(query);
               while (rs.next()) {
                    String artist = rs.getString("Artist");
                    String title = rs.getString("Song");
                    String company = rs.getString("Company");
                    String album = rs.getString("Album");
                    String image_loc = rs.getString("Image");
                    Results details = new Results (artist,title,company,album,image_loc);
                    musicDetails.add(details);
               stmt.close();
               con.close();
          catch (Exception e) {
               System.out.println(e.getMessage());
               e.printStackTrace();
with the above servlet i created, i can search out the data in the database which i've inserted through the insert statement. I still can't search for things i've keyed into the database directly using NJStar..
thank you so much for helping.. really hope any one else who knows the answer to this will reply too... thank you all so much...
-KK

Chinese Characters in ABAP Mapping

Hi All,
I have one problem with chinese characters in ABAP Mapping. Actually there is an ABAP Mapping written in XI which converts IDoc to Idoc Flat file which is provided by SAP and is in the below link.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Chinese characters are properly coming to XI but after this ABAP mapping those characters are being replaced with #. Any idea on this pelase?
Regards,
Dinakar

Hi !
Check this thread:
Unable to get Chinese Characters as output.
Regards,
Matias
ps:please award points if helpful.

Chinese characters does not display in adobe pdf in windows xp machines

Dear All,
I am a application developer using Struts2 framework with jasper reports.Clients want to display chinese characters in the report output pdf documents.
even i could install east asian language (windows xp) support,i did not get the chinese display in the generated pdf file.
In the jasper report viewer the chinese character could be viewed perfectly.but when we save as pdf document the chinese characters are blank
in the generated pdf document.
I did all the procedures specified in forums. but no result.
I could see that when i open the pdf,only helvatica font was used even i put the chinese characters.How could i embed the chinese character in pdf
what is the clear procedure to display the chinese characters in pdf documents?
Thanks and regards,
PKS Rammesh

Hi, there is a pdf tool,(most part of Chinese character supported) you can have a check: http://www.e-iceblue.com/Introduce/pdf-for-net-introduce.html
Good Luck.

Chinese Characters in Netlogon.log -- re-asking

We have 822 occurrences of the following:
[CRITICAL] I_NetlogonLdapLookup: unrecognized character <Chinese characters>
in the last 2 days. The previous thread on this subject was marked "Answered" without being answered, so I'm re-asking:
1. Does anyone have any substantive information about what's sourcing this?
2. How can I associate a source IP with a single entry in the netlogon.log?
Here's what we know so far:
We have a Chinese linguist who has broken the character string down to 2 sections, the first being the same for all occurrences and the second being random-looking. He says the first section refers to "boats" or "water" and is looking
farther, but he says the string definitely looks like virus-like activity.
Second, I_NetlogonLdapLookup is a function inside netlogon.dll, so intuition says something is trying to do an LDAP lookup on the Chinese character string. We are looking into exactly how that function is supposed to be called (we're network guys, not
coders, so this may take longer than it should). Can someone help shorten this search?
C: There's no consistent contextual activity surrounding the actual log entries, so we're expecting to find out that there's more than one source, so it's extra important we figure out how to associate a source IP with these [CRITICAL] log entries,
especially since we may be looking for a root kit or something else that's able to hide from our multiple AV programs.
Assistance is appreciated, good analytical step-oriented result-generating assistance is GREATLY appreciated!
Robert
Oh yeah -- this is being logged on a DC in a 2008R2 domain with a small but growing number of 2012 member servers and almost no remaining servers lower than 2008R2. I can provide more details if anyone needs them

Hi all --
OK. It looks like we're all on the same page.
Here's a summary of the issue:
netlogon.log [CRITICAL] entry is reporting a failed attempt to execute an LDAP lookup on a Chinese character string (I_NetlogonLDAPLookup is a function inside netlogon.dll). There are no audit failures or other Event Log warnings or errors associated
with the log entries, so it's likely that the lookup is being performed after logging on to the domain with valid credentials. We don't think the character string is corrupted data because the first half of the string is identical in every
log entry and the total number of characters used across all occurrences is very small). Also, the variations in the 2nd half of the string are methodical and repetitive.
We hoped that translating the Chinese string would yield a clue pointing to the source of the attempted LDAP lookup. That didn't happen so we now must figure out how work back from the netlogon.log entry to the source platform.
The current situation:
The [CRITICAL] entries continue to be logged.
The distribution across 3 days of logs is making it look like we need to assume not one, but multiple sources.
I appreciate the standard advice re: 3rd-party AV software, DC build practices, security scans, power erasers and the like, but we are a QA/Test lab for a very complex product; scientific method and the need for operational stability preempts
us taking any corrective actions on any of our DCs (8 machines, 4 domains, 2 forests), Exchange servers (4 versions, 2 clusters per version) , Lync (2 versions), OCS, PKI, WSUS, DNS, DHCP, DHCPv6, SQL, or member servers until we actually prove that the machine in
question is a source of the bogus lookup attempts.
Paul -- I REALLY appreciate your straightforward no-bs reply. I can work with "I don't know" . Try-this-article-I-just -Googled Whack-A-Mole easter egg hunts, however.... <grin>
I'm going to close with one last (hopefully ) simple question: Where do I start the search for the UberSME who knows how to read the netlogon.log - specifically how to connect an event with its legitimate predecessor. Somebody
wrote the service, somebody knows how to interpret its logging output. Where do I start looking for them?
Best Regards,
Robert

Chinese Characters in SQL Plus

Hi, I wonder how do I input the chinese characters in SQL plus? I have set the NLS_LANG value to chinese characterset in the REGEDIT but it doesn't display the chinese characters. Is there any chinese version on Oracle JDeveloper Suite?
Cheers

i have installed sqlplus and oracle db in the same PC under chinese win xp.
i found that if you spool the output to a text file, and type in dos-prompt, it still cannot display the chinese character properly. but if you open the text file by notepad, bingo, you can the chinese character.
i think that it is because dos-prompt application is non-unicode application. so it could not display unicode character properly.
as a result, if you want to display unicode character in non-unicode application (run sqlplus under dos-prompt), you have to set the NLS_LANG environment variable which match the character set of non-unicode application which your operating system assigned. in my case, it should be Big5. then oracle would do the conversion for you automatically, i.e. from unicode in DB to Big5 in client.
I either set the NLS_LANG environment variable in one of the 2 ways:
NLS_LANG=american_america.zht16big5 or
NLS_LANG=american_america.zht16hkscs
Regards,
KH

Chinese characters in PDF download of SAPscript

Hi Friends,
I'm facing an issue while downloading SAPscript output in PDF format. The chinese characters fetched from the SAP tables appear as '#' or some junk value whereas the values hardcoded in script with appropriate character formats appear absolutely fine in PDF. The values fetched from table appear fine when output is taken as normal SAPscript output.
Can someone help me out in this regard. Helpful answers will be rewarded points.
Thanks,
Jaison

CNSONG should work, I use that with Chinese PDFs.
You're using CNPDF so that isn't the problem.
You're Unicode which eliminates a host of other possibilities.
And the characters print fine with non-PDF SAPScripts...
I'm running out of ideas. It sounds like you've done everything you need to.
What method are you using to convert this SAPScript to PDF form? CNPDF Printer, a Function Module, something else? If a FM, which one are you using?
Could it be your Adobe Reader? Does it have the chinese language fonts loaded?

Chinese Characters Printing as Boxes in SAPscript

Issue...why would a Chinese standard text print fine using the "INCLUDE" method, but output as boxes when that same Chinese standard text is retrieved successfully using the "PERFORM" method?
Summary...I am currently experiencing problems printing Chinese characters on a custom SAP Script form. This does not appear to be an issue with printer setup or font selection, as I am able to get the Chinese characters to appear depending on the method I use. The problem occurs when I execute a "PERFORM" within the SAP script to retrieve the Chinese standard text, the results are displayed as boxes. If I "INCLUDE" the standard text directly within the SAP script, the Chinese standard text prints without issue. I have executed the SAP script in debug mode and the Chinese text is being retrieved from the "PERFORM" statement as expected, but just does not display correctly as it does by using the "INCLUDE" approach. I'm trying to understand why the two approaches would not both work in the same manner. We are on a UNICODE system.
Though we may be able to use the "INCLUDE" method in a majority of places, we are interested in using the function "ADDRESS_INTO_PRINTFORM" for printing addresses. This would require passing values back to the SAP script line by line.
Below is a simplified version of the two methods...
(PRINTS CHINESE CHARACTERS AS EXPECTED)
INCLUDE 'ZADDRESS_LINE1' OBJECT 'TEXT' ID 'ST' LANGUAGE &NAST-SPRAS& PARAGRAPH IG
(RESULTS IN BOXES BEING PRINTED)
PERFROM GET_TEXT IN PROGRAM ZGET_CHINESE_TEXT
USING &NAST-SPRAS&
CHANGING &ADDRESS_LINE1&
ENDPERFORM.
&ADDRESS_LINE1&
(&ADDRESS_LINE1& contains Chinese characters as expected when debugging SAP script)
FORM GET_TEXT TABLE PT_IN STRUCTURE ITCSY
PT_OUT STRUCTURE ITCSY
...USE FUNCTION 'READ_TEXT' TO RETRIEVE CHINESE TEXT FROM ZADDRESS_LINE1 STANDARD TEXT (works as expected)
read table pt_out index 1.
move ADDRESS_LINE1 to pt_out-value.
modify pt_out index 1.
(PT_OUT table is populated with chinese text as expected)
ENDFORM.

Language for form is 'ZH'.
To clarify the original post, the standard text is being retrieved correctly for both methods. By this I mean that during debugging of the SAP script I can see the Chinese text as expected for both methods. However, during print preview only the "INCLUDE" method displays correctly. I have both methods included in my current script for the same standard text and the "INCLUDE" displays fine, but not the "PERFORM" method.
Does the "CHANGING" parameter which is populated by the "PERFORM" need to be defined in a particular way? Might there an issue with the TDSYMVALUE type that is used for storing the values retrieved from the "PERFORM"?

CMD outputs in chinese characters

Similar Messages

Maybe you are looking for