this seems to me a bug so here's the report:

http://www.realsoftware.com/feedback/viewreport.php?reportid=zjzlfvyl

Tomas

> the keydown event pass key with encoding=utf8. But this is the wrong
> encoding because instead of showing ö (which I pressed in the
> control) it shows ?. In the debugger I can change the key encoding
> and it seems that the correct encoding is ISO-8859-1, so this looks
> like a bug to me.
>
> I'm running Ubuntu Feisty Fawn.
>
> Can someone confirm? it's very easy to reproduce:
>
> - New project
> - window.keydown put just a break
> - Start it press ö or ä or ü and you'll see that in the debugger
> they're all wrong.
>
> If for ex you use the keydown event in an editfield to manually
> process text it won't be shown chars correctly (me.text=me.text+key
> will be full of ?).
>
> Tomas
>
>
>
>> On May 02, 2007, at 22:53 UTC, Tomas Camin wrote:
>>
>>> key as string passed by keydown event has an encoding different than
>>> encoding.systemdefault under linux. Type for example "ö". Is this a
>>> bug?
>>
>> No, there's no reason to suppose the encoding of any particular  
>> string
>> would be Encodings.SystemDefault.  I'm not sure it's that on the Mac
>> either.  But... so?
>>
>>> How do I get the key encoding?
>>
>> Key.Encoding.
>>
>> Best,
>> - Joe
>>
>> --
>> Joe Strout -- [EMAIL PROTECTED]
>> Strout Custom Solutions
>>
>>
>> _______________________________________________
>> Unsubscribe or switch delivery mode:
>> <http://www.realsoftware.com/support/listmanager/>
>>
>> Search the archives:
>> <http://support.realsoftware.com/listarchives/lists.html>
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to