Jean-Marc Lasgouttes wrote:
Le 02/05/2009 17:34, rgheck a écrit :
There are more and less complicated ways to do this. You could have a
new format, like DocBook, but I think what's really wanted is something
that would work more like plaintext, so that you can output any document
as HTML. So we'd have a set of ashtml() routines in the insets, etc,
pretty much everywhere we have latex() and plaintext(), and the overall
structure would be the same.
Yes. It might be that some of the docbook stuff can be reused.
I hope so.
We obviously do not want to hardcode everything. In particular, to have
this work with custom styles, we need a bit of information in the
layouts about what HTML corresponds e.g. to "noun". This is fairly easy,
though it could be made more complicated, in ways at which Jose
gestured. I think we start with easy.
I would think that what is more important in HTML output is the visual
output. I would not have any problem myself with having style "noun"
be output as a <div> (<span>?) with class "noun" and have some css to
make it clear that noun uses small caps.
I'll try to make this as painless and simple as possible, but handling
custom styles will require something along these lines, I think, if only
so that the appropriate CSS gets output. We could have a fixed style
file that got included for noun and the like, but not for custom stuff.
That said, it might be worth having a layout that was specifically
designed for HTML output. That would make LyX usable as a kind of
WYSIWYM HTML editor, as someone else mentioned.
I do not think that it is the goal at this time...
No, not for me, anyway, though someone else mentioned it as a downstream
possibility. Can't recall who.
I am glad you are doing this, BTW.
Thanks. I'm sure I'll shortly be asking a lot of questions. Among the
other things I have to figure out is how the font stuff works.
Richard
