UTF8 as system default character set

Hi,
I'm new to OSX and I moved to a new company few days ago. We work with Tiger workstations and servers, several Linux internet servers and Windows Laptops.
One of the problems I have is to find a way to set UTF8 as the default character set for the system, not just user level preferences. That would solve many of my other problems.
There is probably an easy way to do that?!!
Any tip or trick would be greatly appreciated.
Thanks.

One of the problems I have is to find a way to set UTF8 as the default character set for the system, not just user level preferences. That would solve many of my other problems.
What are your problems exactly? If you give some specifics, someone can probably help.
Generally speaking Unicode UTF-8 is what OS X uses by default for a lot of things. The exception would be the file system, which uses UTF-16 NFD. There is certainly no way to change that.

Similar Messages

System wide default character set

Hi,
I moved to a new company few days ago where we use Tiger workstations and servers.
I've been trying to figure a way to set UTF8 as the default character set for a whole system, not just a user preference.
I suppose there is a way to do that, but I'm afraid I won't have more time to find it.
Any help is welcome.
thx fred

I've been trying to figure a way to set UTF8 as the default character set for a whole system, not just a user preference.
If you could explain exactly why you think you need to do that, someone might be able to help.
Generally speaking Unicode UTF-8 is what OS X uses by default for a lot of things. The exception would be the file system, which uses UTF-16 NFD. There is no way to change that.

Change default character set of JVM

Is there a way to change the default character set of JVM to say, UTF-8?
System.out.println("Default Character Set: " + new java.io.OutputStreamWriter(new java.io.ByteArrayOutputStream()).getEncoding());
System.out.println("File Encoding: " + System.getProperty("file.encoding")); On Windows
==========
Default Character Set: Cp1252
File Encoding: Cp1252
On Linux
========
Default Character Set: ASCII
File Encoding: ANSI_X3.4-1968
I would like to save on the effort of changing the many lines of code that looks like
new BufferedWriter(new OutputStreamWriter(out)); to
new BufferedWriter(new OutputStreamWriter(out, "UTF-8")); Thanks

Try this:
-Dfile.encoding=utf-8
as vm argument.
/Kaj

[SOLVED] default character set in mousepad

Is there a way to set the default character set in mousepad? I want it to always save in utf-8, but it defaults to iso-8859-1.
It's a big pain when you're trying to save something that you've copied from a browser. I always have to go back and type the filename again (and change to utf-8) after getting the error message about not being able to save.
Also, is there a way to set the default locale to utf-8 instead of iso-8859?
Last edited by mrbug (2008-10-31 16:18:12)

You put me on the right track; the problem was that I left the .utf8 part out of the LC_ALL= line in /etc/profile
EDIT: Oops, accidentally put a - between utf and 8. That won't work!
Last edited by mrbug (2008-10-31 16:25:35)

Default character set

I installed the database 10.2.01 with basic installation (not advanced option).
what is the default charater set in the basic installation?
how to show character set in command line?
Can I change it to AL32UTF8?
like:
SQL>alter database character set AL32UTF8;
Thanks

thanks.
I'm using Linux
So default character is "WE8ISO8859P1".
But it seems I can not alter to AL32UTF8, which has the globalization support.
SQL> select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
VALUE
WE8ISO8859P1
SQL> alter database character set AL32UTF8;
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
----------------------

What affects the default character set environment of JVM?

For Example, String.getBytes(); since not specify the characterset, so will use the system default characterset. what is this system default characterset affected by? I have tried in Linux Platform, which is LANG environment variable. Is this right? What about other platforms?
And also, are there some JVM parameters can override the default settings of system default characterset? I have tried -Dfile.encoding but found no effect.
Thanks!

Hi,
I guess it can be Uni CODE.
Regards
Prashant

Default Character Set using JSObject

Hi All,
This problem has been nagging me for a while and am now resorting to this forum for an answer.
I have a jsp page with an embedded applet. Inside the applet, I read the HTML page using JSObject.
The problem is when using the JSObject to get values of controls from the HTML page with Japanese characters.
The HTML page is encoded in UTF-8, however, when I get values from the controls using JSObject in the applet, the values returns as ???. Latin characters are supported but not Japanese characters. So.. I'm wondering what character set the JSObject supports when converting a Javascript string to a Java String.
The following code is executed:
          JSObject win = JSObject.getWindow(this);
          JSObject doc = (JSObject) win.getMember("document");
          JSObject forms = (JSObject) doc.getMember("forms");
     JSObject form = (JSObject)forms.getSlot(0);
          JSObject title = (JSObject)form.getMember("title");
String titleValue = (String)title.getMember("value");
I've also tried form.eval("document.forms[0].title.value") and that returns the same ??? for japanese characters.
Any ideas?
Kent

Hi Larry,
The characters that appear at the beginning of each file - ï»¿ - is the BOM or byte order mark for UTF-8, which is automatically added to the file on creation. These files are UTF-8 encoded, to allow for the support of multi-byte characters. An updated version of the Exporter Tool removes these BOM characters. Please contact Support to obtain this updated version of the Exporter tool.
Alternatively, you can try the following:
If the character set of your Oracle database is not UTF-8, then you have two options:
1) If possible, change the character set of your database to UTF-8. To check the current database characterset, check the "NLS_DATABASE_PARAMETERS" table.
or
2) Open the generated .dat files using Notepad, then use the File | Save As menu option, and set the "Encoding" to ANSI, then save the file. The BOM will now be removed from the .dat files.
I hope this helps.
Regards,
Hilary

How do i change the default character set?

I'm from Brazil, and here we have special characters like "�", "�", "�", etc.
I need the JVM to understand that from the database and print it correctly on my page (I'm using servlets).
How do i do that?
thanks to all.

java works just fine with Brazilian characters....I
should know I developed software for a brazilian
company for the last 5 years using java.
Ok. I believe you do. I just wanna know how. i'm using servlets. So, to print out the page, i use.
PrintWriter out = response.getWriter();
out.println("some_text");
out.println(resultset.getString("some_field"));
If "some_text" contains special characters, they are printed correctly. No problem about that.
the problem is when the string from the database/resultset has special characters. Those aren't printed correctly. And that's what i want to fix.
Any suggestions?

Use of UTF8 and AL32UTF8 for database character set

I will be implementing Unicode on a 10g database, and am considering using AL32UTF8 as the database character set, as opposed to AL16UTF16 as the national character set, primarily to economize storage requirements for primarily English-based string data.
Is anyone aware of any issues, or tradeoffs, for implementing AL32UTF8 as the database character set, as opposed to using the national character set for storing Unicode data? I am aware of the fact that UTF-8 may require 3 bytes where UTF-16 would only require 2, so my question is more specific to the use of the database character set vs. the national character set, as opposed to differences between the encoding itself. (I realize that I could use UTF8 as the national character set, but don't want to lose the ability to store supplementary characters, which UTF8 does not support, as this Oracle character set supports up to Unicode 3.0 only.)
Thanks in advance for any counsel.

I don't have a lot of experience with SQL Server, but my belief is that a fair number of tools that handle SQL Server NCHAR/ NVARCHAR2 columns do not handle Oracle NCHAR/ NVARCHAR2 columns. I'm not sure if that's because of differences in the provided drivers, because of architectural differences, or because I don't have enough data points on the SQL Server side.
I've not run into any barriers, no. The two most common speedbumps I've seen are
- I generally prefer in Unicode databases to set NLS_LENGTH_SEMANTICS to CHAR so that a VARCHAR2(100) holds 100 characters rather than 100 bytes (the default). You could also declare the fields as VARCHAR2(100 CHAR), but I'm generally lazy.
- Making sure that the client NLS_LANG properly identifies the character set of the data going in to the database (and the character set of the data that the client wants to come out) so that Oracle's character set conversion libraries will work. If this is set incorrectly, all manner of grief can befall you. If your client NLS_LANG matches your database character set, for example, Oracle doesn't do a character set conversion, so if you have an application that is passing in Windows-1252 data, Oracle will store it using the same binary representation. If another application thinks that data is really UTF-8, the character set conversion will fail, causing it to display garbage, and then you get to go through the database to figure out which rows in which tables are affected and do a major cleanup. If you have multiple character sets inadvertently stored in the database (i.e. a few rows of Windows-1252, a few of Shift-JIS, and a few of UTF8), you'll have a gigantic mess to clean up. This is a concern whether you're using CHAR/ VARCHAR2 or NCHAR/ NVARCHAR2, and it's actually slightly harder with the N data types, but it's something to be very aware of.
Justin

Export using UTF8 character set

Hi,
My client is having a production database with default character set.
While exporting I need to export the database to create a dump with UTF8 character set.
Please let me know how to export with UTF8 option.
Thanks....

Hi, I am not sure if I got you correst. Here is what I think I have understood:
- your client has a db which uses UTF8 as character set.
- you want to export and make sure that there is no conversion taking place.
for this you must set NLS_LANG variable in the shell from where you call exp, resp. expdp properly.
NLS_LANG is composit and consists of:
NLS_LANGUAGE_NLS_TERRITORY.NLS_CHARACTERSET
In a bash this would look like this:
$ export NLS_LANG=american_america.UTF8
In other shells you might need to first define the varaible and then export:
$ NLS_LANG=american_america.UTF8
$ export NLS_LANG
What you also need to know is that you influence the behavior for decimal separator and grand separator in numeric values and a few more settings by specifying NLS_TERRITORY.
For instance NLS_TERRITORY uses a "." as decimal separator and a "," as grand separator for numeric values.
This can be a pitfall! If you have the wrong territory specified then it might destroy all you numerics!
Hope this helps,
Lutz

Can Firefox be set to use the system default printer?

I would really like it of Firefox would use the system default printer set in the control panel, similar to the way office programs do. Is there no setting in about:config to do this? Or an add-on perhaps?

I really, really wish Firefox would change this, but I did find one thing.
In about:config I set:
print.print_printer to null
print.save_print_settings to false
Now it seems to use the system default. And it doesn't remember any changes with in a session, or from one session to the next. It always uses the system default printer.
I realize different people have different preferences. But on my system the default printer changes automatically depending on what wireless network I'm on at the moment. I wanted Firefox to reflect that.

Oracle character set confused

Dear all:
We installed the Latest NW7.0 SR3 for EP&EP core for my Portal application. After that ,i found that our oralce default character set is UTF-8. But some of other Java codes(Iviews,pages..which we developed on Tomcat envionment.)are based in the environment of Oracle character set ZHS16GBK. So iam confused that The NW7.0 SR3 can only install in 64bit OS and a Unicode system. Can i change the oracle character set from UTF8 to ZHS16GBK. Or how can i install the SAP system whose oracle basing on character set ZHS16GBK.
Thanks everyone.

Hello Shao,
ok lets clarify some things at the beginning.
A SAP Java system is not "only using" the database characterset, it is using the national characterset (column types NCHAR, NVARCHAR2, NCLOB). You can check this by reading sapnote #669902.
You can also check sapnote #456968/#695899 for the supported super sets:
=> As of SAP Web AS Release 7.00 and Oracle client 10g, multibyte character sets are no longer supported
With these informations you can not use ZHS16GBK.
> But some of other Java codes(Iviews,pages..which we developed on Tomcat envionment.)are based in the environment of Oracle character set ZHS16GBK
Sorry but i don't understand this sentence.
What is your problem with the java code? Do you have custom tables with column types CHAR,VARCHAR2 or CLOB?
Regards
Stefan

Reports 9i and character set

We have reports in character set WINDOWS 1251
But iAS do they in UTF 8.
We tried to set character set in uifont.ali, but there was not effect.
How to change default character set from UTF8 to WINDOWS 1251 ?
Environment:
iAS 9i R2
nls_lang=AMERICAN.CL8MSWIN1251
uifont.ali:
COURIER....UTF8=COURIER....CL8MSWIN1251

Laura,
First, You can run the 6i reports with OGD in reports 9i, provided you have your Oracle 6i home is in system path
and the regsitry variable ORACLE_GRAPHICS6I_HOME is set to pint your 6i oracle home
Now, if you wan to open these 6i report with OGD and modify the report in 9i builder, then the OGDs are loast when saving this reports from 9i
buikder, so you would need to recreate the graphs using the graph wizard
Thanks
The Oracle Reports Team

(V8) ORACLE8의 CHARACTER SET의 변경에 대하여

제품 : ORACLE SERVER
작성날짜 : 1997-08-26
Oracle8의 Character Set의 변경에 대하여
Oracle7에서 수행하던 DB의 DB character set(이하 dcs)을 변경하는 방법이
Oracle8에서는 공식적으로 지원하는 command로 변경되었습니다. O7에서는
props$ table의 값을 바꿈으로써 dcs를 바꾸던 방법의 결점은 다음과 같습니다.
1) 새로운 dcs가 올바른 dcs가 아닐 경우, DB를 다시 구동할 수 없슴.
2) 새로운 dcs가 이전 dcs의 super set이 아닐 경우, 새로운 dcs와의
character encoding 호환성 문제로 DB에 저장된 data를 올바른 의미
또는 올바른 값으로 사용할수 없슴.
3) dcs의 호환성 문제로 DB의 crash
물론 위의 문제는 dba의 능력에 따라 발생하지 않을 수도 있습니다. 이런 종류의
모든 문제를 해결하기 위해 O8에서는 dcs와 관련된 table들의 값을 변경하기
이전에 새로운 dcs가 올바른가를 확인하고, 새로운 dcs가 이전 dcs의 super set
인가를 확인하여 모든 것이 정상일 때에만 dcs의 값을 변경할 수 있게 하는 절차를
제공하게 되었습니다.
여기에서 super set이란 A라는 char set에 있는 모든 character가 B라는 char
set에서 똑같은 code 값으로 존재할 때 B는 A의 super set이라 합니다.
즉 한국 환경에서는 다음의 경우가 해당됩니다.
1) ko16ksc5601은 us7acsii의 super set이다.
2) utf8(unicode 2.0의 변형)은 us7ascii의 super set이다.
3) utf8은 ko16ksc5601의 super set이 될 수 없다.
- utf8의 code range는 ko16ksc5601의 super set이지만, code value는
같지 않으므로 dcs 변경 시의 super set은 아니다.
기존의 DB가 us7ascii이고 client 역시 us7ascii를 사용하여 한글 데이타를
DB에 저장시킨 경우 대부분 ksc5601 encoding scheme을 사용하여 한글을
입력시킵니다. 이 때 DB에 입력된 "가"는 0xb0a1으로 저장되는데, 이 DB를
ko16ksc5601으로 변경시키면 ksc5601에서 역시 "가"의 code 값은 0xb0a1이므로
변경된 DB는 정상적인 동작을 하게 된다.
그러나, utf8 encoding scheme을 이용하여 "가"를 입력시키면 DB에는 0xeab080
으로 입력되므로 DB를 ko16ksc5601으로 변경시킨 경우 client에서 이 값을
access하면 다음의 경우가 발생합니다.
1) utf8을 지원하는 기계에서 ko16ksc5601을 이용하는 경우
-> 이전에 입력된 "가"를 볼수 있음
2) 1)을 제외한 경우 정상적으로 data의 의미를 해석할수 없음.
즉 이전 DB에 data의 입력 방식이 ksc5601인 경우 DB를 ko16ksc5601으로
변경하면 아무런 문제 없음. 그리고 이전 DB에 utf8의 입력 방식을 사용한 경우,
DB를 utf8로 변경하면 문제없음. 즉 한국 환경에서는 us7ascii에서
ko16ksc5601으로 변경하는 경우와 us7ascii에서 utf8으로 변경하는 두가지
경우 밖에 존재하지 않는다.
1) us7ascii ----> ko16ksc5601
2) us7ascii ----> utf8
또한 O8에서는 DB의 database character set(dcs) 이외에 national character
set(ncs) 이라는 secondary character set을 지원합니다. 이것의 특징은
문자의 길이가 고정되어 있다는 것입니다. 즉, table 생성 시 특정 column을
nchar 혹은 nvarchar2로 선언하여 입력 시 N'a가'라는 data가 입력되면 이 값은
내부 처리 시, 저장 시, 외부 출력 시 0xa3e1 0xb0a1이라는 문자 당 고정 길이를
갖는 값으로 변경된다. 물론 이런 형태의 지원은 성능 향상을 위한 것이다.
이런 nchar, nvarchar2의 encoding scheme 역시 data base가 생성될 때
지정되고, DB의 dcs과 같은 방법으로 변경될 수 있다. 한국 환경에서 사용할 수
있는 ncs는 ko16ksc5601fixed와 ko16dbcsfixed라는 두 가지가 있는데 이것들은
Oracle 8.0.4부터 지원된다. 그런데 문제는 national char set 변경 시 역시
super set으로 밖에 변경할 수 없다는 제약이 있는데, 일반적인 설치 시 DB의
dcs와 같은 값으로 ncs가 지정된다.
1) ko16ksc5601fixed는 us7ascii의 super set이 아니다.
2) ko16ksc5601fixed는 ko16ksc5601의 super set이 아니다.
3) ko16ksc5601fixed는 utf8의 super set이 아니다.
그러므로 ncs를 ko16ksc5601fixed 혹은 ko16dbcsfixed로 지정하고자 하는
경우에는 DB의 생성 시 지정할 수 밖에 없다. 즉 "create database ..."에
반드시 지정되어야 한다.
또 한가지 고려 사항은 dcs와 ncs의 관계인데, 서로 다른 dcs를 사용하는
server/server, server/client의 경우 code conversion의 주체는 dcs이다.
즉 ncs는 dcs의 값으로 변경되어 상대방의 dcs로 변경되고, 이것은 다시 ncs로
변경되어 DB에 저장된다. 즉 ncs의 code 범위가 dcs보다 크다면 dcs에 포함되지
않는 ncs의 값은 default replacement character인 ?로 대치되어 전달된다는
것이다. dcs와 ncs의 관계는 code range가 초점이 된다.
1) us7ascii(dcs)에 ko16ksc5601fixed(ncs)를 사용할 수 없다.
2) utf8(dcs)에 ko16ksc5601fixed(ncs)를 사용하면 char를 nchar로 변경 시
data를 loss을 가져올 수 있다.
3) ko16ksc5601(dcs)에 ko16ksc5601fixed(ncs)의 사용은 문제 없습.
4) utf8fixed 형태의 char set은 현재까지 지원되지 않음.
Oracle8의 Character Set의 변경 시 지원되는 command
기존 DB의 char set이 us7ascii인 경우 DB char set의 변경은 ko16ksc5601
혹은 utf8으로 밖에 변경시킬 수 없다.
svrmgr>
svrmgr> shutdown
svrmgr> startup mount exclusive
svrmgr> alter system enable restricted session;
svrmgr> alter database open;
svrmgr> alter database character set KO16KSC5601;
or
svrmgr> alter database character set UTF8;
svrmgr> shutdown
svrmgr> startup
svrmgr>

XML data from BLOB to CLOB - character set conversion

Hi All,
I'm trying to solve a problem with a character set conversion in PL/SQL in the following scenario:
1. source is an XML as a BLOB variable.
2. target is an XML as a CLOB variable.
3. the problem I have is the following:
- database character set is set to UTF-8
- XML character set could be anything (UTF-8, ISO 8859-1, ISO 8859-2, ASCII, ...)
- I need to write a procedure which converts the source BLOB content into the target CLOB taking into account the XML encoding and converts it into the DB default character set (UTF8).
I've been able to implement a simple conversion function. However, this function expects static XML encoding ISO-8859-1. The main part of the function looks as follows:
buffer := UTL_RAW.cast_to_varchar2(
UTL_RAW.convert(
DBMS_LOB.SUBSTR(source_blob_variable, 16000, pos)
, 'American_America.UTF8'
, 'American_America.we8iso8859p1')
Does anyone have an idea how to rewrite the code to handle "any" XML encoding in the source BLOB file? In other words, is there a function in Oracle which converts XML character set names into Oracle character set values (ISO-8859-1 to we8iso8859p1, UTF-8 to UTF8, ...)?
Thanks a lot for any help.
Julius

I want to pass a BLOB to some "createXML" procedure and get a proper XMLType in UTF8 character set, properly converted from whatever character set is the input in.As per documentation the generated XML has always the encoding set at the client side depending on NLS_LANG (default UTF-8), regardless of the input encoding, so I don't see a need to parse the PI of the XML:
C:\>echo %NLS_LANG%
%NLS_LANG%
C:\>sqlplus
SQL*Plus: Release 11.1.0.6.0 - Production on Wed Apr 30 08:54:12 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> var cur refcursor
SQL>
SQL> declare
2     b   blob := utl_raw.cast_to_raw ('<a>myxml</a>');
3 begin
4     open :cur for select xmlroot (xmltype (utl_raw.cast_to_varchar2 (b))) xml from dual;
5 end;
6 /
PL/SQL procedure successfully completed.
SQL>
SQL> print cur
XML
<?xml version="1.0" encoding="UTF-8"?><a>myxml</a>
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:\>set NLS_LANG=GERMAN_GERMANY.WE8ISO8859P1
C:\>sqlplus
SQL*Plus: Release 11.1.0.6.0 - Production on Mi Apr 30 08:55:02 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> var cur refcursor
SQL>
SQL> declare
2     b   blob := utl_raw.cast_to_raw ('<a>myxml</a>');
3 begin
4     open :cur for select xmlroot (xmltype (utl_raw.cast_to_varchar2 (b))) xml from dual;
5 end;
6 /
PL/SQL-Prozedur erfolgreich abgeschlossen.
SQL>
SQL> print cur
XML
<?xml version="1.0" encoding="ISO-8859-1"?>
<a>myxml</a>

UTF8 as system default character set

Similar Messages

Maybe you are looking for