[Latex2rtf-users] biblatex

[Ernst Reissner]

Hi all,

I found out in the meanwhile, that more and more people shift to the
package biblatex.
Maybe it is the future to support this also in latex2rtf.

What do you think about that?

Greetings,
Ernst

------------------------------------------------------------------------------

[Dominik Wujastyk]

Yes! Biblatex!

Dominik Wujastyk
​

[Wilfried Hennings]

Post by Ernst Reissner
Hi all,
I found out in the meanwhile, that more and more people shift to the
package biblatex.
Maybe it is the future to support this also in latex2rtf.
What do you think about that?

Well, it would be nice.
But it is complicated to implement.
Currently there is no developer active who could implement this.
I myself can only fix minor things like e.g. adding another special
character to an already existing list of such characters.
Apart from that, I am a bloody beginner in C programming, and
I still don't understand the structure of the latex2rtf program code.
Scott Prahl, who did the C programming in the past, seems to be so
occupied in his profession that he has virtually no time for latex2rtf
programming.
It would be nice if someone else could take over programming.

Regards
Wilfried

[Ernst Reissner]

Hello developers of latex2rtf,

I have a very general question:
I would have expected, that latex, or better tex is just a compiler.
There is a frontend reading tex-sources and maybe various backends
creating dvi, ps, pdf or whatsoever.

In this context I would also have expected that latex2rtf shares a
common frontend
and adds just a backend for rtf.

This seems a wrong assumption.
Why is this not implemented like that?

I ask because that way if a new package occurs in latex, it should not
require actions
to support it in latex2rtf then.


Greetings,

Ernst

[Wilfried Hennings]

Post by Ernst Reissner
Hello developers of latex2rtf,
I would have expected, that latex, or better tex is just a compiler.
There is a frontend reading tex-sources and maybe various backends
creating dvi, ps, pdf or whatsoever.
In this context I would also have expected that latex2rtf shares a
common frontend and adds just a backend for rtf.
This seems a wrong assumption.

Yes this assumption is wrong.

Post by Ernst Reissner
Why is this not implemented like that?
I ask because that way if a new package occurs in latex, it should not
require actions to support it in latex2rtf then.

Principally this would be a good idea.
But (as far as I know) the output of the TeX compiler consists of glyphs
and their coordinates on the print page, while rtf relies on the concept
of words, paragraphs and sections, and formatting styles, which are not
contained in the TeX output.
One would have to completely re-write the TeX compiler to get rtf (or
any other structured) output.

The converter TeX4ht started with the concept of letting TeX do the
parsing, but also ended up with the necessity that for each TeX / LaTeX
package a separate converter package is needed.

Regards
Wilfried