Well thats why we want to have only GtkXmHTML installed and only if it's
needed.
GtkXmHTML is on its way out. Check out the gtkhtml module in CVS. The
only dependency on Gnome is for the test application and the bonobo
component. Otherwise it looks like plain GTK+ stuff to me.
It's not wise
Why not allow the user to choose his/her browser of choice ?
With Netscape, Mozilla, the Gnome Help Browser, kfm, or even
Lynx in an xterm as possible choices, I don't see any problem with this...
So Gimp help should be a set of HTML files and a small exec to launch the
preferred browser
On 10 Nov, Kevin Cozens wrote:
Reading the discussions re: the help system has made me think I
understand why compiling GIMP always broke at a point where it needed
a GtkXmhtml header file. I use a RedHat system without Gnome installed
and I'm beginning to understand that GtkXmhtml is a
On Thu, Nov 11, 1999 at 12:56:58PM +0100, "Ewald R. de Wit" [EMAIL PROTECTED] wrote:
Well the algorithm involved is a simple 256 byte lookup table (or 3 of
them for each of the RGB channels). There is not much one can screw up
about it, both performance and precision wise.
The only different
Marc Lehmann wrote:
demand a net-connection and call babelfish for untranslated items ;)
(runs...)
What about a central site, where developers send their files to be
translated, and a group of volunteers translates them to as many
languajes as they can? Perhaps there could even exists a
Eduardo Perez [EMAIL PROTECTED] wrote:
What about a central site, where developers send their files to be
translated, and a group of volunteers translates them to as many
languajes as they can? Perhaps there could even exists a database of
common expresions ('Yes', 'Save as', 'Are you
Hi,
Why not allow the user to choose his/her browser of choice ?
With Netscape, Mozilla, the Gnome Help Browser, kfm, or even
Lynx in an xterm as possible choices, I don't see any problem with this...
So Gimp help should be a set of HTML files and a small exec to launch the
preferred
Here is my list of minor things to clean up and make better (Without
breaking the freeze). First the list and then the discussion below it.
YES!!
I do especially like the new menu hierarchy you suggested. Any volunteers
for this job?
PS: Sven I think
On 8 Nov, Marc Lehmann wrote:
Hint: It's the way menues are handled by Gtk...
And if this leads to segfaults it is surely a bug in gkt+? No, really,
I am _simply_ interested in how a call to gettext can result in a
"legal" segfault.
The most likely way to cause a segfault is to write
On 10 Nov, Marc Lehmann wrote:
That all plug-ins that are part of the distribution should have
corretc translated menu entries is (for me) obvious. The problem is
new (third-party) plug-ins.
These problems are solvable by a consistent way to handle the
translations. Im working on these but
On Thu, 11 Nov 1999 [EMAIL PROTECTED] wrote:
On 9 Nov, Andrew Kieschnick wrote:
libgimp and libgimpui are LGPLed, so that isn't a problem.
Really? Not mine
Serious: If it'd be LPGLed it would have had such a header in every
source file and in the COPYING file which isn't the
On Thu, Nov 11, 1999 at 08:34:32PM +0100, [EMAIL PROTECTED] wrote:
Serious: If it'd be LPGLed it would have had such a header in every
source file and in the COPYING file which isn't the case...
There certainly is the COPYING file and the files all refer to the library
GPL, I think that is
On Thu, Nov 11, 1999 at 10:47:48PM +0200, Tor Lillqvist [EMAIL PROTECTED] wrote:
It is possible that I decided to use the GPL header because the code
in gimpenv.c was partly moved from gimp proper, which is GPL.
That's bad, so libgimp in cvs is actually GPL ;- My dreams come true ;)
--
Marc Lehmann writes:
On Thu, Nov 11, 1999 at 10:47:48PM +0200, Tor Lillqvist [EMAIL PROTECTED] wrote:
It is possible that I decided to use the GPL header because the code
in gimpenv.c was partly moved from gimp proper, which is GPL.
That's bad, so libgimp in cvs is actually GPL
On Thu, Nov 11, 1999 at 11:20:27PM +0200, Tor Lillqvist [EMAIL PROTECTED] wrote:
I don't think gimpenv.c is in any way unique in this sense, probably
many of the other files in libgimp also contain code snippets that
have originally been in some file in the GIMP proper.
It, of course, depends
Except... gimpenv.c...
Well, I have looked at it know, but it should be fairly easy to make a
cleanroom implementation of the functionality in that file only by looking at
the code that calls it. The header is under the LGPL. Would that count? ;-)
Salut, Sven
On Thu, Nov 11, 1999 at 09:03:46PM +0100, Marc Lehmann wrote:
On Thu, Nov 11, 1999 at 02:50:18AM +0100, David Odin [EMAIL PROTECTED] wrote:
I don't think I'm alone, since nobody complain about gimp perl any more
these days.
They don't? Then why do I get so many complaints? ;)
At
On Thu, Nov 11, 1999 at 10:23:15PM +0100, Eduardo Perez wrote:
Marc Lehmann wrote:
demand a net-connection and call babelfish for untranslated items ;)
(runs...)
What about a central site, where developers send their files to be
translated, and a group of volunteers translates them
On 11 Nov, Andrew Kieschnick wrote:
Hmm, that sure as hell looks like an LGPL to me. I seriously doubt
your copy of gimp is different than mine...
LGPL stands for "Lesser GNU Public Licence". Now do me a favour and
count the word lesser in this COPYING file... Then do this again
for the
19 matches
Mail list logo
