Unicode support of OAS

Hi,
We are involved in the development of a multilingual web application. We are running some cartridges in the OAS. If its an unicode based solution and the cartridge running over the OAS is capable of understanding unicode, is it necessary that OAS should also be an unicode compliant one.. we use oracle 8 which supports unicode.. if OAS is to unicode compliant one then from which version does it supports..
Thanks...

Hi Gaikwad,
Please check matts reply and the document for Dynamic Formatting in this thread:
Re: Cell format information through SDK API
Regards,
---Satish

Similar Messages

How to know whether my oracle 10g instalation in unicode supported or not

Hi
i am new to oracle. I have installed Oracle 10g client and server.
I want to know whether the database created can store unicode data/arabic data.
Please guide me how can i find whether unicode support is on for my db or not.
The outputs of some of the queries run by me are as follows:
SQL> HOST ECHO $NLS_LANG;
$NLS_LANG
SQL> HOST ECHO %NLS_LANG%;
%NLS_LANG%
SQL> @.[%NLS_LANG%];
SP2-0310: unable to open file ".[AMERICAN_AMERICA.WE8MSWIN1252]"
SQL> select cust_eng_name,cust_arb_name from custmast;
select cust_eng_name,cust_arb_name from custmast
ERROR at line 1:
ORA-00942: table or view does not exist
Please reply me asap.

user10817093 wrote:
1. Yeh that is the thing I want. What are the other steps that i need to do with my Oracle Client/Server for unicode support.
Where i am getting trouble is the Oracle Client/Server unicode support.
And how to decide what character set will suite me best.1. If your application is going to be a "true" Unicode application, you can set the NLS_LANG registry/environment setting on your clients to ".UTF8" to enable true Unicode support.
2. Your database needs to support Unicode, too.
The recommended database character set for this in 10g is "AL32UTF8".
If you currently have a single-byte database character set (WE8MSWIN1252), you need to decide how to get this done.
If you can simply create a new database using the "AL32UTF8" character set, this would be the easiest way.
There are several documents available (e.g. on Oracle MetaLink) that describe in detail how to convert the character set of an existing database. Depending on your data this can be a tedious task involving several steps, so may be creating a new database and exporting/importing the data might be the simplest choice if you need to migrate some existing data.
The recommended national character set is "AL16UTF16", by the way, but that shouldn't matter that much once you have a Unicode enabled database using "AL32UTF8" as database character set.
2. How to set/retrive the "Database Character Set" and "National Character Set". This has already been answered partly. Retrieve:
Database Character Set:
SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';National Character Set:
SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';In most of the cases you can't just simply set/alter the character sets, as outlined above.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Is unicode support NOKIA N96?

hi friends..
is unicode support Nokia N96 mobile?
plz help me its urgent..
or any related url which i can find which mobile support unicode...
thnks in advance

N96 is yet to be released. Dont know if it supports unicode. The Nokia official site does not say anything about it.
If my post has helped you please click the white star on the right

How to make Solaris 8 UNICODE supported

My Solaris 8 doesn't support UNICODE. That's why, I can't write � in a file.
I think UNICODE support will remove this problem
How to make Solaris 8 UNICODE supported.

In the initial "dtlogin" screen, select a "UTF-8" locale when you login.
You may have to install additional locale files for UTF-8 support from the Solaris "Languages" CD.

ADf wont support in OAS 10.2.1?

ADf wont support in OAS 10.2.1?
Thanks,

You can run ADF applications on OAS 10.1.2 - see the support matrix here:
http://www.oracle.com/technology/products/jdev/collateral/papers/10g/as_supportmatrix.html
Deployment details here:
http://download.oracle.com/docs/html/B25947_01/deployment_topics006.htm#CIHGIAAE

Unicode support

It seems there is no way to display UTF-8 encoded ePub files in DE 1.5 correctly. If uncompressed, HTML content looks fine in a browser. In DE all common accented characters are substituted with ? character.
There are two similar topics on this forum:
http://www.adobeforums.com/webx/.59b6343e
http://www.adobeforums.com/webx/.59b60d2d
My ePub file was generated via DocBook XSL Stylesheets and there is no problem to display it in FBReader.
I suppose it is caused by default font, which contains probably very limited range of characters. Unfortunately there is no way to select the better one (as it is possible in FBReader).
Something about changing the default font was "discussed" here: http://www.adobeforums.com/webx/.59b5e8b7
If I met this issue 10 years ago, I would understand. If anybody in these days offer software for reading text with no support for non-roman languages, it is hard to believe.
What I would suggest is to deliver DE with any very complete font, for example MinionPro (latin, cyrillic, CE, greek etc.). If this is impossible, please add a feature for selecting the default font.
If I am totally wrong, clarification of this issue is welcomed.
OS - Win XP Pro SP2
Browser - Firefox 3.0.1

Hi Jim--
Thanks very much for the explanation on this...
You know, Adobe could save us all a lot of time if the default faux fonts would include more unicode support....
(I've spent probably a day overall trying to figure out what the issue is, and now I will spend the rest of the day learning/testing embedding a custom font in an epub, just for Digital Editions...)
Even Mobipocket and Kindle are getting these entities right in the three books I'm working on, with their default fonts. (We're not talking about super-obscure characters. Try "Milosevic" with the proper characters, and you get a ? in DE.)
Is there any chance Adobe can get the default fonts smarter in 1.8..?
Thanks for any help/thoughts on this front...I'm sure I don't understand all the issues...it just seems like such an obvious straightforward thing to fix.
--Kate

[SOLVED] Termite terminfo not reporting proper unicode support?

I've just switch from urxvt to termite due to the proper support for fontconfig. However, I'm noticing an issue in some ncurses programs that make use of the "Extended ASCII character set" printing functionality
According to this question ncurses determines what characters to print for a specific extended ascii character based on the current terminal type.
I suspect that termite isn't properly reporting unicode support since when a ncurses program wants to (for example) print arrows it will print (<, ^, v, >) instead of (←, ↑, ↓, →).
I've been trying to read terminfo(5) to understand what I might need to change in the terminfo file (xterm-termite) for it to properly report that it supports unicode, but it's fairly cryptic to me.
Last edited by EvanPurkhiser (2013-05-16 07:53:26)

I've made a little bit of progress on determining why Termite doesn't report support for _some_ extended ASCII characters.
Looking at Termites terminfo file there is an option in there named 'acsc', which describes the terminals support for extended ascii characters. There is some documentation on the options available for this, and I noticed that the arrow characters are not included in termites terminfo.
If I switch my $TERM to screen-256color (which DOES print the extended ASCII arrows properly) and run `infocmp` I see that it does include these characters
acsc=++\,\,--..00``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
I thought I might be able to simply add the proper characters to termites terminfo acsc option and it would fix it, but it didn't. Instead now when it trys to print arrows instead of printing the wedge (^, v) or the unicode characters (like I want), it just prints the corresponding extended ASCII mapping characters (-, .).
The next thing I tried was copying ALL of the screen-256color terminfo options into the source termite.terminfo file. This had the same effect as before.
I also tried completely replacing the (already compiled) xterm-termite terminfo file with the (already compiled) screen-256color terminfo file (`cp /usr/share/terminfo/s/screen-256color /usr/share/terminfo/x/xterm-termite`). This DID work, but obviously this is no different than just `export TERM=screen-256color `
What am I missing? is there some kind of character map that gets encoded into the terminfo file during compilation?
Last edited by EvanPurkhiser (2013-05-16 07:05:02)

Enable unicode support

I have nokia 6500 slide model phone.
How I can enable unicode support for reading "jar" file in regional language, especilly in malayalam language

It is not just about enabling Unicode support (and for all that matters, the phone might already have full Unicode support).
It is a case of having the correct fonts as default/system fonts for displaying the characters.
On S40 based models, you cannot install your own font files to replace system/default fonts.
So, if you want to read/see malayalam language content, and the phone does not support it, you can try a Nokia repair center in case there is a firmware version with support for that language, or you can change to some other phone model which supports the language, or supports installable font files.

Unicode support for Nokia 5233 and the like device...

Hello. I'm just a lurker on the forums but i recently made a switch from my old 6500 slide (Series 40) to a 5233.
When i got my new device, i wasn't exactly happy due to they (The salesmen) didn't inform me about the lack of 3G compatibility but my bigger problem is lack of Unicode support.
I cannot browse my Japanese files on my mSD nor can i browse my Japanese forums and sites on my 5233. I've been using my 5600 slide at the moment and was wondering if there is an avaliable language pack, character set pack or font pack?
Thanks.
EDIT: Fixed a few typos. Hope anyone can help me.

You need to visit a Nokia care center for language packs,they may charge a small fee for it.
If a reply has solved your problem click Accept as solution button, doing it will help others know the solution. Thanks.

Unicoding Support

Dear all
I need to enable unicode support for Oracle 9i(9.2.0.1.0) which is run on windows 2000 (32 bit)
I did edit change NLS_LANG to AMERICAN_AMERICA.UTF8 , but when I try to connect to isqlpluse an error occures
"ORA-12705: invalid or unknown NLS parameter value specified".
Please let me know any additional settings to be done in "pfile" (init.ora)?
Thanking you
Regards Lakmal

Hi, 
 
If I well understand, your source database is in non-unicode, right ? 
But it's not so easy to migrate in unicode database. 
I strongly advise you to read metalink note 260192.1 Changing WE8ISO8859P1/ WE8ISO8859P15 or WE8MSWIN1252 to UTF8 with ALTER DATABASE . 
You can find more info into Globalization Support 
 
Nicolas.

Changes to Unicode support in LabVIEW 8.6

There seems to have been a change in the way LabVIEW handles alternative text input between 8.5.1 and 8.6.
In 8.6, if I try to use type something in Hebrew (alt+shift in Windows changes the input language), the words come out in the wrong order (the first word appears on the left instead of on the right). The actual order of the letters in the word appears correctly (right to left), although sometimes the first letter in the text gets stuck on the left size.
If I try to use Hebrew in a label, I get a message telling me that I can't type a Unicode string into labels and enums.
In all of these cases, copying a string from Notepad and pasting it into LabVIEW displays it correctly (including in labels).
I have tried doing this with UseUnicode INI key set both to T and to F and it happens in both cases.
This SUCKS. Big time. Really.
I know that LabVIEW doesn't officially have support for right to left languages, but at least in previous versions it would sort of behave. I'm pretty sure this isn't what people who were expecting more Unicode support were thinking about.
Does anyone have any idea for a workaround? The only two I can currently think of is copying and pasting or writing a small VI which will reverse the text on demand, both of which are bad solutions.
If there's a patch planned, fixing this will definitely get my vote as something that deserves going in there.
P.S. I'm not sure why the Hebrew input is treated as Unicode. If I'm not mistaken, changing the input language in Windows should still result in ASCII characters and in previous versions it does (the Hebrew chars in the code page LabVIEW uses in 7.0 start at ASCII E0 and in 8.6 it starts at D005 with the next letter being D105).
P.P.S Did I mention this sucks?
Try to take over the world!

I'm going to suggest something really strange as a workaround, but, trust me, I have historical precedent for suggesting this...
Try editing the keyboard shortcuts for LabVIEW and change Quick Drop to be something other than ctrl+spacebar.
Why might this help the problem? When I developed the alignment grid, I thought that ctrl+# was a very intuitive shortcut key for toggling the grid on and off (since the hash symbol looks like a grid). What we found was that when the OS language was set to French, users could no longer type many of the extended grammer characters. The reason was that a critical scan code for the extended character sets overlapped with the scancode for ctrl+shift+3. In LV 8.6, we added ctrl+space, which is the first non-alphabetic shortcut key we've added since the ctrl+#. It might be that whatever keyboard scancode is used for Hebrew happens to overlap, and the code is being translated into a shortcut key for LV instead of a typed character.
I have no evidence that this is what is happening, but it is the only analagous situation that I know of, so I suggest it as something to try.

Where is Unicode Support

I tried buzzword today and got amazed after finding that
there is NO Unicode support. When I tried to write a few Unicode
Hindi word, all it displays was dots like this - ...... I tried to
copy this on my local Notepad, and Unicode characters were
displaying there. So, may be only display problem here?
I think, Unicode support is a must for todays web apps.
Google doc has it, Zoho has it, Thinkfree has it...

Hello there -
I've just
added
a post that addresses this issue. The short answer is that we
fully support Unicode, but we don't have access to many
international characters due to memory and bandwidth constraints.
We expect to address this in the next several builds, but in the
meantime we apologize for our inability to display many
international characters.

Unicode support - unsupported items?

Hello everyone,
I've been looking around for some detailed information concerning the support of Unicode in LabVIEW.
There is some valuable information out there, work-around's and whatnot, but there are things that need to be covered still.
Some valuable LabVIEW & Unicode information can be found here:
A List of Tips and Tools for using Unicode in LabVIEW
After reading the document above, I came to realize that there are some LabVIEW items that are not fully supported.
Some of these items are essential for application development and therefore, someone must have realized and come up with a solution.
I am looking forward to regroup all those solutions, and this will hopefully help others in the future.
For now, I really hope that someone can enlighten me with some of their valuable "tricks" since I need to deploy my application soon.
Here's a list of items that I've had trouble with when it comes to localizing them:
- Run-time menus: As far as I know, there is no Unicode support for them. Is there a way to display multi-byte characters in them?
                               I have even tried changing my system locale settings and nothing. My run-time menu is generated dynamically.
- Page Captions (names of the tabs in a tab control): I found ONE work-around for this item, overlapping transparent string controls over the page captions,
                                                                                   but is that the only way around ?
                                                                                   I have lost the link to this solution, if anyone can spare me the link to the document, it'd be great!
- Window titles: Even when changing the locale settings, bizarre characters appear instead of the correct value. Even when the value doesn't have special characters
                         (like in the picture below - where the title should be "Configuration Panel" only the Letter "C" appears. I wonder if this related to the "spacing"
                         between the Unicode characters? LabVIEW displays "C o n f i g u r a t i o n P a n e l " in a string control when I read the Unicode data from my .xml file.
                         Apparently, someone has had the same problem:
                         Unicode supportable VI title and 'Tip strips'. I would like to know more about the "tweaking the language settings of your host computer" method
- Tips and Descriptions of ANY control & indicator: I found nothing here, but I am probably blindfolded
- Ring control "drop-down" list: This might just be a misconception on my part, but take a look at the attached picture:
    Apparently, the drop-down list on the ring control only displays the Chinese language correctly, and only displays 1 letter on the other languages
    (English, Français and Español). My application loads the available languages depending on the localization files that it found on a specific directory.
    In this case, Chinese.xml, English.xml, French.xml and Spanish.xml were in the folder at the time of the screenshot.
    The xml files are encoded in UCS-2 Little Endian. I have tried prepending the "FFFE" BOM on each value, and no success.
If any of you have dealt with the problems listed above, I would GREATLY appreciate your input. Also, if there are any other controls that I didn't mention
and are not fully supported by LabVIEW when Unicode is enabled, please let me know, and I'll add them to the list!
Things to know:
My application is currently being developed in LabVIEW 2010 SP1
I'm using Arial Unicode MS as my default font everywhere on my application.
Other posts & references:
How to make my application programmatically switch between English and Russian
Thanks for your time,
Jorge
Attachments:
Language selector.png ‏32 KB

Thanks for your reply Josh,
I had already looked at that article. That's where I got the idea of building my Run-time menu dynamically instead of having multiple ones (one per language). However, it is not revelant to the Unicode issue I'm afraid. As far as I know, run-time menus simply DO NOT support Unicode (for now).
My question is, how did others work around this issue? Did they decide not to include any RTM in their application? Did they give up and tried using a different approach? If so, which?
I am mainly looking for solutions available today, preferably from people that have had the same problems. We all know that LabVIEW might eventually support Unicode completely (let's hope it will) but in the meantime, I am sure there are some good "tricks" out there.
Jorge

Unicode support when round-tripping to XML

Hi all,
Last week, I posted a question on round-tripping the symbol font and got no replies...:-) I'm thinking the question was entirely too generic, so I'd like to now add a little detail of what it appears are my primary options as well as current issues.
We have a math product that requires the use of the Symbol font. I'll use the beta here for an example: b. I have tried several methods to get this to display in Frame properly, save to XML, and open back up into Frame, with no success, as follows:
o Trying to enter it directly somehow into the text, either directly or as the value of a user variable, discussed below.
o Creating an element called "symbol" that is set in the EDD to always display as a Symbol font.
This one doesn't make it to the XML -- which complains about the document containing unsupported characters.
You can explicitly apply this font in Frame and it displays properly, but it does not save to XML and then open back up in Frame. I thought it might, given Frame's supposed implicit Unicode support for XML (the dev and ref guides say you don't need to map anything in the rules or create any entities if you are working in XML as opposed to SGML). Further, I can see that it is defined already in the FrameMaker\Structure\isocents directory:
<!ENTITY beta "β"> 
and also as this:
entity "bgr" is fm char 0x62 in "FmSymbol";
I'm not sure which is being used, but I assume my DTD does not need to define it.
So now I have assumed that you need to enter it into Frame explicitly as a Unicode code point, but I cannot figure out how to do that. Here's what I've tried:
Entering it directly as:
\u03B2
...doesn't display a Greek beta in the regular text, although I can enter it this way into a user variable, and a Greek beta is displayed (temporary Eureka!), but only as the value of the variable in the dialog box -- not when I insert that variable into the text, which simply results in a "?".
Using the File | Utilities | Hex Input enters only a "b" -- not a beta glyph. Although the user guide says you should be able to enter a Unicode code point with this tool, I can't see how to do that. If you manually enter the code point for the Greek symbol beta (62 for UTF-8), all you get is just that: 62.
Using the standard Windows Character Map does enter the beta glyph in Symbol font -- but this does not round-trip.
Entering it as "/b" -- not sure where I read about this -- doesn't display the glyph, but DOES save to XML as an entity "/b". Not sure what this means, but this entity only opens back up in Frame as a "/b", not a beta glyph.
We need to have the beta (and other symbols of course) display properly in Frame so we can print to PDF, then save to XML and reopen in Frame. Is this possible? Searches across all the Frame documentation have revealed nothing about how to do this, and I feel as if I'm complicated it unnecessarily, but can't tell how.
Any ideas -- or reasonable workarounds -- would be very much appreciated.
thanks,
Shelley

Shelley,
Whether or not a unicode character displays properly is a function of the font that you are using. If you specifed the \u03B2 codepoint, then unless you're using a Pro type OTF font, chances are that the glyph simply isn't available in that font.
Try using the Files > Utilities > Character Palette to see what's available (and also enter it by clicking on the glyphs) for the specific font that you are using in FM9. The Hex Input isn't the way to go for unicode values.
You might also want to look at installing the Quick Unicode Input tool available at: http://www.cardbox.com/quick.htm
[Addendum: WGL TT fonts may also contain the required greek symbols.]

Mathematical Font for Unicode Support

Hi everyone,
Does anyone know a Font which supports most of the mathematical symbols in Unicode 5.0? by that I mean the following tables from Unicode 5.0 (As much as possible!)
- Math Operators U+2200 - U+22FF
- Math Supplemental Math Operators U+2A00 - U+2AFF
- Misc. Math Symbols - A U+27C0 - U+27EF
- Misc. Math Symbols - B U+2980 - U+29FF
I have tried a lot of fonts but no luck so far. I can really use your help guys!

jhxcx,
It's currently not on our roadmap to include Unicode support for Measurement Studio VC++. You can make a product suggestion at this page http://digital.ni.com/applications/psc.nsf/default?OpenForm&temp1=&node= to keep the issue on R&Ds radar.
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

Unicode support of OAS

Similar Messages

Maybe you are looking for