Unicode String in JFrame's Title Bar / why is java a non-Unicode pgm in XP?

My big question:
Why is Java detected as a non-Unicode program by Windows XP?
I need to do the following before I can write Japanese characters on the JFrame's title bar on Window XP:
From the Control Panel -> Regional Settings and Languages -> Set the Language for non-Unicode Program to Japanese
Thanks in advance,
Noel

Hi Noel,
I'm only guessing here, but I suspect this is still the case...
Under JDK1.3, the title bar produced by a JFrame is provided by the Windows OS, rather than Java itself. You'll find that trying to display foreign characters in a JFrame's title bar on an English Windows system nigh on impossible (you're left with everyone's favourite little rectangles instead). AFAIK, Sun were looking to change this in the future, but I've no idea if they've got there yet.
Windows XP likely refers to Java as a non-Unicode program because it's looking at the main frame. Because the frame is produced by Windows itself (which last I checked was about as Unicode-compliant as my car is), it holds a different encoding to anything else within Java.
At least that's my stab in the dark. ;-)
Ta,
Martin Hughes

Similar Messages

Print JFrame without title bar and border

I am trying to print out a JFrame which contains two JPanels. The following code is part of my implementation of Printable which prints the entire JFrame including the title bar and border. I've considered implementing Printable in the JPanel classes but then I don't know how I would get everything on one page as a single image. Is there some way to just print the contentPane of the JFrame?
     public int print(Graphics g, PageFormat pf, int pi)
          throws PrinterException {
          if (pi >= 1) {
               return Printable.NO_SUCH_PAGE;
          Graphics2D g2 = (Graphics2D) g;
          double scaleX = pf.getImageableWidth()/getWidth();
          double scaleY = pf.getImageableHeight()/getHeight();
          double scale = 1;
          g2.translate((int) pf.getImageableX(), (int) pf.getImageableY());
          if (scaleX < 1 || scaleY < 1) {
               scale = scaleX < scaleY ? scaleX : scaleY;
               g2.scale(scale,scale);
          printAll(g2);
          return Printable.PAGE_EXISTS;
     }

Thanks.
I can get the Jframe without the title bar and I can get it to drag on the desktop with your suggestions. I still need it to have rounded edges.

Displaying Jtimer in the title bar of jframe

we have an urgent requirement to display Time (should run continously) and Date in the title bar of the java
application. Please give input..

To update a frame's title, call setTitle:
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class TitleUpdater {
    public static void main(String[] args) {
        final JFrame f = new JFrame("TitleUpdater");
        JButton btn = new JButton("press here");
        btn.addActionListener(new ActionListener(){
            int count = 0;
            public void actionPerformed(ActionEvent evt) {
                ++count;
                f.setTitle("pressed: " + count + " times.");
        f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        f.getContentPane().add(btn, BorderLayout.NORTH);
        f.setSize(400,100);
        f.setLocationRelativeTo(null);
        f.setVisible(true);
}

Unicode and non-unicode string data types Issue with 2008 SSIS Package

Hi All,
I am converting a 2005 SSIS Package to 2008. I have a task which has SQL Server as the source and Oracle as the destination. I copy the data from a SQL server view with a field nvarchar(10) to a field of a oracle table varchar(10). The package executes fine
on my local when i use the data transformation task to convert to DT_STR. But when I deploy the dtsx file on the server and try to run from an SQL Job Agent it gives me the unicode and non-unicode string data types error for the field. I have checked the registry
settings and its the same in my local and the server. Tried both the data conversion task and Derived Column task but with no luck. Pls suggest me what changes are required in my package to run it from the SQL Agent Job.
Thanks.

What is Unicode and non Unicode data formats
Unicode :
A Unicode character takes more bytes to store the data in the database. As we all know, many global industries wants to increase their business worldwide and grow at the same time, they would want to widen their business by providing
services to the customers worldwide by supporting different languages like Chinese, Japanese, Korean and Arabic. Many websites these days are supporting international languages to do their business and to attract more and more customers and that makes life
easier for both the parties.
To store the customer data into the database the database must support a mechanism to store the international characters, storing these characters is not easy, and many database vendors have to revised their strategies and come
up with new mechanisms to support or to store these international characters in the database. Some of the big vendors like Oracle, Microsoft, IBM and other database vendors started providing the international character support so that the data can be stored
and retrieved accordingly to avoid any hiccups while doing business with the international customers.
The difference in storing character data between Unicode and non-Unicode depends on whether non-Unicode data is stored by using double-byte character sets. All non-East Asian languages and the Thai language store non-Unicode characters
in single bytes. Therefore, storing these languages as Unicode uses two times the space that is used specifying a non-Unicode code page. On the other hand, the non-Unicode code pages of many other Asian languages specify character storage in double-byte character
sets (DBCS). Therefore, for these languages, there is almost no difference in storage between non-Unicode and Unicode.
Encoding Formats:
Some of the common encoding formats for Unicode are UCS-2, UTF-8, UTF-16, UTF-32 have been made available by database vendors to their customers. For SQL Server 7.0 and higher versions Microsoft uses the encoding format UCS-2 to store the UTF-8 data. Under
this mechanism, all Unicode characters are stored by using 2 bytes.
Unicode data can be encoded in many different ways. UCS-2 and UTF-8 are two common ways to store bit patterns that represent Unicode characters. Microsoft Windows NT, SQL Server, Java, COM, and the SQL Server ODBC driver and OLEDB
provider all internally represent Unicode data as UCS-2.
The options for using SQL Server 7.0 or SQL Server 2000 as a backend server for an application that sends and receives Unicode data that is encoded as UTF-8 include:
For example, if your business is using a website supporting ASP pages, then this is what happens:
If your application uses Active Server Pages (ASP) and you are using Internet Information Server (IIS) 5.0 and Microsoft Windows 2000, you can add "<% Session.Codepage=65001 %>" to your server-side ASP script.
This instructs IIS to convert all dynamically generated strings (example: Response.Write) from UCS-2 to UTF-8 automatically before sending them to the client.
If you do not want to enable sessions, you can alternatively use the server-side directive "<%@ CodePage=65001 %>".
Any UTF-8 data sent from the client to the server via GET or POST is also converted to UCS-2 automatically. The Session.Codepage property is the recommended method to handle UTF-8 data within a web application. This Codepage
setting is not available on IIS 4.0 and Windows NT 4.0.
Sorting and other operations :
The effect of Unicode data on performance is complicated by a variety of factors that include the following:
1. The difference between Unicode sorting rules and non-Unicode sorting rules
2. The difference between sorting double-byte and single-byte characters
3. Code page conversion between client and server
Performing operations like >, <, ORDER BY are resource intensive and will be difficult to get correct results if the codepage conversion between client and server is not available.
Sorting lots of Unicode data can be slower than non-Unicode data, because the data is stored in double bytes. On the other hand, sorting Asian characters in Unicode is faster than sorting Asian DBCS data in a specific code page,
because DBCS data is actually a mixture of single-byte and double-byte widths, while Unicode characters are fixed-width.
Non-Unicode :
Non Unicode is exactly opposite to Unicode. Using non Unicode it is easy to store languages like ‘English’ but not other Asian languages that need more bits to store correctly otherwise truncation will occur.
Now, let’s see some of the advantages of not storing the data in Unicode format:
1. It takes less space to store the data in the database hence we will save lot of hard disk space.
2. Moving of database files from one server to other takes less time.
3. Backup and restore of the database makes huge impact and it is good for DBA’s that it takes less time
Non-Unicode vs. Unicode Data Types: Comparison Chart
The primary difference between unicode and non-Unicode data types is the ability of Unicode to easily handle the storage of foreign language characters which also requires more storage space.
Non-Unicode
Unicode
(char, varchar, text)
(nchar, nvarchar, ntext)
Stores data in fixed or variable length
Same as non-Unicode
char: data is padded with blanks to fill the field size. For example, if a char(10) field contains 5 characters the system will pad it with 5 blanks
nchar: same as char
varchar: stores actual value and does not pad with blanks
nvarchar: same as varchar
requires 1 byte of storage
requires 2 bytes of storage
char and varchar: can store up to 8000 characters
nchar and nvarchar: can store up to 4000 characters
Best suited for US English: "One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple
encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters."<sup>1</sup>
Best suited for systems that need to support at least one foreign language: "The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world.
All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred
from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly.
https://irfansworld.wordpress.com/2011/01/25/what-is-unicode-and-non-unicode-data-formats/
Thanks Shiven:) If Answer is Helpful, Please Vote

Difference between IN LEGACY TEXT MODE & TEXT MODE ENCODING NON-UNICODE

Hi,
We're upgrading to ECC5 and the 'open dataset' command needs amending if the program is flagged for Unicode (which usually occurrs in user/fm exits). Therefore is ECC5 this command is no longer valid:
"open dataset DSN in text mode"
We currently interface with systems that may not have unicode enabled. Yet we have not enabled unicode in our own system just yet.
So we think these two commands are the most approriate for replacing the 'old' open dataset command:
"open dataset DSN for input in TEXT MODE encoding NON-UNICODE"
"open dataset DSN in LEGACY TEXT MODE for input"
However we're not really sure what the difference between these two commands is?
Has anyone worked with these commands?
Could you offer some help as to their differences and when each should be used?
Many thanks!

Hi Robert,
   Here is an excerpt from sap documentation.
... TEXT MODE ENCODING {DEFAULT|UTF-8|NON-UNICODE}
Effect:
The addition IN TEXT MODE opens the file as a text file. The addition ENCODING defines how the characters are represented in the text file. When writing in a text file, the content of a data object is converted to the representation entered after ENCODING, and transferred to the file. If the data type is character-type and flat, trailing blanks are cut off. In the data type string, trailing blanks are not cut off. The end-of-line marking of the relevant platform is applied to the transferred data by default. When reading from a text file, the content of the file is read until the next end-of-line marking, converted from the format specified after ENCODING into the current character format, and transferred to a data object.
The end-of-line marking depends on the operating system of the application server. In the MS Windows operating systems, the markings "CRLF" and " LF" are possible, while under Unix, only "LF" is used. If, when using Windows, an existing file is opened without the TYPE addition (see os_addition), the first end-of-line marking is found and used for the whole file. If a new file is created without the TYPE addition, the content of the profile parameter abap/NTfmode is used. If the profile parameter is not set, "CRLF" is used. If a file with the TYPE addition is opened and a valid value is contained in attr, this value is used.
In Unicode programs, only the content of character-type data objects can be transferred to text files and read from text files. The addition ENCODING must be specified in Unicode programs, and can only be omitted in non-Unicode programs.
The additions after ENCODING determine in which character representation the content of the file is handled.
DEFAULT
In a Unicode system, the designation DEFAULT corresponds to the designation UTF-8, and the designation NON-UNICODE in a non-Unicode system.
UTF-8
The characters in the file are handled according to the Unicode character representation UTF-8.
NON-UNICODE
In a non-Unicode system, the data is read or written without being converted. In a Unicode system,the characters in the file are handled according to the non-Unicode-codepage that would be assigned to the current text environment according to the database table TCP0C, at the time of reading or writing in a non-Unicode system.
If the addition ENCODING is not specified in non-Unicode programs, the addition NON-UNICODE is used implicitly.
... LEGACY TEXT MODE [{BIG|LITTLE} ENDIAN] [CODE PAGE cp]
Effect:
Opening a Legacyfile. The addition IN LEGACY TEXT MODE opens the file as a legacy text file. As with legacy binary files, the byte order and the codepage with which the content of the file should be handled can also be specified. The syntax and meaning of {BIG|LITTLE} ENDIAN and CODE PAGE cp are the same as for legacy binary files.
In contrast to legacy binary files, the trailing blanks in a legacy file are cut off when writing character-type flat data objects in a legacy text file. As for a text file, an end-of-line marking is also applied to the transferred data. In contrast to text files opened with the addition INTEXT MODE, Unicode programs do not check whether the data objects used for reading or writing are character-type. Furthermore, the LENGTH additions of the statements READ DATASET and TRANSFER are used for counting in bytes in legacy text files and in the units of a character represented in the memory for text files.
Note:
As with legacy binary files, text files that have been written in a non-Unicode system can be accessed in Unicode systems as legacy text files, and the content is converted accordingly.
Example
A file test.dat is created as a text file, filled with data, changed, and exported. As every TRANSFER statement applies end-of-line marking to written content, after the change, the content of the file has two lines. The first line contains "12ABCD". The second line contains "890". The character "7" has been overwritten by the end-of-line marking of the first line.
DATA: file   TYPE string VALUE `test.dat`,
      result TYPE string.
OPEN DATASET file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER `1234567890` TO file.
CLOSE DATASET file.
OPEN DATASET file FOR UPDATE IN TEXT MODE ENCODING DEFAULT
                             AT POSITION 2.
TRANSFER `ABCD` TO file.
CLOSE DATASET file.
OPEN DATASET file FOR INPUT IN TEXT MODE ENCODING DEFAULT.
WHILE sy-subrc = 0.
READ DATASET file INTO result.
WRITE / result.
ENDWHILE.
CLOSE DATASET file.
Regards,
Ravi

Client Copy between unicode system and non-unicode system

Hello,
we have to build up a new system for japan. It is planned to install a new 4.7Ext200 unicode system and then make a client copy from a non-unicode 4.7Ext200 (language= german, english) system to the unicode system. I don't think that this is possible way, but I can't find information regarding client copies from non-unicode to unicode. I would advice the project to convert the existing non-unicode system to unicode, make a system copy for the new system and then install japan languages. Any information, which can help me.
Regards,
Alexander

Hi,
without conversion client copy is not possible
look at following
Re: Client copy between unicode and Non-unicode
regards,
kaushal

Handling Tab Delimited File generation in non-unicode for multi byte lang

Hi,
Requirement:
We are generating a Tab Delimited File in different languages (Single Byte and Multi Byte) and placing the files at application server.
Problem:
Our system is a Non-unicode system so we are facing problems with generation of Tab delimited file for multibyte languages like Russian, Japanese, Chinese etc.,
I am actually using data: d_tab TYPE X value '09' but it dont work for multi byte. I cant see tab delimited file at application server path.
Any thoughts about how to proceed on this issue?Please let me know.
Thanks & Regards,
Pavan

>
Pavan Ravikanti wrote:
> Thanks for your answer but do you reckon cl_abap_char_utilities will be a work around for data: d_tab type X VALUE '09' .
> Pavan.
On a non-unicode system the X Variant is working, but not on a unicode system. Here you must use the class. On the other hand you can use the class on a non-unicode system und your char var will always be correct (one byte/twobyte depending on which system your report is running).
What you are planning to do is to put a file with an amount of possible characters into a system with has a less amount of characters. Thats not working in no way.
What you can do is to build up a multi-code-page system where the codepage is bound to the user or bound to the logon-language. Here you you can read and process textfiles in several codepages - but not a textfile in unicode. You have to convert the unioce textfile into a non-unicode textfile before processing it.
Remember that SAP does not support multi-code-page Systems anymore and multi-code-page systems will result in much more work when converting the system to unicode.
Even non-unicode system will not be maintained by SAP in the near future.
What you encounter here are problems for what unicode was developped. A unicode system can handle non-unicode textfiles, but the other way round will always lead to problems which cant be solved.

Can't display non-unicode font

When I try to use Symbol font and display it in JLabel, it show a square.
i have read the article written by John O'Conner
http://www.joconner.com/javai18n/articles/TextDisplay.htm.
Thanks for providing those valuable information. it does help to understand some international issue.
however, I am not sure if it apply to Symbol font such as Wingdings, webdings.
    Font fontPalatino = new Font( "Palatino LinoType", Font.PLAIN, 25); //unicode font
    Font fontMapInfo = new Font( "MapInfo Transportation", Font.PLAIN, 25); // non-unicode font
    Font fontWingdings = new Font( "Wingdings", Font.PLAIN, 25);
          // use integer number and convert into equivalent character
          // e.g. if i is 65 then c is A.
          // notes: 65 is a decimal value converted from hex 0041 value
          int i = 65;
          char c = (char)i;
          System.out.println( new Character(c).toString() );
          JLabel jlbl = new JLabel();
          jlbl.setFont(fontSymbol);
          jlbl.setText( new Character(c).toString() );1) I can't display any Wingdings font , any expert can help on this?
2) what is the difference between 0021(character code for Arial font) and 0x21(character code for Wingdings font) shown in character map?

When I try to use Symbol font and display it in
JLabel, it show a square.
i have read the article written by John O'Conner
http://www.joconner.com/javai18n/articles/TextDisplay.htm.
Much of that article is now incorrect or unnecessary for JDK 1.5. Because 1.5 knows how to find a font for the character you're trying to display, you should be able to set your label font to any logical font, and the JRE should find a substitute font if necessary that can display the character.
I'll give your code a try and will post results...is the code you've posted the code I should actually experiment with? It seems like you should want to display something different than 0x0065.
Your other questions:
0x0021 is the exclamation mark regardless of font. I see what you mean, however, since the wingdings font in charmap also says 0x0021. However, that mapping is obviously not a Unicode code point mapping.
I looked in the Misc. Symbols and Dingbats section of Uncode. A few characters might be a reasonable substitution for the pencil character you want:
0x270E (LOWER RIGHT PENCIL)
0x270F (PENCIL)
0x2710 (UPPER RIGHT PENCIL)
I didn't see any mirror images of these, ie LOWER LEFT PENCIL and UPPER LEFT PENCIL, although I admit that I didn't look closely.
Maybe one of these will work for you instead of the Wingdings 0x21 character you mentioned.
Regards,
John O'Conner

Non Unicode R3 to non Unicode BI

Hi,
We have a Non Unicode R3 system. My question is, should I install a non Unicode BI system or a Unicode BI system while installing NW2004s. We only have English language. What is SAP recommended. What are the pros and cons of installing unicode or non-unicode BI when we have a non-unicode R3 system.
Thanks

Go for Unicode BI if you just have one langauge. Sooner or later, R/3 wull be upgradedd by the client, which would be unicode compatible then!
Regards
Prakash

Kernel change for Non Unicode to Unicode

Hi All,
Is it ncessary to change the Non-Unicode Kernel to Unicode Kernel before before starting the Export for Unicode Conversion?
Regards,
Amit

Hi
Is it ncessary to change the Non-Unicode Kernel to Unicode Kernel before before starting the Export for Unicode Conversion?
No
Niel has made every thing clear
Regards
Uday

From non-unicode to Unicode

I want to read texts in a Unicode SolMan 7 sps20 system that were already saved in a non-Unicode SolMan 3.2 system. When, i tried to open docin solar01, i have a message :"No document opened". Any idea?!

Hi Puneet,
You can convert non-unicode single code page systems to unicode for all SAP Applications and SAP NetWeaver systems. Of SAP NetWeaver you can only convert SAP NetWeaver AS (ABAP) and SAP NetWeaver BI to unicode as all other SAP NetWeaver solutions are unicode only anyway. For the SAP Applications please note that only certain releases can be converted to unicode. For SAP R/3, you have to be at release SAP R/3 Enterprise extension set 2.00 before you can convert to unicode.
The other major restriction is that most but not all databases support unicode - the major exception being Informix.
Also it should be pointed out that you can do a conversion in place and therefore do not need to do an application migration (it is simply an export with conversion and a reload into the new database).
Al the requirements and conversion steps are covered in conversion guides found on the service marketplace. http://service.sap.com/unicode@sap -> Unicode Library -> Unicode Conversion Library
I hope this helps,
Mike.

Transport request from non-unicode to unicode

Hi
In our BW landscape we have Development and Production server.
Unfortunately the development server was installed on BW 3.5 with NonUnicode
and production on BW 3.5 with UNICODE option..
We inderstand the architecture change, but we are using only ENGLIGH language in our envn.. Do we still need to do a unicode conversion on our development server ??
I understand that as long as I am using single language & single codepage, I will be needing a unicode conversion
Kindy let me know your feedback..
Thanks & Regards
Madhu

Hi,
We are having a running landscape of non-unicode system.
Now, Another Landscape is being used by parent company of Unicode Systems. Now, All data, programs, objects are being configured on the parent company server. So, there is no chance to migrate non-unicode to unicode.
But, We have to apply all packages developed on Non-unicode system to Unicode System. I have released that request and copied data file and cofile into target developement System (Unicode) then imported on this Server.
Now, we are facing this problem (Above mentioned.). I think, there must be a solution for it conceptually.
Regards
Dharmendra

Double byte language i.e Japanese or Chinese text in non Unicode System

Hi,
I have translated text into Chinese and Japanese in a Unicode system and want to move it into a non Unicode system. Would Chinese/Japanese characters display correctly in a non Unicode system when moved from Unicode system. I am doing translation in ECC60 or SAP 4.7 Unicode system and moving to SAP 4.7 non Unicode system.
Thanks
Balakrishna

Hi Balakrishna,
in general the transport between Unicode and Non-Unicode systems is supported.
However there are restrictions, which are outlined in SAP note 638357.
In your case it is a prerequisite that the objects to be transported are language dependent (text lang. flag is set on the language key - see SAP note 480671) and the languages are properly setup in the target systems.
For double byte data there is a specific issue when transferring data from Unicode to Non-Unicode:
In a Non-Unicode system, one double-byte character needs two bytes, therefore e.g. in a 10 char field, 5 double byte chars are fitting. In a Unicode system, you can insert 10 double-byte chars in a 10 char field. Hence there is a risk of truncating characters in case of Unicode --> Non-Unicode communication.
Please also have a look at SAP notes 1322715 and 745030.
Best regards,
Nils

Unicode in the Title bar of JFrame

Hi
I have a unicode application and I am using the font Arial Unicode MS. I want to show unicode charecters in the title of my JFrame. I am able to show unicode chars in all other controls except for the title of the main JFrame.
I read several posts on the forum and came to an understanding that, the title bar of the JFrame is controlled by the OS.
So I changed the fonts used in my windows also to Arial Unicode MS. But still I see only ??? in place of unicode characters.
Need urgent help.
Thanks
Vineet

import java.awt.*;
import javax.swing.*;
public class X {
    public static void main(String[] args) {
        JFrame.setDefaultLookAndFeelDecorated(true);
        JFrame f = new JFrame("ABCabcXYZxyz");
        Font font = new Font("Lucida Bright", Font.BOLD|Font.ITALIC, 14);
        Container cp = f.getContentPane();
        JLayeredPane lp = f.getLayeredPane();
        for(int i=0, ub=lp.getComponentCount(); i<ub; ++i) {
            Component child = lp.getComponent(i);
            if (child != cp)
                child.setFont(font);
        f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        f.setSize(500,400);
        f.setLocationRelativeTo(null);
        f.setVisible(true);
}1. You have to use a LAF that draws its own title bar. If your platform is drawing your title bar, you'll
have to go the JNI route :-(
2. If you have a menu bar, it'll be in the layered pane as well, so you'll have to skip over the way
content pane is skipped over...

How to change the image in title bar for JFrames

plz give me a small code to change the image of the JFrame in the Title bar.
i know how to change the name of the title bar .
import javax.swing.*;
class Rathna1 extends JFrame
Rathna1()
super("rathna project ");
public class Rathna
public static void main(String ax[])throws Exception
Rathna1 r=new Rathna1();
r.setVisible(true);
r.setSize(400,400);
Like this how to change the image of the title bar
Message was edited by:
therathna

hi,
JFrame frame;
frame.setVisible(true);
frame.setIconImage(new ImageIcon("icons/img007.gif").getImage());
frame.setSize(800,600);
i think the thing u r searching is :
frame.setIconImage(new ImageIcon("icons/img007.gif").getImage());
~~~radha

Unicode String in JFrame's Title Bar / why is java a non-Unicode pgm in XP?

Similar Messages

Maybe you are looking for