We cannot type Polish (non-latin) characters in WebDynpro applications

We cannot type Polish (non-latin) characters in WebDynpro application (in runtime) because 'Browser Help Shortcuts' are fired.
To type a polish character in polish keyboard you need to press AltGr + letter (ie. AltGr + a/c/e/s/o/l/z/x/n). To type an uppercase polish character you need to press AltGr + Shift + letter. This comination is in fact the same as pressing Alt + Ctrl + Shift + letter (because AltGr produces Alt + Ctrl) and it fires some of 'Browser Help Shortcuts'. For example AltGr + Shift + O should produce a letter O with a dash on it's top but instead it fires 'Show nesting of HTML containers'.
We tried to turn off sap-wd-lightspeed, but then other key combinations are reserved for u2018Browser Help Shortcutsu2019.
We need to be able to use AltGr + Shift + a/c/e/s/o/l/z/x/n in runtime.
Product: SAP NW 7.11 SP04
WebDynpro for Java
I hope there is a somewhere a hidden parameter that solves our problem Maybe we're in some kind of debug mode?
Thanks for your help!!

The funny thing is that bold font [when message unread in message list] shows OK, ie in greek, but when i click on unread message, it is assumed to have been read, so it changes over to medium [non bold] and the encoding changes as well into the one that is not greek and thus unreadable. In ~/.sylpheed/sylpheedrc the fonts are:
widget_font=
message_font=-microsoft-sylfaenarm-medium-r-normal-*-*-160-*-*-p-*-iso8859-7
normal_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
bold_font=-monotype-arial-bold-r-normal-*-12-*-*-*-*-*-iso8859-7
small_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
In /etc/gtk, for gtk1.2 apps the file refering to greek encoding [el] seems to be fine [exactly the same as in slackware 9.1].

Similar Messages

Cannot create file with Non-latin characters- I/O

I'm trying to create a file w/ Greek (or any other non-latin) characters ... for use in a RegEx demo.
I can't seem to create the characters. I'm thinking I'm doing something wrong w/ IO.
The code follows. Any insight would be appreciated. - Thanks
import java.util.regex.*;
import java.io.*;
public class GreekChars{
     public static void main(String [ ] args ) throws Exception{
          int c;
          createInputFile();
//          String input = new BufferedReader(new FileReader("GreekChars.txt")).readLine();
//          System.out.println(input);
          FileReader fr = new FileReader("GreekChars.txt");
          while( (c = fr.read()) != -1)
               System.out.println( (char)c );
     public static void createInputFile() throws Exception {
          PrintStream ps = new PrintStream(new FileOutputStream("GreekChars.txt"));
          ps.println("\u03A9\u0398\u03A0\u03A3"); // omega,theta,pi,sigma
          System.out.println("\u03A9\u0398\u03A0\u03A3"); // omega,theta,pi,sigma
          ps.flush();
          ps.close();
          FileWriter fw = new FileWriter("GreekChars.txt");
          fw.write("\u03A9\u0398\u03A0\u03A3",0,4);
          fw.flush();
          fw.close();
// using a printstream to create file ... and BufferedReader to read
C:> java GreekChars
// using a Filewriter to create files .. and FileReader to read
C:> java GreekChars
*/

Construct your file writer using a unicode format. If
you don't then the file is written using the platform
"default" format -probably ascii.
example:
FileWriter fw = new FileWriter("GreekChars.txt",
"UTF-8");I don't know what version of FileWriter you are using, but not that I know of take two string parameters. You should try checking the API before trying to help someone, instead of just making things up.
To the OP:
The proper way to produce a file in UTF-8 format would be this:
OutputStreamWriter writer = new OutputStreamWriter(new FileOutputStream("filename"), "UTF-8");Then to read the file, you would use:
InputStreamReader reader = new InputStreamReader(new FileInputStream("filename"), "UTF-8");

Non-Latin Characters lead to finder distress.

One of the nicest features of Macintosh from the time I first played on an SE30 is the capacity to quickly type non-Latin characters. While to many this might not seem like a big deal, for me being able to write Tetris™ without a second thought is a great convenience.
So I was very surprised when I began typing µ in the Finder under Snow Leopard and didn't end up on a file that started with µ but rather on m. As if that wasn't irritating enough µ is not treated as m so the file becomes completely unreachable by alphabetic selection. This is something I use almost constantly in Finder so having a file unreachable is even worse than merely having the character interpreted incorrectly.
Just to be certain that this wasn't merely a flaw with that one character I examined other common characters.
ƒ, é, π, ∑ all suffer from the same problem, misinterpreted when typed and interpreted correctly during the comparison.
So the question is, “Is this an error in how I set up my machine, an error in the string comparison system, or an error in the Finder program?”

Yes, I just double checked, and I was in error, accented Latins do work as expected. I am certain that the inclusion of such in the prior list was a user error.
However the fact that the Greek key layout works begins to suggest the root of the problem.
Interestingly enough this also applies to the Greek layouts internal option modified keys.
I am strongly suspecting a bug here.

KDE, HAL, cannot open the non-latin mount point

I just installed ArchLinux for a few days and there is a problem here: I use KDE and hal, USB disk and CDROM can be auto-mounted. But if the USB Disk lable or CDROM label is non-latin characters, KDE, actually, Konqueror cannot open that mount point.
I think my charset is correct because in konqueror, the directory name of the mount point is correct. When I try to open this directory, konqueror complained that she cannot open that directory and the directory name which the error message dialog shows is wrong.
Any ideas? Thanks a lot.

kartwall wrote:
Problem solved -- modify the HAL mount point, so HAL will not use disk's lable to create a directory as mount point. Although this is not a perfect solution, but it works.
http://mail.kde.org/pipermail/kde-fr...il/000545.html
I think this is the page:
http://mail.kde.org/pipermail/kde-freeb … 00545.html
http://www.centos.org/modules/newbb/pri … SC&start=0
fifth and sixth post

Non latin characters in Safari search

In Safari 6 the search and URL fields are combined. That's fine, except...
We can no longer search using non-Latin characters, because the field accepts only Latin characters. I was trying to search for a Japanese term, and when I switch to Hiragana input and move to the search field, the input switches back to English.
What's the workaround??

The problem has gone away. I suspect it was a problem with corrupted prefs. I trashed the Safari prefs and rebooted to clear another problem and no longer have the problem with search using Japanese characters.
FWIW, the problem I had when I trashed the prefs was with trying to mail a Safari page. I ran in to this originally a week or two ago and called Apple who told me to delete the Safari prefs and reboot. (Actually they gave an alternate procedure to try first, but I didn't bother.) That appears to be a recurrent problem and since there was no hesitation on the solution when I called I would guess that it will be fixed in an early patch. I had already tried trashing the mail prefs since that's where the problem actually appeared (an extra copy of Mail would open, and then hang) but it was in fact the Safari prefs that was causing the problem. I've had to do the delete-and-reboot routine every few days. Not sure why the reboot is required, but it obviously is since just quitting Safari or even logging out doesn't fix it.

Non latin characters in .cfm filename

Hi - I have users who want to name files with non latin characters. i.e.
Логотип_БелРусь_2500x1.cfm
We get a file not found error, it is not an IIS issue and we have UTF-8 encoding and are running CF8.
Yes we can rename the files but for now would like to know if non latin characters are allowed in .cfm file names.
Thank you!
Sapna

PaulH wrote:
en_US is the JRE locale. is that the same as the OS? and what file encoding?
(check via cfadmin).
i ask, because pretty sure you can't use non-ascii file names w/cf. there's an
open bug on that:
http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#bugId=77177
only can guess that file encoding isn't latin-1, etc. and/or OS locale equals
the same language as the file name.
cfadmin gives pretty much the same information. Here's a direct copy
Server Product
ColdFusion
Version
9,0,0,241018
Edition
Developer
Serial Number
Operating System
Windows 2000
OS Version
5.0
Update Level
/C:/ColdFusion9/lib/updates/hf900-78588.jar
Adobe Driver Version
4.0 (Build 0005)
JVM Details
Java Version
1.6.0_12
Java Vendor
Sun Microsystems Inc.
Java Vendor URL
http://java.sun.com/
Java Home
C:\ColdFusion9\runtime\jre
Java File Encoding
Cp1252
Java Default Locale
en_US
File Separator
Path Separator
Line Separator
Chr(13)

Replacing non latin characters

Hi experts,
i have to check some fields of non latin characters.
When the fields include some of non latin charcters I have to replace them
with an "Y".
Have somesone a code example for this case?
Thanks for help!
Alex

This should give you an Idea
WHILE p_faxno CA sy-abcde. " to check if varaible contains any abcde...Z
p_faxno+sy-fdpos(1) = 'Y'.
ENDWHILE.
CONDENSE p_faxno NO-GAPS

Non- Latin characters not available following iCloud problem

Following help from HKQ recovering my Reminders (it turned out there was a problem with iCloud), my non-Latin characters (and the little globe icon for them have just vanished !) This must have happened during the reset or switching on iCloud. I need this really urgently to send emails to people. Please help,
thank you !

it's ok I found and added foreign keyboard. But the numbers give $ instead of £ even though it says it's on UK English,

Non-Latin Characters

I am getting an error that my file name has non-latin characters, the file is named 01h_backM.jpg I am using save for web.

Are you saving to a folder with symbols in the name? Try saving to a different folder.
Benjamin

Non-Latin characters no displaying properly in Safari on iPhone

I am having an issue where non-English (Chinese, Japanese etc) characters are displaying as squares on the iPhone's Safari browser. I've seen this issue on Windows when you haven't installed support for Asian languages.
It would appear that the version of OS-X on the iPhones does not have support for non-Latin character sets.
Has anyone else experienced this problem?

I am having an issue where non-English (Chinese,
Japanese etc) characters are displaying as squares on
the iPhone's Safari browser.
Could you provide the urls? It may be the pages have bad coding. Correctly coded pages will display according to tests I've seen:
http://homepage.mac.com/thgewecke/iphonesafarilang.jpg
But unlike OS X the iPhone has no way yet to manually correct for miscoded pages via a View > Text Encoding menu.

Non-latin characters in photo books

Has anybody used symbols or non-latin alphabets when designing photo books? They come out on screen and on proofs just fine (well... it's an Apple, isn't it?) and I assume iPhoto just goes ahead and puts Unicode characters into .pdf verbatim before uploading, however, online printing services may have a problem when processing text.
I am particularly interested in using Greek/Cyrillic alphabets when printing in the UK.

The problem has gone away. I suspect it was a problem with corrupted prefs. I trashed the Safari prefs and rebooted to clear another problem and no longer have the problem with search using Japanese characters.
FWIW, the problem I had when I trashed the prefs was with trying to mail a Safari page. I ran in to this originally a week or two ago and called Apple who told me to delete the Safari prefs and reboot. (Actually they gave an alternate procedure to try first, but I didn't bother.) That appears to be a recurrent problem and since there was no hesitation on the solution when I called I would guess that it will be fixed in an early patch. I had already tried trashing the mail prefs since that's where the problem actually appeared (an extra copy of Mail would open, and then hang) but it was in fact the Safari prefs that was causing the problem. I've had to do the delete-and-reboot routine every few days. Not sure why the reboot is required, but it obviously is since just quitting Safari or even logging out doesn't fix it.

Mountain Lion Mail cannot search for non-alpha characters in Subject Lines

Under 10.8.3, Mail 6.3 often cannot successfully find messages if the search string contains a non-alpha character.
I have only tested this searching for Subject lines that are KNOWN to contain non-alpha characters
Specfic examples:
Subject starts with "[ABC..."
Mail cannot find it if you search using "[ABC"
Mail CAN find it if you search using just "ABC"
Subject contains the numeral "2"
Mail cannont find it if you enter "2" as the search string...even if you further constrain the search to "Subject contains: 2"
Other problem characters I have found:
The failure when using square bracket is a real pain since a lot of mailing lists are tagged using strings wrapped in square brackets.
Sometimes it WORKS when I include multiple non-alpha characters in the search string, like "55" or "4/19"
Anyone else see this?

Please follow these directions to delete the Mail "sandbox" folder.
Back up all data.
Triple-click anywhere in the line below on this page to select it:
~/Library/Containers/com.apple.mail
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu.* A Finder window should open with a folder named "com.apple.mail" selected. If it does, move the selected folder — not just its contents — to the Desktop. Leave the Finder window open for now.
Log out and log back in. Launch Mail and test. If the problem is resolved, you may have to recreate some of your Mail settings. You can then delete the folder you moved and close the Finder window. If you still have the problem, quit Mail again and put the folder back where it was, overwriting the one that may have been created in its place. Post your results.
Caution: If you change any of the contents of the sandbox, but leave the folder itself in place, Mail may crash or not launch at all. Deleting the whole sandbox will cause it to be rebuilt automatically.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combinationcommand-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.

Unicode: non-Latin characters in identifiers and data

I would like to use Unicode escapes in identifiers, say create
a variable name that is Japanese. But I can't seem to get this
to work.
I have a product (Japanese Partner) that lets me key in latin
characters then converts these to Japanese (kana or Kanji,
depending on various options) in Unicode and passes them
to the input line.
But I can't get these to compile.
Also, if I code:
char Jletter = '\u2f80';
System.out.println("Jletter = " + Jletter);
The runtime output is:
Jletter = ?
I thought it was supposed to display as a Unicode escape.
TIA for any help.

Perhaps, but I'm going on:
"Programs are written in Unicode (�3.1), but lexical translations are provided (�3.2) so that Unicode escapes (�3.3) can be used to include any Unicode character using only ASCII characters."
Then ...
"3.2 Lexical Translations
A raw Unicode character stream is translated into a sequence of tokens, using the following three lexical translation steps, which are applied in turn:
1. A translation of Unicode escapes (�3.3) in the raw stream of Unicode characters to the corresponding Unicode character. A Unicode escape of the form \uxxxx, where xxxx is a hexadecimal value, represents the UTF-16 code unit whose encoding is xxxx. This translation step allows any program to be expressed using only ASCII characters.
2. A translation of the Unicode stream resulting from step 1 into a stream of input characters and line terminators (�3.4).
3. A translation of the stream of input characters and line terminators resulting from step 2 into a sequence of input elements (�3.5) which, after white space (�3.6) and comments (�3.7) are discarded, comprise the tokens (�3.5) that are the terminal symbols of the syntactic grammar (�2.3). "
I take this to mean you can Unicode escapes for Unicode characters. But
it doesn't seem to work, so maybe my understanding is deficient. Maybe
the docs need to be more clear.

Non-Latin characters in Sylpheed's subject when in gnome/kde

So, this is curious and i'm not expecting an answer, but anyway i post it:
Sylpheed 0.9.5 [simple, not claws], works ok when opened in fluxbox or window maker; but when opened in gnome or kde, following curious behaviour shows: in the "Subject" field, when I switch over to greek keyboard layout, it doesn't show greek characters but some not identified encoding, probably iso8859-2 or so. This is mirrored everywhere where "Subject" field shows [ie in the headers on top of the message]. But then, if i type some greek characters in "Subject" field (which show weird there) and then copy-paste them in the message body (when composing a message), then they show allright as the greek characters i intended to type. In the message body everything shows as it should be, ie greek, there's no problem there or when composing a message, only the subject (and only in kde & gnome). Needless to say that this "subject" encoding behaviour also shows in message list, so most messages of mine cannot be identified via message list in sylpheed.
Every locale setting in Arch is correct, so please don't focus there. This doesn't happen in slackware 9.0 or 9.1 or in debian sid, so it's probably either a gnome/kde problem or a sylpheed problem.
I'm interested to know if there's someone else facing the same problem with sylpheed in arch [and probably with gtk+1.2 apps]. By this i don't neccessarily mean with greek but say with cyrillic or some other character set and encoding.
So, this is it. Any clues?

The funny thing is that bold font [when message unread in message list] shows OK, ie in greek, but when i click on unread message, it is assumed to have been read, so it changes over to medium [non bold] and the encoding changes as well into the one that is not greek and thus unreadable. In ~/.sylpheed/sylpheedrc the fonts are:
widget_font=
message_font=-microsoft-sylfaenarm-medium-r-normal-*-*-160-*-*-p-*-iso8859-7
normal_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
bold_font=-monotype-arial-bold-r-normal-*-12-*-*-*-*-*-iso8859-7
small_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
In /etc/gtk, for gtk1.2 apps the file refering to greek encoding [el] seems to be fine [exactly the same as in slackware 9.1].

Filenames with non-latin characters aren't found by the filesystem [S]

This might be a bug, but I'm hoping it's just a config file problem.
I have a few files here and there on my NTFS drive that have Japanese characters in their filenames. Sometime recently (I don't have an exact date when they disappeared), they stopped showing up at all. If I browse to a folder that used to contain filenames with Japanese characters, it just appears empty in Gnome. Using ls from a terminal also says the directory is empty. They used to work just fine, but a recent upgrade must have broken them.
Does anyone have any ideas what I can do to get my files to appear again? Is there some way to enable unicode support for filenames or something?
Many thanks!
Edit: Rebooting the system fixed it, though I still think that was a pretty strange problem. Any ideas what was up?
Last edited by ColdPie (2007-11-11 02:07:11)

The funny thing is that bold font [when message unread in message list] shows OK, ie in greek, but when i click on unread message, it is assumed to have been read, so it changes over to medium [non bold] and the encoding changes as well into the one that is not greek and thus unreadable. In ~/.sylpheed/sylpheedrc the fonts are:
widget_font=
message_font=-microsoft-sylfaenarm-medium-r-normal-*-*-160-*-*-p-*-iso8859-7
normal_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
bold_font=-monotype-arial-bold-r-normal-*-12-*-*-*-*-*-iso8859-7
small_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
In /etc/gtk, for gtk1.2 apps the file refering to greek encoding [el] seems to be fine [exactly the same as in slackware 9.1].

We cannot type Polish (non-latin) characters in WebDynpro applications

Similar Messages

Maybe you are looking for