[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sgml-tools for Linuxdoc
Hi.
# I cut some addresses from Cc:
In <[email protected]>,
at Date: Tue, 21 Dec 1999 19:33:50 +0100,
on Subject: Re: sgml-tools for Linuxdoc,
Stein Gjoen <[email protected]> writes:
> > In <[email protected]>, at Date: Mon, 20 Dec 1999 10:40:09 +0100,
> > on Subject: Re: sgml-tools for Linuxdoc, Stein Gjoen <[email protected]> writes:
> >
> > > Another annoying bug is that any <tt> tags in a heading causes
> > > these entries in the table of contents to cut the title at the
> > > position of the tag.
> > >
> > > Example:
> > > HTML: 6.3 Linux md Kernel Patch
> > > 12.8 fstab
> > > ASCII: 6.3 Linux
> > > 12.8 (TT
>
> [snip]
>
> > Can you show me the sample sgml file ? I think this problem
> > has been fixed in upstream. I have not worked on this, but
> > sgml-tools 1.0.9 does not show this problem when I create
> > and check a sample sgml file.
>
> Certainly: the source file is available at
> http://www.nyx.net/~sgjoen/disk.sgml
Ah, we (JF) have translation of this 'HOWTO: Multi Disk System Tuning'
written by you. I learned a lot from reading this via the translation
when I started to use Linux. I am glad to hear from the author of it :)
# Current Japanese Translation is based on previous version, v0.23d,
# and it was finished at 12 Dec 1999. Strangely, it happened to be
# the same date of your new version 0.23e.
> Come to think of it, there is another mysterious error message
> that appears when processing that file with sgml2txt. I do not
> have the error message at hand but I can post it later.
I check this disk.sgml (v0.23e) with sgml2txt from our Debian pacakge
of sgmltools_1.0.9-5 (the most updated one). The messages I got is:
$ sgml2txt disk.sgml
Processing file disk.sgml
<standard input>:3250: warning: can't break line
I doubt the groff which is called from sgml2txt (or fmt_txt.pl) output
the warning in last message.
But this warning is to complain that the specified line can not be broken
in order to fill the specified width of the text (so the output may have
longer line than expected width), and can be ignored in most cases.
At least I think so.
The output from sgml2txt (disk.txt) shows
6. Technologies
6.1 RAID
6.1.1 SCSI-to-SCSI
6.1.2 PCI-to-SCSI
6.1.3 Software RAID
6.1.4 RAID Levels
6.2 Volume Management
6.3 Linux md Kernel Patch
6.4 Compression
6.5 ACL
6.6 cachefs
6.7 Translucent or Inheriting File Systems
6.8 Physical Track Positioning
6.8.1 Disk Speed Values
6.9 Stacking
6.10 Recommendations
and
12. Implementation
12.1 Drives and Partitions
12.2 Partitioning
12.3 Repartitioning
12.4 Microsoft Partition Bug
12.5 Multiple Devices (md)
12.6 Formatting
12.7 Mounting
12.8 fstab
12.9 Recommendations
in it's table of contents.
I check the contents of disk.sgml, and it has
<sect1>Linux <tt/md/ Kernel Patch
<p>
<nidx>disk!technologies!md</nidx>
<nidx>disk!technologies!raid</nidx>
<nidx>disk!technologies!striping</nidx>
<nidx>disk!technologies!translucence</nidx>
The Linux Multi Disk (md) provides a number of block level features
in various stages of development.
and
<sect1><tt/fstab/
<p>
<nidx>disk!implementation!fstab</nidx>
<nidx>disk!fstab</nidx>
During the booting process the system mounts all partitions
as described in the <tt/fstab/ file which can look something
like this:
as a contents.
I think this problem has been fixed, maybe in the upstream,
because I have not worked on this, although I am not sure
if modifications in our Debian package (from members and users of
Debian, including me) happens to come to fix this as well as
other problems.
Have you checked this with original sgml_tools 1.0.9 ?
Thanks.
--
Taketoshi Sano: <[email protected]>,<[email protected]>,<[email protected]>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]