> Andre> The ones related to Formats are for output, the 'global' one is
> Andre> for LyX's own drawing.
>
> but for output, if you output \firstname{...}, there is no need for
> fonts...
That's why I dropped that Font part for the LaTeX output in the second
mail IIRC.
Andre'
On Mon, Nov 03, 2003 at 08:42:43PM +0100, Lars Gullik Bjønnes spake thusly:
...
> the question is if we want to base this upon InsetElement.
> I guess yes... but I don't want InsetElement in unless we are going to
> make it also work (not necessarily in the same patch) with other
> output
This patch offers an inset to contain an XML element that is smaller
than a paragraph, typically a word or small phrase. It is used in
docbook and the example document for demonstration. Currently only
firstname, surname, filename and literate, but that's only the start
-- there's lots of those
On Mon, Nov 03, 2003 at 07:29:49PM +0200, Martin Vermeer wrote:
This patch offers an inset to contain an XML element that is smaller
than a paragraph, typically a word or small phrase. It is used in
docbook and the example document for demonstration. Currently only
firstname, surname
Martin Vermeer [EMAIL PROTECTED] writes:
| This patch offers an inset to contain an XML element that is smaller
| than a paragraph, typically a word or small phrase. It is used in
| docbook and the example document for demonstration. Currently only
| firstname, surname, filename and literate
On Mon, Nov 03, 2003 at 06:25:42PM +0100, Lars Gullik Bjønnes wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
| This patch offers an inset to contain an XML element that is smaller
| than a paragraph, typically a word or small phrase. It is used in
| docbook and the example document
Andre Poenitz [EMAIL PROTECTED] writes:
| On Mon, Nov 03, 2003 at 07:29:49PM +0200, Martin Vermeer wrote:
This patch offers an inset to contain an XML element that is smaller
than a paragraph, typically a word or small phrase. It is used in
docbook and the example document for demonstration
Andre Poenitz [EMAIL PROTECTED] writes:
|- three-box-drawing
Do you _really_ need that...
This is just for very short phrases... one two words.
Then with a bit more magic we will have character style support...
emph and noun should both use this.
| But with single-box-drawing UI would
On Mon, Nov 03, 2003 at 06:46:32PM +0100, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
|- three-box-drawing
Do you _really_ need that...
This is just for very short phrases... one two words.
If so, than probably not. But it would hamper its usability for
we'd like to have
This \firstname{Lars Gullik} is my firstname.
And in docbook (xml):
This firstnameLars Gullik/firstname is my firstname.
to work.
First we need something to hold the firstname in LyX. f.ex. an inset.
Could also be done by dynamic font properties.
We also want the user
.
And in docbook (xml):
This firstnameLars Gullik/firstname is my firstname.
to work.
First we need something to hold the firstname in LyX. f.ex. an inset.
Could also be done by dynamic font properties.
We also want the user to be able to set how this firstname should be
rendered, bold
like to have
This \firstname{Lars Gullik} is my firstname.
And in docbook (xml):
This firstnameLars Gullik/firstname is my firstname.
to work.
First we need something to hold the firstname in LyX. f.ex. an inset.
Could also be done by dynamic font properties.
We
Andre Poenitz [EMAIL PROTECTED] writes:
| CharacterStyle FirstName
| Format LaTeX
| Header \firstname{
| Footer }
| Font
| Series xxx
| Sizeyyy
| EndFont
| End
| Format
On Monday 03 November 2003 17:56, Andre Poenitz wrote:
But I still don't get the difference to either InsetEnvironment (bigger
things) or 'Font changes as insets' (smaller things), both of which
do not seem to get much support...
As I understand it we have two reasons:
1) a clear
Andre Poenitz [EMAIL PROTECTED] writes:
| Is is probably better:
| Format LaTeX
| Preamble \newcommand{\firstname}[1]{\emph{\small #1}}
| Header \firstname{
| Footer }
| End
| but you get the idea...
Perhaps better, perhaps not... in the
On Mon, Nov 03, 2003 at 07:29:49PM +0200, Martin Vermeer wrote:
This patch offers an inset to contain an XML element that is smaller
than a paragraph, typically a word or small phrase. It is used in
docbook and the example document for demonstration. Currently only
firstname, surname
On Mon, Nov 03, 2003 at 06:39:01PM +, Jose' Matos wrote:
Yet André does not get too many complains about mathed present navigational
model. :-)
Indeed, he doesn't. That's because typing and typesetting of math as
opposed to text is very different in terms of user experience (logical
On Monday 03 November 2003 18:02, Lars Gullik Bjønnes wrote:
First we need something to hold the firstname in LyX. f.ex. an inset.
Could also be done by dynamic font properties.
We also want the user to be able to set how this firstname should be
rendered, bold, smallcaps, italics, red etc.,
Andre Poenitz wrote:
CharacterStyle FirstName
Format LaTeX
Header \firstname{
Footer }
Font
Series xxx
Sizeyyy
EndFont
End
Is is probably better:
Format LaTeX
Preamble \newcommand{\firstname}[1]{\emph{\small #1}}
Header \firstname{
Footer }
End
but you get the
On Monday 03 November 2003 18:46, John Levon wrote:
Indeed, he doesn't. That's because typing and typesetting of math as
opposed to text is very different in terms of user experience (logical
structure is nearer the surface in the user's model, most formulae are
rather fiddly, the structure
On Monday 03 November 2003 18:52, Angus Leeming wrote:
Is is probably better:
Format LaTeX
Preamble \newcommand{\firstname}[1]{\emph{\small #1}}
Header \firstname{
Footer }
End
but you get the idea...
This is suspiciously like the language used in lib/external_templates.
Jose' Matos wrote:
This is suspiciously like the language used in
lib/external_templates. Is the latter an ExternalStyle? I guess
that it is really.
No, since it is not related with external entities.
Sorry José, I don't understand. external_templates is definitely
concerned with
Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| Is is probably better:
| Format LaTeX
| Preamble \newcommand{\firstname}[1]{\emph{\small #1}}
| Header \firstname{
| Footer }
| End
| but you get the idea...
Perhaps better, perhaps not... in the .layout file
On Mon, Nov 03, 2003 at 06:25:42PM +0100, Lars Gullik Bjønnes spake thusly:
| Comments please.
Please dont' think that this is XML specific.
By just adding a bit more code this might be used for character
styles. (logical markup)
Damn.
Can't I keep anything secret from you
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| Is is probably better:
| Format LaTeX
| Preamble \newcommand{\firstname}[1]{\emph{\small #1}}
| Header \firstname{
| Footer }
| End
| but you get the idea...
Perhaps
On Monday 03 November 2003 19:04, Angus Leeming wrote:
Jose' Matos wrote:
This is suspiciously like the language used in
lib/external_templates. Is the latter an ExternalStyle? I guess
that it is really.
No, since it is not related with external entities.
Sorry José, I don't
On Mon, Nov 03, 2003 at 07:29:55PM +0100, Lars Gullik Bjønnes spake thusly:
Andre Poenitz [EMAIL PROTECTED] writes:
...
This I like.
Mee too (except for some minor detail). Just cannot invest the time
right now, and I want it to work for XML now -- which doesn't need
what you propose here
mathed present navigational
model. :-)
No... actually I would have preferred to use that kind of inset rather
than this collapsable inset. An inline, limited updatable inset,
freely nestable.
Actually as i see it, more important (for XML at least) than providing
layout and user configurability
Martin Vermeer [EMAIL PROTECTED] writes:
| Mee too (except for some minor detail). Just cannot invest the time
| right now, and I want it to work for XML now -- which doesn't need
| what you propose here (which BTW is rather similar to what John dreamt
| up in a previous life).
the question
On Mon, Nov 03, 2003 at 08:42:43PM +0100, Lars Gullik Bjønnes spake thusly:
Martin Vermeer [EMAIL PROTECTED] writes:
| Mee too (except for some minor detail). Just cannot invest the time
| right now, and I want it to work for XML now -- which doesn't need
| what you propose here (which BTW
Lars Gullik Bjønnes wrote:
Perhaps better, perhaps not... in the .layout file this can be used,
but when inserted by the user (in some dialog) I don't want the user
to be required to know what the latex will look like.
Noble goal, I must admit that I resort to the LaTeX Companion far less
Martin Vermeer wrote:
Don't let the perfect be the enemy of the adequate.
Who said The cost of perfection is bankrupty ?
Garst
Jose' Matos wrote:
2) UI where it is assumed that the box inside a box model is too difficult
for the normal user to grasp.
Does LyX have any normal users ?
Garst
Garst R. Reese [EMAIL PROTECTED] writes:
| Martin Vermeer wrote:
|
Don't let the perfect be the enemy of the adequate.
| Who said The cost of perfection is bankrupty ?
Some english businessman: The cost of perfection is prohibitive.
basically the only reference I found.
--
Lgb
On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
It would be fairly easy, surely, to use ERT-style inline always, and add
a conglomerate-style note at the bottom of the inset :
Foo foo foo Stevennn foo foo foo foo
\--First
Martin Vermeer wrote:
On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
It would be fairly easy, surely, to use ERT-style inline always,
and add a conglomerate-style note at the bottom of the inset :
Foo foo foo Stevennn foo foo foo foo
\--First
Martin Vermeer [EMAIL PROTECTED] writes:
| On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
|
It would be fairly easy, surely, to use ERT-style inline always, and add
a conglomerate-style note at the bottom of the inset :
Foo foo foo Stevennn foo foo
On Mon, Nov 03, 2003 at 06:52:32PM +, Jose' Matos wrote:
Ok, but did I got the objections right?
Think so. ...
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
On Tue, Nov 04, 2003 at 12:17:14AM +0200, Martin Vermeer wrote:
Foo foo foo Stevennn foo foo foo foo
\--First name--/
How? Inline yes, but this? And wouldn't the following do
[Element: firstname] Stevennn
With a frame around it,
On Tue, Nov 04, 2003 at 12:21:16AM +0100, Lars Gullik Bjønnes spake thusly:
| On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
a conglomerate-style note at the bottom of the inset :
| [Element: firstname] Stevennn
Isn't that a bit verbose? (space greedy)
This patch offers an inset to contain an XML element that is smaller
than a paragraph, typically a word or small phrase. It is used in
docbook and the example document for demonstration. Currently only
firstname, surname, filename and literate, but that's only the start
-- there's lots of those
On Mon, Nov 03, 2003 at 07:29:49PM +0200, Martin Vermeer wrote:
> This patch offers an inset to contain an XML element that is smaller
> than a paragraph, typically a word or small phrase. It is used in
> docbook and the example document for demonstration. Currently only
> firstn
Martin Vermeer <[EMAIL PROTECTED]> writes:
| This patch offers an inset to contain an XML element that is smaller
| than a paragraph, typically a word or small phrase. It is used in
| docbook and the example document for demonstration. Currently only
| firstname, surname, filename and li
On Mon, Nov 03, 2003 at 06:25:42PM +0100, Lars Gullik Bjønnes wrote:
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> | This patch offers an inset to contain an XML element that is smaller
> | than a paragraph, typically a word or small phrase. It is used in
> | docbook and
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Mon, Nov 03, 2003 at 07:29:49PM +0200, Martin Vermeer wrote:
>> This patch offers an inset to contain an XML element that is smaller
>> than a paragraph, typically a word or small phrase. It is used in
>> docbook
Andre Poenitz <[EMAIL PROTECTED]> writes:
|- three-box-drawing
Do you _really_ need that...
This is just for very short phrases... one two words.
>> Then with a bit more magic we will have character style support...
>> emph and noun should both use this.
>
| But with single-box-drawing UI
On Mon, Nov 03, 2003 at 06:46:32PM +0100, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> |- three-box-drawing
>
> Do you _really_ need that...
> This is just for very short phrases... one two words.
If so, than probably not. But it would hamper its usability for
ngs"), both of which
| do not seem to get much support...
The difference implementation wise might not be huge.
Just to have a short recap on character styles:
in latex we'd like to have
"This \firstname{Lars Gullik} is my firstname."
And in docbook (xml):
"This
Gullik} is my firstname."
>
> And in docbook (xml):
>
> "This Lars Gullik is my firstname."
>
> to work.
>
> First we need something to hold the firstname in LyX. f.ex. an inset.
> Could also be done by dynamic "font properties".
> We also
ecap on character styles:
> >
> > in latex we'd like to have
> >
> >"This \firstname{Lars Gullik} is my firstname."
> >
> > And in docbook (xml):
> >
> > "This Lars Gullik is my firstname."
> >
> > to work.
> >
>
Andre Poenitz <[EMAIL PROTECTED]> writes:
| CharacterStyle FirstName
| Format LaTeX
| Header "\firstname{"
| Footer "}"
| Font
| Series xxx
| Sizeyyy
| EndFont
| End
| Format
On Monday 03 November 2003 17:56, Andre Poenitz wrote:
>
> But I still don't get the difference to either InsetEnvironment ("bigger
> things") or 'Font changes as insets' ("smaller things"), both of which
> do not seem to get much support...
As I understand it we have two reasons:
1) a clear
Andre Poenitz <[EMAIL PROTECTED]> writes:
| Is is probably better:
>
| Format LaTeX
| Preamble "\newcommand{\firstname}[1]{\emph{\small #1}}"
| Header "\firstname{"
| Footer "}"
| End
>
| but you get the idea...
Perhaps better, perhaps not...
On Mon, Nov 03, 2003 at 07:29:49PM +0200, Martin Vermeer wrote:
> This patch offers an inset to contain an XML element that is smaller
> than a paragraph, typically a word or small phrase. It is used in
> docbook and the example document for demonstration. Currently only
> firstn
On Mon, Nov 03, 2003 at 06:39:01PM +, Jose' Matos wrote:
> Yet André does not get too many complains about mathed present navigational
> model. :-)
Indeed, he doesn't. That's because typing and typesetting of math as
opposed to text is very different in terms of user experience (logical
On Monday 03 November 2003 18:02, Lars Gullik Bjønnes wrote:
>
> First we need something to hold the firstname in LyX. f.ex. an inset.
> Could also be done by dynamic "font properties".
>
> We also want the user to be able to set how this firstname should be
> rendered, bold, smallcaps, italics,
Andre Poenitz wrote:
>> CharacterStyle FirstName
>> Format LaTeX
>> Header "\firstname{"
>> Footer "}"
>> Font
>> Series xxx
>> Sizeyyy
>> EndFont
>> End
>
> Is is probably better:
>
> Format LaTeX
> Preamble "\newcommand{\firstname}[1]{\emph{\small #1}}"
> Header "\firstname{"
> Footer
On Monday 03 November 2003 18:46, John Levon wrote:
>
> Indeed, he doesn't. That's because typing and typesetting of math as
> opposed to text is very different in terms of user experience (logical
> structure is "nearer the surface" in the user's model, most formulae are
> rather fiddly, the
On Monday 03 November 2003 18:52, Angus Leeming wrote:
> > Is is probably better:
> >
> > Format LaTeX
> > Preamble "\newcommand{\firstname}[1]{\emph{\small #1}}"
> > Header "\firstname{"
> > Footer "}"
> > End
> >
> > but you get the idea...
>
> This is suspiciously like the language used in
Jose' Matos wrote:
>> This is suspiciously like the language used in
>> lib/external_templates. Is the latter an ExternalStyle? I guess
>> that it is really.
>
> No, since it is not related with external entities.
Sorry José, I don't understand. external_templates is definitely
concerned
Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | Is is probably better:
>>
> | Format LaTeX
> | Preamble "\newcommand{\firstname}[1]{\emph{\small #1}}"
> | Header "\firstname{"
> | Footer "}"
> | End
>>
> | but you get the idea...
>
> Perhaps better, perhaps
On Mon, Nov 03, 2003 at 06:25:42PM +0100, Lars Gullik Bjønnes spake thusly:
>
> | Comments please.
>
> Please dont' think that this is XML specific.
>
> By just adding a bit more code this might be used for character
> styles. (logical markup)
Damn.
Can't I keep any
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> Andre Poenitz <[EMAIL PROTECTED]> writes:
>>
>> | Is is probably better:
>>>
>> | Format LaTeX
>> | Preamble "\newcommand{\firstname}[1]{\emph{\small #1}}"
>> | Header "\firstname{"
>> | Footer "}"
>> | End
>>>
>> |
On Monday 03 November 2003 19:04, Angus Leeming wrote:
> Jose' Matos wrote:
> >> This is suspiciously like the language used in
> >> lib/external_templates. Is the latter an ExternalStyle? I guess
> >> that it is really.
> >
> > No, since it is not related with external entities.
>
> Sorry José,
On Mon, Nov 03, 2003 at 07:29:55PM +0100, Lars Gullik Bjønnes spake thusly:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
...
> This I like.
Mee too (except for some minor detail). Just cannot invest the time
right now, and I want it to work for XML now -- which doesn't need
what
ny complains about mathed present navigational
> model. :-)
No... actually I would have preferred to use that kind of inset rather
than this collapsable inset. An inline, limited updatable inset,
freely nestable.
Actually as i see it, more important (for XML at least) than providing
layout and
Martin Vermeer <[EMAIL PROTECTED]> writes:
| Mee too (except for some minor detail). Just cannot invest the time
| right now, and I want it to work for XML now -- which doesn't need
| what you propose here (which BTW is rather similar to what John dreamt
| up in a previous life).
the qu
On Mon, Nov 03, 2003 at 08:42:43PM +0100, Lars Gullik Bjønnes spake thusly:
>
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> | Mee too (except for some minor detail). Just cannot invest the time
> | right now, and I want it to work for XML now -- which doesn't need
>
Lars Gullik Bjønnes wrote:
>
> Perhaps better, perhaps not... in the .layout file this can be used,
> but when inserted by the user (in some dialog) I don't want the user
> to be required to know what the latex will look like.
Noble goal, I must admit that I resort to the LaTeX Companion far
Martin Vermeer wrote:
> Don't let the perfect be the enemy of the adequate.
Who said "The cost of perfection is bankrupty" ?
Garst
Jose' Matos wrote:
> 2) UI where it is assumed that the box inside a box model is too difficult
> for the normal user to grasp.
>
Does LyX have any "normal" users ?
Garst
"Garst R. Reese" <[EMAIL PROTECTED]> writes:
| Martin Vermeer wrote:
|
>> Don't let the perfect be the enemy of the adequate.
| Who said "The cost of perfection is bankrupty" ?
Some english businessman: "The cost of perfection is prohibitive."
basically the only reference I found.
--
On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
> It would be fairly easy, surely, to use ERT-style inline always, and add
> a conglomerate-style note at the bottom of the inset :
>
> Foo foo foo Stevennn foo foo foo foo
> \--First
Martin Vermeer wrote:
> On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
>
>> It would be fairly easy, surely, to use ERT-style inline always,
>> and add a conglomerate-style note at the bottom of the inset :
>>
>> Foo foo foo Stevennn foo foo foo foo
>>
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
|
>> It would be fairly easy, surely, to use ERT-style inline always, and add
>> a conglomerate-style note at the bottom of the inset :
>>
>> Foo foo foo
On Mon, Nov 03, 2003 at 06:52:32PM +, Jose' Matos wrote:
> Ok, but did I got the objections right?
Think so. ...
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
On Tue, Nov 04, 2003 at 12:17:14AM +0200, Martin Vermeer wrote:
> > Foo foo foo Stevennn foo foo foo foo
> > \--First name--/
>
> How? Inline yes, but this? And wouldn't the following do
>
> [Element: firstname] Stevennn
With a frame
On Tue, Nov 04, 2003 at 12:21:16AM +0100, Lars Gullik Bjønnes spake thusly:
>
> | On Mon, Nov 03, 2003 at 06:43:59PM +, John Levon spake thusly:
> >> a conglomerate-style note at the bottom of the inset :
> | [Element: firstname] Stevennn
>
> Isn't that a bit verbose? (space
On Tue, Aug 05, 2003 at 08:51:08AM +0200, Asger Kunuk Alstrup wrote:
No. As a file format, the exchange of documents to other systems is
important, and here XML has an advantage. Also, since the basic LyX
data structure is a tree, a format designed for tree structures makes
much sense. Also
On Tue, Aug 05, 2003 at 08:51:08AM +0200, Asger Kunuk Alstrup wrote:
> No. As a file format, the exchange of documents to other systems is
> important, and here XML has an advantage. Also, since the basic LyX
> data structure is a tree, a format designed for tree structures makes
>
On Tue, 5 Aug 2003, John Levon wrote:
I take it you're against moving to an XML format for the file format
then.
No. As a file format, the exchange of documents to other systems is
important, and here XML has an advantage. Also, since the basic LyX
data structure is a tree, a format designed
On Tue, 5 Aug 2003, John Levon wrote:
> I take it you're against moving to an XML format for the file format
> then.
No. As a file format, the exchange of documents to other systems is
important, and here XML has an advantage. Also, since the basic LyX
data structure is a tree, a format de
.
This will do just fine:
lastExternalTemplate = xfig
Given that there seems to be a push to use xml for the lyx file format, it
seems reasonable to not invent yet another language where xml will fit the
bill. However, my knowledge of xml is very limited and I don't want to
reinvent the wheel here.
XML
Asger Kunuk Alstrup wrote:
Oh, I beg you, don't go down that road.
Capisco!
--
Angus
On Mon, Aug 04, 2003 at 10:40:16PM +0200, Asger Kunuk Alstrup wrote:
I have worked with XML for three years professionally now, and am
continuously monitoring the technology to do this. Most of my experience
comes from the Xerces brand of parsers, because those are ironically the
most mature
you, don't go down that road.
This will do just fine:
lastExternalTemplate = "xfig"
> Given that there seems to be a push to use xml for the lyx file format, it
> seems reasonable to not invent yet another language where xml will fit the
> bill. However, my knowledge of xm
Asger Kunuk Alstrup wrote:
> Oh, I beg you, don't go down that road.
Capisco!
--
Angus
On Mon, Aug 04, 2003 at 10:40:16PM +0200, Asger Kunuk Alstrup wrote:
> I have worked with XML for three years professionally now, and am
> continuously monitoring the technology to do this. Most of my experience
> comes from the Xerces brand of parsers, because those are ironically t
Does boost contain a simple XML parser?
Or is 'expat' state of the art?
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Andre Poenitz [EMAIL PROTECTED] writes:
| Does boost contain a simple XML parser?
No. Unless it is part of the spirit examples.
--
Lgb
Does boost contain a simple XML parser?
Or is 'expat' state of the art?
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Andre Poenitz <[EMAIL PROTECTED]> writes:
| Does boost contain a simple XML parser?
No. Unless it is part of the spirit examples.
--
Lgb
On Sat, Oct 12, 2002 at 11:03:35PM +0200, Torsten Bronger wrote:
Can anybody give ma a concise status of this plan?
The plan is still there.
Parts of the file format (tables) are already
moved to a XML-like format.
Andre'
--
Those who desire to give up Freedom in order to gain Security
On Mon, Oct 14, 2002 at 10:41:48AM +0200, Andre Poenitz wrote:
Parts of the file format (tables) are already
moved to a XML-like format.
Since we may as well have a flamewar, has anybody considered using XSLT
for our output forms, when we have an XML .lyx file ? This would remove
huge amounts
On Mon, Oct 14, 2002 at 01:11:55PM +0100, John Levon wrote:
Parts of the file format (tables) are already
moved to a XML-like format.
Since we may as well have a flamewar, has anybody considered using XSLT
for our output forms, when we have an XML .lyx file ? This would remove
huge
On Monday 14 October 2002 13:11, John Levon wrote:
Since we may as well have a flamewar, has anybody considered using XSLT
for our output forms, when we have an XML .lyx file ? This would remove
huge amounts of gook from all the inset files etc.
That would replace all the latex, linuxdoc
On Mon, Oct 14, 2002 at 01:59:12PM +0100, José Abílio Oliveira Matos wrote:
That would replace all the latex, linuxdoc, docbook and ascii output
methods. Or am I wrong?
Right.
I bring this since one the possible enhancements that we have discussed this
year at Porto was the visitor
On Mon, Oct 14, 2002 at 01:59:12PM +0100, José Abílio Oliveira Matos wrote:
That would replace all the latex, linuxdoc, docbook and ascii output
methods. Or am I wrong?
We would have one 'xml' (or 'write') method instead. So in an ideal world: yes.
I bring this since one the possible
On Mon, Oct 14, 2002 at 01:56:02PM +0100, John Levon wrote:
That'd certainly be a massive improvement on the current ugliness, but
it still has the problems of C++ output, like inflexibity and
awkwardness (not to mention lots of extra code).
The visitor pattern does not solve any problem, it
John Levon [EMAIL PROTECTED] writes:
| On Mon, Oct 14, 2002 at 10:41:48AM +0200, Andre Poenitz wrote:
Parts of the file format (tables) are already
moved to a XML-like format.
| Since we may as well have a flamewar, has anybody considered using XSLT
| for our output forms, when we have
801 - 900 of 1040 matches
Mail list logo
