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.

Similar Messages

Replacing any non english Characters

How can I Replace any non english characters I have alot of the characters that look like a block.
--John

Probably the easiest way to code would be to convert the string to a byte array and back again using the ASCII character encoding. That should give you ? for any non ASCII characters.
Something like;
String newString = new String(oldString.getBytes("ASCII"), "ASCII");

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

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

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.

Question marks in PDF for non-english characters.

I'm get report from APEX 3.0.1 (Default Report Layout) with BI Publisher 10.1.3.3.1 Base.
In Adobe Reader 7.0.8 instead of non-english(cyrillic) characters see question marks.
How to tune BI Publisher?

After installation BI Publisher 10.1.3.3.1 Base (standalone, OC4J) :
Directory of F:\bip\jdk\lib\fonts
13/10/2007 21:16 15 196 128R00.TTF
13/10/2007 21:16 18 473 348 ALBANWTJ.ttf
13/10/2007 21:16 18 777 132 ALBANWTK.ttf
13/10/2007 21:16 18 676 084 ALBANWTS.ttf
13/10/2007 21:16 18 788 600 ALBANWTT.ttf
13/10/2007 21:16 276 384 ALBANYWT.ttf
13/10/2007 21:16 12 860 B39R00.TTF
13/10/2007 21:16 18 800 MICR____.TTF
13/10/2007 21:16 6 580 UPCR00.TTF
Directory of F:\bip\jdk\jre\lib\fonts
01/08/2006 19:25 75 144 LucidaBrightDemiBold.ttf
01/08/2006 19:25 75 124 LucidaBrightDemiItalic.ttf
01/08/2006 19:25 80 856 LucidaBrightItalic.ttf
01/08/2006 19:25 344 908 LucidaBrightRegular.ttf
01/08/2006 19:25 317 896 LucidaSansDemiBold.ttf
01/08/2006 19:25 698 236 LucidaSansRegular.ttf
01/08/2006 19:25 234 068 LucidaTypewriterBold.ttf
01/08/2006 19:25 242 700 LucidaTypewriterRegular.ttf
Directory of F:\bip\jre\1.4.2\lib\fonts
24/03/2004 19:12 75 144 LucidaBrightDemiBold.ttf
24/03/2004 19:12 75 124 LucidaBrightDemiItalic.ttf
24/03/2004 19:12 80 856 LucidaBrightItalic.ttf
24/03/2004 19:12 344 908 LucidaBrightRegular.ttf
24/03/2004 19:12 317 896 LucidaSansDemiBold.ttf
24/03/2004 19:12 698 236 LucidaSansRegular.ttf
24/03/2004 19:12 234 068 LucidaTypewriterBold.ttf
24/03/2004 19:12 242 700 LucidaTypewriterRegular.ttf
What is wrong?
In Adobe Reader's Document Properties -> Fonts
+Helvetica:
Type: Type1
Encoding: Ansi
Actual Font: ArialMT
Actual Font Type: TrueType
I feel BIP use wrong encoding . . .

Support for non-English characters in Safari?

When I browse Japanese and Chinese websites, Safari only shows blank lines and empty blocks, it seems Safari doesn't support non-English encoding or UTF-8?
Windows XP Pro

It (usually) works if you use an English version of Windows. Not if you use a Chinese or Japanese version.

Problem in converting Spool to PDF file, having non-English characters

Hi All,
I have problem in converting Spool to PDF format.
Scenario : I have a spool which has non-English characters. I am using CONVERT_ABAPSPOOLJOB_2_PDF FM to perform conversion. But my output is having junk values( ie # ) for non-English characters. Any pointers to solve this issue will be appreciated.
I even tried with report RSTXPDFT4 , it also gives me the same junk characters.
Regards,
Navin.

Hi All,
I have problem in converting Spool to PDF format.
Scenario : I have a spool which has non-English characters. I am using CONVERT_ABAPSPOOLJOB_2_PDF FM to perform conversion. But my output is having junk values( ie # ) for non-English characters. Any pointers to solve this issue will be appreciated.
I even tried with report RSTXPDFT4 , it also gives me the same junk characters.
Regards,
Navin.

Can't CF use non English characters in URLs ???? (critical for SEO)

Hi all,
I want to use non English characters (Greek characters) for folders of the URLs.
eg   http://www.mysite.com/Φάκελος/index.cfm
where "Φάκελος" is a non English word (Greek).
When the called page is simple HTML eg   www.mysite.com/Φάκελος/index.HTM
it's displayed just fine.
When the called page is CF page eg   www.mysite.com/Φάκελος/index.CFM
I get a "FILE NOT FOUND" error.
In the page where the link exists everything is UTF-8.
What's the problem ? Can't CF use non English characters in URLs ????
It's critical for SEO issues.
I use CF9. Any ideas ???
Thanks in advance.
Anastassios

I don't have this setting in the email application. But as I know, html with Exchange is working only with the 2007 version, my server is still 2003 so I think in my case it's plain text only.
But I'm telling again: good old (and now starting to miss) E60 with MfE worked very well!

Replace non-english characters function

Hi folks,
I have a text which includes non english characters. Is there any trick, how can I replace those characters with "closest" english character?
Examples:
"Hytölä" to become "Hytola"
"Säynatsälo" to become "Säynatsälo"
etc ...
I was thinking about usage of REGEXP
select regexp_replace('Hytölä Säynatsälo ', '[^0-9A-Za-z]', '') from dual
but a pattern is not correct.
Any suggesitons?

There is something that smells like a hack for me (source: replace characters with accent with their base letter)
However
with data as (
select 'Hytölä' str from dual
union all
select 'Säynatsälo' from dual
select
str
,utl_raw.cast_to_varchar2(nlssort(str, 'NLS_SORT=BINARY_AI')) nstr
,length(utl_raw.cast_to_varchar2(nlssort(str, 'NLS_SORT=BINARY_AI'))) l
from data
STR
NSTR
L
Hytölä
hytola
7
Säynatsälo
saynatsalo
11
Notice that change in length through an extra null bit at the end of the strings.
And the loss of the uppercase.
For this kind of questions it's helpful to know about the requirements. Why there shuóuld be a baseletter conversion? For search purposes for example.
not to forget the db characterset.

Non-English characters in URL for rwservlet

I'm having a problem when I try to use non-english characters in a URL request to generate a report.
This works fine:
http://...rwservlet?report=r1.jsp&m1=Fred
But if I try FrÃ©d (e with accent graph) the report does not return any data even though the SQL by itself would find data.
I tried UTF-8 encoding
http://...rwservlet?report=r1.jsp&m1=Fr%C3%A9d
8859-1 encoding
http://...rwservlet?report=r1.jsp&m1=Fr%E9d
Or just spell it out (not sure what that gets encode as):
http://...rwservlet?report=r1.jsp&m1=FrÃ©d
But noting works. Any ideas?
Thanks, Andreas

Suggestions
1) Try with NLS_LANG as
SWEDISH_SWEDEN.WE8DEC
2) Make a paramform and enter via paramform (unencoded)
(This is just for testing purpose)
3) Change machine locale to swedish and try
4) Which reports version is this ?
Please see
BUG 2713695 - NLS CHARACTERS FOR PARAMETERS CHANGE TO QUESTION MARKS WHEN PASSED ON URL BAR
Get in touch with Support to see if this is the issue and if "yes" get a one-off patch.
[    All Docs for all versions    ]
http://otn.oracle.com/documentation/reports.html
[     Publishing reports to web - 10G ]
http://download.oracle.com/docs/html/B10314_01/toc.htm (html)
http://download.oracle.com/docs/pdf/B10314_01.pdf (pdf)
[   Building reports - 10G ]
http://download.oracle.com/docs/pdf/B10602_01.pdf (pdf)
http://download.oracle.com/docs/html/B10602_01/toc.htm (html)
[   Forms Reports Integration whitepaper 9i ]
http://otn.oracle.com/products/forms/pdf/frm9isrw9i.pdf
---------------------------------------------------------------------------------

URLEneQuery encoding is failing for some non english characters

While creating a URLEneQuery we are getting error com.endeca.navigation.InternalException: No support for 8-bit urls.
This error happens when the query string has some non english characters. (eg: Á).

UrlENEQuery is designed around processing URL data, and URLs are not permitted non-ASCII characters in their production. To represent non-ASCII characters they must be %-encoded in URLs according to their byte(s) representation in a particular character-encoding, and you should prefer UTF-8 for URLs. So your LATIN CAPITAL LETTER A WITH ACUTE (U+00C1) should appear as %C3%81 in your URL, then UrlENEQuery should be able to process that character.

Predictive text non-English characters to be made ...

I just filled an enhancement request on this feature, please vote for it HERE:
Predictive text non-English characters to be made optional
The story is: while using predictive text for non-English languages (Polish in my case) the dictionary words are grammar correct which include special characters like: ą,ę,ć,ś,ż,ź,ó,ł etc. For texting (SMS) operators count these as 3 characters making a message much longer than it looks. Therefore I can tell you no one uses these characters while texting and people use EN only characters instead a,e,c,s,z,o,l... which makes using the predictive text useless for eg Polish language.
I'd like to have an option to switch using these non-en chars off for predicting text, which is grammatically not correct but in real life that's how people type.
So basically if there's an option to disable lang specific characters I would be getting an example suggestion of 'Prosze' instead of grammatically correct 'Proszę'. 'Prosze' is a 6 character word, 'Proszę' is a 5+3=8 character word. Considering a single SMS message a 300 chars, than it really makes a difference.
Simple solution would be to replace every char ą with a, ć with c, ó with o etc... in each word suggested for the ones who have this option enabled.

HI,
You can write a code in PAI of main screen. there by using loop at screen you can make that field editable or disabled.
Code sample:
loop at screen.
****condition for value check
if screen-name = 'TEXT_EDIT_NAME'
screen-output = 1.
screen-input = 0.
modify screen.
endif.
endloop.
Hope this will help you.

Only VBA does not recognize non-English characters

Hello guys,
I have a new laptop with Windows 8.1 bought in the USA and I'm having a difficulties with Excel VBA (Office 365 University-64x bought in the Czech Republic - Central Europe). The VBA does not recognize non-English characters (particularly "ř" and
"ů") which causes me problem when running some codes that I wrote earlier on my previous laptop (Windows 7, bought in the Czech Republic with the same Office).
The problem with non-English characters has occurred only in VBA so far, otherwise I can use these characters normally in Excel cells, Word... I tried to install both English and Czech version of the Office with no change, I also installed Czech proofreading
tools and set everything to Czech in the Office. The location and language preferences in the Windows are also set up to Czech. And it is not a problem of a font. I also mentioned that when I tried to look up these characters, using Ctrl+F, it changes
original ř to r after a search and again this is only an issue of the VBA.
Thank you very much for any help.
Tom

Hi Tom,
VBA for Excel can only recognize ASCII code from 0 to 255, if you use other special characters like "ř" or "ů", it will returns 63(?) to you. To use this kind of characters, you have to utilize ChrW function to parse a decemal to the
character.
http://msdn.microsoft.com/en-us/library/ee177465.aspx
for example, the hex code and dec code for these two characters are as below:
Hex   Dec
ř 159   345
ů 016F 367
So to get these two characters in VBA, you could code as below:
ChrW(&H159) or ChrW(345)
ChrW(&H16F) or ChrW(367)
You can get the hex code of the character by searching in the system character map(in the Win8.1 start view, search "character map"), then convert the hex code to decimal code by yourself.
Range("A1").Value = ChrW(&H159) & ChrW(&H16F)
Range("A1").Value = ChrW(345) & ChrW(367)
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Word Replacements for Non- English Characters

Similar Messages

Maybe you are looking for