On Thu, Dec 02, 1999 at 10:52:26AM +0000, Jules Bean wrote:
> On Thu, 2 Dec 1999, Jose Abilio Oliveira Matos wrote:
>
> > As Allan said there are already several steps in that direction in
> > the docbook support. There are several abstractions that would allow
> > to make another backend really easy. One example, if anyone has the
> > time or the energy to do it is a native html backend...
>
> Yuck. What an unpleasant idea ;-) Hmm... uh.. depends what you mean by
> backend, I guess. Certainly, native editing of HTML documents is, IMO, a
> feature of only slight usefulness - HTML is a horrible format. However,
> editing in a SGML/XML designed for the purpose and then exporting to HTML
> would be cool.
>
Ok, I'm sorry for the confusion, I don't want LyX to be one more html
editor, that's really an unpleseant idea :)
What I was refering is the present ability to load the textclasses,
where some configuration is available and extend it. As I said
some time ago (not sure how long :) the textclasses are our stylesheets,
more like css than dsssl or XLT.
This could be extended, I think, to further control the final output.
> > I think that we also need a way to change a document from latex to
> > docbook and convert the document structure from one to the other, and
> > vice versa. That mechanism doesn't exist now.
>
> Tricky though, isn't it. I guess there are enough similarities between
> article.cls and docbook that it could probably be done for articles and
> related classes. A very hard problem in general, though.
Why not? ;-)
I don't mean the general problem, but some sort of filters, between
specific layouts. Use this filter if you have it, ignore it otherwise.
A simple example, the layout that is intended to have (computer) code
is the LyX-Code in article, and Code in docbook. If you import any lyx
latex related document chunck it would lost all the information only
because the layout have different names even if they represent the same thing.
Now suppose that you create a certain xml document, does this means that
all the code paragraphs should be called LyX-Code so that the simple copy
and past from other latex class documents doesn't loose this knowleadge?
The filters I am refering to could be as simple as this:
Latex class -> xml myDTD class
layout LyX-Code Code
BlaBla Standard #difficult to translate
Title Mytitle
Does this makes sense? :)
> Jules
>
> /----------------+-------------------------------+---------------------\
> | Jelibean aka | [EMAIL PROTECTED] | 6 Evelyn Rd |
> | Jules aka | [EMAIL PROTECTED] | Richmond, Surrey |
> | Julian Bean | [EMAIL PROTECTED] | TW9 2TF *UK* |
> +----------------+-------------------------------+---------------------+
> | War doesn't demonstrate who's right... just who's left. |
> | When privacy is outlawed... only the outlaws have privacy. |
> \----------------------------------------------------------------------/
--
Jos�
