Project's favorite license????

2013-07-05 Thread Steve Litt
Hi all,

I'm about half way through a program to convert the output of LyX's
HTML (not XHTML) export to a form will work right as an ePub, as well
as collecting table of contents info to make it easy to create your
toc.ncx. I've written it in Python because I understand that's the
project's favorite non-C++ language. Once I'm done with this, I'll do
the same thing with the LyX's XHTML export.

Obviously I need to put a license on it. I never use GPL3 or that one
license that includes an indemnification, but I'm pretty open to all
other licenses, including GPL2 without the clause or later.

So,  what's the project's favorite license? 

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


Re: Project's favorite license????

2013-07-05 Thread Richard Heck

On 07/05/2013 08:04 AM, Steve Litt wrote:

Hi all,

I'm about half way through a program to convert the output of LyX's
HTML (not XHTML)


I assume you are talking about export to HTML format. Just FYI, that
is not part of LyX. LyX uses various external programs, such as tex4ht
and eLyXer, to do that export. Neither of these is connected to LyX or
part of LyX, any more than LaTeX is.


export to a form will work right as an ePub, as well
as collecting table of contents info to make it easy to create your
toc.ncx. I've written it in Python because I understand that's the
project's favorite non-C++ language. Once I'm done with this, I'll do
the same thing with the LyX's XHTML export.


For what it's worth, my own view is that this is the wrong approach.
What exactly LyX exports when it exports XHTML can change, and does
change, as it is improved, and I would suppose the same is true of other
tools. The right approach would be to improve the XHTML export itself
(which is part of LyX). But of course you can do as you wish.


Obviously I need to put a license on it. I never use GPL3 or that one
license that includes an indemnification, but I'm pretty open to all
other licenses, including GPL2 without the clause or later.


Since your project is presumably not part of LyX, it doesn't really matter
to us what license you use.

Richard



Re: Lyx2doc: was Anyone know of a best-seller written in LyX

2013-07-05 Thread Richard Heck

On 06/11/2013 03:25 PM, Steve Litt wrote:

On Tue, 11 Jun 2013 14:38:23 -0400
Richard Heck rgh...@lyx.org wrote:


On 06/11/2013 02:03 PM, Steve Litt wrote:

On Tue, 11 Jun 2013 10:32:12 -0400
Richard Heck rgh...@lyx.org wrote:


On 06/10/2013 06:05 PM, Steve Litt wrote:

These days, it could be used as a front end to anything with the
proper styles defined, and the proper converter. So the same LyX
file could be used to output LaTeX, MSWord doc, XHTML, HTML,
simple HTML, or who knows what else.

To more easily accommodate this, it seems to me like layout files
should be split into an input side and an output side, with the
output side capable of multiple output formats. So the input side
might look something like this:

CharStyle MyEmph
Font
Shape Italic
EndFont

if outputtype == latex
  outputNamelatexlayout.layout/myemphL
  outputTypeCommand
elsif outputtype == simplehtml
  outputNamesimphtmllayout.layout/myemphH
  outputTypeInlineTag
else outputtype == msword
  outputNamewinwordlayout.layout/myemphW
  outputTypeCharacterStyle
End

Environments would be similar.

Ideally it would be designed so that it doesn't syntax check
inside the output type's it's not. That way you can develop one
output type at a time without getting errors from the ones you
haven't developed yet.

This can already be done, more or less. That is, I can't imagine
anything you'd want to do, as far as XHTML export goes, that isn't
provided for in the layout files.

Indeed, I am sufficiently confident about this that I'd be
surprised if it were not possible to build the sort of simple HTML
export you want simply by writing a new layout file.

Thanks Richard,

When I tried to do this with my layout file, it failed miserably.
Try as I might, I couldn't get Standard to map to p, nor could I
get Section to map to h1, etc.

If you want to send me your layout file, I will get it working.

Richard

Thanks Richard,

I'm sending you an entire tarballed directory tree with a minimal
example. As you'll see, LyxHTML convert respects my HTMLtag configs in
my layout file, except for mapping of Section and Subsection to h1
and h2 respectively, instead it maps to h1 and h3 respectively.


This is because you mis-spelled the layout name: It should be
Subsection, not SubSection. Same for Subsubsection and for
Subparagraph. These have to match what is in stdclass.inc, which
you are including, and which in turn includes stdsections.inc.

If you look on the paragraph style drop down, you will see that you
are getting new styles instead of modifying the old ones.


Convert to HTML does not respect my layout file's HTMLTag configs at
all.


That is because eLyXer does not know anything about layout files.
(It also does not know what LyX knows about translation.) As I said
in a separate message, this is in large part because it is not part of
LyX.

Richard



Re: Project's favorite license????

2013-07-05 Thread Steve Litt
On Fri, 05 Jul 2013 10:18:52 -0400
Richard Heck rgh...@lyx.org wrote:

 On 07/05/2013 08:04 AM, Steve Litt wrote:

  export to a form will work right as an ePub, as well
  as collecting table of contents info to make it easy to create your
  toc.ncx. I've written it in Python because I understand that's the
  project's favorite non-C++ language. Once I'm done with this, I'll
  do the same thing with the LyX's XHTML export.
 
 For what it's worth, my own view is that this is the wrong approach.
 What exactly LyX exports when it exports XHTML can change, and does
 change, as it is improved, and I would suppose the same is true of
 other tools. The right approach would be to improve the XHTML export
 itself (which is part of LyX).

You very well could be right Richard. It would certainly be better
for ePub authors to choose Export-ePub than choose Export-HTML and
then outside LyX run my program.

The reason I'm doing it the way I'm doing it so there will be a
solution in a few days, without my needing to learn the internals of
tex4ht and eLyXer, or the project's need to incorporate it. If my code
is good, and my code is licensed right, it very well could be that I or
someone else can tear chunks out of my code and put them in LyX or
eLyXer or make a shellscript or whatever.

I just looked up the licenses of LyX and eLyXer. LyX is GPL 2 or
greater at the user's option, which is probably compatible with the
GPL2 and only GPL2 I would use. eLyXer is GPL3 or greater, so I don't
think my code could be incorporated. Perhaps I could license it user's
choice of GPL2 or GPL3 (without the and later, without knowing in
advance what that later would agree to). I'll check with some of my
buddies.

Worst case I'll write a doc how to use my stuff on eLyXer produced
stuff to produce the HTML part of an ePub plus the ePub's toc.ncx.

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


Re: Why no docbook export on LyX 2.03?

2013-07-05 Thread Wolfgang Keller
 No, I'm using a derivative of the LaTeX Book style. Shouldn't I be
 able to export to docbook anyway?

Of course not, since the document structure(s) won't match.

To be able to export to docbook, you need to use a LaTeX document class
that matches the docbook structure.

And even then, LyX afaik does not enforce a schema like XML/SGML
editors do, so you can still end up accidentally creating a document
that wouldn't validate/convert.

Sincerely,

Wolfgang


Re: Project's favorite license????

2013-07-05 Thread Liviu Andronic
On Fri, Jul 5, 2013 at 6:50 PM, Steve Litt sl...@troubleshooters.com wrote:
 tex4ht and eLyXer, or the project's need to incorporate it. If my code
 is good, and my code is licensed right, it very well could be that I or
 someone else can tear chunks out of my code and put them in LyX or
 eLyXer or make a shellscript or whatever.

I can easily imagine Alex, the author of eLyXer, accepting an ePub
export switch in his converter.

My 2 cents,
Liviu


Re: Project's favorite license????

2013-07-05 Thread Alex Fernandez
Hi,

On Fri, Jul 5, 2013 at 9:58 PM, Liviu Andronic landronim...@gmail.comwrote:

 On Fri, Jul 5, 2013 at 6:50 PM, Steve Litt sl...@troubleshooters.com
 wrote:
  tex4ht and eLyXer, or the project's need to incorporate it. If my code
  is good, and my code is licensed right, it very well could be that I or
  someone else can tear chunks out of my code and put them in LyX or
  eLyXer or make a shellscript or whatever.
 
 I can easily imagine Alex, the author of eLyXer, accepting an ePub
 export switch in his converter.


I would be happy to. Just fork and send a pull request when you are ready
to:
  https://github.com/alexfernandez/elyxer/
That is how things work these days, and I cannot complain. Sadly I don't
have the time to do most things myself, but I have already received some
juicy pull requests and have integrated them happily.

As for the license, we can work things out to our mutual benefit. Open
source licenses are a means to an end.

Alex.


Project's favorite license????

2013-07-05 Thread Steve Litt
Hi all,

I'm about half way through a program to convert the output of LyX's
HTML (not XHTML) export to a form will work right as an ePub, as well
as collecting table of contents info to make it easy to create your
toc.ncx. I've written it in Python because I understand that's the
project's favorite non-C++ language. Once I'm done with this, I'll do
the same thing with the LyX's XHTML export.

Obviously I need to put a license on it. I never use GPL3 or that one
license that includes an indemnification, but I'm pretty open to all
other licenses, including GPL2 without the clause or later.

So,  what's the project's favorite license? 

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


Re: Project's favorite license????

2013-07-05 Thread Richard Heck

On 07/05/2013 08:04 AM, Steve Litt wrote:

Hi all,

I'm about half way through a program to convert the output of LyX's
HTML (not XHTML)


I assume you are talking about export to HTML format. Just FYI, that
is not part of LyX. LyX uses various external programs, such as tex4ht
and eLyXer, to do that export. Neither of these is connected to LyX or
part of LyX, any more than LaTeX is.


export to a form will work right as an ePub, as well
as collecting table of contents info to make it easy to create your
toc.ncx. I've written it in Python because I understand that's the
project's favorite non-C++ language. Once I'm done with this, I'll do
the same thing with the LyX's XHTML export.


For what it's worth, my own view is that this is the wrong approach.
What exactly LyX exports when it exports XHTML can change, and does
change, as it is improved, and I would suppose the same is true of other
tools. The right approach would be to improve the XHTML export itself
(which is part of LyX). But of course you can do as you wish.


Obviously I need to put a license on it. I never use GPL3 or that one
license that includes an indemnification, but I'm pretty open to all
other licenses, including GPL2 without the clause or later.


Since your project is presumably not part of LyX, it doesn't really matter
to us what license you use.

Richard



Re: Lyx2doc: was Anyone know of a best-seller written in LyX

2013-07-05 Thread Richard Heck

On 06/11/2013 03:25 PM, Steve Litt wrote:

On Tue, 11 Jun 2013 14:38:23 -0400
Richard Heck rgh...@lyx.org wrote:


On 06/11/2013 02:03 PM, Steve Litt wrote:

On Tue, 11 Jun 2013 10:32:12 -0400
Richard Heck rgh...@lyx.org wrote:


On 06/10/2013 06:05 PM, Steve Litt wrote:

These days, it could be used as a front end to anything with the
proper styles defined, and the proper converter. So the same LyX
file could be used to output LaTeX, MSWord doc, XHTML, HTML,
simple HTML, or who knows what else.

To more easily accommodate this, it seems to me like layout files
should be split into an input side and an output side, with the
output side capable of multiple output formats. So the input side
might look something like this:

CharStyle MyEmph
Font
Shape Italic
EndFont

if outputtype == latex
  outputNamelatexlayout.layout/myemphL
  outputTypeCommand
elsif outputtype == simplehtml
  outputNamesimphtmllayout.layout/myemphH
  outputTypeInlineTag
else outputtype == msword
  outputNamewinwordlayout.layout/myemphW
  outputTypeCharacterStyle
End

Environments would be similar.

Ideally it would be designed so that it doesn't syntax check
inside the output type's it's not. That way you can develop one
output type at a time without getting errors from the ones you
haven't developed yet.

This can already be done, more or less. That is, I can't imagine
anything you'd want to do, as far as XHTML export goes, that isn't
provided for in the layout files.

Indeed, I am sufficiently confident about this that I'd be
surprised if it were not possible to build the sort of simple HTML
export you want simply by writing a new layout file.

Thanks Richard,

When I tried to do this with my layout file, it failed miserably.
Try as I might, I couldn't get Standard to map to p, nor could I
get Section to map to h1, etc.

If you want to send me your layout file, I will get it working.

Richard

Thanks Richard,

I'm sending you an entire tarballed directory tree with a minimal
example. As you'll see, LyxHTML convert respects my HTMLtag configs in
my layout file, except for mapping of Section and Subsection to h1
and h2 respectively, instead it maps to h1 and h3 respectively.


This is because you mis-spelled the layout name: It should be
Subsection, not SubSection. Same for Subsubsection and for
Subparagraph. These have to match what is in stdclass.inc, which
you are including, and which in turn includes stdsections.inc.

If you look on the paragraph style drop down, you will see that you
are getting new styles instead of modifying the old ones.


Convert to HTML does not respect my layout file's HTMLTag configs at
all.


That is because eLyXer does not know anything about layout files.
(It also does not know what LyX knows about translation.) As I said
in a separate message, this is in large part because it is not part of
LyX.

Richard



Re: Project's favorite license????

2013-07-05 Thread Steve Litt
On Fri, 05 Jul 2013 10:18:52 -0400
Richard Heck rgh...@lyx.org wrote:

 On 07/05/2013 08:04 AM, Steve Litt wrote:

  export to a form will work right as an ePub, as well
  as collecting table of contents info to make it easy to create your
  toc.ncx. I've written it in Python because I understand that's the
  project's favorite non-C++ language. Once I'm done with this, I'll
  do the same thing with the LyX's XHTML export.
 
 For what it's worth, my own view is that this is the wrong approach.
 What exactly LyX exports when it exports XHTML can change, and does
 change, as it is improved, and I would suppose the same is true of
 other tools. The right approach would be to improve the XHTML export
 itself (which is part of LyX).

You very well could be right Richard. It would certainly be better
for ePub authors to choose Export-ePub than choose Export-HTML and
then outside LyX run my program.

The reason I'm doing it the way I'm doing it so there will be a
solution in a few days, without my needing to learn the internals of
tex4ht and eLyXer, or the project's need to incorporate it. If my code
is good, and my code is licensed right, it very well could be that I or
someone else can tear chunks out of my code and put them in LyX or
eLyXer or make a shellscript or whatever.

I just looked up the licenses of LyX and eLyXer. LyX is GPL 2 or
greater at the user's option, which is probably compatible with the
GPL2 and only GPL2 I would use. eLyXer is GPL3 or greater, so I don't
think my code could be incorporated. Perhaps I could license it user's
choice of GPL2 or GPL3 (without the and later, without knowing in
advance what that later would agree to). I'll check with some of my
buddies.

Worst case I'll write a doc how to use my stuff on eLyXer produced
stuff to produce the HTML part of an ePub plus the ePub's toc.ncx.

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


Re: Why no docbook export on LyX 2.03?

2013-07-05 Thread Wolfgang Keller
 No, I'm using a derivative of the LaTeX Book style. Shouldn't I be
 able to export to docbook anyway?

Of course not, since the document structure(s) won't match.

To be able to export to docbook, you need to use a LaTeX document class
that matches the docbook structure.

And even then, LyX afaik does not enforce a schema like XML/SGML
editors do, so you can still end up accidentally creating a document
that wouldn't validate/convert.

Sincerely,

Wolfgang


Re: Project's favorite license????

2013-07-05 Thread Liviu Andronic
On Fri, Jul 5, 2013 at 6:50 PM, Steve Litt sl...@troubleshooters.com wrote:
 tex4ht and eLyXer, or the project's need to incorporate it. If my code
 is good, and my code is licensed right, it very well could be that I or
 someone else can tear chunks out of my code and put them in LyX or
 eLyXer or make a shellscript or whatever.

I can easily imagine Alex, the author of eLyXer, accepting an ePub
export switch in his converter.

My 2 cents,
Liviu


Re: Project's favorite license????

2013-07-05 Thread Alex Fernandez
Hi,

On Fri, Jul 5, 2013 at 9:58 PM, Liviu Andronic landronim...@gmail.comwrote:

 On Fri, Jul 5, 2013 at 6:50 PM, Steve Litt sl...@troubleshooters.com
 wrote:
  tex4ht and eLyXer, or the project's need to incorporate it. If my code
  is good, and my code is licensed right, it very well could be that I or
  someone else can tear chunks out of my code and put them in LyX or
  eLyXer or make a shellscript or whatever.
 
 I can easily imagine Alex, the author of eLyXer, accepting an ePub
 export switch in his converter.


I would be happy to. Just fork and send a pull request when you are ready
to:
  https://github.com/alexfernandez/elyxer/
That is how things work these days, and I cannot complain. Sadly I don't
have the time to do most things myself, but I have already received some
juicy pull requests and have integrated them happily.

As for the license, we can work things out to our mutual benefit. Open
source licenses are a means to an end.

Alex.


Project's favorite license????

2013-07-05 Thread Steve Litt
Hi all,

I'm about half way through a program to convert the output of LyX's
HTML (not XHTML) export to a form will work right as an ePub, as well
as collecting table of contents info to make it easy to create your
toc.ncx. I've written it in Python because I understand that's the
project's favorite non-C++ language. Once I'm done with this, I'll do
the same thing with the LyX's XHTML export.

Obviously I need to put a license on it. I never use GPL3 or that one
license that includes an indemnification, but I'm pretty open to all
other licenses, including GPL2 without the clause "or later".

So,  what's the project's favorite license? 

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


Re: Project's favorite license????

2013-07-05 Thread Richard Heck

On 07/05/2013 08:04 AM, Steve Litt wrote:

Hi all,

I'm about half way through a program to convert the output of LyX's
HTML (not XHTML)


I assume you are talking about export to HTML format. Just FYI, that
is not part of LyX. LyX uses various external programs, such as tex4ht
and eLyXer, to do that export. Neither of these is connected to LyX or
part of LyX, any more than LaTeX is.


export to a form will work right as an ePub, as well
as collecting table of contents info to make it easy to create your
toc.ncx. I've written it in Python because I understand that's the
project's favorite non-C++ language. Once I'm done with this, I'll do
the same thing with the LyX's XHTML export.


For what it's worth, my own view is that this is the wrong approach.
What exactly LyX exports when it exports XHTML can change, and does
change, as it is improved, and I would suppose the same is true of other
tools. The right approach would be to improve the XHTML export itself
(which is part of LyX). But of course you can do as you wish.


Obviously I need to put a license on it. I never use GPL3 or that one
license that includes an indemnification, but I'm pretty open to all
other licenses, including GPL2 without the clause "or later".


Since your project is presumably not part of LyX, it doesn't really matter
to us what license you use.

Richard



Re: Lyx2doc: was Anyone know of a best-seller written in LyX

2013-07-05 Thread Richard Heck

On 06/11/2013 03:25 PM, Steve Litt wrote:

On Tue, 11 Jun 2013 14:38:23 -0400
Richard Heck  wrote:


On 06/11/2013 02:03 PM, Steve Litt wrote:

On Tue, 11 Jun 2013 10:32:12 -0400
Richard Heck  wrote:


On 06/10/2013 06:05 PM, Steve Litt wrote:

These days, it could be used as a front end to anything with the
proper styles defined, and the proper converter. So the same LyX
file could be used to output LaTeX, MSWord doc, XHTML, HTML,
simple HTML, or who knows what else.

To more easily accommodate this, it seems to me like layout files
should be split into an input side and an output side, with the
output side capable of multiple output formats. So the input side
might look something like this:

CharStyle MyEmph
Font
Shape Italic
EndFont

if outputtype == latex
  outputNamelatexlayout.layout/myemphL
  outputTypeCommand
elsif outputtype == simplehtml
  outputNamesimphtmllayout.layout/myemphH
  outputTypeInlineTag
else outputtype == msword
  outputNamewinwordlayout.layout/myemphW
  outputTypeCharacterStyle
End

Environments would be similar.

Ideally it would be designed so that it doesn't syntax check
inside the output type's it's not. That way you can develop one
output type at a time without getting errors from the ones you
haven't developed yet.

This can already be done, more or less. That is, I can't imagine
anything you'd want to do, as far as XHTML export goes, that isn't
provided for in the layout files.

Indeed, I am sufficiently confident about this that I'd be
surprised if it were not possible to build the sort of simple HTML
export you want simply by writing a new layout file.

Thanks Richard,

When I tried to do this with my layout file, it failed miserably.
Try as I might, I couldn't get Standard to map to , nor could I
get Section to map to , etc.

If you want to send me your layout file, I will get it working.

Richard

Thanks Richard,

I'm sending you an entire tarballed directory tree with a minimal
example. As you'll see, LyxHTML convert respects my HTMLtag configs in
my layout file, except for mapping of Section and Subsection to 
and  respectively, instead it maps to  and  respectively.


This is because you mis-spelled the layout name: It should be
"Subsection", not "SubSection". Same for "Subsubsection" and for
"Subparagraph". These have to match what is in stdclass.inc, which
you are including, and which in turn includes stdsections.inc.

If you look on the paragraph style drop down, you will see that you
are getting new styles instead of modifying the old ones.


Convert to HTML does not respect my layout file's HTMLTag configs at
all.


That is because eLyXer does not know anything about layout files.
(It also does not know what LyX knows about translation.) As I said
in a separate message, this is in large part because it is not part of
LyX.

Richard



Re: Project's favorite license????

2013-07-05 Thread Steve Litt
On Fri, 05 Jul 2013 10:18:52 -0400
Richard Heck  wrote:

> On 07/05/2013 08:04 AM, Steve Litt wrote:

> > export to a form will work right as an ePub, as well
> > as collecting table of contents info to make it easy to create your
> > toc.ncx. I've written it in Python because I understand that's the
> > project's favorite non-C++ language. Once I'm done with this, I'll
> > do the same thing with the LyX's XHTML export.
> 
> For what it's worth, my own view is that this is the wrong approach.
> What exactly LyX exports when it exports XHTML can change, and does
> change, as it is improved, and I would suppose the same is true of
> other tools. The right approach would be to improve the XHTML export
> itself (which is part of LyX).

You very well could be right Richard. It would certainly be better
for ePub authors to choose Export->ePub than choose Export->HTML and
then outside LyX run my program.

The reason I'm doing it the way I'm doing it so there will be a
solution in a few days, without my needing to learn the internals of
tex4ht and eLyXer, or the project's need to incorporate it. If my code
is good, and my code is licensed right, it very well could be that I or
someone else can tear chunks out of my code and put them in LyX or
eLyXer or make a shellscript or whatever.

I just looked up the licenses of LyX and eLyXer. LyX is GPL 2 or
greater at the user's option, which is probably compatible with the
GPL2 and only GPL2 I would use. eLyXer is GPL3 or greater, so I don't
think my code could be incorporated. Perhaps I could license it user's
choice of GPL2 or GPL3 (without the "and later", without knowing in
advance what that "later" would agree to). I'll check with some of my
buddies.

Worst case I'll write a doc how to use my stuff on eLyXer produced
stuff to produce the HTML part of an ePub plus the ePub's toc.ncx.

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


Re: Why no docbook export on LyX 2.03?

2013-07-05 Thread Wolfgang Keller
> No, I'm using a derivative of the LaTeX Book style. Shouldn't I be
> able to export to docbook anyway?

Of course not, since the document structure(s) won't match.

To be able to export to docbook, you need to use a LaTeX document class
that matches the docbook structure.

And even then, LyX afaik does not enforce a "schema" like XML/SGML
editors do, so you can still end up accidentally creating a document
that wouldn't validate/convert.

Sincerely,

Wolfgang


Re: Project's favorite license????

2013-07-05 Thread Liviu Andronic
On Fri, Jul 5, 2013 at 6:50 PM, Steve Litt  wrote:
> tex4ht and eLyXer, or the project's need to incorporate it. If my code
> is good, and my code is licensed right, it very well could be that I or
> someone else can tear chunks out of my code and put them in LyX or
> eLyXer or make a shellscript or whatever.
>
I can easily imagine Alex, the author of eLyXer, accepting an ePub
export switch in his converter.

My 2 cents,
Liviu


Re: Project's favorite license????

2013-07-05 Thread Alex Fernandez
Hi,

On Fri, Jul 5, 2013 at 9:58 PM, Liviu Andronic wrote:

> On Fri, Jul 5, 2013 at 6:50 PM, Steve Litt 
> wrote:
> > tex4ht and eLyXer, or the project's need to incorporate it. If my code
> > is good, and my code is licensed right, it very well could be that I or
> > someone else can tear chunks out of my code and put them in LyX or
> > eLyXer or make a shellscript or whatever.
> >
> I can easily imagine Alex, the author of eLyXer, accepting an ePub
> export switch in his converter.
>

I would be happy to. Just fork and send a pull request when you are ready
to:
  https://github.com/alexfernandez/elyxer/
That is how things work these days, and I cannot complain. Sadly I don't
have the time to do most things myself, but I have already received some
juicy pull requests and have integrated them happily.

As for the license, we can work things out to our mutual benefit. Open
source licenses are a means to an end.

Alex.