Re: gtk2.0 conversion & prerequisites
> On Sun, 2 Jun 2002 10:14:20 +0200, > "CC" == Cyrille Chepelov <[EMAIL PROTECTED]> wrote: CC> *** libgdk-pixbuf2: CC> This one seems to have been swallowed by libgtk2.0; has CC> it ??? Yes. it's merged to gtk+2.0. CC> (I'm totally unsure it's wise to keep GNOME-Print. We're not that CC> incompetent at printing by ourselves, and unless Win32 also has GNOME-Print, CC> we'll have to keep our own way of doing, anyway. We might be able to use CC> libgnomeprintui, though). Does someone know how other projects containing Win32 is intended to do about printing? CC> It looks like the scope of imlib2 is different from imlib1; I see no CC> gdk-imlib2 package. OTOH, I see that libgtk2.0-0 seems to have built-in CC> capability to load PNG and JPEGs, and it seems we didn't need ImLib for much CC> else. Yes, we should no longer need imlib. Regards, -- Akira TAGOH : [EMAIL PROTECTED] / Japan GNOME Users Group [EMAIL PROTECTED] : [EMAIL PROTECTED] / GNOME-DB Project : [EMAIL PROTECTED] / Red Hat, Inc. : [EMAIL PROTECTED] / Debian Project ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
dia 0.90: printing Japanese using --enable-freetype ?
I tried to build dia 0.90 using --enable-freetype everything seems to work fine except printing using fonts which have many characters (e.g. Japanese TrueType fonts like Kochi Mincho or other big fonts like MS Arial Unicode). A simple example dia file 'test.dia' is attached (decompressed). This file contains the string "xyz" two times, once using the Japanese "Kochi Mincho" font and once more using the Latin1 only "Omega Serif" font[1]. The "xyz" in from the "Omega Serif" font prints correctly, the "xyz" from the "Kochi Mincho" prints as three double width yen-signs ($B!o!o!o(B) . This double width yen-sign happens to be the very last character of kochi-mincho.ttf (I checked that with pfaedit). Both fonts are embedded completely into the PostScript output: %%BeginResource: font OmegaSerif88591 %!PS-TrueTypeFont 11 dict begin /FontName /OmegaSerif88591 def [... snip ...] %%BeginResource: font Kochi-Mincho %!PS-TrueTypeFont 11 dict begin /FontName /Kochi-Mincho def [... snip ...] %%EndProlog Then the fonts are both used in the same way: %%BeginSetup %%EndSetup %%Page: 1 1 gs [... snip ...] /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi ] /e0 exch def /Kochi-Mincho_e0 undefinefont /Kochi-Mincho_e0 /Kochi-Mincho findfont dup length dict begin {1 index /FID ne {def} {pop pop} ifelse} forall /Encoding e0 def currentdict end definefont pop /Kochi-Mincho_e0 ff 2.00 scf sf ( !") gs 1 -1 sc sh gr 5.00 5.00 m /OmegaSerif88591_e0 undefinefont /OmegaSerif88591_e0 /OmegaSerif88591 findfont dup length dict begin {1 index /FID ne {def} {pop pop} ifelse} forall /Encoding e0 def currentdict end definefont pop /OmegaSerif88591_e0 ff 2.00 scf sf ( !") gs 1 -1 sc sh gr gr showpage This works for OmegaSerif88591, but fails for Kochi-Mincho. I found that it fails for all fonts which have many characters, i.e. all east Asian TrueType fonts and also fonts like MS Arial Unicode or Bitstream Cyberbit which try to cover most of Unicode. The problem is not only that one cannot print the Asian glyphs, one cannot print anything correctly when using these fonts, not even a simple ASCII string like "xyz". If this problem is solved, I guess printing will work for east Asian languages when '--enable-freetype' is used. Looking into the above postscript file, I see that in both cases the "xyz" is encoded as "( !")", i.e. only one byte is used for each character. How is this supposed to work for a font which has much more than 256 characters? Is the font split up in smaller portions? Does /OmegaSerif88591_e0 specify a subset of the /OmegaSerif88591 font? Do you have any hints how this can be fixed? Footnotes: [1] both fonts are free, if you don't already have them you can download them here to reproduce the problem: http://www.suse.de/~mfabian/misc/kochi-mincho.ttf http://www.suse.de/~mfabian/misc/lt1-r-omega-serif.ttf test.dia Description: Binary data -- Mike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian $B?gL2ITB-$O;E;v$NE($@!#(B
Re: dia 0.90: printing Japanese using --enable-freetype ?
Le Wed, Jun 05, 2002, à 04:37:20PM +0200, Mike Fabian a écrit: > [... snip ...] > > /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi > ] /e0 exch def Can you unsnip the complete array ? > The problem is not only that one cannot print the Asian glyphs, one > cannot print anything correctly when using these fonts, not even a > simple ASCII string like "xyz". If this problem is solved, I guess > printing will work for east Asian languages when '--enable-freetype' > is used. Does it work, in your experience, when --disable-freetype ? Which locale are you using ? > Looking into the above postscript file, I see that in both cases the > "xyz" is encoded as "( !")", i.e. only one byte is used for each > character. How is this supposed to work for a font which has much more > than 256 characters? Is the font split up in smaller portions? Does > /OmegaSerif88591_e0 specify a subset of the /OmegaSerif88591 font? Yes: > /Kochi-Mincho_e0 undefinefont > /Kochi-Mincho_e0 > /Kochi-Mincho findfont > dup length dict begin > {1 index /FID ne {def} {pop pop} ifelse} forall > /Encoding e0 def > currentdict end > definefont pop Unfortunately, this doesn't work as well in practice for non-latinN as I originally thought it would. Proper solution will require talking CID and doing some font matching (which is best done by Pango). -- Cyrille -- Grumpf. ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
Re: dia 0.90: printing Japanese using --enable-freetype ?
Cyrille Chepelov <[EMAIL PROTECTED]> writes: > Le Wed, Jun 05, 2002, � 04:37:20PM +0200, Mike Fabian a �crit: > > >> [... snip ...] >> >> /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi >> ] /e0 exch def > > Can you unsnip the complete array ? %%BeginSetup %%EndSetup %%Page: 1 1 gs 28.346457 -28.346457 scale 2.822200 -26.877799 translate n 0.00 0.00 m 15.355599 0.00 l 15.355599 24.055599 l 0.00 24.055599 l 0.00 0.00 l clip 0.00 0.00 0.00 srgb 5.00 3.00 m [ /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /x /y /z /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi ] /e0 exch def /Kochi-Mincho_e0 undefinefont /Kochi-Mincho_e0 -- Mike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。 ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
Re: dia 0.90: printing Japanese using --enable-freetype ?
Cyrille Chepelov <[EMAIL PROTECTED]> writes: >> The problem is not only that one cannot print the Asian glyphs, one >> cannot print anything correctly when using these fonts, not even a >> simple ASCII string like "xyz". If this problem is solved, I guess >> printing will work for east Asian languages when '--enable-freetype' >> is used. [...] > Which locale are you using ? ja_JP.eucJP, ja_JP.UTF-8, de_DE@euro, ... with dia-0.90 and --enable-freetype the problem seems to be the same in all locales. -- Mike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian $B?gL2ITB-$O;E;v$NE($@!#(B ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
Re: dia 0.90: printing Japanese using --enable-freetype ?
Cyrille Chepelov <[EMAIL PROTECTED]> writes: > Le Wed, Jun 05, 2002, à 04:37:20PM +0200, Mike Fabian a écrit: > > >> [... snip ...] >> >> /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi >> ] /e0 exch def > > Can you unsnip the complete array ? > >> The problem is not only that one cannot print the Asian glyphs, one >> cannot print anything correctly when using these fonts, not even a >> simple ASCII string like "xyz". If this problem is solved, I guess >> printing will work for east Asian languages when '--enable-freetype' >> is used. > > Does it work, in your experience, when --disable-freetype ? No, Japanese printing does not work without '--enable-freetype' either. In that case fonts are not embedded into the PostScript output, printer resident (or Ghostscript resident) fonts are used instead. I could make Japanese printing work with dia-0.88.1 by applying the attached patch, but this patch doesn't work anymore for dia-0.90, because the reencoding of the fonts for printing seems to have been changed on dia-0.90 and I was unable to fix it. This patch does: - use gdk_fontset_load instead of gdk_font_load *except* for fonts which have "fontspecific" in their XLFD (Symbol and Dingbats), for these fonts gdk_fontset_load failed for reasons unknown to me. - increase NUM_X11_FONTS to 3 and add the URW PostScript fonts as the preferred fonts to the font_data[] array in font.c and leave the bitmap fonts only as a fallback The bitmap fonts are not scalable if the directories are marked with ":unscaled" in /etc/X11/XF86Config. SuSE Linux >= 7.3 has ":unscaled" by default on all directories containing bitmap fonts, RedHat Linux as well. This causes problems with dia as Dia can't scale the fonts anymore. Using the scalable URW PostScript fonts fixes the problem. On top of that the URW fonts look better and agree better with the printing output one gets. For each of the basic Adobe PostScript fonts there is one URW font which very closely resembles the Adobe font. Therefore using the URW fonts for display on X11 as well will look very similar to the final output on the printer. If one prints via Ghostscript, the URW fonts are even used for printing, i.e. using the URW fonts on screen as well improves WYSIWYG. The URW fonts are available on practically all Linux systems, therefore it should not hurt to make them the default and leave the adobe bitmap fonts only as a fallback. - added Japanese fonts to font_data[]: + /* Japanese, Sat Mar 2 02:13:21 2002 Mike Fabian <[EMAIL PROTECTED]> */ + { "Ryumin-Light-EUC-H", +"Ryumin-Light-EUC-H", +{ "-kochi-mincho-medium-r-normal-*-%d-*-*-*-*-*-*-*", + NULL, + NULL +} + }, + { "GothicBBB-Medium-EUC-H", +"GothicBBB-Medium-EUC-H", +{ "-kochi-gothic-medium-r-normal-*-%d-*-*-*-*-*-*-*", + NULL, + NULL } - avoid the reencoding of the Japanese fonts and the URW Dingbats font: diff -ru dia-0.88.1.orig/app/render_eps.c dia-0.88.1/app/render_eps.c --- dia-0.88.1.orig/app/render_eps.c Mon Mar 26 03:05:16 2001 +++ dia-0.88.1/app/render_eps.c Thu Mar 21 12:36:28 2002 @@ -167,7 +167,12 @@ { /* Don't reencode the Symbol font, as it doesn't work in latin1 encoding. * Instead, just define Symbol-latin1 to be the same as Symbol. */ - if (!strcmp(fontname, "Symbol")) + /* Don't do that for the Dingbats and the Japanese fonts either! */ + /* Sat Mar 2 02:08:34 2002 Mike Fabian <[EMAIL PROTECTED]> */ + if (strcasestr(fontname, "Symbol") || + strcasestr(fontname, "Dingbats") || + strcasestr(fontname, "Ryumin") || + strcasestr(fontname, "GothicBBB")) fprintf(file, "/%s-latin1\n" "/%s findfont\n" @@ -310,6 +315,8 @@ print_reencode_font(file, "Symbol"); print_reencode_font(file, "ZapfChancery-MediumItalic"); print_reencode_font(file, "ZapfDingbats"); + print_reencode_font(file, "Ryumin-Light-EUC-H"); + print_reencode_font(file, "GothicBBB-Medium-EUC-H"); #endif /* !HAVE_UNICODE */ fprintf(file, This made Japanese work on screen and for printing. It also made the Dingbats font print correctly, which it didn't do before. Unfortunately this patch doesn't work for Japanese anymore for dia-0.90, print_reencode seems to be gone in dia-0.90 and I could not yet find how to adapt this patch to make it work again. dia-fonts.dif Description: Binary data -- Mike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian $B?gL2ITB-$O;E;v$NE($@!#(B
Re: dia 0.90: printing Japanese using --enable-freetype ?
Mike Fabian <[EMAIL PROTECTED]> writes: > Cyrille Chepelov <[EMAIL PROTECTED]> writes: > >>> The problem is not only that one cannot print the Asian glyphs, one >>> cannot print anything correctly when using these fonts, not even a >>> simple ASCII string like "xyz". If this problem is solved, I guess >>> printing will work for east Asian languages when '--enable-freetype' >>> is used. >> >> Does it work, in your experience, when --disable-freetype ? > > No, Japanese printing does not work without '--enable-freetype' > either. In that case fonts are not embedded into the PostScript > output, printer resident (or Ghostscript resident) fonts are used > instead. > > I could make Japanese printing work with dia-0.88.1 by applying the > attached patch, but this patch doesn't work anymore for dia-0.90, > because the reencoding of the fonts for printing seems to have been > changed on dia-0.90 and I was unable to fix it. [...] > Unfortunately this patch doesn't work for Japanese anymore for > dia-0.90, print_reencode seems to be gone in dia-0.90 and I could not > yet find how to adapt this patch to make it work again. Here I attach my current tentative patch against dia-0.90. I believe parts of it are still useful, for example using the URW fonts as the default fonts for display on X11 in preference to the adobe bitmap fonts. Maybe you can include that into the next version of dia. For the entries concerning freetype in font_data[] I used the URW fonts whereever possible as well because they are free, available on most Linux distributions and closely match the original Adobe PostScript fonts. This might be useful for inclusion into the next version of dia as well. For the Asian fonts I also added freetype related entries in font_data[], using freely available TrueType fonts (the 'Baekmuk' font for Korean, the 'Kochi' fonts for Japanese and the 'Arphic PL' fonts for Chinese). But I couldn't make the printing for Asian languages work again like it did in dia-0.88.1. Therefore I tried '--enable-freetype' in the hope that this would make printing of Asian languages possible. I believe if the printing problem with '--enable-freetype' can be solved, it is a better solution than the old printing support which I used in dia-0.88.1 to print Japanese, because it embeds the fonts in the PostScript output and therefore doesn't require the printer to have the fonts. It is nice to be able to print CJK on any printer, even without CJK fonts. On top of that, when the freetype support is enabled, dia automatically finds all installed TrueType and Type1 fonts in the X11 font-path, even those which are not mentioned in font_data[] at all. This makes it very easy for the user to use other fonts with dia, one just has to drop them in a directory in the X11 font path and that's it. Therefore I believe that freetype is the way to go for dia. Is there an easy way to make the printing work for large fonts? dia-fonts.dif Description: Binary data -- Mike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian $B?gL2ITB-$O;E;v$NE($@!#(B
Re: dia 0.90: printing Japanese using --enable-freetype ?
Le Wed, Jun 05, 2002, à 06:02:16PM +0200, Mike Fabian a écrit: > Cyrille Chepelov <[EMAIL PROTECTED]> writes: > > > Le Wed, Jun 05, 2002, ??? 04:37:20PM +0200, Mike Fabian a ???crit: > > > > > >> [... snip ...] > >> > >> /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi > >> ] /e0 exch def > > > > Can you unsnip the complete array ? > 5.00 3.00 m [ /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi >/xi > /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi > /x /y /z /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi And you actually tried to print the (latin) letters x and z from Kochi Mincho ? -- Cyrille, puzzled. -- Grumpf. ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
Re: dia 0.90: printing Japanese using --enable-freetype ?
Cyrille Chepelov <[EMAIL PROTECTED]> writes: > Le Wed, Jun 05, 2002, � 06:02:16PM +0200, Mike Fabian a �crit: >> Cyrille Chepelov <[EMAIL PROTECTED]> writes: >> >> > Le Wed, Jun 05, 2002, ??? 04:37:20PM +0200, Mike Fabian a ???crit: >> > >> > >> >> [... snip ...] >> >> >> >> /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi >> >> ] /e0 exch def >> > >> > Can you unsnip the complete array ? > >> 5.00 3.00 m [ /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi >/xi >> /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi >> /x /y /z /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi /xi > > > And you actually tried to print the (latin) letters x and z from Kochi > Mincho ? Yes. Looks like in this screen shot: http://www.suse.de/~mfabian/screeenshots/dia-0.90-freetype-problem-with-big-fonts.png Full PostScript output file is here: http://www.suse.de/~mfabian/misc/output.ps.bz2 I believe you can easily reproce that using the fonts http://www.suse.de/~mfabian/misc/kochi-mincho.ttf http://www.suse.de/~mfabian/misc/lt1-r-omega-serif.ttf I had the same problem with all TrueType fonts which contained thousands of glyphs. kochi-mincho.ttf is a nice test example but the problem seems to occur with all other big fonts as well. > -- Cyrille, puzzled. -- Mike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。 ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
Re: dia 0.90: printing Japanese using --enable-freetype ?
On Wed, 5 Jun 2002, Mike Fabian wrote: > Mike Fabian <[EMAIL PROTECTED]> writes: > > I believe if the printing problem with '--enable-freetype' can be > solved, it is a better solution than the old printing support which I > used in dia-0.88.1 to print Japanese, because it embeds the fonts in > the PostScript output and therefore doesn't require the printer to > have the fonts. It is nice to be able to print CJK on any printer, > even without CJK fonts. > > On top of that, when the freetype support is enabled, dia > automatically finds all installed TrueType and Type1 fonts in the X11 > font-path, even those which are not mentioned in font_data[] at all. > This makes it very easy for the user to use other fonts with dia, one > just has to drop them in a directory in the X11 font path and that's > it. > > Therefore I believe that freetype is the way to go for dia. > > Is there an easy way to make the printing work for large fonts? > > I have submitted a patch for printing Simplified Chinese characters, which works for Simplified Chinese CJK fonts, and I believe it should also work for other CJK fonts (Korean & Japanese, by properly modifying the font_data structure and disabling freetype support), but it breaks the printing of non-latin0 fonts. Please read the discussions on the following subjects: About the zh_CN.GB2312 locale printing on the Simpl. Chinese and other non-latin1 locales Printing and weird (non-latin0 ;-) ) charsets -- summary LB -- ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list
Re: dia 0.90: printing Japanese using --enable-freetype ?
> On Wed, 05 Jun 2002 19:02:42 +0200, > "MF" == Mike Fabian <[EMAIL PROTECTED]> wrote: MF> Here I attach my current tentative patch against dia-0.90. > On Wed, 05 Jun 2002 19:02:42 +0200, > "MF" == Mike Fabian <[EMAIL PROTECTED]> wrote: MF> diff -ru dia-0.90/app/render_eps.c dia-0.90.new/app/render_eps.c MF> --- dia-0.90/app/render_eps.c Tue May 7 22:52:58 2002 MF> +++ dia-0.90.new/app/render_eps.c Mon Jun 3 12:45:23 2002 MF> @@ -499,7 +499,12 @@ MF> #ifndef HAVE_UNICODE MF>/* Don't reencode the Symbol font, as it doesn't work in latin1 encoding. MF> * Instead, just define Symbol-latin1 to be the same as Symbol. */ MF> - if (!strcmp(fontname, "Symbol")) MF> + /* Don't do that for the Dingbats and the Japanese fonts either! */ MF> + /* Sat Mar 2 02:08:34 2002 Mike Fabian <[EMAIL PROTECTED]> */ MF> + if (strcasestr(fontname, "Symbol") || MF> + strcasestr(fontname, "Dingbats") || MF> + strcasestr(fontname, "Ryumin") || MF> + strcasestr(fontname, "GothicBBB")) MF> fprintf(file, MF> "/%s-latin1\n" MF> "/%s findfont\n" I'm sure it's l10n, not i18n. but I have no idea to fix this now. MF>{ "GothicBBB-Medium", MF> - "GothicBBB-Medium", MF> - { "-*-gothic-medium-r-normal-*-%d-*-*-*-*-*-*-*", MF> - NULL MF> - } MF> +"GothicBBB-Medium-EUC-H", MF> +{ "-kochi-gothic-medium-r-normal-*-%d-*-*-*-*-*-*-*", MF> + NULL, MF> + NULL MF> +}, MF> +"Kochi Gothic", "Regular" MF>}, No, this is wrong. if dia supports the vertical writing, do you intend to add -EUC-V entry too? and that patch is meaningless because right now correctly PostScript dia outputs doesn't depend on Ghostscript. MF>{ "Ryumin-Light", MF> - "Ryumin-Light", MF> - { "-*-mincho-medium-r-normal-*-%d-*-*-*-*-*-*-*", MF> - NULL MF> - } MF> +"Ryumin-Light-EUC-H", MF> +{ "-kochi-mincho-medium-r-normal-*-%d-*-*-*-*-*-*-*", MF> + NULL, MF> + NULL MF> +}, MF> +"Kochi Mincho", "Regular" MF>}, ditto. MF> @@ -503,8 +576,10 @@ MF> bufsize = strlen(x11_font)+6; /* Should be enought*/ MF> buffer = (char *)g_malloc(bufsize); MF> g_snprintf(buffer, bufsize, x11_font, 100); MF> - MF> -gdk_font = gdk_font_load(buffer); MF> + MF> +gdk_font = gdk_fontset_load (buffer); MF> +if (!gdk_font) gdk_font = gdk_font_load(buffer); MF> + MF> if (gdk_font!=NULL) { font-> fontname_x11 = x11_font; MF> } MF> @@ -521,7 +596,9 @@ MF>buffer = (char *)g_malloc(bufsize); MF>g_snprintf(buffer, bufsize, x11_font, 100); MF> - gdk_font = gdk_font_load(buffer); MF> + gdk_font = gdk_fontset_load(buffer); MF> + if (!gdk_font) gdk_font = gdk_font_load(buffer); MF> + MF>g_free(buffer); MF>if (gdk_font!=NULL) { MF> message_warning(_("Warning no X Font for %s found, \nusing %s instead.\n"), font->public.name, x11_font); those codes shouldn't be needed because those gdk_font_load() is just used for checking existence of fonts. it's not related for displaying and printing. Did you see any problem? original codes works for me though. Regards, -- Akira TAGOH : [EMAIL PROTECTED] / Japan GNOME Users Group [EMAIL PROTECTED] : [EMAIL PROTECTED] / GNOME-DB Project : [EMAIL PROTECTED] / Red Hat, Inc. : [EMAIL PROTECTED] / Debian Project ___ Dia-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/dia-list