Ethereal-dev: Re: [Ethereal-dev] docboook Makeifle: experimental patch attached

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Tue, 8 Mar 2005 13:18:42 +0100
On Tue, Mar 08, 2005 at 07:48:22AM +0100, Ulf Lamping wrote:
> Sorry for the late response, I was on holiday.

I'm in no hurry.

> >- the big html-files are generated in the docbook directory, not in a
> > subdirectory.
> >
> I *really* don't like that. This solution makes it hard to find all the 
> files needed for the specific output format. With the current solution 
> you can simply copy the output directory you need and you're done.
> 
> With your solution you have to *know* that you must copy the graphics 
> directory too. And even worse, you cannot put the graphics into the html 
> dir, as this would result in broken graphics links.

Well, if you feel about it thaaaaaat strongly, I can change it back :-)
I just want you to consider the following: You have to know what to
copy in the first place. It just changed from 1 directory to 2 directories
(in the chunked html case) and 1 directory + 1 file in the big html case.
I fact, if you want to provide both html texts on a web page, you don't
have to replicate all the images. So my question is: is it really that bad?
Would an install target that created a tar.gz or zip file help to get
around your concerns? If not, see my first words in ths paragraph, let
me know and I'll change it back.

> >- the html chunked and windows help files don't copy the graphics
> > subdirectories any more but use the original ones instead.
> > 
> >
> Same thing as above.
> 
> Ok, the chm file will include the graphics so the situation is a 
> bit.different here.

I take it that I won't have to change this one back no matter how you
decide on the html case?

> >Please let me know whether it works and what you think of the other
> >changes.
> >
> I won't try that patch for the reasons described above.

I'd still be happy to know whether the change works on a technical
level. If I were to commit just the change you answered with ok now,
I wouldn't know whether I'd break things on the Windows side.

  Ciao
          Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.