Re: Re: Project: texi2latex

MathML is great, but unfortunately cannot be read by the simplified brows=
ers (like links, dillo, blazer, etc.). Thus a MathML solution, in compari=
son to a plain html solution is less portable... (when I test texnfo I us=
e a standard desktop pc, than a P50/32MB notebook with links, dillo and o=
pera and finally a palmos based pda with a palmos browser - if the output=
 is read correctly on all three systems it is OK for me, because it makes=
 texinfo user indipendent from both hardware and operating system + softw=
are)...

A software which is free for personal use and not free for commercial use=
, called tth, does an excellent job in transforming latex math into plain=
 html... unfortunately tth does not support division into nodes and it is=
 not gpl (a very bad choice imho)...

The Latex possibilities is not a caprise... I like texinfo markup very mu=
ch - it is very intuitive - but when it happens to you to deal on the one=
 hand with different languages (italian, french, german, italian, bulgari=
an, russian, etc.) on the other with some very small but compulsory layou=
t specifications like tex frames - it becomes very difficult to use latex=
 for one document and texinfo for another one because of language constra=
ints... and the fact is that texinfo and latex structures are not very fa=
r one from the others, at least 70% of latex constructs do find texinfo c=
orrespondences.

Wel, Karl... I found your name with reference to the WEB language, the on=
e Donald Knuth used when creating tex... it was quite a surprise...

Cheers,


Valentino

On Sat, 18 Dec 2004 20:32:55 +0100
Torsten Bronger <[email protected]> wrote:

> Hall=F6chen!
>=20
> [email protected] writes:
>=20
> > [...]
> >
> > regarding equations and maths and info: well, the trick would be
> > just to describe the math info cannot represent... as a matter of
> > fact the latex math conventions are complex but quite easy to
> > understand.
> >
> > \fract{1}{2+3} in Latex would be 1/(2+3) in info...
> >
> > and so on...
>=20
> (makeinfo has to cope with {1 \over 2+3}.)
>=20
> rms may hire an assassin for me(*), but it's very simple to do this
> with MathML as the origin.  This is true for all other formats,
> too.  So: Convert Texinfo to XML losslessly and create DocBook,
> HTML, and LaTeX from there!  :-)
>=20
> > the real advantages latex would give is the possibility to pass
> > commands regarding the hardcopy layout as well as input and font
> > encodings, etc. if we could find the minimum common denominator of
> > latex and texinfo lexical structures it would be a good leap frog.
>=20
> This is a very important point.  How do we pass layout information
> to the backends?  Plain TeX is clear.  DocBook contains no layout.
> makeinfo's HTML has a CSS hook and the single/multiple file switch.
> But can one pass layout directives to a "back-backend" like my
> texi2latex?  Or must they reside in a separate cfg/sty/whatever
> file?
>=20
> I don't remember wheter @c comments are included into the XML.  If
> so, they could be used to transport meta info like in Postscript.
> *shiver*
>=20
> Tsch=F6,
> Torsten.
>=20
> (*) Forunately, I am too unimportant.  ;-)
> --=20
> Torsten Bronger, aquisgrana, europa vetus
>=20
> _______________________________________________
> Texinfo home page: http://www.gnu.org/software/texinfo/
> [email protected]
> http://ff0.org/mailman/listinfo/texinfo-pretest
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
[email protected]
http://ff0.org/mailman/listinfo/texinfo-pretest