- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NLS settings
Operating System - HP-UX
1821541
Members
2550
Online
109633
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2001 04:08 AM
05-29-2001 04:08 AM
NLS settings
Hello friends,
I have a Oracle Database set-up on HP-UX 11.01 m/c with the following NLS parameters,
nls_language = american
nls_territory = america
NLS_CHARACTERSET = UTF8
Now I have inserted some Arabic characters into one of the tables through my VB application running on Arabic-enabled Windows 2000 server. When I query through my application I can see proper arabic characters on my Windows 2000 server PC. But when I start a telnet client on my Windows 2000 server PC and connect to Database through SQL*PLUS from my telnet-client, I see only ???? ( question marks) on the screen. Can anybody tell me any specific settings required to be done for the tty of my telnet session to view proper arabic characters.
I even tried settings like LC_ALL=C.utf8
stty cs8 -istrip
but this didn't work :-(
Thanks in advance
Amit Kureel
I have a Oracle Database set-up on HP-UX 11.01 m/c with the following NLS parameters,
nls_language = american
nls_territory = america
NLS_CHARACTERSET = UTF8
Now I have inserted some Arabic characters into one of the tables through my VB application running on Arabic-enabled Windows 2000 server. When I query through my application I can see proper arabic characters on my Windows 2000 server PC. But when I start a telnet client on my Windows 2000 server PC and connect to Database through SQL*PLUS from my telnet-client, I see only ???? ( question marks) on the screen. Can anybody tell me any specific settings required to be done for the tty of my telnet session to view proper arabic characters.
I even tried settings like LC_ALL=C.utf8
stty cs8 -istrip
but this didn't work :-(
Thanks in advance
Amit Kureel
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2001 08:40 AM
05-29-2001 08:40 AM
Re: NLS settings
Amit,
I don't have any definite answers for you, but I can offer several suggestions which might help explain the situation.
It would appear that you have configured your database to encode characters internally in the UTF-8 (or Unicode) character set, which allows Arabic, English, and most other characters to coexist within the same environment. Your Windows 2000 application is then able to view the Arabic characters, because Windows 2000 uses an implementation of Unicode for its native format, so your Oracle database is able to convert the UTF-8 characters to the Windows 2000 native format and back without any loss in consistency.
However, the problem arises when you are attempting to display in a terminal (ie, telnet) application, and the problem is twofold:
1) Your telnet application needs to understand the Arabic character set. I do not know if there are any telnet applications which support this.
2) If your telnet application does support the Arabic character set (ie, iso8859-6), you *might* be able to set your LANG variable to ar_SA.iso88596, and hopefully the SQL*Forms program will convert the UTF-8 characters to the appropriate character set (ISO8859-6) and display them correctly to your screen.
I know this isn't a definite answer, but I hope this is at least a place to start.
I don't have any definite answers for you, but I can offer several suggestions which might help explain the situation.
It would appear that you have configured your database to encode characters internally in the UTF-8 (or Unicode) character set, which allows Arabic, English, and most other characters to coexist within the same environment. Your Windows 2000 application is then able to view the Arabic characters, because Windows 2000 uses an implementation of Unicode for its native format, so your Oracle database is able to convert the UTF-8 characters to the Windows 2000 native format and back without any loss in consistency.
However, the problem arises when you are attempting to display in a terminal (ie, telnet) application, and the problem is twofold:
1) Your telnet application needs to understand the Arabic character set. I do not know if there are any telnet applications which support this.
2) If your telnet application does support the Arabic character set (ie, iso8859-6), you *might* be able to set your LANG variable to ar_SA.iso88596, and hopefully the SQL*Forms program will convert the UTF-8 characters to the appropriate character set (ISO8859-6) and display them correctly to your screen.
I know this isn't a definite answer, but I hope this is at least a place to start.
I think, therefore I am... I think!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP