Number-to-text for non-English locale?

Hi,
I know you can easily display numbers as text in BI Publisher, but it works only for English version. Is it possible to add that functionality for other languages too? Without some dirty work in database?

Hi,
According to your post, my understanding is that you wanted to validate for non-english character on a single line text field.
I recommend to use jQuery to attach regular expression validation. Please refer to:
Using #jQuery to attach regular expression validation to a #SharePoint list form field
In addition, for custom validations you can create your own Types. Refer to
this[^] for creating custom field type
More information:
SharePoint Custom Field - Regex Validator
Thanks,
Linda Li
Forum Support
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 Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

Similar Messages

How to validate for non-english character on a single line text field

In a "Single Line Text" field we would like to allow the users to enter alpha numeric values only. We should show error when the user enter non-English values like
carácter
Vijayaragavan, MCTS

Hi,
According to your post, my understanding is that you wanted to validate for non-english character on a single line text field.
I recommend to use jQuery to attach regular expression validation. Please refer to:
Using #jQuery to attach regular expression validation to a #SharePoint list form field
In addition, for custom validations you can create your own Types. Refer to
this[^] for creating custom field type
More information:
SharePoint Custom Field - Regex Validator
Thanks,
Linda Li
Forum Support
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 Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

SetMnemonic for non-english characters

Does anybody knos how to set JButtons mnemonic for non-english characters?
My mnemonic is loaded from a resource bundle, and in the documentation the setMnemonic(char) is only limited to english and it is written that the user should call setMnemonic(int) instead.
So what value should this int contains in order to display the non-english char which is loaded from resource bundle?
Thanks in advanve,
Hanoch

It seems that this is an issue that has popped up in various forums before, here's one example from last year:
http://forum.java.sun.com/thread.jspa?forumID=16&threadID=490722
This entry has some suggestions for handling mnemonics in resource bundles, and they would take care of translated mnemonics - as long as the translated values are restricted to the values contained in the VK_XXX keycodes.
And since those values are basically the English (ASCII) character set + a bunch of function keys, it doesn't solve the original problem - how to specify mnemonics that are not part of the English character set. The more I look at this I don't really understand the reason for making setMnemonic (char mnemonic) obsolete and making setMnemonic (int mnemonic) the default. If anything this has made the method more difficult to use.
I also don't understand the statement in the API about setMnemonic (char mnemonic):
"This method is only designed to handle character values which fall between 'a' and 'z' or 'A' and 'Z'."
If the type is "char", why would the character values be restricted to values between 'a' and 'z' or 'A' and 'Z'? I understand the need for the value to be restricted to one keystroke (eliminating the possibility of using ideographic characters), but why make it impossible to use all the Latin-1 and Latin-2 characters, for instance? (and is that in fact the case?) It is established practice on other platforms to be able to use characters such as '�', '�' and '�', for instance.
And if changes were made, why not enable the simple way of specifying a mnemonic that other platforms have implemented, by adding an '&' in front of the character?
Sorry if this disintegrated into a rant - didn't mean to... :-) I'm sure there must be good reasons for the changes, would love to understand them.

PDF generation for Non English Characters from ADF

Hi
We are using below piece of code to generate pdf from ADF Managed bean. It works fine. However for non English Characters(eg. Japanese,Vietnamese,Arabic) it puts
I got few blogs
https://blogs.oracle.com/BIDeveloper/entry/non-english_characters_appears
However we are not using BI Publisher product . We are using its API's
Can anyone tell where do we need to setup fonts within ADF or Weblogic or Server ?
Input Parameters are
a)xml Data
b)InputStream ie rtf Template
import oracle.apps.xdo.XDOException;
import oracle.apps.xdo.template.FOProcessor;
import oracle.apps.xdo.template.RTFProcessor;
    public static byte[] genPdfRep(String pOutFileType,byte[] pXmlOut ,InputStream pTemplate)
        byte[] dataBytes = null;
        try {
            //Process RTF template to convert to XSL-FO format
            RTFProcessor rtfp = new RTFProcessor(pTemplate);
            ByteArrayOutputStream xslOutStream = new ByteArrayOutputStream();
            rtfp.setOutput(xslOutStream);
            rtfp.process();
            //Use XSL Template and Data from the VO to generate report and return the OutputStream of report
            ByteArrayInputStream xslInStream = new ByteArrayInputStream(xslOutStream.toByteArray());
            FOProcessor processor = new FOProcessor();
            ByteArrayInputStream dataStream = new ByteArrayInputStream((byte[])pXmlOut);
            processor.setData(dataStream);
            processor.setTemplate(xslInStream);
            ByteArrayOutputStream pdfOutStream = new ByteArrayOutputStream();
            processor.setOutput(pdfOutStream);
            byte outFileTypeByte = FOProcessor.FORMAT_PDF;
            processor.setOutputFormat(outFileTypeByte); //FOProcessor.FORMAT_HTML
            processor.generate();
            dataBytes = pdfOutStream.toByteArray();
        } catch (XDOException e) {
            e.printStackTrace();
        return dataBytes;
Appreciate your help.
Thanks,
Abhijit

Fonts are defined in the template you use to generate the pdf. Your application add the data and both is processed yb the FOP processor. Now there are two possible causes of the '???' :
1. the data you sent to the template contains the '???' already
2. the template can't digest the data (the special characters) and puts '???' in the pdf.
Before going on you have to find out which one is your problem. The 2nd is the problem you better ask this in a FOP forum as you have to solve it by changing the template.
Timo

Word Replacements for Non- English Characters

Hi
Does anyone have an idea on implementing Word Replacements for non- english characters in TCA- DQM 11i.
We are trying to identify, capture and cleanse common accented characters like à, â , ê
However, the default language for replacement is American English , So even if we add these in the existing lists it will not take any effect
Is creating a new Word replacement list for every language the solution ?? any patch recommendations???
Thanks in advance

It seems that this is an issue that has popped up in various forums before, here's one example from last year:
http://forum.java.sun.com/thread.jspa?forumID=16&threadID=490722
This entry has some suggestions for handling mnemonics in resource bundles, and they would take care of translated mnemonics - as long as the translated values are restricted to the values contained in the VK_XXX keycodes.
And since those values are basically the English (ASCII) character set + a bunch of function keys, it doesn't solve the original problem - how to specify mnemonics that are not part of the English character set. The more I look at this I don't really understand the reason for making setMnemonic (char mnemonic) obsolete and making setMnemonic (int mnemonic) the default. If anything this has made the method more difficult to use.
I also don't understand the statement in the API about setMnemonic (char mnemonic):
"This method is only designed to handle character values which fall between 'a' and 'z' or 'A' and 'Z'."
If the type is "char", why would the character values be restricted to values between 'a' and 'z' or 'A' and 'Z'? I understand the need for the value to be restricted to one keystroke (eliminating the possibility of using ideographic characters), but why make it impossible to use all the Latin-1 and Latin-2 characters, for instance? (and is that in fact the case?) It is established practice on other platforms to be able to use characters such as '�', '�' and '�', for instance.
And if changes were made, why not enable the simple way of specifying a mnemonic that other platforms have implemented, by adding an '&' in front of the character?
Sorry if this disintegrated into a rant - didn't mean to... :-) I'm sure there must be good reasons for the changes, would love to understand them.

Customer conversion for Non-English languages

Hi:
We have a requirement to convert customer data from lagacy system to Oracle EBS supporting English and Non-English languages. Our conversion programs for english is working fine but we are not sure about the approach for other language converions. Can anyboody share the knowledge if faced similar requirements?
Thanks /Santanu

Duplicate thread (please post only once) ...
Customer conversion for non-english language
Re: Customer conversion for non-english language

ISF/javascript code doesn't work for non-English RequestCenter proile

ISF/javascript code doesn't work for non-English RequestCenter proile
Hello,
I am not sure if i posted the same question before also. We have some customers who have set thier language profile in newScale requestcenter to French. However, all the javascript customizations configured on the service forms do not function for 'French' as a Langauge preference. Has anyone encountered the similar issue before and can anyone please suggest a solution for it?
Thanks,
Mihir

we had a similar issue a while back where the Approval button was not working in Spanish, needed a fix from nS for it
The way to fix this would be to locate the language XML file, override the French caption with Submit and on onLoad write a global JS that would write the button label again (not so sure about this)
But really its an major defect and they should be able to fix it.

Forum-board for non-english speaking users?

Hello!
As my English isn't very good, and sometimes i don't know how to discribe my problem in English i'd like to ask if it's pssible to open a new Board for non-English speaking ArchLinux Users?
Perhaps one in German, French etc.
There non-english speaking Users could ask for help in their language and other German/French/Spanish-speaking users could help them.
CU ActionNews

sarah31 wrote:well i have notice that there are some more common non-english language users on this forum. there are quite a few germans, various latin languages (spanish, portugese, etc), and so forth. i wonder if it would not be possible to have catagories on this forum for our foreign language user so that if they feel more comfortable working in their own language they can post there. i mean really it is not that much of a drain of resources. if these cata gories became very active more organization or splitting could then be done.
The problem with separate categories for different languages is, as somebody already pointed out, that potentially useful information is then also separated. As a non-native English speaker myself, I still feel much more comfortable trying to understand bad English than perfect German of French.
I also reckon that here are not that many Finnish archers that we could have forum of our own.. and even if there was Finnish category I would propably still post to the English forums.
just my 0.02€
.murkus

Got multiple values for non null local custom field

Hi,
I get the following error message while saving a MPP from Project Professional to MS Project Server:
Got multiple values for non null local custom field.
I checked the MPP and found that there are fields with same alias as Enterprise field names. However, these fields are at a Task level, whereas the Enterprise fields are at a Project Level.
I would like to know why this is happening and the resolution for this issue. I don't want to delete the local fields.
Any help in this regard will be appreciated.

Then try to find any inconsistencies in the project plans with the issues, like required values not entered. Also try to save the plan as XML format and save it back as an mpp file to see if it helps (be aware that any formatting will be lost).
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Support issue for non-English characters (in html forms)

Hi group!
I just want to post an issue here and see if anyone else has the same problem. First off, Im running Windows XP MCE but the French version (not the english version). This may help find out where the problem really is.
Second, I know a bit of html and such, and I'm referring to HTML Character entities for this thread, there's a quite complete list here for reference: http://www.faqs.org/docs/htmltut/characterentitiesfamsupp69.html
I noticed that some, not all, non-English characters written in a textarea (which is, basically, a multi-lined input box) doesnt pass well or at all to the server when sending the form from Safari. Most of the time, the content of the text area is reduced to the beginning and ends where the first accentued character is met.
The most used French accents (é, à) are usually well interpreted (but may, once in a while, produce that bug too) by safari, but ô and î doesnt do that well.
Oddly, this bug doesnt happen all the time and doesnt "crash" in the same manner everytime.
So I started a thread just to see if there's anyone else having issues with any non-english characters mostly in forms. Probably flash/shockwave does work, but I'm not sure- I have not tested yet.
Acer Aspire 5044 Windows XP Turion 1.8GHz, 1Gb SDRam, ATI 200M xpress

Yes, it is a known issue. I also noticed that it sometimes works, but most of the time it does not. It will hopefully be solved in the future. According to http://www.apple.com/safari/download/ changes that will come include:
# Support for International users
# International text input methods
# Advanced text (contextual forms, international scripts)
Sony Vaio Windows XP

Phoneme mode for non-English voices in OS X 10.7

Hi!
I need to make the text-to-speech synthesizer speak via phoneme input method with non-English voices.
Is it possible? As far as I can see, only English voices support phoneme input method.
I'm using the OS X 10.7 voices.
Do I need to set the speech channel differently?
Thanks!

Tom,
Unfortunately, I tried that and it's still stuck in Spanish. On things like...the Login Screen, Warning Screens, etc. My menu and apps, finder, etc. are all in English, but some of the core items seem still stuck in Spanish. Any other ideas of how to fix this? Will there be a chance to adjust this when Mountain Lion is available?
Thanks for your help!

Is Lightroom intentionally made difficult for non-English users?

Could it be that Lightroom is intentionally made difficult for the non-English user? I came to this forum today hoping to find an answer and all I see is problems when I try searching the forum, and complicated instructions on how to, supposdely, solve this issue. The issue I am facing has to do with localization, compatibility, interoperability and compliance. The problem is that I can't use many of the Lightroom shortcuts. Many of the ones that require the use of a modifier key on my keyboard just don't work. So what if I have a Swedish keyboard? Sweden is one of the most computer literate contries in the world, and Sweden has played a major role in the development of early computers and new technologies. Adobe has a presence in this country, and I'm quite sure Sweden is an important market for Adobe. So why not make Lightroom compatible with the Swedish keyboard? Why should I care to go through complicated instructions on how to hacktivate my keyboard by the means of editing config or script files? Why can't it just work out of the box?
I feel like this is intentional. Could it be that Lightroom users are only to be found in English speaking countries like USA, UK, New Zealand and Australia? I don't think so.
Swedish user:
http://forums.adobe.com/message/1459525#1459525
Swiss user:
http://forums.adobe.com/message/4375318#4375318
German user:
http://forums.adobe.com/message/3588746#3588746
http://forums.adobe.com/message/3817657#3817657
How about the ability to change keyboard shortcut bindings, i.e. custom shortcuts? I just found that this is not even possible in Lightroom! That explains why people take these strange measures and kludgy ways of making custom shortcuts in Lightroom. Changing shortcuts is often times tricky business because you have to change them in respect to other shortcuts. It's likely that one will have to change several keyboard shortcuts to avoid conflicts, etc. Lightroom needs a shortcut editor!
One should really not even have to change the default shortcuts, Adobe should choose some intelligent key combinations that make sense, and they should just work on any keyboard. I've tried changing the language from English to Swedish in Lightroom settings. The result of this is that nearly all shortcuts are changed to something else, so I would have to re-learn some of the shortcuts I have already learned using Lightroom in English, and of course this also changes the language of the interface which is not something I want. I will have to change my keyboard layout to English to make this work, or get a secondary keyboard, one with English layout. This is something I will only have to do when I work in Lightroom, because many of the professional programs that I use are working just fine with my keyboard. Perhaps Adobe can make the keyboard localization (shortcut maps) as an option, separate from the interface language setting? And for God sake integrate a keyboard shortcut editor for once!

Another Swiss user on Lightroom forums:
http://www.lightroomforums.net/showthread.php?6867-Flippy-Key-Using-Lightroom-in-english-w ith-a-non-english-keyboard-layout
I ended up removing the Keyboard Tamer plugin and then manually adding following strings to C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\TranslatedStrings.txt. This is by the way something that the Keyboard Tamer plugin does as well, because when I removed it I found two files named TranslatedStrings.txt in the Recycle Bin. The Keyboard Tamer is just supposed to save you the time and effort of manually manipulating these strings.
"$$$/AgLibrary/Menu/View/ZoomIn=Zoom In"
"$$$/AgLibrary/Menu/View/ZoomIn/Key=Cmd+."
"$$$/AgLibrary/Menu/View/ZoomInMinor=Slow Zoom In"
"$$$/AgLibrary/Menu/View/ZoomInMinor/Key=Cmd+Shift+."
"$$$/AgLibrary/Menu/View/ZoomOut=Zoom Out"
"$$$/AgLibrary/Menu/View/ZoomOut/Key=Cmd+-"
"$$$/AgLibrary/Menu/View/ZoomOutMinor=Slow Zoom Out"
"$$$/AgLibrary/Menu/View/ZoomOutMinor/Key=Cmd+Shift+-"
I found this thread helpful:
http://forums.adobe.com/message/1459525#1459525#1459525
I just replaced AgDevelop with AgLibrary. This of course only changes the key binding for Zoom In and Zoom Out in the Library module. Is there perhaps a document somewhere that explains the structure of the TranslatedStrings.txt file? There seems to be one of these files in each of the language specific folders under the Resources folder.
This file is known to be found in:
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources>dir /b /s TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\de\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\es\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\fr\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\it\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\ja\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\ko\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\nl\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\pt\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\sv\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\zh_cn\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\zh_tw\TranslatedStrings.txt
I will study the structure of this file in Resources\sv\ and try to understand it. And as I find new "flaws" in the shortcut key bindings I will make new edits to the file I saved in Resources\en\ accordingly.
Here's an idea: those of you who don't mind re-learning all the shortcuts - the localized shortcuts for Swedish keyboards - simply copy the TranslatedStrings.txt file from C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\sv\ and paste it in C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\. What this does it allows you to keep English as your interface language, but it changes the shortcut map to something that's more adopted for the Swedish keyboard layout. You get the same shortcut key bindings as the ones you see when you change the language to Swedish in the settings. But this way you are preventing Lightroom from changing the interface language.
Either that, or add new strings to an empty Resources\en\TranslatedStrings.txt file for each key binding you find to be broken and not compatible with your keyboard. This way you are only making changes to the key bindings that don't work very well for your keyboard, you are not chaning all of the shortcut key bindings. The other key bindings stay the same, the default key bindings found in the English version of Lightroom (or with English as language settings).
This is a way to adapt Lightroom for your own environment. But this is still too complicated and unncessary. A simple shortcut editor built into Lightroom would have solved this. But what are we going to do?... this is up to Adobe... Lightrooms have been complaining about the lack of a shortcut editor since at least Lightroom 2 and Adobe has not listened. So I don't expect to see this feature in the following years to come. It might just come along in maybe Lightroom version seven or something... but who cares?... At that time I might even ditch Lightroom altogether.
Ligthroom 5 upgrade...
I just found out that the new Lightroom 5 is not compatible with Windows Vista. I have the Vista Ultimate 64-bit on my desktop where I use Lightroom. This was not made very clear by Adobe. They simply state that Lightroom 5 works on Mac and on Windows. You have to read the fine print. I almost purchased the upgrade. I'm glad I didn't. I won't upgrade from Vista to Windows 7 just to run Lightroom 5! We, the early Windows Vista adapters, got screwed by Microsoft. Now, we are getting screwed by Adobe too! I see no reason not to support Windows Vista as it is pretty much the same system as Windows 7, and one would expect Adobe to support them both. I found a thread about it where one user asked why Vista was not supported and Adobe failed to give any explanation. They just silently dropped the OS support.
I guess they can do whatever they want. They are Adobe.
But I will not upgrade to Windows 7 because of Lightroom, so I won't upgrade to Lightroom 5. This is a great oppertunity for Phase One to strike with a good deal, such as a discounted migration upgrade for Capture One. I am sure many Lightroom 4 users would be happy to leave the Lightroom ship in favor of Capture One. At the end of life of Lightroom 4 I will probably just go to Capture One, even if I have to pay full price. At least they support Windows Vista.

UTL_RAW.REVERSE for non english characters

I'm trying to reverse a non-English work like the following and it does not work ....
SELECT '中国' Original, UTL_RAW.cast_to_varchar2(UTL_RAW.REVERSE (UTL_RAW.cast_to_raw ('中国'))) Not_correctly_Reversed FROM DUAL;
ORIGINAL NOT_CORRECTLY_REVERSED
中国 ��
Any thoughts please ?
Appreciate responses. Thanks !

chris227 wrote:
Works well for meNo, it does not. It will fail if table has duplicate strings of two digit length but, what is even worse, it will produce wrong results if table has small duplicate strings:
SQL> with testdata as (
2                    select '19 character string' str from dual union all
3                    select '19 character string' str from dual
4                   )
5 select distinct
6    listagg(substr(str,level,1))within group ( order by level desc) over (partition by str) r
7 from testdata
8 connect by
9 level <= length(str)
10 and str = prior str
11 and prior sys_guid() is not null
12 /
from testdata
ERROR at line 7:
ORA-01489: result of string concatenation is too long
Elapsed: 00:00:36.08
SQL> with testdata as (
2                    select 'ABC' str from dual union all
3                    select 'ABC' str from dual
4                   )
5 select distinct
6    listagg(substr(str,level,1))within group ( order by level desc) over (partition by str) r
7 from testdata
8 connect by
9 level <= length(str)
10 and str = prior str
11 and prior sys_guid() is not null
12 /
R
CCCCCCCCBBBBAA
Elapsed: 00:00:00.00You need to identify rows uniquely. With real table it is easy - rowid. With subquery factoring we need another view with, for example, ROW_NUMBER. However here we use subquery factoring to create sample table on-the-fly and assume OP will have real table. So I'd leave your example as is, but would let OP know to use:
select distinct
listagg(substr(str,level,1))within group ( order by level desc) over (partition by str) r
from testdata
connect by
level <= length(str)
and rowid = prior rowid
and prior sys_guid() is not null
/But this still will not work. Why? Same answer - duplicates:
SQL> create table testdata as (
2      select 'ABC' str from dual union all
3      select 'ABC' str from dual
4     );
Table created.
Elapsed: 00:00:00.42
SQL> select distinct
2    listagg(substr(str,level,1))within group ( order by level desc) over (partition by str) r
3 from testdata
4 connect by
5 level <= length(str)
6 and rowid = prior rowid
7 and prior sys_guid() is not null
8 /
R
CCBBAA
Elapsed: 00:00:00.01
SQL>Again, partition by str doesn't identify rows uniquery. We need to partition by rowid. But even this will not help:
SQL> select distinct
2    listagg(substr(str,level,1))within group ( order by level desc) over (partition by rowid) r
3 from testdata
4 connect by
5 level <= length(str)
6 and rowid = prior rowid
7 and prior sys_guid() is not null
8 /
R
CBA
Elapsed: 00:00:00.00
SQL>We got one row back instead of two. You probably put DISTINCT trying to resolve all these issues caused by building hierarchy and partitions on a non-unique bases. So now, when we identify rows uniquely by rowid, DISTINCT is not needed and should be replaced by GROUP BY (along with using aggregate LISTAGG instead of analytic LISTAGG). So final solution would be:
select listagg(substr(str,level,1))within group ( order by level desc) r
from testdata
connect by
level <= length(str)
and rowid = prior rowid
and prior sys_guid() is not null
group by rowid
R
CBA
CBA
Elapsed: 00:00:00.00
SQL>And with 19 character string:
SQL> insert
2    into testdata
3 select '19 character string' str from dual union all
4                    select '19 character string' str from dual;
2 rows created.
Elapsed: 00:00:00.00
SQL> select listagg(substr(str,level,1))within group ( order by level desc) r
2 from testdata
3 connect by
4 level <= length(str)
5 and rowid = prior rowid
6 and prior sys_guid() is not null
7 group by rowid
8 /
R
CBA
CBA
gnirts retcarahc 91
gnirts retcarahc 91
Elapsed: 00:00:00.00
SQL>SY.

Problem: Adding support for non-english charachter sets in UCCX 8.0

We have just moved from windows-based UCCX 7.0 to UCCX 8.0, the upgrade process went successfully so far, but for some reasons, Cisco Agents are experiencing problems displaying non-english charachter sets, everything was working fine prior to upgrading to the new version.
Is there a way to add support for these character sets?
Thanks in advance.

Hi Bala,
Follow the command. I believe that the space is normal.
This command can take significantly long time,
and can also effect the system wide IOWAIT on your system.
Continue (y/n)?y
Filesystem            Size Used Avail Use% Mounted on
/dev/sda6              90G   46G   41G 54% /common
8.0K    /var/log/inactive/
admin:
admin:
admin:show diskusage activelog
This command can take significantly long time,
and can also effect the system wide IOWAIT on your system.
Continue (y/n)?y
Filesystem            Size Used Avail Use% Mounted on
/dev/sda6              90G   46G   41G 54% /common
8.0K    /var/log/active/mgetty
0       /var/log/active/sa
4.0K    /var/log/active/platform/snmp/sappagt/sappagt.index
4.0K    /var/log/active/platform/snmp/sappagt/sappagt.log
4.0K    /var/log/active/platform/snmp/sappagt/startup.txt
16K     /var/log/active/platform/snmp/sappagt
4.0K    /var/log/active/platform/snmp/hostagt/hostagt.index
Thanks,
Wilson

Customer conversion for non-english language

Hi:
We have a requirement to convert customer data from lagacy system to Oracle EBS supporting English and Non-English languages. Our conversion programs for english is working fine but we are not sure about the approach for other language converions. Can anyboody share the knowledge if faced similar requirements?
Thanks /Santanu

I believe your conversion programs should work regardless of the language the data is stored in, as long as the database and Apps use UTF8 characterset. To the code, data is data, whether it is in English or in another language. Your approach should be to test your conversion programs in test instances and tweak them as necessary. Are there specific concerns you have with using data in other languages ?
Srini

Number-to-text for non-English locale?

Similar Messages

Maybe you are looking for