Issue 345

Summary: Make Open office Draw Chinese GB2312 character
Product: gsl Reporter: issues@www <issues>
Component: codeAssignee: Unknown <non-migrated>
Status: CLOSED WONT_FIX QA Contact: issues@www <issues>
Severity: Trivial    
Priority: P3 CC: issues
Version: 613   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: PATCH Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
patch for salgdi3.cxx none

Description issues@www 2001-01-28 06:51:47 UTC 
This patch Can Make OO Draw Chinese GB2312 Character correctly
I just add some decoding code in ConvertTextItem16 function
(and char of GB2312 char with 0x7f, this convert it to iso2022 encoding,
because under X, fonts for GB2312 in iso2022(KJS) Encoding)
But you have to set fonts manually if you want it Display Chinese Correctly.
I'll add some code to make it auto select fonts between chinese and other
Latin Character.
Comment 1 issues@www 2001-01-28 06:52:31 UTC 
Created attachment 64 [details]
patch for salgdi3.cxx
Comment 2 Unknown 2001-01-31 11:41:11 UTC 
Thanks for the patch, but it is impossible for us to integrate this:
- Please send an DIFF which includes only your changes and not the complete file 
- If your changes are more than 10 lines, please send us at first the Copyright 
Assignment Form
See: http://www.openoffice.org/contributing.html
Comment 3 michael.bemmer 2003-03-11 18:11:26 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-11 18:11:49 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 5 michael.bemmer 2003-03-11 18:18:54 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.