Nico Williams wrote:
> On Tue, Dec 25, 2012 at 7:50 PM, Pavel Sanda wrote:
> > I think we can support your converter via recognition in configure.py
> > so XML convertor appears in View/Export menus when installed.
> > We can also put it in contrib section on our ftp server, if you would like.
>
On Wed, 2012-12-12 at 15:59 +0100, Jean-Marc Lasgouttes wrote:
> I guess you have first to pick a date :) Organize your conference
> according to the local constraints and then tell us what the
> possibilities are. Then, depedning on how many people really can come,
> you will know whether there
Regarding an inquiry by Richard, I am happy to have any contributions I
make be included in LyX. Thus,
I hereby authorize my contributions to LyX to be licensed under GPL version
2 or later.
Jacob Bishop
On Wed, Dec 26, 2012 at 5:45 AM, Pavel Sanda wrote:
> Nico Williams wrote:
>> I've filed a request for enhancement so that external "plugins" can be
>> found by configure.py.
>
> Sure, I know. What I don't know is whether or when someone will pick it up and
> implement it. Changing configure.py is
Also, not to belabor the point, but one of the things I want to be
able to do is import from XML. LyXHTML, as a presentation format, is
not a very good choice for generating .lyx from.
On Dec 26, 2012 5:46 AM, "Pavel Sanda" wrote:
> The problem is that once we ship it under LyX flag officially we are
> responsible to fix its bug and maintain it in future. That's why so
> much fuss around.
One more thing: with a few simple rules we can make lyx2xml a maintenance
fee script. The
Nico Williams wrote:
> And that (document class affecting details of LyXHTML output) is as it
> should be for a presentation format, but it's a disaster for a
> document format.
Yep, your point is clear, that's why I asked about DocBook -- I'm not
using it but from the few bits I have seen it look
Regarding Docbook... if it can preserve all LyX metadata, including custom
insets and such and not lose much in a round-trip conversion, great, but I
suspect it can't. Really, you need an XML schema that is as closer an
analog of .lyx as possible.
XSLT is not going away. Reproducing its power in
And my script is a Python script. It enables the use of XSLT by producing
XML, but no knowledge of XSLT is needed to support that script. As for
future XML document conversions based on XSLT, I think once you familiarize
yourself with XSLT you'll agree with me that it's much better and easier to
On Wed, Dec 26, 2012 at 2:02 PM, Nico Williams wrote:
> On Dec 26, 2012 5:46 AM, "Pavel Sanda" wrote:
>> The problem is that once we ship it under LyX flag officially we are
>> responsible to fix its bug and maintain it in future. That's why so
>> much fuss around.
>
> One more thing: with a few
Nico Williams wrote:
> future XML document conversions based on XSLT, I think once you familiarize
> yourself with XSLT you'll agree with me that it's much better and easier to
> use XSLT than to write C++ to do the same task.
I no way I wanted to trigger religious war about the best language. My
On Wed, Dec 26, 2012 at 5:54 PM, Pavel Sanda wrote:
> Nico Williams wrote:
>> future XML document conversions based on XSLT, I think once you familiarize
>> yourself with XSLT you'll agree with me that it's much better and easier to
>> use XSLT than to write C++ to do the same task.
>
> I no way I
Nico Williams wrote:
> No, it doesn't. I've tried. I need more metadata than Docbook knows.
> Please either be much more specific about how to make Docbook meet my
> needs or accept my explanations for why it won't do.
Ah, somehow I didn't catch that you already discovered it's impossible
to sp
13 matches
Mail list logo
