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: 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: 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.


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: 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: 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.


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: 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: 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.