Issue 15451 - X11: Input encoding for windows set incorrectly
Summary: X11: Input encoding for windows set incorrectly
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.3
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: OOo 1.0.4
Assignee: ed
QA Contact: issues@porting
URL:
Keywords: merge_pending
Depends on:
Blocks:
 
Reported: 2003-06-10 08:46 UTC by ed
Modified: 2008-03-24 12:40 UTC (History)
3 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
cd vcl; patch -p0 < vcl.PORTS103.i18n.patch (652 bytes, patch)
2003-06-10 08:47 UTC, ed 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ed 2003-06-10 08:46:38 UTC 
For 103 version of PORTS.  Code was added to revise salframe.cxx's input method to use UTF8 if 
an input method object is present.  On OS X, we do have an input method object since the X server 
will perform IM filtering of compositing events (dual keystroke accented character combinations).  
The actual input encoding, however, is not Unicode.  Therefore comment out the defaulting to 
UTF8 for the input method encoding in salframe and use the default system encoding (the thread 
encoding) so we can properly interpret events flying out of a Mac X server.
Comment 1 ed 2003-06-10 08:47:25 UTC 
Created attachment 6763 [details]
cd vcl; patch -p0 < vcl.PORTS103.i18n.patch
Comment 2 ed 2003-06-10 08:48:00 UTC 
Added keyword approval_pending for commit to PORTS.
Comment 3 fa 2003-06-10 14:50:30 UTC 
Patch is completely Mac OS X specific, therefore approved for commit to PORTS.

Dan
Comment 4 fa 2003-06-10 15:16:46 UTC 
Patch committed to PORTS.

Dan
Comment 5 Martin Hollmichel 2003-07-03 09:21:03 UTC 
is this fixed now, Ed ?
Comment 6 fa 2003-07-03 14:06:08 UTC 
Martin,

Yes, this works as expected in PORTS.  Its present in our 1.0.3 GM release.

Dan
Comment 7 fa 2004-01-11 22:16:43 UTC 
Hmm, see Issue 29326 for some info, that issue invalidates this fix.  this fix also got merged to 
1.1.0 so closing anyway
Comment 8 Martin Hollmichel 2008-03-24 12:40:13 UTC 
close issue