GNOME Bugzilla – Bug 34953
Texttool does not work.
Last modified: 2002-05-06 07:38:22 UTC
Package: gimp Version: 1.1.30 Name...........: Stephan Hegel Email..........: stephan.hegel@gmx.de Platform.......: Siemens Scenic 710, Linux 2.2.16 GIMP Version...: 1.1.30 GTK Version....: 1.2 WM/Version.....: Enlightenment 0.16 --- Problem description: Using the Texttool opens the Fontselector Window. I choose a font and the preview displays the choosen font correctly. Pressing the O.K. button pops up a window which states that the font was not found. The font name is not the same I have choosen. However, the font exists on the system. (xlsfonts). --- --- How to repeat: See Problem description. --- --- Other comments: Screenshot available on request. --- ------- Additional Comments From Simon.Budig@unix-ag.org 2000-12-15 07:26:57 ---- Subject: Re: Bug#34953: Texttool does not work From: Simon Budig <Simon.Budig@unix-ag.org> To: 34953@bugs.gnome.org Cc: Stephan Hegel <stephan.hegel@gmx.de> Message-Id: <20001215132657.A40366@vmax.unix-ag.uni-siegen.de> Date: Fri, 15 Dec 2000 13:26:57 +0100 Stephan Hegel (stephan.hegel@gmx.de) wrote: > 2. It does not matter what font size I select, the error message states > always trice of the size of the requested font. A 180 font produces > an error message asking for 540 font. The problem here is, that the text-tool does some antialiasing, by requesting a font three times as specified and then downscales the resulting image. You can disable this by doubleclicking on the Tool-Icon (to open the tool-options) and disable antialiasing. We probably should automagically disable the antialiasing, if the "bigger" font is unavailable. Bye, Simon -- Simon.Budig@unix-ag.org http://www.home.unix-ag.org/simon/ ------- Additional Comments From austin@gimp.org 2000-12-15 07:40:34 ---- Subject: Re: Bug#34953: Texttool does not work From: Austin Donnelly <austin@gimp.org> To: 34953@bugs.gnome.org Message-Id: <14906.4418.478059.392196@hornet.cl.cam.ac.uk> Date: Fri, 15 Dec 2000 12:40:34 +0000 On Friday, 15 Dec 2000, Simon Budig wrote: > Stephan Hegel (stephan.hegel@gmx.de) wrote: > > 2. It does not matter what font size I select, the error message states > > always trice of the size of the requested font. A 180 font produces > > an error message asking for 540 font. > > The problem here is, that the text-tool does some antialiasing, by > requesting a font three times as specified and then downscales the > resulting image. You can disable this by doubleclicking on the > Tool-Icon (to open the tool-options) and disable antialiasing. > > We probably should automagically disable the antialiasing, if the > "bigger" font is unavailable. When I put the gtk text tool in to the gimp all those years ago, I did a bit of poking around and fixed the error message so that: If the font doesn't exist, tell the user about it also, if the antialias toggle is turned on tell the user to try again with it off. I don't know what happened to this logic; it might still be there, but the error message is now produced in a different place. Basically someone broke my lovely code! :) Nowadays, the message should also tell people to change to pixels rather than points if the font isn't found (and the image res != monitor res). Austin ------- Additional Comments From austin@gimp.org 2000-12-15 14:36:50 ---- Subject: Re: Bug#34953: Texttool does not work From: Austin Donnelly <austin@gimp.org> To: 34953@bugs.gnome.org Message-Id: <14906.29394.828848.243976@hornet.cl.cam.ac.uk> Date: Fri, 15 Dec 2000 19:36:50 +0000 On , 15 Dec 2000, Sven Neumann wrote: > Will you fix the beloved code so it works again? The real problem is that linux font servers are quite forgiving and will scale bitmaps to give you something that almost works. To test this properly I need my trusty old NCD X terminal from the stone ages - it only does bitmap fonts, and won't even scale them! Austin ------- Additional Comments From Simon.Budig@unix-ag.org 2000-12-16 13:59:50 ---- Subject: Re: Bug#34953: Texttool does not work (fwd) From: Simon Budig <Simon.Budig@unix-ag.org> To: 34953@bugs.gnome.org Message-Id: <20001216195950.B40398@vmax.unix-ag.uni-siegen.de> Date: Sat, 16 Dec 2000 19:59:50 +0100 [Forwarding this again, because of an ancient bug in the bugtracker...] ----- Forwarded message from Simon Budig <simon@vmax.unix-ag.uni-siegen.de> ----- Date: Sat, 16 Dec 2000 19:46:25 +0100 From: Simon Budig <simon@vmax.unix-ag.uni-siegen.de> To: Austin Donnelly <austin@gimp.org>, 34953@bugs.gnome.org Subject: Re: Bug#34953: Texttool does not work Austin Donnelly (austin@gimp.org) wrote: > The real problem is that linux font servers are quite forgiving and > will scale bitmaps to give you something that almost works. [Assuming XFree86] If you append ":noscaled" to the Elements of the Fontpath that point to Bitmap Fonts XFree86 wont scale the fonts. So you can test this behaviour. Bye, Simon -- Simon.Budig@unix-ag.org http://www.home.unix-ag.org/simon/ ----- End forwarded message ----- -- Simon.Budig@unix-ag.org http://www.home.unix-ag.org/simon/ ------- Additional Comments From stephan.hegel@gmx.de 2000-12-16 17:43:12 ---- Subject: Re: Bug#34953: Texttool does not work From: Stephan Hegel <stephan.hegel@gmx.de> To: 34953@bugs.gnome.org Message-Id: <29047.977006592@www14.gmx.net> Date: Sat, 16 Dec 2000 23:43:12 +0100 (MET) Simon Budig wrote: > The problem here is, that the text-tool does some antialiasing, by > requesting a font three times as specified and then downscales the > resulting image. You can disable this by doubleclicking on the > Tool-Icon (to open the tool-options) and disable antialiasing. Switching off antialiasing really changes the things a bit: now it is asking for a "140" size font. But I still get an error message since it is asking for a "140-1-1" font instead for the "140-75-75" font. > We probably should automagically disable the antialiasing, if the > "bigger" font is unavailable. Or try to downsize it from double the size ? Just an idea since I do not know the implemented algorithm. Bye, Stephan. -- Sent through GMX FreeMail - http://www.gmx.net ------- Additional Comments From stephan.hegel@gmx.de 2000-12-23 07:48:42 ---- Subject: Texttool does not work From: Stephan Hegel <stephan.hegel@gmx.de> To: 34953@bugs.gnome.org Message-Id: <30975.977575722@www30.gmx.net> Date: Sat, 23 Dec 2000 13:48:42 +0100 (MET) Hi all, After the 1.1.31 mess I upgraded to Gimp 1.1.32. Another experience to my bug report from last week: The following procedure makes the things partly work. 1st: Open the mentioned and posted JPG-Image (it is RGB) (BTW, has somebody tried it ???) 2nd: Use Texttool as described - it fails. 3rd: Transform it to indexed mode by Image->Mode->Indexed with default settings. 4th: Save as a GIF file and use the existing image. 5th: Use Texttool as described - it fails. 6th: Close and Load the GIF file again. 7th: Use Texttool as previously described - it works. That means: I have to save the file as a GIF (indexed mode) first, close it and load the file again. Somehow strange. Any hint how to debug this ? Starting gimp and attaching gdb to the free running plugin via PID works fine but how to continue ? I would love to help here ... any hint ? Cheers, Stephan. -- Sent through GMX FreeMail - http://www.gmx.net ------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-28 11:04 ------- This bug was previously known as bug 34953 at http://bugs.gnome.org/ http://bugs.gnome.org/show_bug.cgi?id=34953 Originally filed under the gimp product and general component. The original reporter (stephan.hegel@gmx.de) of this bug does not have an account here. Reassigning to the exporter, debbugs-export@bugzilla.gnome.org. Reassigning to the default owner of the component, egger@suse.de.
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
The previous comment from Austin saying "The real problem is that linux font servers are quite forgiving and will scale bitmaps to give you something that almost works." is not true anymore. Some Linux distributions such as SuSE 7.2, 7.3 and later (using XFree86 4.x) are not that forgiving, which results in some frustration from the users who cannot get the fonts that they have selected. *** This bug has been marked as a duplicate of 58848 ***