LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Thu, 10 Apr 2003 11:21:24 -0400
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Content-Type: text/plain; charset=us-ascii
From: William F Hammond <[log in to unmask]>
MIME-Version: 1.0
In-Reply-To: <[log in to unmask]>
Organization: Dept of Math & Stat, Univ at Albany (SUNY), Albany, NY
Comments: RFC822 error: <W> Incorrect or incomplete address field found and ignored.
Parts/Attachments: text/plain (29 lines)
[log in to unmask] (TomH) writes to comp.text.tex:

> I have a number of books that I have marked up in Latex, and I would
> like to donate them to the Gutenberg project. For good or ill, they
> like plaintext files formatted according to strict rules.
> . . .
> Is there anything that converts Latex to a plain text file (say
> in Gutenberg format)?  . . .

Sadly, one of the problems when an author's investment in marking up a
document is tied to LaTeX, the possibilities for robust automatic
translation without human intervention to other editable formats range
from limited (for collections of LaTeX documents with a reasonable
amount of structure and some consistency) to nil (for arbitrary

It really would not be that hard to remedy this by providing a kind of
LaTeX document that is both LaTeX-able and translatable[*], but it
does need shared attention.  Implementation would involve much work by
a team.  Wouldn't this be a sensible step for LaTeX4?

                                    -- Bill

[*] A document is translatable if it has a markup structure that
furnishes a non-ambiguous base for the writing of automatic processors
that operate on its structure.  The project might well choose to
provide one or two such translations both for utility value and for
illustrating the implementation of a translation.