>> > groff to XML to HTML via doclifter produces better HTML than any of
>> > the direct groff -> HTML tools.
>>
>> Sadly, this is true. grohtml would need a big hug with much love to
>> grow up, but currently nobody really takes care of it.
>
> The problem is fundamental - a good conversion nee
Werner LEMBERG :
>
> > groff to XML to HTML via doclifter produces better HTML than any of
> > the direct groff -> HTML tools.
>
> Sadly, this is true. grohtml would need a big hug with much love to
> grow up, but currently nobody really takes care of it.
The problem is fundamental - a good con
> groff to XML to HTML via doclifter produces better HTML than any of
> the direct groff -> HTML tools.
Sadly, this is true. grohtml would need a big hug with much love to
grow up, but currently nobody really takes care of it.
Werner
Peter Schaffter :
> Larry's correct, too, about transforming groff markup to other
> languages. As Steve can attest, I think, it's generally simpler to
> convert groff markup into acceptable XML than to produce good pdfs
> from XML filtered through groff.
Automated groff to XML is hard, but with
On Tue, May 08, 2012, Larry Kollar wrote:
> But I think there's room for a third kind of markup. I
> call it *humanist* markup. Humanist markup has structure —
> headings, lists, paragraphs, are easy to denote and
> separated from presentation. The markup is simple to
> transform to other language
Anton Shepelev wrote:
> I think, groff and TeX macro packages do provide a
> means for structural mark-up, and, considering the
> example above, it is of course possible to redefine
> the macro .B to achieve the desired result? For
> clarity, it could also be renamed as "EMPH".
>
> I
> On the PostScript side, it should be theoretically possible to
> use the `GlyphNames2Unicode' dictionary (an undocumented Adobe
> Distiller extension) so that PS->PDF software can provide
> non-standard mappings. Right now, I haven't found a full
> example code for that.
An interesting point.
Steve Izma wrote:
> I've made a lot of notes about this, and I promise that soon I
> will try to document this and other issues that make XML to groff
> processing tricky.
Most of us would like to read this, it's a very intersting
issue about troff. Please, inform the list when you've got a
draf
