Bug 59788 - Can't print out for CJK.
Summary: Can't print out for CJK.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gedit
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-13 11:44 UTC by Akira TAGOH
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-01 22:47:37 UTC
Embargoed:


Attachments (Terms of Use)
I made a patch. is this useful? (14.48 KB, patch)
2002-02-13 11:47 UTC, Akira TAGOH
no flags Details | Diff

Description Akira TAGOH 2002-02-13 11:44:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20020129

Description of problem:
gedit is hardcoded a font for the printing. so that the characters which can't
handle with Helvetica and Courier isn't printed out.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.LANG=ja_JP.eucJP gedit
2.input something Japanese.
3.preview or print out
	

Actual Results:  characters is nothing. ASCII only is printed out.

Expected Results:  those characters should be printed out correctly.

Additional info:

Comment 1 Akira TAGOH 2002-02-13 11:47:00 UTC
Created attachment 45502 [details]
I made a patch. is this useful?

Comment 2 Havoc Pennington 2002-02-13 16:12:17 UTC
Can we submit this to the upstream gedit maintainers?

Comment 3 Akira TAGOH 2002-02-14 07:09:25 UTC
I re-create a patch for CVS, I already filed to bugzilla.
see also http://bugzilla.gnome.org/show_bug.cgi?id=71364

Comment 4 Havoc Pennington 2002-03-01 22:47:32 UTC
Feel free to rebuild the gedit rpm with this patch if you want. I'll do it 
soon if you don't have time.

Comment 5 Akira TAGOH 2002-03-04 09:45:29 UTC
Ok, I have build it with my patch. this problem is fixed in 0.9.4-9. Thanks.


Note You need to log in before you can comment on or make changes to this bug.