Bugzilla – Bug 61299
Japanese strings don't print out with OOo on SL9.2 beta3
Last modified: 2007-06-05 12:40:52 UTC
Japanese strings displays at textarea in OOo, but Japanese strings printout is be blank.
<!-- SBZ_reproduce --> Open this file with OOo, ftp://ftp.novell.co.jp/outgoing/SuSE/font_test.doc printer setting need to be done on the system before this operation. Printout font_test.doc from OOo. Japanese strings will be blank.
At Gnome session, Japanese strings printout be done correctly. This bug is seen with KDE session.
OOo in the gnome session has also many bugs: see bug 61365
The doc file above can't be shown correctly when you don't install Novell-ricoh-fonts.
ftp://ftp.novell.co.jp/outgoing/nld/ja_commercial/Novell-ricoh-fonts- 0.20040921-1.3.1.noarch.rpm This package will install the Novell-ricoh-fonts and this will configure the OOo replacing font on SL9.2.
Of course, when you installed Novell-ricoh-fonts, OOo works. But not every user has Novell-ricoh-fonts, and this doc file isn't shown correctly on such a system. Should be anohter bug. I confirmed that OOo printing of this doc file works fine in the Gnome session. Since this is related with KDE-OOo, I add kendy to Cc.
Added OOo maintainer to Cc, too.
It could be solved in the config file /usr/lib/ooo-1.1/share/registry/data/org/openoffice/VCL.xcu For each known font there could be defined subtitutions for the fonts used on the screen, in MS file formats, in post script and in HTML file format. The following example defines substitutions for the font Thorndale AMT: <node oor:name="thorndaleamt" oor:op="replace"> <prop oor:name="SubstFonts"> <value>thorndaleamt;thorndale;thorndaleamt;timesnewroman;nimbusromanno9l;nimbusromanno9l;times;timesroman;newyork;timmons;serif;lucidaserif;lucidabright;roman;nimbusromanno9;bookman;itcbookman;garamond;garamondmt;palatino</value> </prop> <prop oor:name="SubstFontsMS"> <value>Times New Roman</value> </prop> <prop oor:name="SubstFontsPS"> <value>Times</value> </prop> <prop oor:name="SubstFontsHTML"> <value>serif</value> </prop> <prop oor:name="FontWeight"> <value>Normal</value> </prop> <prop oor:name="FontWidth"> <value>Normal</value> </prop> <prop oor:name="FontType"> <value>Default,Standard,Normal,Serif</value> </prop> </node> I do not know if something like that could be defined for the Japanese, Chinese, etc. fonts and how much time it could take.
It's not reproducible here. The visible PostScript with japanese letters is created both on Gnome and KDE sessions. Nevertheless, MS P Mincho and MS P Gothic seem not well substituted. With the Novell-ricoh-fonts on STABLE, they are not printed at all. With the one from ftp.novell.co.jp, it's shown better in the window (mincho is shown as mincho), but both are printed in gothic.
* This comment was added by mail. Please try http://w3.suse.de/~mfabian/misc/fonts-config-20041001-1.noarch.rpm http://w3.suse.de/~mfabian/misc/fonts-config-20041001-1.src.rpm http://w3.suse.de/~mfabian/misc/commercial/Novell-ricoh-fonts-0.20040603-3.noarch.rpm http://w3.suse.de/~mfabian/misc/commercial/Novell-ricoh-fonts-0.20040603-3.src.rpm Seems to work somewhat better. There is a very strange effect though: The title line for the 8th font on the second page shows "MS PGothic" in the OpenOffice buffer but "MS UIGo thic" (with that strange line break!) in the printout. Same for the second font on the third page. In the OpenOffice buffer one sees "MS Gothic" and in the printout "MSUIGo thic" Any ideas what's wrong here? The behavior is the same if only the Sazanami fonts are installed or if the Sazanami fonts *and* the Novell-ricoh-fonts are installed.
Created attachment 24408 [details] openoffice-print.png screen shot illustrating the problem in the last comment.
Reduce priority to major because it works much better now than in the original report (although it still doesn't work perfectly).
Created attachment 79474 [details] font_test.doc attaching font_test.doc for retesting with SuSE 10.1.
Created attachment 79476 [details] font_test.ps
Created attachment 79477 [details] font_test.png
The remaining problem explained in comment #10 seems to be fixed in SuSE Linux 10.1 RC1, see the postscript file attached in comment #14 and the screenshot of kghostview in comment #15. By the way, "gv" could display only the first page of the postscript file from comment #14.
closing as FIXED.