I have an idea for the Fire up the GIMP section; please tell me if you
agree wihtthis and I'll implement it.
First, the section title: I tried to rephrase the title since fire up the
GIMP is an awful one that doesn't belong in a help file, but it just means
running GIMP which is already the name
I can rewrite that section for 2.6 - it's not much of a change - and keep
this version for when, gnu willing, the new version comes out.
2011/3/29 Julien Hardelin jm.h...@wanadoo.fr
Hi Roman,
On Thu, Mar 03, 2011 at 07:07:00AM +0100, Julien Hardelin wrote:
For that, we need:
- a
2011/3/26 Ulf-D. Ehlert ud...@web.de
I wonder if we won't get a copyright problem if the images are
replaced... And even if not, shouldn't we show respect for the
original author?
Obviously not - the entire thing is under the GNU Free documentation
License. The original images were taken
2011/3/24 Owen rc...@pcug.org.au
Could I suggest that you run autogen.sh again, and read the last 20 or
so lines.
Just see what programs weren't found and install them.
Now if you have the style sheets on your computer, it shouldn't have
to go to the net to get them. Install all the
IT's taken some time (I had a rather optimistic estimate of tmy free time)
but I'm finally making some headway with rewriting parts of the
documentation. My current aim is to rewrite Gimplite Quickies. Problem is, I
still don't know how to build the html. I was told here on the mailing list
that
2011/2/23 Julien Hardelin jm.h...@wanadoo.fr
Hi Michael,
OK for substance.
Some remarks about form:
- TAB are set to 2 spaces.
- Lines are less than 80 characters and spaces.
OK, figured out how to do those with Notepad++.
- When explaining a term, please add an indexterm
So, in the last couple of weeks I tried to look up material about Docbook.
I'm still not sure about how you people edit the help files, and I'd
obviously prefer a more wysiwg way of doing things, but for now I'll settle
for XML-aware editors. I downloaded the repository to my Linux volume but
I'm
