Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Am Samstag, 13. März 2004 13:10 schrieb Sven Neumann: > Hi, > > Frank Noack <[EMAIL PROTECTED]> writes: > > Its the same problem that i had before. It works fine with build in > > language (en) if i use it in german it fails. Now i can print with > > Turborint but without ppd-file. I show at > > http://gimp-print.sourceforge.net/ > > Did you update to gimp-print 4.2.6 yet ? Yes i did :-) And it works, but not with using ppd file. With LANG=en it works completly Frank ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Am Samstag, 13. März 2004 13:06 schrieb David Neary: > Hi Frank, > > Frank Noack wrote: > > Its the same problem that i had before. It works fine with build in > > language (en) if i use it in german it fails. Now i can print with > > Turborint but without ppd-file. I show at > > http://gimp-print.sourceforge.net/ > > You might try updating to gimp-print 4.2.6 - there were some > problems with localisation in earlier versions of gimp-print > 4.2.x which have been fixed since (there is even a message about > this when you run configure in the GIMP source tree). > Sorry, but i use gimp-print 4.2.6. As i used 4.2.5 i cant print with [EMAIL PROTECTED] Since i use 4.2.6 i can print but only without using ppd file. If i use the ppd file i lost the preview in the Gimp print dialog and i get no print output. It all works fine with LANG=en. Frank ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
On Sat, Mar 13, 2004 at 09:11:02PM -0500, Robert L Krawitz wrote: >From: Sven Neumann <[EMAIL PROTECTED]> >Date: 14 Mar 2004 02:50:09 +0100 > >Robert L Krawitz <[EMAIL PROTECTED]> writes: > >> Fink and Darwinports are simply not options for mainline OS X >> users. Mac users want to literally buy a machine and turn it on. >> Think about what happens when you buy a lamp, you plug it into >> the wall and turn it on. They're amazingly close to that, with >> things like Airport. >From a user engineering standpoint, it's a >> tour de force. > >Afak, you can build binary images from darwinport packages with a >single command. If you provide such an image file to your users, >it's a matter or dragging the file onto the finder and the software >is installed, ready to be used. But certainly you know about this >and I assume that this is the way you are offering the gimp-print >software to MacOS X users. It would be easy to include glib2 as >part of this gimp-print image file. > > That's what I meant; that would be a possibility. We would just need > to make sure it didn't collide with anything else. I prefer to > minimize the amount of stuff we install in the background, but that > could conceivably be an option. Whether it's worthwhile is a second > question. Why not just statically link to glib 2 when you make the OS X binary build? Seems that'd solve this whole issue nicely. -Yosh ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
From: Sven Neumann <[EMAIL PROTECTED]> Date: 14 Mar 2004 02:50:09 +0100 Robert L Krawitz <[EMAIL PROTECTED]> writes: > Fink and Darwinports are simply not options for mainline OS X > users. Mac users want to literally buy a machine and turn it on. > Think about what happens when you buy a lamp, you plug it into > the wall and turn it on. They're amazingly close to that, with > things like Airport. >From a user engineering standpoint, it's a > tour de force. Afak, you can build binary images from darwinport packages with a single command. If you provide such an image file to your users, it's a matter or dragging the file onto the finder and the software is installed, ready to be used. But certainly you know about this and I assume that this is the way you are offering the gimp-print software to MacOS X users. It would be easy to include glib2 as part of this gimp-print image file. That's what I meant; that would be a possibility. We would just need to make sure it didn't collide with anything else. I prefer to minimize the amount of stuff we install in the background, but that could conceivably be an option. Whether it's worthwhile is a second question. > I think we have a problem when something goes from current to > obsolete in 18 months. That's a rather long time and since you are developing a new version of gimp-print at the moment, you should seriously consider to base it on libraries that are current and not something that dates back to the year 2001. A lot has happened since then. I don't have glib-1.2 installed any longer on any of the computers I am using. You can expect that this will be the case for most if not all distributions emerging over the next months. It's a long time for developers who are used to living on the bleeding edge. It's not a long time for end users who don't want to upgrade something that works. Like I said, note that even Microsoft was forced to backtrack when they tried to force people off Windows 98. -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi, Robert L Krawitz <[EMAIL PROTECTED]> writes: > Fink and Darwinports are simply not options for mainline OS X users. > Mac users want to literally buy a machine and turn it on. Think about > what happens when you buy a lamp, you plug it into the wall and turn > it on. They're amazingly close to that, with things like Airport. > >From a user engineering standpoint, it's a tour de force. Afak, you can build binary images from darwinport packages with a single command. If you provide such an image file to your users, it's a matter or dragging the file onto the finder and the software is installed, ready to be used. But certainly you know about this and I assume that this is the way you are offering the gimp-print software to MacOS X users. It would be easy to include glib2 as part of this gimp-print image file. > I think we have a problem when something goes from current to obsolete > in 18 months. That's a rather long time and since you are developing a new version of gimp-print at the moment, you should seriously consider to base it on libraries that are current and not something that dates back to the year 2001. A lot has happened since then. I don't have glib-1.2 installed any longer on any of the computers I am using. You can expect that this will be the case for most if not all distributions emerging over the next months. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Re : Fwd : Re : Re : [Gimp-developer] splash pictur [jean-luc.coulon@wanadoo.fr]
Hi, Alan Horkan <[EMAIL PROTECTED]> writes: > PS How are the Splash and About images still PPM format* because I was > wondering why they aren't in a smaller format like PNG? > (* I dont have the latest copy of GIMP 2.0 handy otherwise I'd check) Please get a recent copy then or refrain from commenting on our code. These files are PNG for more than 2 years now. You could have downloaded a new version in the meantime. Of course we know about the problems that l10n can introduce. However the solution to this problem is not to add some arbitrary extra space but to adjust either the widget or the font size dynamically. Usually the widget is adjusted but for the about dialog we adjust the font size and I consider to do the same for the splash. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
From: Sven Neumann <[EMAIL PROTECTED]> Date: 14 Mar 2004 01:33:10 +0100 Robert L Krawitz <[EMAIL PROTECTED]> writes: > Just to make it clear: the reason we don't use Glib in the core > is that it isn't part of the standard load on a lot of platforms > (in particular, OS X). We've had enough issues on OS X with > Ghostscript, which is *necessary* (there's no workaround > whatsoever) in a lot of cases; OS X users want a single binary > blob. We've made a conscious choice that we're going to play as > well as possible with the working methods of OS X users. OS X > users are already suspicious enough of the UNIX core (command > line geeks) and don't want to be reminded of the fact. They see > their computers as appliances. I really don't want to get into an argument with you but glib-2.0 (or rather 2.2 and soon 2.4) works just fine on MacOS X, is easy to install through fink or darwinports and it would help you to avoid a good deal of code duplication. Fink and Darwinports are simply not options for mainline OS X users. Mac users want to literally buy a machine and turn it on. Think about what happens when you buy a lamp, you plug it into the wall and turn it on. They're amazingly close to that, with things like Airport. >From a user engineering standpoint, it's a tour de force. Fink Commander (a GUI interface to Fink) is quite difficult to set up. It's not trivial for me, and I understand things like CVS, and I know the relationships between the different packages. Macintosh users don't, and they absolutely don't want to. We've had this discussion before in a different context. I don't think that most people in the free software world really understand this point. >From an software engineering standpoint I want to avoid code duplication. From a user perspective, architecture and implementation don't help them get their job done. > I tried a while back to install Gnumeric on my SuSE 8.1 (not even > 18 months old) systems, and it was a horrible mess indeed. I had > to install more or less the entire GNOME stack, and that caused > other problems with older Gnome 2 stuff in SuSE. gnumeric is a GNOME application. Of course it needs a full GNOME stack. We are talking about glib here, which has no dependencies. Fair enough. > If the problem's with the Print plugin or libgimpprintui, we can > obviously afford to use Glib 1.2 (there are lots of GIMP 1.2 users > out there, and I don't want to break them). glib-1.2 doesn't have the functionality you need in order to handle the problem this thread started about. Besides that, it is not any longer maintained and it is missing support for Unicode and UTF-8 and you can hardly get away without that nowadays. I think we have a problem when something goes from current to obsolete in 18 months. I upgrade my systems roughly every 3 releases; SuSE spaces releases 6-8 months apart, so we're talking an 18-24 month cycle. Note what happened when Microsoft tried to drop support for Windows 98 (which is somewhat older); even they were forced to backtrack; a lot of people are still using Windows 95 and earlier because it works for them. Dropping support for GIMP 1.2 simply means that people won't be able to use Gimp-Print 5.0 with it. I want Gimp-Print to be at the bleeding edge of printer quality and support, on both current and older printers (we still get a lot of questions about printers such as the Epson 3000 and even the 600, which is at least 6 years old). Note that theoretical support for a printer is useless if it won't run on somebody's system, so we've deliberately been very conservative about adopting newer support technologies. -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Re : Fwd : Re : Re : [Gimp-developer] splash pictur [jean-luc.coulon@wanadoo.fr]
On Sat, 13 Mar 2004, Jean-Luc Coulon (f5ibh) wrote: > Date: Sat, 13 Mar 2004 16:42:37 +0100 > From: "Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> > To: Sven Neumann <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: [iso-8859-1] Re : Fwd : Re : Re[iso-8859-1] : > [Gimp-developer[iso-8859-1] ] splash pictur [EMAIL PROTECTED] > > Hi Sven, > > Le 13.03.2004 16:20, Sven Neumann a écrit : > >Hi, > > > >"Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> writes: > > > >> I don't think my font size is so huge ;-) > > > >Well, your font isn't that huge but you've choosen a very wide font. > >It's of course up to you, but you will be suffering from this problem > >in all dialogs. I suggest you don't use an oblique font for your > >desktop. I've always been told that for localisation reasons you have always have to leave extra space anyway, most noteably up to 2/3 extra for the talkative Germans (I think that is the usual figure that gest mentioned but dont quote me on it). For accessibility reasons space for larger fonts would be also be needed. I think it would be an interesting change if the GIMP had splash screen that was Landscape, but that it really up to Jimmac of course but it would help cover up this glitch. > While we are speaking of splash screen a 3:2 ratio or 4:3 ratio or > "magic number" ratio rectangle instead of a square shape would looks > even better, but it is a matter of taste ;-) aha! but do you try and anticipate the size of the status bar, window and window decorations and attempt to have it so that the overall ratio is 3:2/4:3 or do you just do it for the image? (consider that a rhetorical question). Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/ PS How are the Splash and About images still PPM format* because I was wondering why they aren't in a smaller format like PNG? (* I dont have the latest copy of GIMP 2.0 handy otherwise I'd check) ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi, Robert L Krawitz <[EMAIL PROTECTED]> writes: > Just to make it clear: the reason we don't use Glib in the core is > that it isn't part of the standard load on a lot of platforms (in > particular, OS X). We've had enough issues on OS X with Ghostscript, > which is *necessary* (there's no workaround whatsoever) in a lot of > cases; OS X users want a single binary blob. We've made a conscious > choice that we're going to play as well as possible with the working > methods of OS X users. OS X users are already suspicious enough of > the UNIX core (command line geeks) and don't want to be reminded of > the fact. They see their computers as appliances. I really don't want to get into an argument with you but glib-2.0 (or rather 2.2 and soon 2.4) works just fine on MacOS X, is easy to install through fink or darwinports and it would help you to avoid a good deal of code duplication. > I tried a while back to install Gnumeric on my SuSE 8.1 (not even 18 > months old) systems, and it was a horrible mess indeed. I had to > install more or less the entire GNOME stack, and that caused other > problems with older Gnome 2 stuff in SuSE. gnumeric is a GNOME application. Of course it needs a full GNOME stack. We are talking about glib here, which has no dependencies. > If the problem's with the Print plugin or libgimpprintui, we can > obviously afford to use Glib 1.2 (there are lots of GIMP 1.2 users > out there, and I don't want to break them). glib-1.2 doesn't have the functionality you need in order to handle the problem this thread started about. Besides that, it is not any longer maintained and it is missing support for Unicode and UTF-8 and you can hardly get away without that nowadays. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
From: Roger Leigh <[EMAIL PROTECTED]> Date: Sat, 13 Mar 2004 20:29:09 + Sven Neumann <[EMAIL PROTECTED]> writes: > Roger Leigh <[EMAIL PROTECTED]> writes: > >> Sven Neumann <[EMAIL PROTECTED]> writes: >> >> > Note to the gimp-print developers: You should consider to stop using >> > scanf() and similar locale-dependant functions to read your config >> > files. Setting LC_NUMERIC to C is a workaround but it's rather ugly >> > and easy to forget. >> >> What should be used instead (given that Standard C does not have >> locale objects)? > > http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-strtod > http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-dtostr > http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-formatd I wish we were able to use Glib :-( Just to make it clear: the reason we don't use Glib in the core is that it isn't part of the standard load on a lot of platforms (in particular, OS X). We've had enough issues on OS X with Ghostscript, which is *necessary* (there's no workaround whatsoever) in a lot of cases; OS X users want a single binary blob. We've made a conscious choice that we're going to play as well as possible with the working methods of OS X users. OS X users are already suspicious enough of the UNIX core (command line geeks) and don't want to be reminded of the fact. They see their computers as appliances. I suppose there would be an option to bundle a binary of Glib in with Gimp-Print, but that would certainly complicate matters some. In general, we want to stay on the trailing edge with non-core functionality, such as utility libraries and language features. I tried a while back to install Gnumeric on my SuSE 8.1 (not even 18 months old) systems, and it was a horrible mess indeed. I had to install more or less the entire GNOME stack, and that caused other problems with older Gnome 2 stuff in SuSE. I did get Gnumeric to work, but too many other things fell apart as a result and I had to back it out. Gimp-Print is core printer functionality for a lot of people, and they won't be too sympathetic to issues like this. If there's no way around it, we can crib code, which we would then have to maintain. If the problem's with the Print plugin or libgimpprintui, we can obviously afford to use Glib 1.2 (there are lots of GIMP 1.2 users out there, and I don't want to break them). -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Sven Neumann <[EMAIL PROTECTED]> writes: > Hi, > > Roger Leigh <[EMAIL PROTECTED]> writes: > >> Sven Neumann <[EMAIL PROTECTED]> writes: >> >> > Note to the gimp-print developers: You should consider to stop using >> > scanf() and similar locale-dependant functions to read your config >> > files. Setting LC_NUMERIC to C is a workaround but it's rather ugly >> > and easy to forget. >> >> What should be used instead (given that Standard C does not have >> locale objects)? > > http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-strtod > http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-dtostr > http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-formatd I wish we were able to use Glib :-( -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi, Roger Leigh <[EMAIL PROTECTED]> writes: > Sven Neumann <[EMAIL PROTECTED]> writes: > > > Note to the gimp-print developers: You should consider to stop using > > scanf() and similar locale-dependant functions to read your config > > files. Setting LC_NUMERIC to C is a workaround but it's rather ugly > > and easy to forget. > > What should be used instead (given that Standard C does not have > locale objects)? http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-strtod http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-dtostr http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-formatd Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re : Fwd : Re : Re : [Gimp-developer] splash pictur [jean-luc.coulon@wanadoo.fr]
Hi Sven, Le 13.03.2004 16:20, Sven Neumann a écrit : Hi, "Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> writes: I don't think my font size is so huge ;-) Well, your font isn't that huge but you've choosen a very wide font. It's of course up to you, but you will be suffering from this problem in all dialogs. I suggest you don't use an oblique font for your desktop. Snifff ... I loved it ... But you are right, in the past, I had a problem with the gnome-panel and italic fonts, the right-end character was truncated (fixed in gnome 2.6). For The Gimp, with simple arial, up to 12, there is no problem. While we are speaking of splash screen a 3:2 ratio or 4:3 ratio or "magic number" ratio rectangle instead of a square shape would looks even better, but it is a matter of taste ;-) -- J-L Sven pgp0.pgp Description: PGP signature
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Sven Neumann <[EMAIL PROTECTED]> writes: > Note to the gimp-print developers: You should consider to stop using > scanf() and similar locale-dependant functions to read your config > files. Setting LC_NUMERIC to C is a workaround but it's rather ugly > and easy to forget. What should be used instead (given that Standard C does not have locale objects)? -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Fwd : Re : Re : [Gimp-developer] splash pictur [jean-luc.coulon@wanadoo.fr]
Hi, "Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> writes: > I don't think my font size is so huge ;-) Well, your font isn't that huge but you've choosen a very wide font. It's of course up to you, but you will be suffering from this problem in all dialogs. I suggest you don't use an oblique font for your desktop. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re : Re : [Gimp-developer] splash picture and its container window
Hi David, Le 13.03.2004 15:22, David Neary a écrit : hi Jean-Luc, Jean-Luc Coulon (f5ibh) wrote: So, I forgot: it is the 2.0-pre cvs version from 20040312. Locale is [EMAIL PROTECTED], but I tried with LC_MESSAGES=C and got the same effect (less annoying anyway because the English sentences are mostly shorter). This may be a problem related to your desktop fonts. Here with fr_FR and en_UK or C I have no problem. If you use a bigger font in your gtk+ theme, that might make the text wide enough to over-run the splash box. This is the case, my font size is 12 8-) What's your expected behaviour here. That the text be chopped at the edges of the splash, or that the window be big enough for the biggest string from the start? *My* expected behaviour is ... nothing. I just *think* it would have a better "sex appeal" for the end user who is comming from an other software and who thinks the look is important. Any of your suggestions is acceptable: - text cropped : motly nobody read it as it is moving very quickly - larger window can be *the* solution but you will have to fix/compute and acceptable width. -- Regards - Jean-Luc Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Fwd : Re : Re : [Gimp-developer] splash pictur [jean-luc.coulon@wanadoo.fr]
Le 13.03.2004 15:28, Jean-Luc Coulon (f5ibh) a écrit : Le 13.03.2004 15:13, Sven Neumann a écrit : Hi, "Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> writes: >> The container window for this spash picture has its width resized >> according to the with of the text line(s) displayed. This >> produces an a not nice "oscillating" effect on the screen. Your font size got to be HUGE. I would suggest you start gimp using the --no-splash command-line option to workaround this problem. Sven PS: I am planning to do some changes to the splash window today or tomorrow. Should be trivial to work around this problem by cutting the text off if it's too wide. I don't think my font size is so huge ;-) I join (for you, not for the list, as requested by Henrik) a screenshot of what happens with the French locale. I was not able, after lots of tries, to get a capture of the same thing with the C locale, I'm always out of sync: this happens only in one case, when it is loading the "Resource configuration" and the displayed path is too long, it is "/home/jean-luc/.gimp1.3/pluginrc" ; this text is larger that the width of the splash image so the windows width is increased accordingly. *I* can survive with this "problem". It is not looking so pretty that's all .. -- Regards - Jean-Luc pgp0.pgp Description: PGP signature
Re: Re : [Gimp-developer] splash picture and its container window
hi Jean-Luc, Jean-Luc Coulon (f5ibh) wrote: > So, I forgot: it is the 2.0-pre cvs version from 20040312. > Locale is [EMAIL PROTECTED], but I tried with LC_MESSAGES=C and got the same > effect (less annoying anyway because the English sentences are mostly > shorter). This may be a problem related to your desktop fonts. Here with fr_FR and en_UK or C I have no problem. If you use a bigger font in your gtk+ theme, that might make the text wide enough to over-run the splash box. What's your expected behaviour here. That the text be chopped at the edges of the splash, or that the window be big enough for the biggest string from the start? Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Re : [Gimp-developer] splash picture and its container window
Hi, "Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> writes: > >> The container window for this spash picture has its width resized > >> according to the with of the text line(s) displayed. This > >> produces an a not nice "oscillating" effect on the screen. Your font size got to be HUGE. I would suggest you start gimp using the --no-splash command-line option to workaround this problem. Sven PS: I am planning to do some changes to the splash window today or tomorrow. Should be trivial to work around this problem by cutting the text off if it's too wide. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Re : [Gimp-developer] splash picture and its container window
On Sat, 13 Mar 2004 14:11:48 +0100, Henrik Brix Andersen <[EMAIL PROTECTED]> wrote: > On Sat, 2004-03-13 at 14:06, Jean-Luc Coulon (f5ibh) wrote: > > Locale is [EMAIL PROTECTED], but I tried with LC_MESSAGES=C and got the same > > effect (less annoying anyway because the English sentences are mostly > > shorter). > > I can not reproduce the problem here using LANG=C. Can you provide a > screen shot showing the problem? It probably depends on the font size that you are using. I could reproduce the annoying resizing problem by reducing the width of the splash screen in order to make the problem more obvious. Just edit $PREFIX/share/gimp/1.3/images/gimp_splash.png and make it smaller. You will then see the splash window getting wider and narrower during start-up. I don't know if we should try to have a wider splash screen. Is this a real issue in many locales? -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] the GIMP help system, i18n and other problems
On Mar 12, 2004, at 1:59 pm, Sven Neumann wrote:
What I dislike about this is that the base for the references in the
XML files is not the directory the XML file is located in. So
there's some special knowledge needed to interpret the references.
I suggest this structure intead:
${gimpprefix}/help/en/gimp-help.xml
${gimpprefix}/help/en/index.html
${gimpprefix}/help/fr/gimp-help.xml
${gimpprefix}/help/fr/index.html
Of course the gimp-help.xml file could also use absolute URLs so the
help files don't absolutely need to be in the same directory and
might even be online on some web-server.
This makes a whole lot more sense. I like it.
Servus,
Daniel
PGP.sig
Description: This is a digitally signed message part
Re: Re : [Gimp-developer] splash picture and its container window
On Sat, 2004-03-13 at 14:06, Jean-Luc Coulon (f5ibh) wrote: > >Under which locale are you running The GIMP? > > Locale is [EMAIL PROTECTED], but I tried with LC_MESSAGES=C and got the same > effect (less annoying anyway because the English sentences are mostly > shorter). I can not reproduce the problem here using LANG=C. Can you provide a screen shot showing the problem? ./Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re : [Gimp-developer] splash picture and its container window
Henrik, Le 13.03.2004 13:47, Henrik Brix Andersen a écrit : Hi, On Sat, 2004-03-13 at 13:34, Jean-Luc Coulon (f5ibh) wrote: The container window for this spash picture has its width resized according to the with of the text line(s) displayed. This produces an a not nice "oscillating" effect on the screen. Which version of The GIMP? So, I forgot: it is the 2.0-pre cvs version from 20040312. Under which locale are you running The GIMP? Locale is [EMAIL PROTECTED], but I tried with LC_MESSAGES=C and got the same effect (less annoying anyway because the English sentences are mostly shorter). -- Regards - Jean-Luc Sincerely, Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> pgp0.pgp Description: PGP signature
Re: [Gimp-developer] splash picture and its container window
Hi, On Sat, 2004-03-13 at 13:34, Jean-Luc Coulon (f5ibh) wrote: > The container window for this spash picture has its width resized > according to the with of the text line(s) displayed. This produces an > a not nice "oscillating" effect on the screen. Which version of The GIMP? Under which locale are you running The GIMP? Sincerely, Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] splash picture and its container window
Hello, The spash picture is dispayed in a window where the system display a progress dialog for the loading process. The container window for this spash picture has its width resized according to the with of the text line(s) displayed. This produces an a not nice "oscillating" effect on the screen. -- Regards - Jean-Luc pgp0.pgp Description: PGP signature
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi, Frank Noack <[EMAIL PROTECTED]> writes: > Its the same problem that i had before. It works fine with build in > language (en) if i use it in german it fails. Now i can print with > Turborint but without ppd-file. I show at > http://gimp-print.sourceforge.net/ Did you update to gimp-print 4.2.6 yet ? Sven Note to the gimp-print developers: You should consider to stop using scanf() and similar locale-dependant functions to read your config files. Setting LC_NUMERIC to C is a workaround but it's rather ugly and easy to forget. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi Frank, Frank Noack wrote: > Its the same problem that i had before. It works fine with build in language > (en) if i use it in german it fails. Now i can print with Turborint but > without ppd-file. I show at http://gimp-print.sourceforge.net/ You might try updating to gimp-print 4.2.6 - there were some problems with localisation in earlier versions of gimp-print 4.2.x which have been fixed since (there is even a message about this when you run configure in the GIMP source tree). Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Am Samstag, 13. März 2004 12:45 schrieb Robert L Krawitz: >From: Sven Neumann <[EMAIL PROTECTED]> >Date: 13 Mar 2004 12:03:21 +0100 > >Frank Noack <[EMAIL PROTECTED]> writes: >> As first the good, i can print now with gimp2.0pre4. And now the >> bad. If i use a ppd file in the preferences from postscript >> level2 in gimp i lost the preview and i get no printer >> output. Only if i dont use a ppd file for my Stylus 670 with >> turboprint driver i get a preview and a good print. I use Suse >> 8.2 with updatet ghostscript7.07.1rc1 (gimp-print 4.2.6), >> turboprint1.86, cups1.1.18. > >This is a problem with gimp-print. Although the gimp-print library >has gimp in the name, the GIMP developers as represented on this >list, are not involved with the gimp-print project. Thus we cannot >help you. > >Please check the gimp-print homepage at >http://gimp-print.sourceforge.net/. There should be information on >how you can get your question answered. > > Also try using the native driver (rather than turboprint) -- > Gimp-Print has a built-in driver for the 670 that will give you access > to more features. Finally, make sure that the PPD file you're giving > it exists and is readable. Its the same problem that i had before. It works fine with build in language (en) if i use it in german it fails. Now i can print with Turborint but without ppd-file. I show at http://gimp-print.sourceforge.net/ Thanks ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
From: Sven Neumann <[EMAIL PROTECTED]> Date: 13 Mar 2004 12:03:21 +0100 Frank Noack <[EMAIL PROTECTED]> writes: > As first the good, i can print now with gimp2.0pre4. And now the > bad. If i use a ppd file in the preferences from postscript > level2 in gimp i lost the preview and i get no printer > output. Only if i dont use a ppd file for my Stylus 670 with > turboprint driver i get a preview and a good print. I use Suse > 8.2 with updatet ghostscript7.07.1rc1 (gimp-print 4.2.6), > turboprint1.86, cups1.1.18. This is a problem with gimp-print. Although the gimp-print library has gimp in the name, the GIMP developers as represented on this list, are not involved with the gimp-print project. Thus we cannot help you. Please check the gimp-print homepage at http://gimp-print.sourceforge.net/. There should be information on how you can get your question answered. Also try using the native driver (rather than turboprint) -- Gimp-Print has a built-in driver for the 670 that will give you access to more features. Finally, make sure that the PPD file you're giving it exists and is readable. -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi, Frank Noack <[EMAIL PROTECTED]> writes: > As first the good, i can print now with gimp2.0pre4. And now the bad. If i > use a ppd file in the preferences from postscript level2 in gimp i lost the > preview and i get no printer output. Only if i dont use a ppd file for my > Stylus 670 with turboprint driver i get a preview and a good print. I use > Suse 8.2 with updatet ghostscript7.07.1rc1 (gimp-print 4.2.6), > turboprint1.86, cups1.1.18. This is a problem with gimp-print. Although the gimp-print library has gimp in the name, the GIMP developers as represented on this list, are not involved with the gimp-print project. Thus we cannot help you. Please check the gimp-print homepage at http://gimp-print.sourceforge.net/. There should be information on how you can get your question answered. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
