I'm beginning to feel like the perpetual troublemaker on this list. Here's yet another bug I found. At least, I think it is partly a new one. By the way, if you folks would prefer me to report these somewhere else, or in some other way, to be more helpful, let me know. I'm still new here. This time it's about the Windows-codepage-specific characters in the hex80-9F range and how they are handled (a) in keyboard input, and (b) in importing. Most prominent example: The Euro sign, u+20AC, hex80 in cp1252. My German keyboard has it on AltGr-e. (a) When I type AltGr-e, nothing at all happens. Other AltGr combinations work fine, so I suppose it's because of the character not being in ISO-Latin-1. I've tried to look at the code in ev_Win32Keyboard.cpp, but I'm afraid I don't really understand enough of the code to work out what's happening. (b) When I import from other applications, either through an .rtf or .txt file or through the clipboard, different things happen. If exported from MS Word or from Internet Explorer, all works fine (AW receives "€" and displays correctly). But if exported from some other applications (either plaintext editors or non-Unicode Wordprocessors: UltraEdit, Lotus Wordpro, the Windows Character Map), AW apparently interprets everything as ISO-Latin-1, so it reads u+0080. This is then, of course, displayed as an unknown-character glyph. I guess somebody needs to tell Abiword that when receiving characters from other Windows applications it should assume cp1252 as the default codepage, not ISO-Latin-1, right? Lukas ----------------------------------------------------- Lukas Pietsch University of Freiburg English Department Phone (p.) (#49) (761) 696 37 23 mailto:[EMAIL PROTECTED]
