On Saturday 09 May 2009 15:17:41 rgheck wrote:
> My intention was to do it this way for HTML, rather than to hardcode
> everything. It's obviously possible to do the same for plaintext, though
> I'm not sure how useful that would be.
Easier to configure. :-)
In any case if the html part is done t
José Matos wrote:
On Friday 08 May 2009 22:20:40 Abdelrazak Younes wrote:
I must have missed the purpose of Inset::plaintext()... ;-)
That is only half of the story. :-)
The other half is coded in the text classes (layout files).
Take the section style as an example (I took this chun
On Friday 08 May 2009 22:20:40 Abdelrazak Younes wrote:
> I must have missed the purpose of Inset::plaintext()... ;-)
That is only half of the story. :-)
The other half is coded in the text classes (layout files).
Take the section style as an example (I took this chunk from stdsections.inc):
St
On 08/05/2009 23:16, José Matos wrote:
On Friday 08 May 2009 20:18:31 Andre Poenitz wrote:
This is a general dilemma, but I think HTML is "important enough" to
justify the 'asHtml()' approach.
+1
If we go this way, using the special syntax for html then we should do it as
well for
On Friday 08 May 2009 20:18:31 Andre Poenitz wrote:
> This is a general dilemma, but I think HTML is "important enough" to
> justify the 'asHtml()' approach.
If we go this way, using the special syntax for html then we should do it as
well for plain text, this will simplify a lot of hardwired pla
On Fri, May 08, 2009 at 07:46:12PM +0200, Vincent van Ravesteijn - TNW wrote:
>
> >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 laintext, so
> >that you can output any
>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 laintext, so
>that you can output any document as HTML. So we'd have a set
>of ashtml() routines in the insets, etc, pretty m
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'
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() rout
cmira...@kde-france.org wrote:
rgheck wrote:
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 a
rgheck wrote:
> 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 inset
Pavel Sanda wrote:
Richard Heck wrote:
Kornel Benko wrote:
Am Samstag 02 Mai 2009 schrieb Edwin Leuven:
richard wrote:
Comments, as said, welcome.
why not rather work on XML?
I am also all for it. But I fear, this is not near fu
Richard Heck wrote:
> Kornel Benko wrote:
>> Am Samstag 02 Mai 2009 schrieb Edwin Leuven:
>>
>>> richard wrote:
>>>
Comments, as said, welcome.
>>> why not rather work on XML?
>>>
>>
>> I am also all for it. But I fear, this is not near future. Therefore it is
>> bett
Kornel Benko wrote:
Am Samstag 02 Mai 2009 schrieb Edwin Leuven:
richard wrote:
Comments, as said, welcome.
why not rather work on XML?
I am also all for it. But I fear, this is not near future. Therefore it is
better to create html output, readable by all colleagues not
Am Samstag 02 Mai 2009 schrieb Edwin Leuven:
> richard wrote:
> > Comments, as said, welcome.
>
> why not rather work on XML?
I am also all for it. But I fear, this is not near future. Therefore it is
better to create html output, readable by all colleagues not having lyx :)
> edwin
Kor
richard wrote:
> Comments, as said, welcome.
why not rather work on XML?
edwin
16 matches
Mail list logo
