Hi All,
I've converted some Mac fonts with t1unmac from the t1utils package to the
endianness of my x86 PC, and am seeing strange behaviour in the GIMP.
Basically some do and some don't work. In particular one font which has
expert features like hanging numbers and small caps etc. completely
Nick Lamb wrote:
Enough hilarity. If you know of something which must be done before
1.2.0 please follow on to this mail. If you know of a reason why
we should unfreeze Gimp instead, feel free to let loose.
1. VAGUE: Documentation should be "good" (definition anyone?)
2. Critical/ Severe
On Monday, 25 Sep 2000, Nick Lamb wrote:
1. VAGUE: Documentation should be "good" (definition anyone?)
2. Critical/ Severe bug reports should be fixed or marked down (bug #s?)
3. VAGUE: Gimp should build out-of-box on lots of systems
99. Find and #ifdef any debug scribble to console
100.
Austin Donnelly wrote:
snipped... an extremely useful list. Thank you for composing it
B: Plugins
--
For plugins, I think we need to take some tough decisions as to which
plugins are supported, and which aren't. I don't know how to do this,
but others have suggested looking at
I need to squeeze a little time out of my currently hectic schedule to
go back and finish proofreading the help docs. I now have CVS access so
I just need to find time and learn how to use CVS and it won't be bad on
my part. (if anyone cares about docs that is)
bex
ps--i know i havent been on
In regard to: Re: TODO for 1.2 release, Garry R. Osgood said (at 5:38am on...:
Nick Lamb wrote:
Enough hilarity. If you know of something which must be done before
1.2.0 please follow on to this mail. If you know of a reason why
we should unfreeze Gimp instead, feel free to let loose.
1.
In regard to: TODO for 1.2 release, Nick Lamb said (at 8:21pm on Sep 25, 2000):
Now, I bet a lot of money that Gimp 1.2 wouldn't be released in 2000
To make me lose,
I still remember the announcement for the pre-1.0 party, where S
uttered the famous words, "One-point-Oh is close". 21 test
On 26 Sep, Tim Mooney wrote:
Grepped through the source and couldn't find any C++ style
comments...
cc: Error: lighting_ui.c, line 387: Invalid statement. (badstmt)
// GtkWidget *spinbutton;
--^
This is from 1.1.26/plug-ins/Lighting. I haven't made the build
proceed any farther, to
In regard to: Re: TODO for 1.2 release, [EMAIL PROTECTED] said (at 12:19am on...:
Perhaps it's been fixed in CVS already, and that's what you're looking
at?
No, it's not fixed in CVS but for some reason
find -name *.c | grep "//" -
You need to quote the '*.c', it's getting
On 26 Sep, Tim Mooney wrote:
You need to quote the '*.c', it's getting expanded by the shell before
it ever gets fed to find. :-)
Actually that's not the problem since there are no *.c files in the
directory I started the search in...
Anita:/mnt2/src/gimp # find -name *.c
On Tuesday, 26 Sep 2000, Tim Mooney wrote:
@@ -2322,6 +2322,7 @@
G_IO_ERROR_NONE,
G_IO_ERROR_AGAIN,
G_IO_ERROR_INVAL,
+ G_IO_ERROR_INTR,
G_IO_ERROR_UNKNOWN
} GIOError;
This breaks backwards binary compatibility, since the numeric value of
G_IO_ERROR_UNKNOWN changes. I
In regard to: Re: TODO for 1.2 release, Austin Donnelly said (at 11:35pm on...:
On Tuesday, 26 Sep 2000, Tim Mooney wrote:
@@ -2322,6 +2322,7 @@
G_IO_ERROR_NONE,
G_IO_ERROR_AGAIN,
G_IO_ERROR_INVAL,
+ G_IO_ERROR_INTR,
G_IO_ERROR_UNKNOWN
} GIOError;
This breaks backwards
[EMAIL PROTECTED] wrote:
On 26 Sep, Tim Mooney wrote:
Grepped through the source and couldn't find any C++ style
comments...
cc: Error: lighting_ui.c, line 387: Invalid statement. (badstmt)
// GtkWidget *spinbutton;
--^
There are a number of C++ style comments. I ran the following
"Moses P. Milazzo" wrote:
Why not:
grep "//" `find . -name "*.[ch]"` | grep -v 'p://'
You should include -print as part of the find statement or else you will
wind up getting a list of lines containing C++ style comments without
knowing the name of the file that needs to be edited.
Cheers!
In regard to: Re: TODO for 1.2 release, Moses P. Milazzo said (at 4:28pm on...:
Better:
find . -name '*.c' -o -name '*.h' -exec egrep '//' {} /dev/null \; | \
grep -v '://'
(to get rid of false matches on URLs)
Why not:
grep "//" `find . -name "*.[ch]"` | grep -v 'p://'
(the -o
15 matches
Mail list logo
