Docbook in Red Hat 7.1

Docbook in Red Hat 7.1

[Peter Toft]

It appears that Red Hat has made significant opdates
from Red Hat 7.0 to 7.1 regarding DocBook tools. It
seems that many of my script do not work now.
For one - now jadewrapper has come in and
the good old Marc Galassi stylesheet is
gone: /usr/lib/sgml/stylesheets/cygnus-both.dsl

Well I found with Red Hat 7.1 I can generate HTML
output, but PDF has problems. Running jade to get
my HTML.index (for collateindex.pl) the screen is
soon filled with:

jade:/usr/share/sgml/docbook/utils-0.6/docbook-utils.dsl:417:19:E: reference to undefined variable "%admon-font-family%"
jade:/usr/share/sgml/docbook/utils-0.6/docbook-utils.dsl:411:7:E: reference to undefined variable "HSIZE"
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.59/html/dbhtml.dsl:316:17:E: invalid value for "attributes" characteristic
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.59/html/dbhtml.dsl:316:17:E: invalid value for "attributes" characteristic
...
...
The last line is repeated forever....

I tried to run

jade -t sgml -ihtml -d /usr/share/sgml/docbook/utils-0.6/docbook-utils.dsl\#print -V html-index -V nochunks bog.sgml > ged.html

Clues??


-- 

     .--.      Peter Toft, Ph.D.
    |o_o |     [pto@sslug.dk]
    |:_/ |     http://www.sslug.dk/~pto
   //   \ \
  (|     | )   Penguin power
 /'\_   _/`\
 \___)=(___/

Re: Docbook in Red Hat 7.1

[Mark Galassi]

Dear Peter,

As it turns out, Red Hat has completed what Eric and I did but never
formally released: if they are using "jadewrapper" it means that they
took our stuff out of CVS (and out of our interim release) and put
that out.

I'll take a better look.  Just a few hours ago I finally started
preparing a new release based on all the work Eric and I did last
summer/fall, and I think it will be good.

One thing you don't mention in your note is what overall wrapper they
have.

I'll also take a look at the index collating: I have done little with
that, and I have not tested it either.

Re: Docbook in Red Hat 7.1

[Peter Toft]

On 21 Apr 2001, Mark Galassi wrote:

>
> Dear Peter,

Hi Mark :-)))

>
> As it turns out, Red Hat has completed what Eric and I did but never
> formally released: if they are using "jadewrapper" it means that they
> took our stuff out of CVS (and out of our interim release) and put
> that out.
>
> I'll take a better look.  Just a few hours ago I finally started
> preparing a new release based on all the work Eric and I did last
> summer/fall, and I think it will be good.
>
> One thing you don't mention in your note is what overall wrapper they
> have.

db2html uses /usr/bin/jw - a jadewrapper - which has
text in the beginning saying that Eric collects
comments.
The jadewrapper jw comes from the Red Hat 7.1 package
docbook-utils-0.6-13.*rpm
(Package naming has changed a lot from RH 7.0 to 7.1)

>
> I'll also take a look at the index collating: I have done little with
> that, and I have not tested it either.

That would be a big help for me!

Thank you.


-- 
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

"Open Source and Linux: All of us win"

Re: Docbook in Red Hat 7.1

[Tim Waugh]

On Sat, Apr 21, 2001 at 03:41:11PM -0600, Mark Galassi wrote:

> As it turns out, Red Hat has completed what Eric and I did but never
> formally released: if they are using "jadewrapper" it means that they
> took our stuff out of CVS (and out of our interim release) and put
> that out.

Eric Bischoff had been pressing for us to use the new-trials packages,
and it became more attractive with LSB acceptance.  What we have in
Red Hat Linux 7.1 is basically the new-trials packages with some
slight re-packaging and some fixes.  I haven't yet sent the fixes
back, but it's on my list.

> I'll take a better look.  Just a few hours ago I finally started
> preparing a new release based on all the work Eric and I did last
> summer/fall, and I think it will be good.

Cool.

> One thing you don't mention in your note is what overall wrapper they
> have.

The 'jw' script from docbook-utils-0.6.

> I'll also take a look at the index collating: I have done little with
> that, and I have not tested it either.

(Me either.)

Tim.
*/
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE64gtBONXnILZ4yVIRAp8UAJ9uD82ydTOfkLVGOLXNAtyVf3sCUACeLM/h
xbPCMRTqR4P1dIGQUPuhlcs=
=Unca
-----END PGP SIGNATURE-----

Re: Docbook in Red Hat 7.1

[Edward C. Bailey]

>>>>> "Tim" == Tim Waugh <twaugh@redhat.com> writes:

Tim> On Sat, Apr 21, 2001 at 03:41:11PM -0600, Mark Galassi wrote:
...
>> I'll also take a look at the index collating: I have done little with
>> that, and I have not tested it either.

Tim> (Me either.)

I've done a bit with it (I hacked up a new frontend and backend for jw that
uses collateindex.pl and did some cursory testing under the 7.1 beta).  I've
done tried it on the gold bits yet; after I give it a try, I'll post it
here if you like...

                            Ed
-- 
Ed Bailey        Red Hat, Inc.          http://www.redhat.com/

Re: Docbook in Red Hat 7.1

[Peter Toft]

On 21 Apr 2001, Edward C. Bailey wrote:

> >>>>> "Tim" == Tim Waugh <twaugh@redhat.com> writes:
>
> Tim> On Sat, Apr 21, 2001 at 03:41:11PM -0600, Mark Galassi wrote:
> ...
> >> I'll also take a look at the index collating: I have done little with
> >> that, and I have not tested it either.
>
> Tim> (Me either.)
>
> I've done a bit with it (I hacked up a new frontend and backend for jw that
> uses collateindex.pl and did some cursory testing under the 7.1 beta).  I've
> done tried it on the gold bits yet; after I give it a try, I'll post it
> here if you like...

It sure would be nice to know how to get RH 7.1 docbook
tools to work - so please do :)
Using collateindex.pl seems to be non-trivial.

-- 
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

"I don't think Microsoft is evil in itself; I just think that they make
really crappy operating systems." -- Linus Torvalds

Re: Docbook in Red Hat 7.1

[Edward C. Bailey]

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

>>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:

Peter> On 21 Apr 2001, Edward C. Bailey wrote:
...
>>  I've done a bit with it (I hacked up a new frontend and backend for jw
>> that uses collateindex.pl and did some cursory testing under the 7.1
>> beta).  I've done tried it on the gold bits yet; after I give it a try,
>> I'll post it here if you like...

Peter> It sure would be nice to know how to get RH 7.1 docbook tools to
Peter> work - so please do :) Using collateindex.pl seems to be
Peter> non-trivial.

It's not that bad, really.  Basically you run your SGML through jade once
to get an HTML index file; then you run collateindex.pl against this,
creating a DocBook index.  Finally, you run your SGML (including the
newly-generated index) through jade one last time.

Some notes on these scripts:

    o Minimal testing, blah, blah, blah, it's somewhat stupid, blah, blah,
      blah, works for me, blah, blah, blah... :-)

    o Usage is:

<path-to-script>/flo-db2indexed-html <SGML-file>.sgml

    o Puts final output in a subdirectory called <SGML-file>

    o Assumes the following entity definition and reference is in the SGML
      file:

<!ENTITY GENERATED-INDEX SYSTEM "generated-index.sgml">

      And where ever you want the index to appear:

&GENERATED-INDEX;

      (The script will recreate generated-index.sgml each time it runs; the
      first time jade runs there will be no file by this name, so you'll
      see an error.)

    o Assumes that any graphics referenced in the SGML reside in a
      subdirectory called "figs".  This subdirectory is copied into the
      <SGML-file> subdirectory, so the entire <SGML-file> directory tree
      can be tarred up, and dropped on a website, ready to go...

    o flo-db2indexed-html refers to a .dsl file that we've hacked, but this
      should be removable so the default DSSSL is used instead.

I think that's about it...

                                Enjoy,

                                    Ed


[-- Attachment #2: flo-db2indexed-html --]
[-- Type: text/x-shellscript, Size: 1115 bytes --]

#! /bin/sh

# Make sure we have an absolute path to the backend and stylesheet, as
# jw doesn't like relative paths...

STUFFPATH=`dirname $0`
if [ -n "${STUFFPATH##/*}" ]
then
    STUFFPATH=$PWD/$STUFFPATH
fi

# Figure out what our output directory should be called.  Note that we
# also check to see if the user explicitly specified an output directory,
# in which case we'll use their choice...

O_OPTION=0
for i in "$@"
do
    if [ $O_OPTION = "1" ]
        then
            OUTPUTDIR=$i
            O_OPTION=0
        fi
    if [ $i = "-o" ]
        then
            O_OPTION=1
        fi
done

# See if the user specified an output directory...

if [ -z $OUTPUTDIR ]
    then
# Nope -- default to the name of the SGML file...
        OUTPUTDIR="`echo $i | sed 's,\.sgml$,,;s,\.sgm$,,'`"
    fi

# Nuke the output directory (if it exists); jw will create it for us...

if [ -d $OUTPUTDIR ]
    then
	echo -n "Cleaning out $OUTPUTDIR..."
	rm -rf $OUTPUTDIR
	echo "Done!"
    fi

jw -f docbook \
    -b $STUFFPATH/flo-indexed-html \
    -d $STUFFPATH/stylesheets/flo-redhat-html.dsl \
    -o $OUTPUTDIR \
    $*

[-- Attachment #3: flo-indexed-html --]
[-- Type: text/plain, Size: 2190 bytes --]

# Based on original from Eric Bischoff <eric@caldera.de>

# Create an HTML document with index and figures in place.
# This is done by:

# 1. Converting from SGML to HTML
# 2. Generating an SGML index based on the HTML
# 3. Converting from SGML to HTML (taking into account the index this time)
# 4. Copying figures from original source tree into the output directory

# The end result is a directory tree ready for publishing/packaging/whatever...

# Magic variables.  I feel uncomfortable about the version number in these
# paths, but feel even more uncomfortable wildcarding it... :-(

HTML_STYLESHEET=/usr/share/sgml/docbook/dsssl-stylesheets-1.59/test/docbook.css
ADMON_GRAPHICS=/usr/share/sgml/docbook/dsssl-stylesheets-1.59/images/*.gif

FINAL_INDEX=generated-index.sgml
INDEXFILE=INDEX$$

# Convert to HTML, generating the HTML.index file that we'll use to
# create an SGML index...

echo Running $SGML_JADE...

$SGML_JADE -t sgml -V html-index $SGML_ARGUMENTS

# Generate the index, fixing up the problem of bogus empty closing tags (</>)...

echo Indexing...
perl /usr/bin/collateindex.pl -g -o ../$FINAL_INDEX HTML.index

# Not sure if these are still needed; when we first tried collateindex;
# it threw "</>" in the generated index in certain cases...

cat ../$FINAL_INDEX | sed 's,^[        ]*</>[  ]*$,,' > ../$INDEXFILE
mv -f ../$INDEXFILE ../$FINAL_INDEX

# Nuke the HTML.index file; we don't need it anymore...

rm -f HTML.index

echo Rerunning $SGML_JADE...

$SGML_JADE -t sgml $SGML_ARGUMENTS

echo -n "Copying cascading stylesheet and admon graphics..."
cp ${HTML_STYLESHEET} ./
mkdir ./stylesheet-images
cp ${ADMON_GRAPHICS} ./stylesheet-images/
echo "Done!"

if [ -d ../figs/ ]
    then
        echo -n "Moving figures..."
        (cd ../ ; tar cf - figs/) | (tar xf -)
        echo "Done!"
        echo -n "Cleaning CVS..."
        find ./figs/ -type d -name "CVS"|xargs rm -rf
        echo -n "EPS..."
        find ./figs/ -type f -name "*eps"|xargs rm -f
        echo -n " .xvpics..."
        find ./figs/ -type d -name ".xvpics"|xargs rm -rf
        echo -n "directories..."
        find ./figs/ -type d -empty|xargs rm -rf
        echo "Done!"
    fi
# 
exit 0

Re: Docbook in Red Hat 7.1

[Wookey]

On Tue 24 Apr, Edward C. Bailey wrote:
> >>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:
>  Using collateindex.pl seems to be non-trivial.

> It's not that bad, really.  Basically you run your SGML through jade once
> to get an HTML index file; then you run collateindex.pl against this,
> creating a DocBook index.  Finally, you run your SGML (including the
> newly-generated index) through jade one last time.

Do you know if this/the new set of files/tools works properly for PDF index
generation?

I posted here a while back about how I can generate a perfectly good SGML
index file using collateindex, and that db2html does a fine job of then
generating an html book with an index.

But if I try to do the same for PDF the final PDF index only has some 30% of
the references filled out, and most of those seem to be wrong. No-one had any
suggestions as to what might be going wrong and my understanding of the
process is too poor to know what to fiddle with. Doing a small (few pages)
PDF file seemed to work OK, but my full (150 pages) book suffers the above
problem, so right now it is annoyingly indexless.

I don't know if I should be looking at what jade does or what jadetex does to
get to the bottom of this.

I have two different methods of generating the PDF version - both of which
suffer the above problem.

In either case start with:
jade -c $CATALOG -t sgml -V html-index -ihtml -d ${DB_STYLESHEET} book
perl ./collateindex.pl -s Symbols -t Index -g -i index -o genindex.sgm HTML.index

(following this with 
 jade -c $CATALOG -t sgml -ihtml -d ${DB_STYLESHEET} book
 produces nicely-indexed HTML)
 
Then do either: 
1) jade -t tex -d ${DB_STYLESHEET} -o ${TMPFN}.tex book
 pdfjadetex $TMPFN
 pdfjadetex $TMPFN
 pdfjadetex $TMPFN

2) jade -t tex -d ${DB_STYLESHEET} -o ${TMPFN}.tex book
 jadetex ${TMPFN}.tex
 jadetex ${TMPFN}.tex
 jadetex ${TMPFN}.tex
dvips -o guide.ps book.dvi
ps2pdf book.ps

this second method has the advantage that it puts the pictures in. version 1
ought to but gives an error saying 'unrecognised format .eps'. 

Can anyone give me a clue about how to fix/diagnose the index problem (or how
to get pdfjadtex to put the pictures in).

thanx

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/

Re: Docbook in Red Hat 7.1

[Peter Toft]

On Thu, 26 Apr 2001, Wookey wrote:

> 1) jade -t tex -d ${DB_STYLESHEET} -o ${TMPFN}.tex book
>  pdfjadetex $TMPFN
>  pdfjadetex $TMPFN
>  pdfjadetex $TMPFN
>
> 2) jade -t tex -d ${DB_STYLESHEET} -o ${TMPFN}.tex book
>  jadetex ${TMPFN}.tex
>  jadetex ${TMPFN}.tex
>  jadetex ${TMPFN}.tex
> dvips -o guide.ps book.dvi
> ps2pdf book.ps
>
> this second method has the advantage that it puts the pictures in. version 1
> ought to but gives an error saying 'unrecognised format .eps'.
>
> Can anyone give me a clue about how to fix/diagnose the index problem (or how
> to get pdfjadtex to put the pictures in).

I had some of those problems too, and switched to using
png-pictures then running for pdf-output. I got
excellent help from this list regarding handling this
issue. Now I run pdfjadetex directly with png's only.

-- 
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

"Peace, Love, and Linux" -- IBM

Re: Docbook in Red Hat 7.1

[Peter Toft]

On Thu, 26 Apr 2001, Wookey wrote:

> On Tue 24 Apr, Edward C. Bailey wrote:
> > >>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:
> >  Using collateindex.pl seems to be non-trivial.
>
> > It's not that bad, really.  Basically you run your SGML through jade once
> > to get an HTML index file; then you run collateindex.pl against this,
> > creating a DocBook index.  Finally, you run your SGML (including the
> > newly-generated index) through jade one last time.
>
> Do you know if this/the new set of files/tools works properly for PDF index
> generation?
>
> I posted here a while back about how I can generate a perfectly good SGML
> index file using collateindex, and that db2html does a fine job of then
> generating an html book with an index.
>
> But if I try to do the same for PDF the final PDF index only has some 30% of
> the references filled out, and most of those seem to be wrong. No-one had any
> suggestions as to what might be going wrong and my understanding of the
> process is too poor to know what to fiddle with. Doing a small (few pages)
> PDF file seemed to work OK, but my full (150 pages) book suffers the above
> problem, so right now it is annoyingly indexless.

Strange - I seem to be able run a set of books together
with the new RH 7.1 tools and produce 800 pages (five
books collected) with more than 1000 index-words -
seems to be fine.

However the who idea of using flo-* is still "young" -
it lacks support for set-indexes (now only ordinary
indexes are ok), national language-settings etc. I am
hacking on those problems right now.


-- 
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

Linux - Open Source - freedom : that's cool !

Re: Docbook in Red Hat 7.1

[Wookey]

On Fri 27 Apr, Peter Toft wrote:
> On Thu, 26 Apr 2001, Wookey wrote:
> 

> > I posted here a while back about how I can generate a perfectly good SGML
> > index file using collateindex, and that db2html does a fine job of then
> > generating an html book with an index.
> >
> > But if I try to do the same for PDF the final PDF index only has some 30%
> > of the references filled out, and most of those seem to be wrong. No-one
> > had any suggestions as to what might be going wrong and my understanding
> > of the process is too poor to know what to fiddle with. Doing a small
> > (few pages) PDF file seemed to work OK, but my full (150 pages) book
> > suffers the above problem, so right now it is annoyingly indexless.
> 
> Strange - I seem to be able run a set of books together
> with the new RH 7.1 tools and produce 800 pages (five
> books collected) with more than 1000 index-words -
> seems to be fine.

That seems encouraging - (but did you have the same prob as me before
switching to this software set?). Anyway sounds like I should try it. Except
I have debian boxes and prefer to stick wit the Debs in general. Can someone
tell me which versions of the tools are in the RH7.1 software set and which
bits (eg this jadewrapper) are perhaps not (yet) found anywhere else. Then I
can compare with the current Debian state of the art and see what the easiest
path to up-to-date software might be....

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/

Re: Docbook in Red Hat 7.1

[Peter Toft]

On 24 Apr 2001, Edward C. Bailey wrote:

> >>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:
>
> Peter> On 21 Apr 2001, Edward C. Bailey wrote:
> ...
> >>  I've done a bit with it (I hacked up a new frontend and backend for jw
> >> that uses collateindex.pl and did some cursory testing under the 7.1
> >> beta).  I've done tried it on the gold bits yet; after I give it a try,
> >> I'll post it here if you like...
>
> Peter> It sure would be nice to know how to get RH 7.1 docbook tools to
> Peter> work - so please do :) Using collateindex.pl seems to be
> Peter> non-trivial.
>
> It's not that bad, really.  Basically you run your SGML through jade once
> to get an HTML index file; then you run collateindex.pl against this,
> creating a DocBook index.  Finally, you run your SGML (including the
> newly-generated index) through jade one last time.

For the stuff Ed posted two days ago I found that
(Red Hat Linux 7.1) I have to run the scripts
through dos2unix and (Ed has been very helpful
off-list)

you have to delete the line 49
    -d $STUFFPATH/stylesheets/flo-redhat-html.dsl \

and if you want to do an index for other languages -
for Danish I want to run collateindex.pl with options
-s Symboler  -t Stikordsregister -g -i stikord -N
then I have to hack directly into
flo-indexed-html since I cannot parse those as
arguments

I am no there 100% yet - but it (I hope) seems close
now...


-- 
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

                         (o_
(o_  (o_  (o_  (o_  (o_  //\  Penguins on the move !
(/)_ (/)_ (/)_ (/)_ (/)_ V_/_

Re: Docbook in Red Hat 7.1

[Edward C. Bailey]

>>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:
...
Peter> For the stuff Ed posted two days ago I found that (Red Hat Linux
Peter> 7.1) I have to run the scripts through dos2unix and (Ed has been
Peter> very helpful off-list)

More like very confused (but willing to communicate my confusion)
off-list... ;-)

I'm not sure why this is necessary; I just pulled the files down from my
email, and compared them with the originals, and the files have identical
md5sums.  So if anyone else sees this kind of problem, please let me know.
That way I can try to figure out whether it is my mailer doing bad MIME
things or not...

                            Ed
-- 
Ed Bailey        Red Hat, Inc.          http://www.redhat.com/

Re: Docbook in Red Hat 7.1

[Hugo van der Kooij]

On 26 Apr 2001, Edward C. Bailey wrote:

> >>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:
> ...
> Peter> For the stuff Ed posted two days ago I found that (Red Hat Linux
> Peter> 7.1) I have to run the scripts through dos2unix and (Ed has been
> Peter> very helpful off-list)
>
> More like very confused (but willing to communicate my confusion)
> off-list... ;-)
>
> I'm not sure why this is necessary; I just pulled the files down from my
> email, and compared them with the originals, and the files have identical
> md5sums.  So if anyone else sees this kind of problem, please let me know.
> That way I can try to figure out whether it is my mailer doing bad MIME
> things or not...

I noticed they were encoded as:
	Application/OCTET-STREAM

Which should mean the get transfered pretty much transparant. But after I
saved them I found they were using CR/LF and vim reported this as:
	"flo-db2indexed-html" [dos] 51L, 1166C

It might be an issue with the email software:
	User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

Hugo.

-- 
Alle email aan mij verzonden is gebonden aan de regels beschreven op mijn homepage.
All email send to me is bound to the rules described on my homepage.

    Hugo van der Kooij; Oranje Nassaustraat 16; 3155 VJ  Maasland
    hvdkooij@vanderkooij.org		http://hvdkooij.xs4all.nl/

	    Don't meddle in the affairs of sysadmins,
	    for they are subtle and quick to anger.

Re: Docbook in Red Hat 7.1

[Edward C. Bailey]

>>>>> "Hugo" == Hugo van der Kooij <hvdkooij@vanderkooij.org> writes:

Hugo> On 26 Apr 2001, Edward C. Bailey wrote:
...
>> I'm not sure why this is necessary; I just pulled the files down from my
>> email, and compared them with the originals, and the files have
>> identical md5sums.  So if anyone else sees this kind of problem, please
>> let me know.  That way I can try to figure out whether it is my mailer
>> doing bad MIME things or not...

Hugo> I noticed they were encoded as: Application/OCTET-STREAM

Hugo> Which should mean the get transfered pretty much transparant. But
Hugo> after I saved them I found they were using CR/LF and vim reported
Hugo> this as: "flo-db2indexed-html" [dos] 51L, 1166C

Interesting; vim does not report this when I open the original file
here...

Hugo> It might be an issue with the email software: User-Agent: Gnus/5.0808
Hugo> (Gnus v5.8.8) Emacs/20.7

Since I got matching md5sums on the original and the files taken from my
email, we either have a situation where my emailer (gnus) is both encoding
and decoding incorrectly (so they cancel out, and I see no change), or I'm
guilty of cockpit error, or some peoples' emailers are doing something
incorrect when decoding.  I'm not sure which it is, so I'll do some
research on my end to see if I'm messing it up or not... :-)

                                Ed
-- 
Ed Bailey        Red Hat, Inc.          http://www.redhat.com/

Re: Docbook in Red Hat 7.1

[Hugo van der Kooij]

On 26 Apr 2001, Edward C. Bailey wrote:

> >>>>> "Hugo" == Hugo van der Kooij <hvdkooij@vanderkooij.org> writes:
>
> Hugo> On 26 Apr 2001, Edward C. Bailey wrote:
> ...
> >> I'm not sure why this is necessary; I just pulled the files down from my
> >> email, and compared them with the originals, and the files have
> >> identical md5sums.  So if anyone else sees this kind of problem, please
> >> let me know.  That way I can try to figure out whether it is my mailer
> >> doing bad MIME things or not...
>
> Hugo> I noticed they were encoded as: Application/OCTET-STREAM
>
> Hugo> Which should mean the get transfered pretty much transparant. But
> Hugo> after I saved them I found they were using CR/LF and vim reported
> Hugo> this as: "flo-db2indexed-html" [dos] 51L, 1166C
>
> Interesting; vim does not report this when I open the original file
> here...

I think the used MIMETYPE is confusing. When I check the original message,
with all the MIME stuff inside it, I noticed there do not seem to be any
DOS like CR/LF entries.

In my case PINE may be at fault (which just puts the ball back to Red Hat
as I use a Vanilla PINE from the latest errata ;-)

Hugo.

-- 
All email send to me is bound to the rules described on my homepage.
    hvdkooij@vanderkooij.org		http://hvdkooij.xs4all.nl/
	    Don't meddle in the affairs of sysadmins,
	    for they are subtle and quick to anger.

Re: Docbook in Red Hat 7.1

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Le Sunday 22 April 2001 02:48, Edward C. Bailey a écrit :
>
> Tim> On Sat, Apr 21, 2001 at 03:41:11PM -0600, Mark Galassi wrote:
> >> I'll also take a look at the index collating: I have done little with
> >> that, and I have not tested it either.
>
> I've done a bit with it (I hacked up a new frontend and backend for jw that
> uses collateindex.pl and did some cursory testing under the 7.1 beta). 
> I've done tried it on the gold bits yet; after I give it a try, I'll post
> it here if you like...

Send it to me as well, please. I'd like to integrate your additions to the 
docbook-utils. Please give me a lot of instructions on the use of your new 
backend/frontends, I'm very ignorant on collateindex.pl issues, and it could 
also allow me to explain it better in the "crash course to docbook"

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
+----------------------------------------------------------------------+