SL-FO converters in
TeX/LaTex/PDFTeX, but that has proven to be a pretty difficult
taks, and those work on those apps never reached the point where
they became usable for production-quality work.
I wonder if it would be easier to implement an XSL-FO to PDF
converter in groff, or harder.
--Mike
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> There is a very important concept if you work with groff requests and
> escapes: The default scaling indicator. For \l, it is the em unit.
> This:
>
> \l'\n(.l*.80'
>
> is thus handled as
>
> \l'\n(.lm*.80m'
I see now. Before I posted I had bee
What is the recommended markup for rendering a horizontal line,
with the length of the horizonal line being some arbitrary
fraction of the global line length (that is, the distance from the
left margin to the right margin -- ll).
To specify a line whose length is 80 percent of the line length, I
a
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> I suggest that you download an original version of the groff package
> (from gnu.org), not the Debian version which is heavily patched --
> maybe the Japanese extension (which I don't support) is buggy, causing
> the problems you experience.
Indeed, it
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> > I notice that the groff info page says this:
> >
> > To tell `gtroff' how to hyphenate words on the fly, use the `\%'
> > escape, also known as the "hyphenation character". Preceding a
> > word with this character prevents it from being hyphen
Greetings from Tokyo.
Question: What's the correct inline groff markup for preventing an
individual word from being hyphenated?
I notice that the groff info page says this:
To tell `gtroff' how to hyphenate words on the fly, use the `\%'
escape, also known as the "hyphenation character". Pr
