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
On Thursday 30 April 2009 21:07:11 Richard Heck wrote:
> How much of this do you think could be done using regexes?
When I see this question I always remember the quote:
"Sometimes you have a programming problem and it seems like the best solution
is to use regular expressions; now you have two
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
So I'm going to try to do this. Here's an outline for discussion before
I start. When I start, I don't know. Maybe bits and pieces soon.
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 wo
Alex Fernandez wrote:
Hi Richard,
On Fri, May 1, 2009 at 2:02 PM, rgheck wrote:
Anyway, once exams are over and my life settles down, I'll do some work on
this. If nothing else, I'm thinking it will help me learn more about the
output process and maybe force me to learn something about how
Hi Richard,
On Fri, May 1, 2009 at 2:02 PM, rgheck wrote:
> Anyway, once exams are over and my life settles down, I'll do some work on
> this. If nothing else, I'm thinking it will help me learn more about the
> output process and maybe force me to learn something about how math works.
If the ou
Jean-Marc Lasgouttes wrote:
Le 01/05/2009 02:55, rgheck a écrit :
I am not sure it will help LyX if a layout or module designer had to
think in 3 languages (LyX layout, HTML and LaTeX) instead of currently
two. See docbook as example for the "creeping separation" due to
different user groups (ag
Le 01/05/2009 02:55, rgheck a écrit :
I am not sure it will help LyX if a layout or module designer had to
think in 3 languages (LyX layout, HTML and LaTeX) instead of currently
two. See docbook as example for the "creeping separation" due to
different user groups (again this can serve as argumen
On 01/05/2009 02:55, rgheck wrote:
Sure: Write a new parser in python, and then have it do everything LyX
does to update counters, etc, etc. You could do this, but it's insane.
Why re-write LyX in python?
Exactly my point of view. python is fine and good and maybe easier than
C++, but that do
Guenter Milde wrote:
Figuring out how the bibliography is supposed to be rendered will be
more difficult,
Not more difficult than writing a bibtex style in the first place.
I suppose an approach similar to biblatex will help: divide the
"extract and sort" from the "render and style"
On 2009-04-30, Richard Heck wrote:
>> On Thu, Apr 30, 2009 at 4:13 PM, Richard Heck wrote:
>>> You can easily create a LyX document with some BibTeX. And if you
>>> want to work on this, then you can probably use the python-bibtex
>>> package to parse the files.
Good idea.
Generally, as eLyXer
On Thu, Apr 30, 2009 at 10:27 PM, Richard Heck wrote:
> Here's a simple sample, attached.
Thanks! I will get back to you privately.
> My point was much the same as Pavel's: the existing tools actually do much
> the same sort of job, and just about as well, though perhaps with fewer
> bells and w
Alex Fernandez wrote:
Hi Richard,
On Thu, Apr 30, 2009 at 4:13 PM, Richard Heck wrote:
Hi, Alex. This is going to seem critical, but it is going to end up being
constructive. See below.
Contrary to my expectations it did not get constructive in the end, so
busy people can safely skip
Alex Fernandez wrote:
> On Thu, Apr 30, 2009 at 5:49 PM, Pavel Sanda wrote:
> >> Yes, of course, that's fine, but then it looks to me like something that
> >> doesn't desperately need to be included in LyX.
> >
> > i agree and iirc Alex was satisfied with the detect-only solution.
>
> Sure, I am
José Matos wrote:
On Thursday 30 April 2009 16:26:08 Richard Heck wrote:
Yes, I think that's right. But if we're thinking of HTML as a different
output format, then of course LaTeX-based ERT isn't really relevant, any
more than it would be to DocBook.
I'm trying to think of this more in a wa
On Thursday 30 April 2009 16:26:08 Richard Heck wrote:
> Yes, I think that's right. But if we're thinking of HTML as a different
> output format, then of course LaTeX-based ERT isn't really relevant, any
> more than it would be to DocBook.
>
> I'm trying to think of this more in a way that involves
On Thu, Apr 30, 2009 at 5:49 PM, Pavel Sanda wrote:
>> Yes, of course, that's fine, but then it looks to me like something that
>> doesn't desperately need to be included in LyX.
>
> i agree and iirc Alex was satisfied with the detect-only solution.
Sure, I am quite happy with it. I will also try
Hi Richard,
On Thu, Apr 30, 2009 at 4:13 PM, Richard Heck wrote:
> Hi, Alex. This is going to seem critical, but it is going to end up being
> constructive. See below.
Contrary to my expectations it did not get constructive in the end, so
busy people can safely skip the discussion below.
> This
Richard Heck wrote:
>> this looks like something you can't get completely right. now what i mean
>> 'right' here - right means to get the same version of the document in pdf
>> or
>> html - in the sense of content not appearance...
>> i can't imagine how you would care about various ERTs - imagine
Pavel Sanda wrote:
Richard Heck wrote:
Alex, do you know C++? I'd be happy to help with this, once exams are over.
this looks like something you can't get completely right. now what i mean
'right' here - right means to get the same version of the document in pdf or
html - in the sense
Richard Heck wrote:
> Alex, do you know C++? I'd be happy to help with this, once exams are over.
this looks like something you can't get completely right. now what i mean
'right' here - right means to get the same version of the document in pdf or
html - in the sense of content not appearance...
Hi, Alex. This is going to seem critical, but it is going to end up
being constructive. See below.
What's more problematic, to my mind, is that the framework isn't extensible.
Yes, I know that the programmer can add support for new layout types, etc,
but as things now stand even simple layout
36 matches
Mail list logo
