Re: [Gimp-developer] Current work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



   From: Sven Neumann <sven@xxxxxxxx>
   Date: 05 Dec 2001 14:15:42 +0100

   what would be the additional features you have in mind here? I
   don't see any advantange in relying on advanced capabilities in the
   help browser. I agree however that shipping the HTML with the
   sources is not a perfect solution. Converting at installation time
   is an option, but then it adds a new requirement to the build
   environment and I doubt that a lot of people have a working
   featureful XSLT processor installed. It is probably a good idea to
   continue to do the conversion when packaging the help tarball (on
   'make dist').

Gimp-print generates the HTML (and .pdf, and .ps) manuals at packaging
time.  The docbook toolchain seems to be incredibly fragile; different
versions of tools emit different warnings and/or fail in different
ways.  I would not recommend requiring the docbook toolchain at
compile time.

-- 
Robert Krawitz <rlk@xxxxxxxxxxxx>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lpf@xxxxxxxxxxxx
Project lead for Gimp Print/stp --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton


[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux