Gimp Manual format.

Is the Gimp online manual also available in another format?
Currently I am printing out the html pages a small batch at a time.
That's a tedious process. A printed version or even a version in a
single electronic file would save a lot of time. A printed and
bound version would be handier to use than a ring binder of 8.5 x
11 pages. Once I printed out the 880 pages of the Kylander Manual
but that dated back to version 1 or thereabouts. That was as I
recall in a single file. Therefore I could print it out using poor
man's duplexing, (even pages first, then reload the paper stack
and print odds.)

I agree! A PDF version would be fantastic!!!!
Anyone interested in the job?

-----Original Message-----
From: gimp-user-bounces@lists.XCF.Berkeley.EDU
[mailto:gimp-user-bounces@lists.XCF.Berkeley.EDU] On Behalf Of John Culleton
Sent: Thursday, 18 June 2009 11:36 PM
To: Gimp-user@lists.xcf.berkeley.edu
Subject: [Gimp-user] Gimp Manual format.


Is the Gimp online manual also available in another format?
Currently I am printing out the html pages a small batch at a time.
That's a tedious process. A printed version or even a version in a
single electronic file would save a lot of time. A printed and
bound version would be handier to use than a ring binder of 8.5 x
11 pages. Once I printed out the 880 pages of the Kylander Manual
but that dated back to version 1 or thereabouts. That was as I
recall in a single file. Therefore I could print it out using poor
man's duplexing, (even pages first, then reload the paper stack
and print odds.)

http://html-pdf-converter.com/
PDF Converter, HTML to PDF Converter For Free

Michaela Baulderstone wrote:
> I agree! A PDF version would be fantastic!!!!
> Anyone interested in the job?
>
> -----Original Message-----
> From: gimp-user-bounces@lists.XCF.Berkeley.EDU
> [mailto:gimp-user-bounces@lists.XCF.Berkeley.EDU] On Behalf Of John Culleton
> Sent: Thursday, 18 June 2009 11:36 PM
> To: Gimp-user@lists.xcf.berkeley.edu
> Subject: [Gimp-user] Gimp Manual format.
>
>
> Is the Gimp online manual also available in another format?
> Currently I am printing out the html pages a small batch at a time.
> That's a tedious process. A printed version or even a version in a
> single electronic file would save a lot of time. A printed and
> bound version would be handier to use than a ring binder of 8.5 x
> 11 pages. Once I printed out the 880 pages of the Kylander Manual
> but that dated back to version 1 or thereabouts. That was as I
> recall in a single file. Therefore I could print it out using poor
> man's duplexing, (even pages first, then reload the paper stack
> and print odds.)

> -----Original Message-----
> From: gimp-user-bounces@lists.XCF.Berkeley.EDU
> [mailto:gimp-user-bounces@lists.XCF.Berkeley.EDU] On Behalf Of John Culleton
> Sent: Thursday, 18 June 2009 11:36 PM
> To: Gimp-user@lists.xcf.berkeley.edu
> Subject: [Gimp-user] Gimp Manual format.
>
>
> Is the Gimp online manual also available in another format?
> Currently I am printing out the html pages a small batch at a time.
> That's a tedious process. A printed version or even a version in a
> single electronic file would save a lot of time. A printed and
> bound version would be handier to use than a ring binder of 8.5 x
> 11 pages. Once I printed out the 880 pages of the Kylander Manual
> but that dated back to version 1 or thereabouts. That was as I
> recall in a single file. Therefore I could print it out using poor
> man's duplexing, (even pages first, then reload the paper stack
> and print odds.)

On 06/18/2009 10:40 AM, Michaela Baulderstone wrote:
> I agree! A PDF version would be fantastic!!!!
> Anyone interested in the job?
>

I know nothing of the workflow that results in the current HTML manual
format. It would seem to me that producing one or more other formats
should come out of that same workflow. I cannot imagine the labor would
be justified to do a one-time-only current-state PDF version that would
be almost instantly out of date. That probably means that the authoring
workflow and environment needs to be considered. This type of
documentation is one of the prime beneficiaries of single-source,
multiple-output authoring tools. I have not kept up on the current
state of those tools and I am especially not aware of their status and
capabilities in the open-source arena. However, I do know that there
are a variety of approaches, each with their strengths and weaknesses.

Jay

Hi,

>> Is the Gimp online manual also available in another format?
>> Currently I am printing out the html pages a small batch at a time.
>> That's a tedious process. A printed version or even a version in a
>> ...

This might be cheaper than paper, ink, electricity, your time, and a
potential option:

GIMP User Manual: GNU Image Manipulation Program : Photo Retouching,
Image Composition and Image Authoring (Paperback)
by GIMP DocumentationTeam (Author), $30.05
http://www.amazon.com/GIMP-User-Manual-Manipulation-Composition/dp/1441419322/


>> ..

>> I agree! A PDF version would be fantastic

This was from the Gimp FAQ:
http://www.gimp.org/docs/userfaq.html#Manual
Is there a user manual?
Yes. It is available in HTML form, and in PDF.

But it seems the PDF is 2.4, not 2.6.

> I know nothing of the workflow that results in the current HTML manual
> format. It would seem to me that producing one or more other formats
> should come out of that same workflow. I cannot imagine the labor would

I'm in the same boat, so I hope I'm stepping lightly.

There are tools on Linux to convert from various formats. And Windows
too. I'm think'n download the documentation, or it might already be
installed as part of Gimp's help, and run it through one of these
tools to create a PDF format from html.

For the raw Gimp documentation, I'd just like to mention Asciidoc. It
allows you to write documents in text and process them (python) into
html, docbook, pdf, and more. I've followed the google support list
and there was a thread about an author using it for an OReilly book,
who also created a web site. If it would help, in any fashion, the
link is: http://www.methods.co.nz/asciidoc/

On Thursday 18 June 2009 11:05:44 am Jay Smith wrote:
> > -----Original Message-----
> > From: gimp-user-bounces@lists.XCF.Berkeley.EDU
> > [mailto:gimp-user-bounces@lists.XCF.Berkeley.EDU] On Behalf Of
> > John Culleton Sent: Thursday, 18 June 2009 11:36 PM
> > To: Gimp-user@lists.xcf.berkeley.edu
> > Subject: [Gimp-user] Gimp Manual format.
> >
> >
> > Is the Gimp online manual also available in another format?
> > Currently I am printing out the html pages a small batch at a
> > time. That's a tedious process. A printed version or even a
> > version in a single electronic file would save a lot of time.
> > A printed and bound version would be handier to use than a
> > ring binder of 8.5 x 11 pages. Once I printed out the 880
> > pages of the Kylander Manual but that dated back to version 1
> > or thereabouts. That was as I recall in a single file.
> > Therefore I could print it out using poor man's duplexing,
> > (even pages first, then reload the paper stack and print odds.)
>
> On 06/18/2009 10:40 AM, Michaela Baulderstone wrote:
> > I agree! A PDF version would be fantastic!!!!
> > Anyone interested in the job?
>
> I know nothing of the workflow that results in the current HTML
> manual format. It would seem to me that producing one or more
> other formats should come out of that same workflow. I cannot
> imagine the labor would be justified to do a one-time-only
> current-state PDF version that would be almost instantly out of
> date. That probably means that the authoring workflow and
> environment needs to be considered. This type of documentation
> is one of the prime beneficiaries of single-source,
> multiple-output authoring tools. I have not kept up on the
> current state of those tools and I am especially not aware of
> their status and capabilities in the open-source arena. However,
> I do know that there are a variety of approaches, each with their
> strengths and weaknesses.
>
> Jay
> _______________________________________________
> Gimp-user mailing list
> Gimp-user@lists.XCF.Berkeley.EDU
> https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

All manuals are out of date. The fact that a manual is instantly
updateable does not guarantee that all sections will be fully
updated concurrently with the latest stable Gimp. There are only
so many skilled hands to do it. In terms of paper books I work
primarily from _Grokking the Gimp_ (2000) and the newer but sill
obsolete _Artist's Guide to Gimp Effects_ (2007). The html manual
is the most up to date best we have at the moment, and represents
a huge work effort on the part of many people.

But even within its present constraints the html manual can be
improved by renaming the html files for the beginning section
covered in numeric order. Some are named that way but most are not.
One segment of Chapter 3, six segments of chapter 5 and two each
for chapters 11 and 12 are so named. The rest have descriptive
names.

An index would also help.

Hi,

On Thu, 2009-06-18 at 17:17 -0400, John Culleton wrote:

> An index would also help.

What's wrong with http://docs.gimp.org/2.6/en/gimp-help-index.html ?


Sven

Hi,

On Thu, 2009-06-18 at 11:05 -0400, Jay Smith wrote:

> I know nothing of the workflow that results in the current HTML manual
> format. It would seem to me that producing one or more other formats
> should come out of that same workflow.

Indeed. The manual is written in Docbook/XML and you can get a variety
of output formats from that source. If you checkout the gimp-help-2
repository from git.gnome.org (I suggest to do a shallow clone due to
the immense size of the project), then you will get the Docbook/XML
sources, the images and a build system that spits out HTML and
optionally PDF or ODF.

Here's what I did to get a PDF version of the english user manual:

git clone --depth=0 git://git.gnome.org/gimp-help-2
cd gimp-help-2
./autogen.sh
LINGUAS=en make
LINGUAS=en make pdf-local

And to check the result:

pdfinfo pdf/en/gimp.pdf

Title: GNU Image Manipulation Program
Subject:
Keywords:
Author:
Creator: DBLaTeX-0.2.10-1
Producer: pdfTeX-1.40.3
CreationDate: Thu Jun 18 23:57:05 2009
ModDate: Thu Jun 18 23:57:05 2009
Tagged: no
Pages: 849
Encrypted: no
Page size: 595.276 x 841.89 pts (A4)
File size: 39395416 bytes
Optimized: no
PDF version: 1.4


Sven

On Thursday 18 June 2009 06:09:09 pm Sven Neumann wrote:
> Hi,
>
> On Thu, 2009-06-18 at 11:05 -0400, Jay Smith wrote:
> > I know nothing of the workflow that results in the current HTML
> > manual format. It would seem to me that producing one or more
> > other formats should come out of that same workflow.
>
> Indeed. The manual is written in Docbook/XML and you can get a
> variety of output formats from that source. If you checkout the
> gimp-help-2 repository from git.gnome.org (I suggest to do a
> shallow clone due to the immense size of the project), then you
> will get the Docbook/XML sources, the images and a build system
> that spits out HTML and optionally PDF or ODF.
>
> Here's what I did to get a PDF version of the english user
> manual:
>
> git clone --depth=0 git://git.gnome.org/gimp-help-2
> cd gimp-help-2
> ./autogen.sh
> LINGUAS=en make
> LINGUAS=en make pdf-local
>
> And to check the result:
>
> pdfinfo pdf/en/gimp.pdf
>
> Title: GNU Image Manipulation Program
> Subject:
> Keywords:
> Author:
> Creator: DBLaTeX-0.2.10-1
> Producer: pdfTeX-1.40.3
> CreationDate: Thu Jun 18 23:57:05 2009
> ModDate: Thu Jun 18 23:57:05 2009
> Tagged: no
> Pages: 849
> Encrypted: no
> Page size: 595.276 x 841.89 pts (A4)
> File size: 39395416 bytes
> Optimized: no
> PDF version: 1.4
>
>
> Sven

This is just what I was looking for! Thanks. Am I correct in
assuming that setting depth=0 delivers just the latest version?

John Culleton wrote:
>> git clone --depth=0 git://git.gnome.org/gimp-help-2
>>
> This is just what I was looking for! Thanks. Am I correct in
> assuming that setting depth=0 delivers just the latest version?
>
>

You get the latest version also without --depth=0, but you also get the
entire history of gimp-help-2, which is huge. So unless you want the
history, --depth=0 will save you vast amounts of data copying.

/ Martin

On Thursday 18 June 2009 06:09:09 pm Sven Neumann wrote:
> Hi,
>
> On Thu, 2009-06-18 at 11:05 -0400, Jay Smith wrote:
> > I know nothing of the workflow that results in the current HTML
> > manual format. It would seem to me that producing one or more
> > other formats should come out of that same workflow.
>
> Indeed. The manual is written in Docbook/XML and you can get a
> variety of output formats from that source. If you checkout the
> gimp-help-2 repository from git.gnome.org (I suggest to do a
> shallow clone due to the immense size of the project), then you
> will get the Docbook/XML sources, the images and a build system
> that spits out HTML and optionally PDF or ODF.
>
> Here's what I did to get a PDF version of the english user
> manual:
>
> git clone --depth=0 git://git.gnome.org/gimp-help-2
> cd gimp-help-2
> ./autogen.sh
> LINGUAS=en make
> LINGUAS=en make pdf-local
>
> And to check the result:
>
> pdfinfo pdf/en/gimp.pdf
>
> Title: GNU Image Manipulation Program
> Subject:
> Keywords:
> Author:
> Creator: DBLaTeX-0.2.10-1
> Producer: pdfTeX-1.40.3
> CreationDate: Thu Jun 18 23:57:05 2009
> ModDate: Thu Jun 18 23:57:05 2009
> Tagged: no
> Pages: 849
> Encrypted: no
> Page size: 595.276 x 841.89 pts (A4)
> File size: 39395416 bytes
> Optimized: no
> PDF version: 1.4
>
>
> Sven
>
>
> _______________________________________________
> Gimp-user mailing list
> Gimp-user@lists.XCF.Berkeley.EDU
> https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user

Addendum: you need to download and install DBLaTeX first. And have
TeX of course.

Sven Neumann schreef:
> Hi,
>
> On Thu, 2009-06-18 at 11:05 -0400, Jay Smith wrote:
>
>
>> I know nothing of the workflow that results in the current HTML manual
>> format. It would seem to me that producing one or more other formats
>> should come out of that same workflow.
>>
>
> Indeed. The manual is written in Docbook/XML and you can get a variety
> of output formats from that source. If you checkout the gimp-help-2
> repository from git.gnome.org (I suggest to do a shallow clone due to
> the immense size of the project), then you will get the Docbook/XML
> sources, the images and a build system that spits out HTML and
> optionally PDF or ODF.
>
> Here's what I did to get a PDF version of the english user manual:
>
> git clone --depth=0 git://git.gnome.org/gimp-help-2
> cd gimp-help-2
> ./autogen.sh
> LINGUAS=en make
> LINGUAS=en make pdf-local
>
> And to check the result:
>
> pdfinfo pdf/en/gimp.pdf
>
> Title: GNU Image Manipulation Program
> Subject:
> Keywords:
> Author:
> Creator: DBLaTeX-0.2.10-1
> Producer: pdfTeX-1.40.3
> CreationDate: Thu Jun 18 23:57:05 2009
> ModDate: Thu Jun 18 23:57:05 2009
> Tagged: no
> Pages: 849
> Encrypted: no
> Page size: 595.276 x 841.89 pts (A4)
> File size: 39395416 bytes
> Optimized: no
> PDF version: 1.4
>
>
> Sven
>
>
>

On Sat, 20 Jun 2009 21:35:25 +0200
Jogchum Reitsma <j.reitsma@hccnet.nl> wrote:

> Sven Neumann schreef:

> > Here's what I did to get a PDF version of the english user manual:
> >
> > git clone --depth=0 git://git.gnome.org/gimp-help-2
> > cd gimp-help-2
> > ./autogen.sh
> > LINGUAS=en make
> > LINGUAS=en make pdf-local


That snippet from Sven was fantastic, thanks, worked like a charm



>
>
> Seems a perfect solution, be it that in my case (Suse 11.1), the first
> make fails with
>
> *** Making html for en ...
> /usr/bin/xsltproc \
> --nonet \
> --xinclude \
> --stringparam l10n.gentext.default.language en \
> -o html/en/ \
> stylesheets/plainhtml.xsl \
> xml/en/gimp.xml
> I/O error : Attempt to load network entity
> http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
> warning: failed to load external entity
> "http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl"
> compilation error: file stylesheets/plainhtml.xsl line 8 element
> import xsl:import : unable to load
> http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
> make[1]: *** [html/en/index.html] Fout 5
>
> The URL is accessable in a browser, so that's not the problem.
>
> Any idea what that might be?




I had no trouble, but then again, I had installed anything that looked
like docbook, stylesheets into Ubuntu-9.04 when it came out, so all I
can suggest is that you get all the stylesheets.

However you might be better off looking at the Makefile and seeing what
it wants. I notice these things which you probably should have
installed.

DBLATEX = /usr/bin/dblatex
DOCBOOK2ODF = /usr/bin/docbook2odf
XML2PO = /usr/bin/xml2po
XMLLINT = /usr/bin/xmllint

Installing those may have other dependencies that should bring your
system up to date


Owen

Hi,

On Sat, 2009-06-20 at 21:35 +0200, Jogchum Reitsma wrote:

> Seems a perfect solution, be it that in my case (Suse 11.1), the first
> make fails with
>
> *** Making html for en ...
> /usr/bin/xsltproc \
> --nonet \
> --xinclude \
> --stringparam l10n.gentext.default.language en \
> -o html/en/ \
> stylesheets/plainhtml.xsl \
> xml/en/gimp.xml
> I/O error : Attempt to load network entity
> http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
> warning: failed to load external entity
> "http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl"
> compilation error: file stylesheets/plainhtml.xsl line 8 element import
> xsl:import : unable to load
> http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
> make[1]: *** [html/en/index.html] Fout 5
>
> The URL is accessable in a browser, so that's not the problem.
>
> Any idea what that might be?

Your installation of the Docbook tools is incomplete. The make rules
explicitly disable the use of non-local style-sheets (that's what
--nonet does), so you need to have a complete Docbook/XML installation
locally.


Sven

Sven Neumann schreef:
> Hi,
>
> On Sat, 2009-06-20 at 21:35 +0200, Jogchum Reitsma wrote:
>
>
>> Seems a perfect solution, be it that in my case (Suse 11.1), the first
>> make fails with
>> <...>
>>
>> Any idea what that might be?
>>
>
> Your installation of the Docbook tools is incomplete. The make rules
> explicitly disable the use of non-local style-sheets (that's what
> --nonet does), so you need to have a complete Docbook/XML installation
> locally.
>
>
> Sven
>
That did it.

Thanks Sven, thanks Owen!

Jogchum

On Sunday 21 June 2009 05:52:00 am Sven Neumann wrote:
> Hi,
>
> On Sat, 2009-06-20 at 21:35 +0200, Jogchum Reitsma wrote:
> > Seems a perfect solution, be it that in my case (Suse 11.1),
> > the first make fails with
> >
> > *** Making html for en ...
> > /usr/bin/xsltproc \
> > --nonet \
> > --xinclude \
> > --stringparam l10n.gentext.default.language en \
> > -o html/en/ \
> > stylesheets/plainhtml.xsl \
> > xml/en/gimp.xml
> > I/O error : Attempt to load network entity
> >
> > http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.
> >xsl warning: failed to load external entity
> >
> > "http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk
> >.xsl" compilation error: file stylesheets/plainhtml.xsl line 8
> > element import xsl:import : unable to load
> >
> > http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.
> >xsl make[1]: *** [html/en/index.html] Fout 5
> >
> > The URL is accessable in a browser, so that's not the problem.
> >
> > Any idea what that might be?
>
> Your installation of the Docbook tools is incomplete. The make
> rules explicitly disable the use of non-local style-sheets
> (that's what --nonet does), so you need to have a complete
> Docbook/XML installation locally.
>
>
> Sven

My run seems to blow up on LaTeX code that presumes MSWIn.
I use Slackware 12.2.
Here are some of the error messages:
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for docbook
no support found for unicode
<portions omitted>

gimp_tmp.tex:6847: Undefined control sequence \windows.
gimp_tmp.tex:6847: leading text: \nolinkurl{C:\windows\fonts}
gimp_tmp.tex:6847: Undefined control sequence \fonts.
gimp_tmp.tex:6847: leading text: \nolinkurl{C:\windows\fonts}
gimp_tmp.tex:6848: Undefined control sequence \winnt.
gimp_tmp.tex:6848: leading text: \nolinkurl{C:\winnt\fonts}
gimp_tmp.tex:6848: Undefined control sequence \fonts.
gimp_tmp.tex:6848: leading text: \nolinkurl{C:\winnt\fonts}
gimp_tmp.tex:9385: Undefined control sequence \Documents.
gimp_tmp.tex:9385: leading
text: ...nd~Settings\[Username]\.gimp-2.6\menurc}
gimp_tmp.tex:9385: Undefined control sequence \@nil.
gimp_tmp.tex:9385: leading
text: ...nd~Settings\[Username]\.gimp-2.6\menurc}
gimp_tmp.tex:9385: Incomplete \iffalse; all text was ignored after
line 9385.
gimp_tmp.tex: Emergency stop.
----------------------------------------------------

Here is my compile script, taken from Sven's post:

----------------------------------------------------------------
git clone --depth=0 git://git.gnome.org/gimp-help-2
cd gimp-help-2
./autogen.sh
LINGUAS=en make
LINGUAS=en make pdf-local
pdfinfo pdf/en/gimp.pdf
-----------------------------------------
I can't find on my system gimp_tmp.tex referred to in the error
messages. Hence I can't patch the TeX code myself.

> On Sunday 21 June 2009 05:52:00 am Sven Neumann wrote:
>> Hi,
>>
>> On Sat, 2009-06-20 at 21:35 +0200, Jogchum Reitsma wrote:
>> > Seems a perfect solution, be it that in my case (Suse 11.1),
>> > the first make fails with
>> >
>> > *** Making html for en ...
>> > /usr/bin/xsltproc \
>> > --nonet \
>> > --xinclude \
>> > --stringparam l10n.gentext.default.language en \
>> > -o html/en/ \
>> > stylesheets/plainhtml.xsl \
>> > xml/en/gimp.xml
>> > I/O error : Attempt to load network entity
>> >
>> > http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.
>> >xsl warning: failed to load external entity
>> >
>> > "http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk
>> >.xsl" compilation error: file stylesheets/plainhtml.xsl line 8
>> > element import xsl:import : unable to load
>> >
>> > http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.
>> >xsl make[1]: *** [html/en/index.html] Fout 5
>> >
>> > The URL is accessable in a browser, so that's not the problem.
>> >
>> > Any idea what that might be?
>>
>> Your installation of the Docbook tools is incomplete. The make
>> rules explicitly disable the use of non-local style-sheets
>> (that's what --nonet does), so you need to have a complete
>> Docbook/XML installation locally.
>>
>>
>> Sven
>
> My run seems to blow up on LaTeX code that presumes MSWIn.
> I use Slackware 12.2.
> Here are some of the error messages:
> no support found for ifxetex
> no support found for fontspec
> no support found for xltxtra
> no support found for fontenc
> no support found for inputenc
> no support found for fancybox
> built-in module makeidx registered
> no support found for docbook
> no support found for unicode
> <portions omitted>
>
> gimp_tmp.tex:6847: Undefined control sequence \windows.
> gimp_tmp.tex:6847: leading text: \nolinkurl{C:\windows\fonts}
> gimp_tmp.tex:6847: Undefined control sequence \fonts.
> gimp_tmp.tex:6847: leading text: \nolinkurl{C:\windows\fonts}
> gimp_tmp.tex:6848: Undefined control sequence \winnt.
> gimp_tmp.tex:6848: leading text: \nolinkurl{C:\winnt\fonts}
> gimp_tmp.tex:6848: Undefined control sequence \fonts.
> gimp_tmp.tex:6848: leading text: \nolinkurl{C:\winnt\fonts}
> gimp_tmp.tex:9385: Undefined control sequence \Documents.
> gimp_tmp.tex:9385: leading
> text: ...nd~Settings\[Username]\.gimp-2.6\menurc}
> gimp_tmp.tex:9385: Undefined control sequence \@nil.
> gimp_tmp.tex:9385: leading
> text: ...nd~Settings\[Username]\.gimp-2.6\menurc}
> gimp_tmp.tex:9385: Incomplete \iffalse; all text was ignored after
> line 9385.
> gimp_tmp.tex: Emergency stop.





You need at xetex, (tex-live xetex)

You need to follow Sven's advice above about Docbook as well

Do that and then see what residual errors you have

Hi,


On Thu, 2009-06-18 at 10:05 -0400, John Culleton wrote:
> Is the Gimp online manual also available in another format?

That's a question for the gimp-docs mailing-list.


Sven