Re: comments in Koma script article

[Jürgen Spitzmüller]

Am Sonntag, dem 12.09.2021 um 09:37 +0200 schrieb Wolfgang Engelmann:
> I exported a lyx Koma script article to pdf, but the comments are not
> shown. I thought, comments are, in contrast to notes, shown in pdf.

No, comments are, in contrast to notes, visible in the TeX file (not
the PDF). If you want the latter, use greyedout notes or the PDF
Comments or TODONotes module.

Jürgen



signature.asc
Description: This is a digitally signed message part
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

comments in Koma script article

[Wolfgang Engelmann]

I exported a lyx Koma script article to pdf, but the comments are not 
shown. I thought, comments are, in contrast to notes, shown in pdf.

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

TeX comments in preamble (was: Biblatex in LyX 2.3 and newer)

[Guenter Milde]

On 2018-11-10, jezZiFeR wrote:

> Also the lines:
> \urlstyle{%}
> \usepackage{%}
> \begin{%}

> caused some errors – do I really have to remove all of them? Is there
> is one obvious reason for this?

In TeX (and the LyX-user-preamble), a % starts a comment that stretches till
the end of line. Therefore, all these lines produce unbalanced braces, for
TeX the code becomes:

 \urlstyle{
 \usepackage{
 \begin{

Günter

Re: Toggle comments in Lyx->LaTeX Preamble

[Wolfgang Engelmann]

Am 23.02.2018 um 12:02 schrieb Jean-Marc Lasgouttes:

Le 23/02/2018 à 11:47, Wolfgang Engelmann a écrit :

Jean-Marc,
where can I find the description and handling of "the 'title and 
preamble hacks' module"?

I searched for it in all available Helps for Lyx, but did not find it.
Wolfgang


The only documentation that I know is in the document settings dialog, 
modules panel.


Quote:

Provides two new styles: 1. An 'In Preamble' style that puts whatever 
is entered into it into the preamble. This can be used, if one wishes, 
to include preamble code in the body of the LyX document. 2. An 'In 
Title' style that will put its contents into the body of the LaTeX 
document, but before \maketitle is issued. This is useful for making 
branches and notes in title-related material. (If you put these in a 
Standard layout, this signals to LyX to output \maketitle, which may 
then come too early.)


JMarc

ok, got it
thanks, Wolfgang

Re: Toggle comments in Lyx->LaTeX Preamble

[Jean-Marc Lasgouttes]

Le 23/02/2018 à 11:47, Wolfgang Engelmann a écrit :

Jean-Marc,
where can I find the description and handling of "the 'title and 
preamble hacks' module"?

I searched for it in all available Helps for Lyx, but did not find it.
Wolfgang


The only documentation that I know is in the document settings dialog, 
modules panel.


Quote:

Provides two new styles: 1. An 'In Preamble' style that puts whatever is 
entered into it into the preamble. This can be used, if one wishes, to 
include preamble code in the body of the LyX document. 2. An 'In Title' 
style that will put its contents into the body of the LaTeX document, 
but before \maketitle is issued. This is useful for making branches and 
notes in title-related material. (If you put these in a Standard layout, 
this signals to LyX to output \maketitle, which may then come too early.)


JMarc

Re: Toggle comments in Lyx->LaTeX Preamble

[Wolfgang Engelmann]

Am 23.02.2018 um 10:57 schrieb Jean-Marc Lasgouttes:

Le 22/02/2018 à 20:52, Daniel Gómez Martínez a écrit :

Hello everyone,

I have large sections of customized TeX code in the LaTeX preamble of 
some LyX templates I've created over time. I would like to know if 
there's a way to quickly toggle between commented and uncommented 
line for a given selection of lines (say, with a keyboard shortcut), 
and in case there's not a quick way to do this, I would like to ask 
the developers if they can include this feature in 
Settings->Document->LaTeX Preamble and in the TeX code environment 
(the one you have with Ctrl+L), it would also be great if a message 
of how to do so (toggle comment lines keyboard shortcut) could be 
included in the Settings->Document->LaTeX Preamble sub-window.


Using the 'title and preamble hacks' module, you can add preamble 
items in your document as normal paragraphs.


Then, one can include these things in branch(es) and you're done !

HTH,
JMarc

Jean-Marc,
where can I find the description and handling of "the 'title and 
preamble hacks' module"?

I searched for it in all available Helps for Lyx, but did not find it.
Wolfgang

Re: Toggle comments in Lyx->LaTeX Preamble

[Jean-Marc Lasgouttes]

Le 22/02/2018 à 20:52, Daniel Gómez Martínez a écrit :

Hello everyone,

I have large sections of customized TeX code in the LaTeX preamble of 
some LyX templates I've created over time. I would like to know if 
there's a way to quickly toggle between commented and uncommented line 
for a given selection of lines (say, with a keyboard shortcut), and in 
case there's not a quick way to do this, I would like to ask the 
developers if they can include this feature in Settings->Document->LaTeX 
Preamble and in the TeX code environment (the one you have with Ctrl+L), 
it would also be great if a message of how to do so (toggle comment 
lines keyboard shortcut) could be included in the 
Settings->Document->LaTeX Preamble sub-window.


Using the 'title and preamble hacks' module, you can add preamble items 
in your document as normal paragraphs.


Then, one can include these things in branch(es) and you're done !

HTH,
JMarc

Re: Toggle comments in Lyx->LaTeX Preamble

[Dr Eberhard Lisse]

Maye some form of LaTeX conditional (\newif), which you then pass as a
Custom option in Documents->Settings?

el


On 22/02/2018 22:05, Joel Kulesza wrote:
> On Thu, Feb 22, 2018 at 12:52 PM, Daniel Gómez Martínez
>  wrote:
> 
> Hello everyone,
> 
> I have large sections of customized TeX code in the LaTeX preamble
> of some LyX templates I've created over time. I would like to know
> if there's a way to quickly toggle between commented and uncommented
> line for a given selection of lines (say, with a keyboard shortcut)
> 
> 
> I don't know of a way to do this.
>  
> 
> , and in case there's not a quick way to do this, I would like to
> ask the developers if they can include this feature in
> Settings->Document->LaTeX Preamble and in the TeX code environment 
> 
> 
> I would be happy to see this also.
>  
> 
> (the one you have with Ctrl+L), it would also be great if a message
> of how to do so (toggle comment lines keyboard shortcut) could be
> included in the Settings->Document->LaTeX Preamble sub-window.
> 
> I'm sure I've read somewhere that LyX tries to the highest extent to
> be so complete that users don't usually have to put TeX or Preamble
> code lines, but as we users have some really customized and variable
> needs
> 
> 
> The approach I use is to write a separate, external, preamble.tex file
> that I then put alongside the .lyx file and in LyX's premable I issue
> "\input{preamble.tex}".  Then, I can (un)comment the contained behavior
> in one line.  Naturally, one can use multiple preamble files to
> segregate behaviors.  Using this approach also allows multiple documents
> to share a common preamble.  Further, by symbolically linking the .tex
> file, an update in one instance updates behaviors globally. 
> 
> - Joel

Re: Toggle comments in Lyx->LaTeX Preamble

[Paul A. Rubin]

On 02/22/2018 05:06 PM, Richard Heck wrote:

On 02/22/2018 04:00 PM, Paul A Rubin wrote:




On 02/22/2018 03:37 PM, Richard Heck wrote:

On 02/22/2018 03:05 PM, Joel Kulesza wrote:
On Thu, Feb 22, 2018 at 12:52 PM, Daniel Gómez Martínez 
> wrote:


Hello everyone,

I have large sections of customized TeX code in the LaTeX
preamble of some LyX templates I've created over time. I would
like to know if there's a way to quickly toggle between
commented and uncommented line for a given selection of lines
(say, with a keyboard shortcut)


I don't know of a way to do this.

, and in case there's not a quick way to do this, I would like
to ask the developers if they can include this feature in
Settings->Document->LaTeX Preamble and in the TeX code environment


I would be happy to see this also.

(the one you have with Ctrl+L), it would also be great if a
message of how to do so (toggle comment lines keyboard
shortcut) could be included in the Settings->Document->LaTeX
Preamble sub-window.

I'm sure I've read somewhere that LyX tries to the highest
extent to be so complete that users don't usually have to put
TeX or Preamble code lines, but as we users have some really
customized and variable needs


The approach I use is to write a separate, external, preamble.tex 
file that I then put alongside the .lyx file and in LyX's premable 
I issue "\input{preamble.tex}".  Then, I can (un)comment the 
contained behavior in one line. Naturally, one can use multiple 
preamble files to segregate behaviors.  Using this approach also 
allows multiple documents to share a common preamble.  Further, by 
symbolically linking the .tex file, an update in one instance 
updates behaviors globally.


If one's preamble-related needs have become this sophisticated, then 
I'd recommend this approach. I don't think we really want to 
implement a full-fledged LaTeX editor inside LyX. What might be more 
plausible, and something I think we have considered, is to have some 
way to launch an external text editor and then read back whatever's 
provided, kind of like we do with graphics (say).


We already have line-begin, self-insert and char-delete-forward 
LFUNs. If someone were to add a "for-each-selected-line" LFUN (with a 
shorter name) that would take a command or command-sequence as its 
argument, block comment/uncomment could be done as a macro.


Those don't apply in the case of hte LaTeX preamble. That's just a 
text editing widget provided by Qt.


Richard


Oops. Missed that.

Paul

Re: Toggle comments in Lyx->LaTeX Preamble

[Richard Heck]

On 02/22/2018 04:00 PM, Paul A Rubin wrote:
>
>
>
> On 02/22/2018 03:37 PM, Richard Heck wrote:
>> On 02/22/2018 03:05 PM, Joel Kulesza wrote:
>>> On Thu, Feb 22, 2018 at 12:52 PM, Daniel Gómez Martínez
>>> > wrote:
>>>
>>> Hello everyone,
>>>
>>> I have large sections of customized TeX code in the LaTeX
>>> preamble of some LyX templates I've created over time. I would
>>> like to know if there's a way to quickly toggle between
>>> commented and uncommented line for a given selection of lines
>>> (say, with a keyboard shortcut)
>>>
>>>
>>> I don't know of a way to do this.
>>>  
>>>
>>> , and in case there's not a quick way to do this, I would like
>>> to ask the developers if they can include this feature in
>>> Settings->Document->LaTeX Preamble and in the TeX code environment
>>>
>>>
>>> I would be happy to see this also.
>>>  
>>>
>>> (the one you have with Ctrl+L), it would also be great if a
>>> message of how to do so (toggle comment lines keyboard shortcut)
>>> could be included in the Settings->Document->LaTeX Preamble
>>> sub-window.
>>>
>>> I'm sure I've read somewhere that LyX tries to the highest
>>> extent to be so complete that users don't usually have to put
>>> TeX or Preamble code lines, but as we users have some really
>>> customized and variable needs
>>>
>>>
>>> The approach I use is to write a separate, external, preamble.tex
>>> file that I then put alongside the .lyx file and in LyX's premable I
>>> issue "\input{preamble.tex}".  Then, I can (un)comment the contained
>>> behavior in one line.  Naturally, one can use multiple preamble
>>> files to segregate behaviors.  Using this approach also allows
>>> multiple documents to share a common preamble.  Further, by
>>> symbolically linking the .tex file, an update in one instance
>>> updates behaviors globally.
>>
>> If one's preamble-related needs have become this sophisticated, then
>> I'd recommend this approach. I don't think we really want to
>> implement a full-fledged LaTeX editor inside LyX. What might be more
>> plausible, and something I think we have considered, is to have some
>> way to launch an external text editor and then read back whatever's
>> provided, kind of like we do with graphics (say).
>
> We already have line-begin, self-insert and char-delete-forward LFUNs.
> If someone were to add a "for-each-selected-line" LFUN (with a shorter
> name) that would take a command or command-sequence as its argument,
> block comment/uncomment could be done as a macro.

Those don't apply in the case of hte LaTeX preamble. That's just a text
editing widget provided by Qt.

Richard

Re: Toggle comments in Lyx->LaTeX Preamble

[Scott Kostyshak]

On Thu, Feb 22, 2018 at 08:37:44PM +, Richard Heck wrote:

> What might be more plausible, and
> something I think we have considered, is to have some way to launch an
> external text editor and then read back whatever's provided, kind of
> like we do with graphics (say).

There is a trac ticket for this somewhere.

Scott


signature.asc
Description: PGP signature

Re: Toggle comments in Lyx->LaTeX Preamble

[Paul A Rubin]

On 02/22/2018 03:37 PM, Richard Heck wrote:

On 02/22/2018 03:05 PM, Joel Kulesza wrote:
On Thu, Feb 22, 2018 at 12:52 PM, Daniel Gómez Martínez 
> wrote:


Hello everyone,

I have large sections of customized TeX code in the LaTeX
preamble of some LyX templates I've created over time. I would
like to know if there's a way to quickly toggle between commented
and uncommented line for a given selection of lines (say, with a
keyboard shortcut)


I don't know of a way to do this.

, and in case there's not a quick way to do this, I would like to
ask the developers if they can include this feature in
Settings->Document->LaTeX Preamble and in the TeX code environment


I would be happy to see this also.

(the one you have with Ctrl+L), it would also be great if a
message of how to do so (toggle comment lines keyboard shortcut)
could be included in the Settings->Document->LaTeX Preamble
sub-window.

I'm sure I've read somewhere that LyX tries to the highest extent
to be so complete that users don't usually have to put TeX or
Preamble code lines, but as we users have some really customized
and variable needs


The approach I use is to write a separate, external, preamble.tex 
file that I then put alongside the .lyx file and in LyX's premable I 
issue "\input{preamble.tex}".  Then, I can (un)comment the contained 
behavior in one line.  Naturally, one can use multiple preamble files 
to segregate behaviors.  Using this approach also allows multiple 
documents to share a common preamble.  Further, by symbolically 
linking the .tex file, an update in one instance updates behaviors 
globally.


If one's preamble-related needs have become this sophisticated, then 
I'd recommend this approach. I don't think we really want to implement 
a full-fledged LaTeX editor inside LyX. What might be more plausible, 
and something I think we have considered, is to have some way to 
launch an external text editor and then read back whatever's provided, 
kind of like we do with graphics (say).
We already have line-begin, self-insert and char-delete-forward LFUNs. 
If someone were to add a "for-each-selected-line" LFUN (with a shorter 
name) that would take a command or command-sequence as its argument, 
block comment/uncomment could be done as a macro.


Paul

Re: Toggle comments in Lyx->LaTeX Preamble

[Richard Heck]

On 02/22/2018 03:05 PM, Joel Kulesza wrote:
> On Thu, Feb 22, 2018 at 12:52 PM, Daniel Gómez Martínez
> > wrote:
>
> Hello everyone,
>
> I have large sections of customized TeX code in the LaTeX preamble
> of some LyX templates I've created over time. I would like to know
> if there's a way to quickly toggle between commented and
> uncommented line for a given selection of lines (say, with a
> keyboard shortcut)
>
>
> I don't know of a way to do this.
>  
>
> , and in case there's not a quick way to do this, I would like to
> ask the developers if they can include this feature in
> Settings->Document->LaTeX Preamble and in the TeX code environment
>
>
> I would be happy to see this also.
>  
>
> (the one you have with Ctrl+L), it would also be great if a
> message of how to do so (toggle comment lines keyboard shortcut)
> could be included in the Settings->Document->LaTeX Preamble
> sub-window.
>
> I'm sure I've read somewhere that LyX tries to the highest extent
> to be so complete that users don't usually have to put TeX or
> Preamble code lines, but as we users have some really customized
> and variable needs
>
>
> The approach I use is to write a separate, external, preamble.tex file
> that I then put alongside the .lyx file and in LyX's premable I issue
> "\input{preamble.tex}".  Then, I can (un)comment the contained
> behavior in one line.  Naturally, one can use multiple preamble files
> to segregate behaviors.  Using this approach also allows multiple
> documents to share a common preamble.  Further, by symbolically
> linking the .tex file, an update in one instance updates behaviors
> globally.

If one's preamble-related needs have become this sophisticated, then I'd
recommend this approach. I don't think we really want to implement a
full-fledged LaTeX editor inside LyX. What might be more plausible, and
something I think we have considered, is to have some way to launch an
external text editor and then read back whatever's provided, kind of
like we do with graphics (say).

Richard

Re: Toggle comments in Lyx->LaTeX Preamble

[Joel Kulesza]

On Thu, Feb 22, 2018 at 12:52 PM, Daniel Gómez Martínez <
dangome...@gmail.com> wrote:

> Hello everyone,
>
> I have large sections of customized TeX code in the LaTeX preamble of some
> LyX templates I've created over time. I would like to know if there's a way
> to quickly toggle between commented and uncommented line for a given
> selection of lines (say, with a keyboard shortcut)
>

I don't know of a way to do this.


> , and in case there's not a quick way to do this, I would like to ask the
> developers if they can include this feature in Settings->Document->LaTeX
> Preamble and in the TeX code environment
>

I would be happy to see this also.


> (the one you have with Ctrl+L), it would also be great if a message of how
> to do so (toggle comment lines keyboard shortcut) could be included in the 
> Settings->Document->LaTeX
> Preamble sub-window.
>
> I'm sure I've read somewhere that LyX tries to the highest extent to be so
> complete that users don't usually have to put TeX or Preamble code lines,
> but as we users have some really customized and variable needs
>

The approach I use is to write a separate, external, preamble.tex file that
I then put alongside the .lyx file and in LyX's premable I issue
"\input{preamble.tex}".  Then, I can (un)comment the contained behavior in
one line.  Naturally, one can use multiple preamble files to segregate
behaviors.  Using this approach also allows multiple documents to share a
common preamble.  Further, by symbolically linking the .tex file, an update
in one instance updates behaviors globally.

- Joel

Toggle comments in Lyx->LaTeX Preamble

[Daniel Gómez Martínez]

Hello everyone,

I have large sections of customized TeX code in the LaTeX preamble of some
LyX templates I've created over time. I would like to know if there's a way
to quickly toggle between commented and uncommented line for a given
selection of lines (say, with a keyboard shortcut), and in case there's not
a quick way to do this, I would like to ask the developers if they can
include this feature in Settings->Document->LaTeX Preamble and in the TeX
code environment (the one you have with Ctrl+L), it would also be great if
a message of how to do so (toggle comment lines keyboard shortcut) could be
included in the Settings->Document->LaTeX Preamble sub-window.

I'm sure I've read somewhere that LyX tries to the highest extent to be so
complete that users don't usually have to put TeX or Preamble code lines,
but as we users have some really customized and variable needs, I think
this would be a good feature to have in order to be more productive: we
could then toggle between the customization lines of our templates and
documents for different reasons, be them debugging or changes in document
appearance.

Best regards,


*Daniel Gómez Martínez | Profesional en ingeniería eléctrica*

*Universidad Nacional de Colombi​a​*

Re: request for comments on EPUB exporting

[Josh Hieronymus]

 In my opinion, language should be taken from the document settings
 since it is already a setting. I think for other fields such as author
 this should be taken from an inset defined by the module/layout. But
 this might be because I don't know anything about EPUB. Can I export
 any document in LyX to EPUB with your method? I would just export from
 the file menu? Or do I have to first add a module?


Right now, things are set up so that any document can be exported to EPUB
using the FileExport menu option without adding an extra module.


 Perhaps an extra
 EPUB fields module could be useful in which the necessary (author
 name) and optional fields are implemented with custom insets.


Is there a good way to distinguish between necessary fields and optional
fields? Also, another issue to consider is that while some fields are not
necessary insofar as EPUB validation is concerned, different distributors
might require several such fields to be provided.


  What I'd like to implement at some point:
  - optional conversion of images to SVG format
  Note: Vector-based graphics scale better than raster-based graphics,
 making
  them well-suited for electronic media.
  Note: EPUB specifications require compliant e-readers to support SVG.
  Note: Older versions of some browsers (primarily IE) don't support SVG.
  Note: Preliminary searches turn up a package named dvisvgm
  (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
  licensed under the GPL v3 or later.
  - ability to split large XHTML files into smaller ones
  Note: Splitting large XHTML files should boost the performance of the
  converted EPUB documents.
  - allow selection of an image for front cover artwork
  Note: Amazon requires JPEG or TIFF format for front cover artwork.

 Thanks for this information. What about EPS/PDF? What are their
 advantages/disadvantages versus SVG?


Good question. As far as EPUB is concerned, the only images that are
required to be supported by compliant e-readers are GIFs, JPEGs, PNGs, and
SVGs, so SVGs are (supposed to be) natively supported, while PDFs and EPSs
aren't necessarily supported, and are required to use a supported type as a
fallback. For HTML in general, most web browsers support SVGs (it helps
that the SVG standard is developed by the W3C), and I think that they don't
typically support EPSs. I'm not sure about to what extent web browsers
support embedded PDFs, though preliminary research suggests that most
might. Another issue with PDFs is that they serve as containers for both
vector- and raster-based information, so if they contain any raster-based
info, that portion will appear pixelated when zoomed in.

Re: request for comments on EPUB exporting

[Scott Kostyshak]

On Mon, Sep 2, 2013 at 12:13 AM, Josh Hieronymus
josh.p.hierony...@gmail.com wrote:
 In my opinion, language should be taken from the document settings
 since it is already a setting. I think for other fields such as author
 this should be taken from an inset defined by the module/layout. But
 this might be because I don't know anything about EPUB. Can I export
 any document in LyX to EPUB with your method? I would just export from
 the file menu? Or do I have to first add a module?


 Right now, things are set up so that any document can be exported to EPUB
 using the FileExport menu option without adding an extra module.


 Perhaps an extra
 EPUB fields module could be useful in which the necessary (author
 name) and optional fields are implemented with custom insets.


 Is there a good way to distinguish between necessary fields and optional
 fields? Also, another issue to consider is that while some fields are not
 necessary insofar as EPUB validation is concerned, different distributors
 might require several such fields to be provided.

Support for optional arguments has been improved in 2.1. See Help 
Customization 5.3.6 Paragraph styles and look for Arguments.
I'm still not sure this is the best way to do it. I hope someone more
knowledgeable comes along and gives their opinion. Perhaps a Document
Setting is indeed best. I wanted to avoid that if possible, but it
would be more straightforward than a module and you would have more
control over the interface.


  What I'd like to implement at some point:
  - optional conversion of images to SVG format
  Note: Vector-based graphics scale better than raster-based graphics,
  making
  them well-suited for electronic media.
  Note: EPUB specifications require compliant e-readers to support SVG.
  Note: Older versions of some browsers (primarily IE) don't support SVG.
  Note: Preliminary searches turn up a package named dvisvgm
  (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
  licensed under the GPL v3 or later.
  - ability to split large XHTML files into smaller ones
  Note: Splitting large XHTML files should boost the performance of the
  converted EPUB documents.
  - allow selection of an image for front cover artwork
  Note: Amazon requires JPEG or TIFF format for front cover artwork.

 Thanks for this information. What about EPS/PDF? What are their
 advantages/disadvantages versus SVG?


 Good question. As far as EPUB is concerned, the only images that are
 required to be supported by compliant e-readers are GIFs, JPEGs, PNGs, and
 SVGs, so SVGs are (supposed to be) natively supported, while PDFs and EPSs
 aren't necessarily supported, and are required to use a supported type as a
 fallback. For HTML in general, most web browsers support SVGs (it helps that
 the SVG standard is developed by the W3C), and I think that they don't
 typically support EPSs. I'm not sure about to what extent web browsers
 support embedded PDFs, though preliminary research suggests that most might.
 Another issue with PDFs is that they serve as containers for both vector-
 and raster-based information, so if they contain any raster-based info, that
 portion will appear pixelated when zoomed in.

Interesting. This is good to know. Also, a quick search suggests that
one can embed raster images in SVGs as well (with base64 encoding):
http://stackoverflow.com/questions/6249664/does-svg-support-embedding-of-bitmap-images

Scott

Re: request for comments on EPUB exporting

[Josh Hieronymus]

 In my opinion, language should be taken from the document settings
 since it is already a setting. I think for other fields such as author
 this should be taken from an inset defined by the module/layout. But
 this might be because I don't know anything about EPUB. Can I export
 any document in LyX to EPUB with your method? I would just export from
 the file menu? Or do I have to first add a module?


Right now, things are set up so that any document can be exported to EPUB
using the FileExport menu option without adding an extra module.


 Perhaps an extra
 EPUB fields module could be useful in which the necessary (author
 name) and optional fields are implemented with custom insets.


Is there a good way to distinguish between necessary fields and optional
fields? Also, another issue to consider is that while some fields are not
necessary insofar as EPUB validation is concerned, different distributors
might require several such fields to be provided.


  What I'd like to implement at some point:
  - optional conversion of images to SVG format
  Note: Vector-based graphics scale better than raster-based graphics,
 making
  them well-suited for electronic media.
  Note: EPUB specifications require compliant e-readers to support SVG.
  Note: Older versions of some browsers (primarily IE) don't support SVG.
  Note: Preliminary searches turn up a package named dvisvgm
  (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
  licensed under the GPL v3 or later.
  - ability to split large XHTML files into smaller ones
  Note: Splitting large XHTML files should boost the performance of the
  converted EPUB documents.
  - allow selection of an image for front cover artwork
  Note: Amazon requires JPEG or TIFF format for front cover artwork.

 Thanks for this information. What about EPS/PDF? What are their
 advantages/disadvantages versus SVG?


Good question. As far as EPUB is concerned, the only images that are
required to be supported by compliant e-readers are GIFs, JPEGs, PNGs, and
SVGs, so SVGs are (supposed to be) natively supported, while PDFs and EPSs
aren't necessarily supported, and are required to use a supported type as a
fallback. For HTML in general, most web browsers support SVGs (it helps
that the SVG standard is developed by the W3C), and I think that they don't
typically support EPSs. I'm not sure about to what extent web browsers
support embedded PDFs, though preliminary research suggests that most
might. Another issue with PDFs is that they serve as containers for both
vector- and raster-based information, so if they contain any raster-based
info, that portion will appear pixelated when zoomed in.

Re: request for comments on EPUB exporting

[Scott Kostyshak]

On Mon, Sep 2, 2013 at 12:13 AM, Josh Hieronymus
josh.p.hierony...@gmail.com wrote:
 In my opinion, language should be taken from the document settings
 since it is already a setting. I think for other fields such as author
 this should be taken from an inset defined by the module/layout. But
 this might be because I don't know anything about EPUB. Can I export
 any document in LyX to EPUB with your method? I would just export from
 the file menu? Or do I have to first add a module?


 Right now, things are set up so that any document can be exported to EPUB
 using the FileExport menu option without adding an extra module.


 Perhaps an extra
 EPUB fields module could be useful in which the necessary (author
 name) and optional fields are implemented with custom insets.


 Is there a good way to distinguish between necessary fields and optional
 fields? Also, another issue to consider is that while some fields are not
 necessary insofar as EPUB validation is concerned, different distributors
 might require several such fields to be provided.

Support for optional arguments has been improved in 2.1. See Help 
Customization 5.3.6 Paragraph styles and look for Arguments.
I'm still not sure this is the best way to do it. I hope someone more
knowledgeable comes along and gives their opinion. Perhaps a Document
Setting is indeed best. I wanted to avoid that if possible, but it
would be more straightforward than a module and you would have more
control over the interface.


  What I'd like to implement at some point:
  - optional conversion of images to SVG format
  Note: Vector-based graphics scale better than raster-based graphics,
  making
  them well-suited for electronic media.
  Note: EPUB specifications require compliant e-readers to support SVG.
  Note: Older versions of some browsers (primarily IE) don't support SVG.
  Note: Preliminary searches turn up a package named dvisvgm
  (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
  licensed under the GPL v3 or later.
  - ability to split large XHTML files into smaller ones
  Note: Splitting large XHTML files should boost the performance of the
  converted EPUB documents.
  - allow selection of an image for front cover artwork
  Note: Amazon requires JPEG or TIFF format for front cover artwork.

 Thanks for this information. What about EPS/PDF? What are their
 advantages/disadvantages versus SVG?


 Good question. As far as EPUB is concerned, the only images that are
 required to be supported by compliant e-readers are GIFs, JPEGs, PNGs, and
 SVGs, so SVGs are (supposed to be) natively supported, while PDFs and EPSs
 aren't necessarily supported, and are required to use a supported type as a
 fallback. For HTML in general, most web browsers support SVGs (it helps that
 the SVG standard is developed by the W3C), and I think that they don't
 typically support EPSs. I'm not sure about to what extent web browsers
 support embedded PDFs, though preliminary research suggests that most might.
 Another issue with PDFs is that they serve as containers for both vector-
 and raster-based information, so if they contain any raster-based info, that
 portion will appear pixelated when zoomed in.

Interesting. This is good to know. Also, a quick search suggests that
one can embed raster images in SVGs as well (with base64 encoding):
http://stackoverflow.com/questions/6249664/does-svg-support-embedding-of-bitmap-images

Scott

Re: request for comments on EPUB exporting

[Josh Hieronymus]

>
> In my opinion, language should be taken from the document settings
> since it is already a setting. I think for other fields such as author
> this should be taken from an inset defined by the module/layout. But
> this might be because I don't know anything about EPUB. Can I export
> any document in LyX to EPUB with your method? I would just export from
> the file menu? Or do I have to first add a module?


Right now, things are set up so that any document can be exported to EPUB
using the File>Export menu option without adding an extra module.


> Perhaps an extra
> "EPUB fields" module could be useful in which the necessary (author
> name) and optional fields are implemented with custom insets.
>

Is there a good way to distinguish between necessary fields and optional
fields? Also, another issue to consider is that while some fields are not
necessary insofar as EPUB validation is concerned, different distributors
might require several such fields to be provided.


> > What I'd like to implement at some point:
> > - optional conversion of images to SVG format
> > Note: Vector-based graphics scale better than raster-based graphics,
> making
> > them well-suited for electronic media.
> > Note: EPUB specifications require compliant e-readers to support SVG.
> > Note: Older versions of some browsers (primarily IE) don't support SVG.
> > Note: Preliminary searches turn up a package named dvisvgm
> > (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
> > licensed under the GPL v3 or later.
> > - ability to split large XHTML files into smaller ones
> > Note: Splitting large XHTML files should boost the performance of the
> > converted EPUB documents.
> > - allow selection of an image for front cover artwork
> > Note: Amazon requires JPEG or TIFF format for front cover artwork.
>
> Thanks for this information. What about EPS/PDF? What are their
> advantages/disadvantages versus SVG?
>

Good question. As far as EPUB is concerned, the only images that are
required to be supported by compliant e-readers are GIFs, JPEGs, PNGs, and
SVGs, so SVGs are (supposed to be) natively supported, while PDFs and EPSs
aren't necessarily supported, and are required to use a supported type as a
fallback. For HTML in general, most web browsers support SVGs (it helps
that the SVG standard is developed by the W3C), and I think that they don't
typically support EPSs. I'm not sure about to what extent web browsers
support embedded PDFs, though preliminary research suggests that most
might. Another issue with PDFs is that they serve as containers for both
vector- and raster-based information, so if they contain any raster-based
info, that portion will appear pixelated when zoomed in.

Re: request for comments on EPUB exporting

[Scott Kostyshak]

On Mon, Sep 2, 2013 at 12:13 AM, Josh Hieronymus
 wrote:
>> In my opinion, language should be taken from the document settings
>> since it is already a setting. I think for other fields such as author
>> this should be taken from an inset defined by the module/layout. But
>> this might be because I don't know anything about EPUB. Can I export
>> any document in LyX to EPUB with your method? I would just export from
>> the file menu? Or do I have to first add a module?
>
>
> Right now, things are set up so that any document can be exported to EPUB
> using the File>Export menu option without adding an extra module.
>
>>
>> Perhaps an extra
>> "EPUB fields" module could be useful in which the necessary (author
>> name) and optional fields are implemented with custom insets.
>
>
> Is there a good way to distinguish between necessary fields and optional
> fields? Also, another issue to consider is that while some fields are not
> necessary insofar as EPUB validation is concerned, different distributors
> might require several such fields to be provided.

Support for optional arguments has been improved in 2.1. See Help >
Customization "5.3.6 Paragraph styles" and look for "Arguments".
I'm still not sure this is the best way to do it. I hope someone more
knowledgeable comes along and gives their opinion. Perhaps a Document
Setting is indeed best. I wanted to avoid that if possible, but it
would be more straightforward than a module and you would have more
control over the interface.


>> > What I'd like to implement at some point:
>> > - optional conversion of images to SVG format
>> > Note: Vector-based graphics scale better than raster-based graphics,
>> > making
>> > them well-suited for electronic media.
>> > Note: EPUB specifications require compliant e-readers to support SVG.
>> > Note: Older versions of some browsers (primarily IE) don't support SVG.
>> > Note: Preliminary searches turn up a package named dvisvgm
>> > (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
>> > licensed under the GPL v3 or later.
>> > - ability to split large XHTML files into smaller ones
>> > Note: Splitting large XHTML files should boost the performance of the
>> > converted EPUB documents.
>> > - allow selection of an image for front cover artwork
>> > Note: Amazon requires JPEG or TIFF format for front cover artwork.
>>
>> Thanks for this information. What about EPS/PDF? What are their
>> advantages/disadvantages versus SVG?
>
>
> Good question. As far as EPUB is concerned, the only images that are
> required to be supported by compliant e-readers are GIFs, JPEGs, PNGs, and
> SVGs, so SVGs are (supposed to be) natively supported, while PDFs and EPSs
> aren't necessarily supported, and are required to use a supported type as a
> fallback. For HTML in general, most web browsers support SVGs (it helps that
> the SVG standard is developed by the W3C), and I think that they don't
> typically support EPSs. I'm not sure about to what extent web browsers
> support embedded PDFs, though preliminary research suggests that most might.
> Another issue with PDFs is that they serve as containers for both vector-
> and raster-based information, so if they contain any raster-based info, that
> portion will appear pixelated when zoomed in.

Interesting. This is good to know. Also, a quick search suggests that
one can embed raster images in SVGs as well (with base64 encoding):
http://stackoverflow.com/questions/6249664/does-svg-support-embedding-of-bitmap-images

Scott

Re: request for comments on EPUB exporting

[Scott Kostyshak]

On Fri, Aug 30, 2013 at 11:31 PM, Josh Hieronymus
josh.p.hierony...@gmail.com wrote:
 Hi everyone,

 I'm working on exporting LyX documents to EPUB as part of my Google Summer
 of Code project, and I'd like to invite you to try out my current
 implementation, which can be found in the epub/master branch of the gsoc
 repository (g...@git.lyx.org:gsoc.git). The export process begins by
 exporting the document to XHTML via LyXHTML, then converting the XHTML to
 EPUB with the scripts in lib/scripts/epub.

I'm not an EPUB user so I cannot test unfortunately.

 - Extracting other metadata fields from the document. The required fields
 are language, title, and identifier. The title field is taken from the
 document, but not  the language or the identifier. I'm taking the title from
 the first paragraph to use the title inset, but there aren't corresponding
 insets for the other elements, so I'm not sure of the best way or ways to
 get the rest of the info. (There's an inset for author, but the author name
 is needed in both reading order and file-as order, and there's only one
 author inset.) One thought is to create custom insets, and another is to ask
 for the information via the document settings.

In my opinion, language should be taken from the document settings
since it is already a setting. I think for other fields such as author
this should be taken from an inset defined by the module/layout. But
this might be because I don't know anything about EPUB. Can I export
any document in LyX to EPUB with your method? I would just export from
the file menu? Or do I have to first add a module? Perhaps an extra
EPUB fields module could be useful in which the necessary (author
name) and optional fields are implemented with custom insets.

 What I'd like to implement at some point:
 - optional conversion of images to SVG format
 Note: Vector-based graphics scale better than raster-based graphics, making
 them well-suited for electronic media.
 Note: EPUB specifications require compliant e-readers to support SVG.
 Note: Older versions of some browsers (primarily IE) don't support SVG.
 Note: Preliminary searches turn up a package named dvisvgm
 (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
 licensed under the GPL v3 or later.
 - ability to split large XHTML files into smaller ones
 Note: Splitting large XHTML files should boost the performance of the
 converted EPUB documents.
 - allow selection of an image for front cover artwork
 Note: Amazon requires JPEG or TIFF format for front cover artwork.

Thanks for this information. What about EPS/PDF? What are their
advantages/disadvantages versus SVG?

Scott

Re: request for comments on EPUB exporting

[Scott Kostyshak]

On Fri, Aug 30, 2013 at 11:31 PM, Josh Hieronymus
josh.p.hierony...@gmail.com wrote:
 Hi everyone,

 I'm working on exporting LyX documents to EPUB as part of my Google Summer
 of Code project, and I'd like to invite you to try out my current
 implementation, which can be found in the epub/master branch of the gsoc
 repository (g...@git.lyx.org:gsoc.git). The export process begins by
 exporting the document to XHTML via LyXHTML, then converting the XHTML to
 EPUB with the scripts in lib/scripts/epub.

I'm not an EPUB user so I cannot test unfortunately.

 - Extracting other metadata fields from the document. The required fields
 are language, title, and identifier. The title field is taken from the
 document, but not  the language or the identifier. I'm taking the title from
 the first paragraph to use the title inset, but there aren't corresponding
 insets for the other elements, so I'm not sure of the best way or ways to
 get the rest of the info. (There's an inset for author, but the author name
 is needed in both reading order and file-as order, and there's only one
 author inset.) One thought is to create custom insets, and another is to ask
 for the information via the document settings.

In my opinion, language should be taken from the document settings
since it is already a setting. I think for other fields such as author
this should be taken from an inset defined by the module/layout. But
this might be because I don't know anything about EPUB. Can I export
any document in LyX to EPUB with your method? I would just export from
the file menu? Or do I have to first add a module? Perhaps an extra
EPUB fields module could be useful in which the necessary (author
name) and optional fields are implemented with custom insets.

 What I'd like to implement at some point:
 - optional conversion of images to SVG format
 Note: Vector-based graphics scale better than raster-based graphics, making
 them well-suited for electronic media.
 Note: EPUB specifications require compliant e-readers to support SVG.
 Note: Older versions of some browsers (primarily IE) don't support SVG.
 Note: Preliminary searches turn up a package named dvisvgm
 (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
 licensed under the GPL v3 or later.
 - ability to split large XHTML files into smaller ones
 Note: Splitting large XHTML files should boost the performance of the
 converted EPUB documents.
 - allow selection of an image for front cover artwork
 Note: Amazon requires JPEG or TIFF format for front cover artwork.

Thanks for this information. What about EPS/PDF? What are their
advantages/disadvantages versus SVG?

Scott

Re: request for comments on EPUB exporting

[Scott Kostyshak]

On Fri, Aug 30, 2013 at 11:31 PM, Josh Hieronymus
 wrote:
> Hi everyone,
>
> I'm working on exporting LyX documents to EPUB as part of my Google Summer
> of Code project, and I'd like to invite you to try out my current
> implementation, which can be found in the "epub/master" branch of the gsoc
> repository (g...@git.lyx.org:gsoc.git). The export process begins by
> exporting the document to XHTML via LyXHTML, then converting the XHTML to
> EPUB with the scripts in lib/scripts/epub.

I'm not an EPUB user so I cannot test unfortunately.

> - Extracting other metadata fields from the document. The required fields
> are language, title, and identifier. The title field is taken from the
> document, but not  the language or the identifier. I'm taking the title from
> the first paragraph to use the "title" inset, but there aren't corresponding
> insets for the other elements, so I'm not sure of the best way or ways to
> get the rest of the info. (There's an inset for author, but the author name
> is needed in both reading order and "file-as" order, and there's only one
> author inset.) One thought is to create custom insets, and another is to ask
> for the information via the document settings.

In my opinion, language should be taken from the document settings
since it is already a setting. I think for other fields such as author
this should be taken from an inset defined by the module/layout. But
this might be because I don't know anything about EPUB. Can I export
any document in LyX to EPUB with your method? I would just export from
the file menu? Or do I have to first add a module? Perhaps an extra
"EPUB fields" module could be useful in which the necessary (author
name) and optional fields are implemented with custom insets.

> What I'd like to implement at some point:
> - optional conversion of images to SVG format
> Note: Vector-based graphics scale better than raster-based graphics, making
> them well-suited for electronic media.
> Note: EPUB specifications require compliant e-readers to support SVG.
> Note: Older versions of some browsers (primarily IE) don't support SVG.
> Note: Preliminary searches turn up a package named dvisvgm
> (http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
> licensed under the GPL v3 or later.
> - ability to split large XHTML files into smaller ones
> Note: Splitting large XHTML files should boost the performance of the
> converted EPUB documents.
> - allow selection of an image for front cover artwork
> Note: Amazon requires JPEG or TIFF format for front cover artwork.

Thanks for this information. What about EPS/PDF? What are their
advantages/disadvantages versus SVG?

Scott

request for comments on EPUB exporting

[Josh Hieronymus]

Hi everyone,

I'm working on exporting LyX documents to EPUB as part of my Google Summer
of Code project, and I'd like to invite you to try out my current
implementation, which can be found in the epub/master branch of the gsoc
repository (g...@git.lyx.org:gsoc.git). The export process begins by
exporting the document to XHTML via LyXHTML, then converting the XHTML to
EPUB with the scripts in lib/scripts/epub.

Right now, documents will successfully export to EPUB 2.0.1, with the
following caveats:
- Almost all metadata fields (author, book id, etc.) are filled in with
default values. Only the title field is taken from the XHTML file from
which the EPUB is converted.
- No intra-document navigation is implemented; the document is just one
long page.
- MathML isn't part of the EPUB 2.0.1 standard, so the document output
settings should be set to output math as images.

What I'd like to implement soon:
- Extracting other metadata fields from the document. The required fields
are language, title, and identifier. The title field is taken from the
document, but not  the language or the identifier. I'm taking the title
from the first paragraph to use the title inset, but there aren't
corresponding insets for the other elements, so I'm not sure of the best
way or ways to get the rest of the info. (There's an inset for author, but
the author name is needed in both reading order and file-as order, and
there's only one author inset.) One thought is to create custom insets, and
another is to ask for the information via the document settings.
- Intra-document navigation. In order to skip around within the document,
add bookmarks, etc., navigation information needs to be added to the
toc.ncx file within the EPUB archive. Which locations in the document
should be added to the list of navigable points is not obvious. First, I
read (here at http://www.gbenthien.net/Kindle%20and%20EPUB/ncx.html) that
some e-readers only work with at most one depth level--only parts, or only
chapters, or only sections, or whatever. I'm not sure whether this is
correct or not. Either way, we can't always assume what depth the user
wants in the table of contents--this is probably something we should ask.
It's probably easiest to pull the navigation info straight from the
document's table of contents, but I don't know if this info is available in
the exported XHTML file without appearing visibly.

What I'd like to implement at some point:
- optional conversion of images to SVG format
Note: Vector-based graphics scale better than raster-based graphics, making
them well-suited for electronic media.
Note: EPUB specifications require compliant e-readers to support SVG.
Note: Older versions of some browsers (primarily IE) don't support SVG.
Note: Preliminary searches turn up a package named dvisvgm (
http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
licensed under the GPL v3 or later.
- ability to split large XHTML files into smaller ones
Note: Splitting large XHTML files should boost the performance of the
converted EPUB documents.
- allow selection of an image for front cover artwork
Note: Amazon requires JPEG or TIFF format for front cover artwork.

I'd love to hear any thoughts, comments, and suggestions you all have,
especially if you encounter any bugs or see something important I'm
overlooking.

Thanks,
Josh

request for comments on EPUB exporting

[Josh Hieronymus]

Hi everyone,

I'm working on exporting LyX documents to EPUB as part of my Google Summer
of Code project, and I'd like to invite you to try out my current
implementation, which can be found in the epub/master branch of the gsoc
repository (g...@git.lyx.org:gsoc.git). The export process begins by
exporting the document to XHTML via LyXHTML, then converting the XHTML to
EPUB with the scripts in lib/scripts/epub.

Right now, documents will successfully export to EPUB 2.0.1, with the
following caveats:
- Almost all metadata fields (author, book id, etc.) are filled in with
default values. Only the title field is taken from the XHTML file from
which the EPUB is converted.
- No intra-document navigation is implemented; the document is just one
long page.
- MathML isn't part of the EPUB 2.0.1 standard, so the document output
settings should be set to output math as images.

What I'd like to implement soon:
- Extracting other metadata fields from the document. The required fields
are language, title, and identifier. The title field is taken from the
document, but not  the language or the identifier. I'm taking the title
from the first paragraph to use the title inset, but there aren't
corresponding insets for the other elements, so I'm not sure of the best
way or ways to get the rest of the info. (There's an inset for author, but
the author name is needed in both reading order and file-as order, and
there's only one author inset.) One thought is to create custom insets, and
another is to ask for the information via the document settings.
- Intra-document navigation. In order to skip around within the document,
add bookmarks, etc., navigation information needs to be added to the
toc.ncx file within the EPUB archive. Which locations in the document
should be added to the list of navigable points is not obvious. First, I
read (here at http://www.gbenthien.net/Kindle%20and%20EPUB/ncx.html) that
some e-readers only work with at most one depth level--only parts, or only
chapters, or only sections, or whatever. I'm not sure whether this is
correct or not. Either way, we can't always assume what depth the user
wants in the table of contents--this is probably something we should ask.
It's probably easiest to pull the navigation info straight from the
document's table of contents, but I don't know if this info is available in
the exported XHTML file without appearing visibly.

What I'd like to implement at some point:
- optional conversion of images to SVG format
Note: Vector-based graphics scale better than raster-based graphics, making
them well-suited for electronic media.
Note: EPUB specifications require compliant e-readers to support SVG.
Note: Older versions of some browsers (primarily IE) don't support SVG.
Note: Preliminary searches turn up a package named dvisvgm (
http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
licensed under the GPL v3 or later.
- ability to split large XHTML files into smaller ones
Note: Splitting large XHTML files should boost the performance of the
converted EPUB documents.
- allow selection of an image for front cover artwork
Note: Amazon requires JPEG or TIFF format for front cover artwork.

I'd love to hear any thoughts, comments, and suggestions you all have,
especially if you encounter any bugs or see something important I'm
overlooking.

Thanks,
Josh

request for comments on EPUB exporting

[Josh Hieronymus]

Hi everyone,

I'm working on exporting LyX documents to EPUB as part of my Google Summer
of Code project, and I'd like to invite you to try out my current
implementation, which can be found in the "epub/master" branch of the gsoc
repository (g...@git.lyx.org:gsoc.git). The export process begins by
exporting the document to XHTML via LyXHTML, then converting the XHTML to
EPUB with the scripts in lib/scripts/epub.

Right now, documents will successfully export to EPUB 2.0.1, with the
following caveats:
- Almost all metadata fields (author, book id, etc.) are filled in with
default values. Only the title field is taken from the XHTML file from
which the EPUB is converted.
- No intra-document navigation is implemented; the document is just one
long page.
- MathML isn't part of the EPUB 2.0.1 standard, so the document output
settings should be set to output math as images.

What I'd like to implement soon:
- Extracting other metadata fields from the document. The required fields
are language, title, and identifier. The title field is taken from the
document, but not  the language or the identifier. I'm taking the title
from the first paragraph to use the "title" inset, but there aren't
corresponding insets for the other elements, so I'm not sure of the best
way or ways to get the rest of the info. (There's an inset for author, but
the author name is needed in both reading order and "file-as" order, and
there's only one author inset.) One thought is to create custom insets, and
another is to ask for the information via the document settings.
- Intra-document navigation. In order to skip around within the document,
add bookmarks, etc., navigation information needs to be added to the
toc.ncx file within the EPUB archive. Which locations in the document
should be added to the list of navigable points is not obvious. First, I
read (here at http://www.gbenthien.net/Kindle%20and%20EPUB/ncx.html) that
some e-readers only work with at most one depth level--only parts, or only
chapters, or only sections, or whatever. I'm not sure whether this is
correct or not. Either way, we can't always assume what depth the user
wants in the table of contents--this is probably something we should ask.
It's probably easiest to pull the navigation info straight from the
document's table of contents, but I don't know if this info is available in
the exported XHTML file without appearing visibly.

What I'd like to implement at some point:
- optional conversion of images to SVG format
Note: Vector-based graphics scale better than raster-based graphics, making
them well-suited for electronic media.
Note: EPUB specifications require compliant e-readers to support SVG.
Note: Older versions of some browsers (primarily IE) don't support SVG.
Note: Preliminary searches turn up a package named dvisvgm (
http://www.ctan.org/pkg/dvisvgm) that converts DVI to SVG, and it's
licensed under the GPL v3 or later.
- ability to split large XHTML files into smaller ones
Note: Splitting large XHTML files should boost the performance of the
converted EPUB documents.
- allow selection of an image for front cover artwork
Note: Amazon requires JPEG or TIFF format for front cover artwork.

I'd love to hear any thoughts, comments, and suggestions you all have,
especially if you encounter any bugs or see something important I'm
overlooking.

Thanks,
Josh

Re: comments with beamer on mac

[Uwe.Ade]

Hi Scott,

Thank you for the Top. I'll read the document and make some Tests ...

Uwe


Am 27.04.2013 um 18:54 schrieb Scott Kostyshak skost...@lyx.org:

 On Sat, Apr 27, 2013 at 6:01 AM, Uwe Ade uwe@gmx.de wrote:
 Hey Scott,
 
 http://mrunix.de/forums/showthread.php?t=66333
 
 describe a Way to get Notes as part of the PDF-Dokument.
 
 uwe
 
 Am 25.04.2013 um 12:09 schrieb Scott Kostyshak skost...@princeton.edu:
 
 On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,
 
 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea 
 how this works with lyx. With google I only find solutions with native 
 latex and not with lyx
 
 What are the solutions with LaTeX? Can you send an example that has
 worked for you with LaTeX?
 
 Scott
 
 Ah, and then you only connect a certain region on your laptop to the
 projector. It looks like this could be done in LyX (although not
 completely sure). Look in Help  Customization for how to get started
 making the layout for a module/local layout.
 
 Scott

Re: comments with beamer on mac

[Uwe.Ade]

Hi Scott,

Thank you for the Top. I'll read the document and make some Tests ...

Uwe


Am 27.04.2013 um 18:54 schrieb Scott Kostyshak skost...@lyx.org:

 On Sat, Apr 27, 2013 at 6:01 AM, Uwe Ade uwe@gmx.de wrote:
 Hey Scott,
 
 http://mrunix.de/forums/showthread.php?t=66333
 
 describe a Way to get Notes as part of the PDF-Dokument.
 
 uwe
 
 Am 25.04.2013 um 12:09 schrieb Scott Kostyshak skost...@princeton.edu:
 
 On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,
 
 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea 
 how this works with lyx. With google I only find solutions with native 
 latex and not with lyx
 
 What are the solutions with LaTeX? Can you send an example that has
 worked for you with LaTeX?
 
 Scott
 
 Ah, and then you only connect a certain region on your laptop to the
 projector. It looks like this could be done in LyX (although not
 completely sure). Look in Help  Customization for how to get started
 making the layout for a module/local layout.
 
 Scott

Re: comments with beamer on mac

[Uwe.Ade]

Hi Scott,

Thank you for the Top. I'll read the document and make some Tests ...

Uwe


Am 27.04.2013 um 18:54 schrieb Scott Kostyshak <skost...@lyx.org>:

> On Sat, Apr 27, 2013 at 6:01 AM, Uwe Ade <uwe@gmx.de> wrote:
>> Hey Scott,
>> 
>> http://mrunix.de/forums/showthread.php?t=66333
>> 
>> describe a Way to get Notes as part of the PDF-Dokument.
>> 
>> uwe
>> 
>> Am 25.04.2013 um 12:09 schrieb Scott Kostyshak <skost...@princeton.edu>:
>> 
>>> On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade <uwe@gmx.de> wrote:
>>>> Hello,
>>>> 
>>>> I use beamer form my lecturers. Now i want put my teacher comments on the 
>>>> side of the screen which is not shown an the Screen. Has someone  an idea 
>>>> how this works with lyx. With google I only find solutions with native 
>>>> latex and not with lyx
>>> 
>>> What are the solutions with LaTeX? Can you send an example that has
>>> worked for you with LaTeX?
>>> 
>>> Scott
> 
> Ah, and then you only connect a certain region on your laptop to the
> projector. It looks like this could be done in LyX (although not
> completely sure). Look in Help > Customization for how to get started
> making the layout for a module/local layout.
> 
> Scott

Re: comments with beamer on mac

[Uwe Ade]

Hey Scott,

http://mrunix.de/forums/showthread.php?t=66333

describe a Way to get Notes as part of the PDF-Dokument.

uwe

Am 25.04.2013 um 12:09 schrieb Scott Kostyshak skost...@princeton.edu:

 On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,
 
 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea 
 how this works with lyx. With google I only find solutions with native latex 
 and not with lyx
 
 What are the solutions with LaTeX? Can you send an example that has
 worked for you with LaTeX?
 
 Scott

Re: comments with beamer on mac

[Scott Kostyshak]

On Sat, Apr 27, 2013 at 6:01 AM, Uwe Ade uwe@gmx.de wrote:
 Hey Scott,

 http://mrunix.de/forums/showthread.php?t=66333

 describe a Way to get Notes as part of the PDF-Dokument.

 uwe

 Am 25.04.2013 um 12:09 schrieb Scott Kostyshak skost...@princeton.edu:

 On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,

 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea 
 how this works with lyx. With google I only find solutions with native 
 latex and not with lyx

 What are the solutions with LaTeX? Can you send an example that has
 worked for you with LaTeX?

 Scott


Ah, and then you only connect a certain region on your laptop to the
projector. It looks like this could be done in LyX (although not
completely sure). Look in Help  Customization for how to get started
making the layout for a module/local layout.

Scott

Re: comments with beamer on mac

[Uwe Ade]

Hey Scott,

http://mrunix.de/forums/showthread.php?t=66333

describe a Way to get Notes as part of the PDF-Dokument.

uwe

Am 25.04.2013 um 12:09 schrieb Scott Kostyshak skost...@princeton.edu:

 On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,
 
 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea 
 how this works with lyx. With google I only find solutions with native latex 
 and not with lyx
 
 What are the solutions with LaTeX? Can you send an example that has
 worked for you with LaTeX?
 
 Scott

Re: comments with beamer on mac

[Scott Kostyshak]

On Sat, Apr 27, 2013 at 6:01 AM, Uwe Ade uwe@gmx.de wrote:
 Hey Scott,

 http://mrunix.de/forums/showthread.php?t=66333

 describe a Way to get Notes as part of the PDF-Dokument.

 uwe

 Am 25.04.2013 um 12:09 schrieb Scott Kostyshak skost...@princeton.edu:

 On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,

 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea 
 how this works with lyx. With google I only find solutions with native 
 latex and not with lyx

 What are the solutions with LaTeX? Can you send an example that has
 worked for you with LaTeX?

 Scott


Ah, and then you only connect a certain region on your laptop to the
projector. It looks like this could be done in LyX (although not
completely sure). Look in Help  Customization for how to get started
making the layout for a module/local layout.

Scott

Re: comments with beamer on mac

[Uwe Ade]

Hey Scott,

http://mrunix.de/forums/showthread.php?t=66333

describe a Way to get Notes as part of the PDF-Dokument.

uwe

Am 25.04.2013 um 12:09 schrieb Scott Kostyshak <skost...@princeton.edu>:

> On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade <uwe@gmx.de> wrote:
>> Hello,
>> 
>> I use beamer form my lecturers. Now i want put my teacher comments on the 
>> side of the screen which is not shown an the Screen. Has someone  an idea 
>> how this works with lyx. With google I only find solutions with native latex 
>> and not with lyx
> 
> What are the solutions with LaTeX? Can you send an example that has
> worked for you with LaTeX?
> 
> Scott

Re: comments with beamer on mac

[Scott Kostyshak]

On Sat, Apr 27, 2013 at 6:01 AM, Uwe Ade <uwe@gmx.de> wrote:
> Hey Scott,
>
> http://mrunix.de/forums/showthread.php?t=66333
>
> describe a Way to get Notes as part of the PDF-Dokument.
>
> uwe
>
> Am 25.04.2013 um 12:09 schrieb Scott Kostyshak <skost...@princeton.edu>:
>
>> On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade <uwe@gmx.de> wrote:
>>> Hello,
>>>
>>> I use beamer form my lecturers. Now i want put my teacher comments on the 
>>> side of the screen which is not shown an the Screen. Has someone  an idea 
>>> how this works with lyx. With google I only find solutions with native 
>>> latex and not with lyx
>>
>> What are the solutions with LaTeX? Can you send an example that has
>> worked for you with LaTeX?
>>
>> Scott
>

Ah, and then you only connect a certain region on your laptop to the
projector. It looks like this could be done in LyX (although not
completely sure). Look in Help > Customization for how to get started
making the layout for a module/local layout.

Scott

Re: comments with beamer on mac

[Scott Kostyshak]

On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,

 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea how 
 this works with lyx. With google I only find solutions with native latex and 
 not with lyx

What are the solutions with LaTeX? Can you send an example that has
worked for you with LaTeX?

Scott

Re: comments with beamer on mac

[Scott Kostyshak]

On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade uwe@gmx.de wrote:
 Hello,

 I use beamer form my lecturers. Now i want put my teacher comments on the 
 side of the screen which is not shown an the Screen. Has someone  an idea how 
 this works with lyx. With google I only find solutions with native latex and 
 not with lyx

What are the solutions with LaTeX? Can you send an example that has
worked for you with LaTeX?

Scott

Re: comments with beamer on mac

[Scott Kostyshak]

On Tue, Apr 23, 2013 at 12:52 PM, Uwe Ade <uwe@gmx.de> wrote:
> Hello,
>
> I use beamer form my lecturers. Now i want put my teacher comments on the 
> side of the screen which is not shown an the Screen. Has someone  an idea how 
> this works with lyx. With google I only find solutions with native latex and 
> not with lyx

What are the solutions with LaTeX? Can you send an example that has
worked for you with LaTeX?

Scott

comments with beamer on mac

[Uwe Ade]

Hello,

I use beamer form my lecturers. Now i want put my teacher comments on the side 
of the screen which is not shown an the Screen. Has someone  an idea how this 
works with lyx. With google I only find solutions with native latex and not 
with lyx

Thanks

uwe

comments with beamer on mac

[Uwe Ade]

Hello,

I use beamer form my lecturers. Now i want put my teacher comments on the side 
of the screen which is not shown an the Screen. Has someone  an idea how this 
works with lyx. With google I only find solutions with native latex and not 
with lyx

Thanks

uwe

comments with beamer on mac

[Uwe Ade]

Hello,

I use beamer form my lecturers. Now i want put my teacher comments on the side 
of the screen which is not shown an the Screen. Has someone  an idea how this 
works with lyx. With google I only find solutions with native latex and not 
with lyx

Thanks

uwe

margin comments in a pdf output file

[ehud.kaplan]

It is often desirable to leave comments in the margins of a document.  
The various TODOnotes facilities work fine, but I have now found that 
they do NOT work in the abstract environment.  Is this a feature or a bug?


EK



--
Ehud Kaplan,

margin comments in a pdf output file

[ehud.kaplan]

It is often desirable to leave comments in the margins of a document.  
The various TODOnotes facilities work fine, but I have now found that 
they do NOT work in the abstract environment.  Is this a feature or a bug?


EK



--
Ehud Kaplan,

margin comments in a pdf output file

[ehud.kaplan]

It is often desirable to leave comments in the margins of a document.  
The various TODOnotes facilities work fine, but I have now found that 
they do NOT work in the abstract environment.  Is this a feature or a bug?


EK



--
Ehud Kaplan,

Export LyX notes/comments

[Michael Bach]

Dear LyX Users and Developers,

I understand that notes are only for the LyX documents, not the exported 
pdf documents. The comment inset exports to comment environments in tex.


I am using the presentation (beamer) class and wondered how to use one 
of the insets to export to a \note macro. Did someone set that up 
already? This would be nice because of the option to include the notes 
in the export if one wants to and also to e.g. use the nice enumerate 
markup in LyX.


Michael Bach

Re: Export LyX notes/comments

[Richard Heck]

On 08/28/2012 09:23 AM, Michael Bach wrote:

Dear LyX Users and Developers,

I understand that notes are only for the LyX documents, not the 
exported pdf documents. The comment inset exports to comment 
environments in tex.


I am using the presentation (beamer) class and wondered how to use one 
of the insets to export to a \note macro. Did someone set that up 
already? This would be nice because of the option to include the notes 
in the export if one wants to and also to e.g. use the nice enumerate 
markup in LyX.


Just create a new inset by copying, e.g., the comment inset, and then 
changing what needs changing. E.g., change the LaTeXName to note, and 
the name of the inset to My Note.


Richard

Re: Export LyX notes/comments

[Michael Bach]

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to note, and
the name of the inset to My Note.



Thanks for the hint Richard. I read in the `Customization´ manual that I 
could add this on a per-file basis via the `Local Layout´. I tried that, 
validated it via button (validate ok) and can find it now in the 
paragraph style dropdown list.


Style MyNote
  MarginDynamic
  LatexType Command
  LatexName note
  Labelstring   MyNote:
End

I followed your advice plus changed LatexType to `Command´. I can now 
find it in the paragraph style dropdown list at the very end.


This works well for simple \note{stuff}, but I would like to be able to 
have an inset that I can insert after an itemize bullet point so that 
the LaTeX looks like


\begin{itemize}
\item one
\item2- two \note[item]2{Note about two}
\end{itemize}

So I went ahead, searched in the docs and the web. Then I tried to 
create an inset:


InsetLayout Note:MyNote
  LyXType   custom
  LabelString   MyNote:
  Decorationclassic
  MarginDynamic
  LatexType command
  LatexName note[item]
  NextNoIndent  1
  LeftMarginMMM
  RightMargin   MMM
  Align Block
  AlignPossible Block, Left, Right, Center
  LabelSep  :x
  LabelFont
Shape   Italic
Series  Bold
Color   collapsable
  EndFont

  TextFont
Color   magenta
Shape   Italic
  EndFont
End

But I cannot find it under Insert  Note  ...

Where am I wrong?

Michael

Re: Export LyX notes/comments

[Michael Bach]

On 8/28/2012 5:54 PM, Michael Bach wrote:

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to note, and
the name of the inset to My Note.



Thanks for the hint Richard. I read in the `Customization´ manual that I
could add this on a per-file basis via the `Local Layout´. I tried that,
validated it via button (validate ok) and can find it now in the
paragraph style dropdown list.

Style MyNote
   MarginDynamic
   LatexTypeCommand
   LatexNamenote
   LabelstringMyNote:
End

I followed your advice plus changed LatexType to `Command´. I can now
find it in the paragraph style dropdown list at the very end.

This works well for simple \note{stuff}, but I would like to be able to
have an inset that I can insert after an itemize bullet point so that
the LaTeX looks like

\begin{itemize}
\item one
\item2- two \note[item]2{Note about two}
\end{itemize}

So I went ahead, searched in the docs and the web. Then I tried to
create an inset:

InsetLayout Note:MyNote
   LyXType custom
   LabelStringMyNote:
   Decorationclassic
   MarginDynamic
   LatexTypecommand
   LatexNamenote[item]
   NextNoIndent1
   LeftMarginMMM
   RightMarginMMM
   AlignBlock
   AlignPossibleBlock, Left, Right, Center
   LabelSep:x
   LabelFont
ShapeItalic
SeriesBold
Colorcollapsable
   EndFont

   TextFont
 Colormagenta
 ShapeItalic
   EndFont
End

But I cannot find it under Insert  Note  ...

Where am I wrong?

Michael




Never Mind. After a bit of experimenting, I got it to work using:

InsetLayout Flex:MyNote
  LyXType   custom
  LabelString   MyNote
  Decorationclassic
  MarginDynamic
  LatexType command
  LatexName note[item]
  LabelFont
Shape   Italic
Series  Bold
Color   collapsable
  EndFont
  TextFont
Color   magenta
Shape   Italic
  EndFont
End

Thanks again for your comment

Michael

Re: Export LyX notes/comments

[Richard Heck]

On 08/28/2012 11:54 AM, Michael Bach wrote:

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to note, and
the name of the inset to My Note.



[snip]

Then I tried to create an inset:

InsetLayout Note:MyNote
  LyXType custom
  LabelStringMyNote:
  Decorationclassic
  MarginDynamic
  LatexTypecommand
  LatexNamenote[item]
  NextNoIndent1
  LeftMarginMMM
  RightMarginMMM
  AlignBlock
  AlignPossibleBlock, Left, Right, Center
  LabelSep:x
  LabelFont
ShapeItalic
SeriesBold
Colorcollapsable
  EndFont

  TextFont
Colormagenta
ShapeItalic
  EndFont
End

But I cannot find it under Insert  Note  ...


It will be under InsertCustom Inset.

rh

Export LyX notes/comments

[Michael Bach]

Dear LyX Users and Developers,

I understand that notes are only for the LyX documents, not the exported 
pdf documents. The comment inset exports to comment environments in tex.


I am using the presentation (beamer) class and wondered how to use one 
of the insets to export to a \note macro. Did someone set that up 
already? This would be nice because of the option to include the notes 
in the export if one wants to and also to e.g. use the nice enumerate 
markup in LyX.


Michael Bach

Re: Export LyX notes/comments

[Richard Heck]

On 08/28/2012 09:23 AM, Michael Bach wrote:

Dear LyX Users and Developers,

I understand that notes are only for the LyX documents, not the 
exported pdf documents. The comment inset exports to comment 
environments in tex.


I am using the presentation (beamer) class and wondered how to use one 
of the insets to export to a \note macro. Did someone set that up 
already? This would be nice because of the option to include the notes 
in the export if one wants to and also to e.g. use the nice enumerate 
markup in LyX.


Just create a new inset by copying, e.g., the comment inset, and then 
changing what needs changing. E.g., change the LaTeXName to note, and 
the name of the inset to My Note.


Richard

Re: Export LyX notes/comments

[Michael Bach]

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to note, and
the name of the inset to My Note.



Thanks for the hint Richard. I read in the `Customization´ manual that I 
could add this on a per-file basis via the `Local Layout´. I tried that, 
validated it via button (validate ok) and can find it now in the 
paragraph style dropdown list.


Style MyNote
  MarginDynamic
  LatexType Command
  LatexName note
  Labelstring   MyNote:
End

I followed your advice plus changed LatexType to `Command´. I can now 
find it in the paragraph style dropdown list at the very end.


This works well for simple \note{stuff}, but I would like to be able to 
have an inset that I can insert after an itemize bullet point so that 
the LaTeX looks like


\begin{itemize}
\item one
\item2- two \note[item]2{Note about two}
\end{itemize}

So I went ahead, searched in the docs and the web. Then I tried to 
create an inset:


InsetLayout Note:MyNote
  LyXType   custom
  LabelString   MyNote:
  Decorationclassic
  MarginDynamic
  LatexType command
  LatexName note[item]
  NextNoIndent  1
  LeftMarginMMM
  RightMargin   MMM
  Align Block
  AlignPossible Block, Left, Right, Center
  LabelSep  :x
  LabelFont
Shape   Italic
Series  Bold
Color   collapsable
  EndFont

  TextFont
Color   magenta
Shape   Italic
  EndFont
End

But I cannot find it under Insert  Note  ...

Where am I wrong?

Michael

Re: Export LyX notes/comments

[Michael Bach]

On 8/28/2012 5:54 PM, Michael Bach wrote:

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to note, and
the name of the inset to My Note.



Thanks for the hint Richard. I read in the `Customization´ manual that I
could add this on a per-file basis via the `Local Layout´. I tried that,
validated it via button (validate ok) and can find it now in the
paragraph style dropdown list.

Style MyNote
   MarginDynamic
   LatexTypeCommand
   LatexNamenote
   LabelstringMyNote:
End

I followed your advice plus changed LatexType to `Command´. I can now
find it in the paragraph style dropdown list at the very end.

This works well for simple \note{stuff}, but I would like to be able to
have an inset that I can insert after an itemize bullet point so that
the LaTeX looks like

\begin{itemize}
\item one
\item2- two \note[item]2{Note about two}
\end{itemize}

So I went ahead, searched in the docs and the web. Then I tried to
create an inset:

InsetLayout Note:MyNote
   LyXType custom
   LabelStringMyNote:
   Decorationclassic
   MarginDynamic
   LatexTypecommand
   LatexNamenote[item]
   NextNoIndent1
   LeftMarginMMM
   RightMarginMMM
   AlignBlock
   AlignPossibleBlock, Left, Right, Center
   LabelSep:x
   LabelFont
ShapeItalic
SeriesBold
Colorcollapsable
   EndFont

   TextFont
 Colormagenta
 ShapeItalic
   EndFont
End

But I cannot find it under Insert  Note  ...

Where am I wrong?

Michael




Never Mind. After a bit of experimenting, I got it to work using:

InsetLayout Flex:MyNote
  LyXType   custom
  LabelString   MyNote
  Decorationclassic
  MarginDynamic
  LatexType command
  LatexName note[item]
  LabelFont
Shape   Italic
Series  Bold
Color   collapsable
  EndFont
  TextFont
Color   magenta
Shape   Italic
  EndFont
End

Thanks again for your comment

Michael

Re: Export LyX notes/comments

[Richard Heck]

On 08/28/2012 11:54 AM, Michael Bach wrote:

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to note, and
the name of the inset to My Note.



[snip]

Then I tried to create an inset:

InsetLayout Note:MyNote
  LyXType custom
  LabelStringMyNote:
  Decorationclassic
  MarginDynamic
  LatexTypecommand
  LatexNamenote[item]
  NextNoIndent1
  LeftMarginMMM
  RightMarginMMM
  AlignBlock
  AlignPossibleBlock, Left, Right, Center
  LabelSep:x
  LabelFont
ShapeItalic
SeriesBold
Colorcollapsable
  EndFont

  TextFont
Colormagenta
ShapeItalic
  EndFont
End

But I cannot find it under Insert  Note  ...


It will be under InsertCustom Inset.

rh

Export LyX notes/comments

[Michael Bach]

Dear LyX Users and Developers,

I understand that notes are only for the LyX documents, not the exported 
pdf documents. The comment inset exports to comment environments in tex.


I am using the presentation (beamer) class and wondered how to use one 
of the insets to export to a \note macro. Did someone set that up 
already? This would be nice because of the option to include the notes 
in the export if one wants to and also to e.g. use the nice enumerate 
markup in LyX.


Michael Bach

Re: Export LyX notes/comments

[Richard Heck]

On 08/28/2012 09:23 AM, Michael Bach wrote:

Dear LyX Users and Developers,

I understand that notes are only for the LyX documents, not the 
exported pdf documents. The comment inset exports to comment 
environments in tex.


I am using the presentation (beamer) class and wondered how to use one 
of the insets to export to a \note macro. Did someone set that up 
already? This would be nice because of the option to include the notes 
in the export if one wants to and also to e.g. use the nice enumerate 
markup in LyX.


Just create a new inset by copying, e.g., the comment inset, and then 
changing what needs changing. E.g., change the LaTeXName to "note", and 
the name of the inset to "My Note".


Richard

Re: Export LyX notes/comments

[Michael Bach]

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to "note", and
the name of the inset to "My Note".



Thanks for the hint Richard. I read in the `Customization´ manual that I 
could add this on a per-file basis via the `Local Layout´. I tried that, 
validated it via button (validate ok) and can find it now in the 
paragraph style dropdown list.


Style MyNote
  MarginDynamic
  LatexType Command
  LatexName note
  Labelstring   "MyNote:"
End

I followed your advice plus changed LatexType to `Command´. I can now 
find it in the paragraph style dropdown list at the very end.


This works well for simple \note{stuff}, but I would like to be able to 
have an inset that I can insert after an itemize bullet point so that 
the LaTeX looks like


\begin{itemize}
\item one
\item<2-> two \note[item]<2>{Note about two}
\end{itemize}

So I went ahead, searched in the docs and the web. Then I tried to 
create an inset:


InsetLayout "Note:MyNote"
  LyXType   custom
  LabelString   "MyNote:"
  Decorationclassic
  MarginDynamic
  LatexType command
  LatexName note[item]
  NextNoIndent  1
  LeftMarginMMM
  RightMargin   MMM
  Align Block
  AlignPossible Block, Left, Right, Center
  LabelSep  :x
  LabelFont
Shape   Italic
Series  Bold
Color   collapsable
  EndFont

  TextFont
Color   magenta
Shape   Italic
  EndFont
End

But I cannot find it under Insert > Note > ...

Where am I wrong?

Michael

Re: Export LyX notes/comments

[Michael Bach]

On 8/28/2012 5:54 PM, Michael Bach wrote:

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to "note", and
the name of the inset to "My Note".



Thanks for the hint Richard. I read in the `Customization´ manual that I
could add this on a per-file basis via the `Local Layout´. I tried that,
validated it via button (validate ok) and can find it now in the
paragraph style dropdown list.

Style MyNote
   MarginDynamic
   LatexTypeCommand
   LatexNamenote
   Labelstring"MyNote:"
End

I followed your advice plus changed LatexType to `Command´. I can now
find it in the paragraph style dropdown list at the very end.

This works well for simple \note{stuff}, but I would like to be able to
have an inset that I can insert after an itemize bullet point so that
the LaTeX looks like

\begin{itemize}
\item one
\item<2-> two \note[item]<2>{Note about two}
\end{itemize}

So I went ahead, searched in the docs and the web. Then I tried to
create an inset:

InsetLayout "Note:MyNote"
   LyXType custom
   LabelString"MyNote:"
   Decorationclassic
   MarginDynamic
   LatexTypecommand
   LatexNamenote[item]
   NextNoIndent1
   LeftMarginMMM
   RightMarginMMM
   AlignBlock
   AlignPossibleBlock, Left, Right, Center
   LabelSep:x
   LabelFont
ShapeItalic
SeriesBold
Colorcollapsable
   EndFont

   TextFont
 Colormagenta
 ShapeItalic
   EndFont
End

But I cannot find it under Insert > Note > ...

Where am I wrong?

Michael




Never Mind. After a bit of experimenting, I got it to work using:

InsetLayout "Flex:MyNote"
  LyXType   custom
  LabelString   "MyNote"
  Decorationclassic
  MarginDynamic
  LatexType command
  LatexName note[item]
  LabelFont
Shape   Italic
Series  Bold
Color   collapsable
  EndFont
  TextFont
Color   magenta
Shape   Italic
  EndFont
End

Thanks again for your comment

Michael

Re: Export LyX notes/comments

[Richard Heck]

On 08/28/2012 11:54 AM, Michael Bach wrote:

On 8/28/2012 4:15 PM, Richard Heck wrote:


Just create a new inset by copying, e.g., the comment inset, and then
changing what needs changing. E.g., change the LaTeXName to "note", and
the name of the inset to "My Note".



[snip]

Then I tried to create an inset:

InsetLayout "Note:MyNote"
  LyXType custom
  LabelString"MyNote:"
  Decorationclassic
  MarginDynamic
  LatexTypecommand
  LatexNamenote[item]
  NextNoIndent1
  LeftMarginMMM
  RightMarginMMM
  AlignBlock
  AlignPossibleBlock, Left, Right, Center
  LabelSep:x
  LabelFont
ShapeItalic
SeriesBold
Colorcollapsable
  EndFont

  TextFont
Colormagenta
ShapeItalic
  EndFont
End

But I cannot find it under Insert > Note > ...


It will be under Insert>Custom Inset.

rh

Theorists labbook package - comments and help solicitation

[Peter Novak]

Hello LyX users and developers,
my name is Peter Novak and since around 2001 I am a (passionate) user of
LyX (as also documented by my bug reports and feature requests at
http://www.lyx.org/trac/search?q=walkmanyi), though I did not read the
LyX-users mailing lists till now.

To scratch one of many itches of my professional life, I created an
unpolished quick-hack LaTeX/LyX package aimed at creation and
manipulation of lab books for theorists. I include a motivation for
writing the package below and discuss it in the accompanying notes to
the package accessible from here:
http://www.aronde.net/theolabbook.tar.gz (readme.pdf/lyx) file.

Hereby I would like to solicit comments from the LyX users community,
which includes also many research professionals, especially in applied
mathematics and computer science, which is what I care for myself. The
best outcome of this announcement for me would be getting help with
improvements of the package - these are also briefly discussed in the
readme notes to the package.

Below, I am including the motivation for writing the package, which
(hopefully) illuminates the problem I want to solve. In the case
somebody finds this kind of work useful, I would be happy to give back
something to the LyX community as I am definitely grateful to the LyX
team for providing this great tool I rely on in my every-day work since
many years.

Best regards,

Peter.



*** Motivation
Keeping a research lab-book is a daily bread for many researchers, such
as experimental physicists. It helps them to keep track of their
experiments, equipment, results, as well as capture their ideas about
the stuff they work on. Typically a researcher, or a team, keeps one
lab-book per project. This suits the typical workflow of experimental
research, where the evolution of a project can be captured as a (more,
or less) linear stream of notes in a lab book.

Scientists in more theoretical disciplines, such as (applied)
mathematics, or in computer science often deal with several intertwined
and related, yet distinct topics at once. In a consequence the evolution
of their thoughts from inception to a finished paper is often rather
non-linear, rather meandering stream of ideas and notes, which are
difficult to order linearly before the idea/project is ripe enough and
finally “clicks in”. Yet, due to this non-linearity, researchers in
theoretical fields are perhaps even more in a need to capture their
research notes so that they do not get lost. There is definitely a need
for flexible tools and workflows to help theorists capture, organize and
expose their ideas and research notes.

Theolabbook is an attempt to solve this problem for users which center
their daily life around TeX related tools, which are especially useful
when one deals with mathematics. The central requirements driving the
development of the theolabbook package are the following:

1.- notes should be media-rich in terms to the extent TeX allows. That is,
should easily include math, pictures, figures, etc.;
2.- notes can be scribbled in a linear fashion, their order should be
irrelevant;
3.- the package should provide tools for rapid and simple organization
and re-organization of the set of notes, result of which is primarily a
document, the lab-book instance;
4.- the editing of the notes should be as simple as possible, yet as good
as possible. This is a no-brainer, LyX is the editor of choice;
5.- the package should facilitate also publishing of the notes on the web
to support the open notebook research
(https://en.wikipedia.org/wiki/Open_notebook_science).

As of publishing this document, the package implements requirements 1-3
(supported only in Unix environments, for reasons, see the internal
philosophy of the package in the readme document), to a large extent
also 4 and completely lacks support for 5.

By publishing the package as is together with the readme ntroductory
text, my hope is to firstly, receive comments, suggestions, and
criticism from interested LyX users; and secondly, solicit help with
improvements, improving upon the implementation of the requirement 4 and
working out 5.

The rest of the readme document is structured as follows: after a brief
discussion of related work and existing tools for the problem of
capturing and organization of a non-linear stream of notes, I explain
the guts of the theolabbook package, provide a step-by-step installation
instructions, explain included examples and finally discuss its
shortcomings and points where I need help from others.


*** Related work
The observation of non-linearity of research notes in many disciplines
is of course a well known issue. Some of the popular solutions to the
problem is the use of wikis and blogs (see
https://en.wikipedia.org/wiki/Open_research,
https://en.wikipedia.org/wiki/Open_notebook_science). While blogs
facilitate publication and open discussion of research

Theorists labbook package - comments and help solicitation

[Peter Novak]

Hello LyX users and developers,
my name is Peter Novak and since around 2001 I am a (passionate) user of
LyX (as also documented by my bug reports and feature requests at
http://www.lyx.org/trac/search?q=walkmanyi), though I did not read the
LyX-users mailing lists till now.

To scratch one of many itches of my professional life, I created an
unpolished quick-hack LaTeX/LyX package aimed at creation and
manipulation of lab books for theorists. I include a motivation for
writing the package below and discuss it in the accompanying notes to
the package accessible from here:
http://www.aronde.net/theolabbook.tar.gz (readme.pdf/lyx) file.

Hereby I would like to solicit comments from the LyX users community,
which includes also many research professionals, especially in applied
mathematics and computer science, which is what I care for myself. The
best outcome of this announcement for me would be getting help with
improvements of the package - these are also briefly discussed in the
readme notes to the package.

Below, I am including the motivation for writing the package, which
(hopefully) illuminates the problem I want to solve. In the case
somebody finds this kind of work useful, I would be happy to give back
something to the LyX community as I am definitely grateful to the LyX
team for providing this great tool I rely on in my every-day work since
many years.

Best regards,

Peter.



*** Motivation
Keeping a research lab-book is a daily bread for many researchers, such
as experimental physicists. It helps them to keep track of their
experiments, equipment, results, as well as capture their ideas about
the stuff they work on. Typically a researcher, or a team, keeps one
lab-book per project. This suits the typical workflow of experimental
research, where the evolution of a project can be captured as a (more,
or less) linear stream of notes in a lab book.

Scientists in more theoretical disciplines, such as (applied)
mathematics, or in computer science often deal with several intertwined
and related, yet distinct topics at once. In a consequence the evolution
of their thoughts from inception to a finished paper is often rather
non-linear, rather meandering stream of ideas and notes, which are
difficult to order linearly before the idea/project is ripe enough and
finally “clicks in”. Yet, due to this non-linearity, researchers in
theoretical fields are perhaps even more in a need to capture their
research notes so that they do not get lost. There is definitely a need
for flexible tools and workflows to help theorists capture, organize and
expose their ideas and research notes.

Theolabbook is an attempt to solve this problem for users which center
their daily life around TeX related tools, which are especially useful
when one deals with mathematics. The central requirements driving the
development of the theolabbook package are the following:

1.- notes should be media-rich in terms to the extent TeX allows. That is,
should easily include math, pictures, figures, etc.;
2.- notes can be scribbled in a linear fashion, their order should be
irrelevant;
3.- the package should provide tools for rapid and simple organization
and re-organization of the set of notes, result of which is primarily a
document, the lab-book instance;
4.- the editing of the notes should be as simple as possible, yet as good
as possible. This is a no-brainer, LyX is the editor of choice;
5.- the package should facilitate also publishing of the notes on the web
to support the open notebook research
(https://en.wikipedia.org/wiki/Open_notebook_science).

As of publishing this document, the package implements requirements 1-3
(supported only in Unix environments, for reasons, see the internal
philosophy of the package in the readme document), to a large extent
also 4 and completely lacks support for 5.

By publishing the package as is together with the readme ntroductory
text, my hope is to firstly, receive comments, suggestions, and
criticism from interested LyX users; and secondly, solicit help with
improvements, improving upon the implementation of the requirement 4 and
working out 5.

The rest of the readme document is structured as follows: after a brief
discussion of related work and existing tools for the problem of
capturing and organization of a non-linear stream of notes, I explain
the guts of the theolabbook package, provide a step-by-step installation
instructions, explain included examples and finally discuss its
shortcomings and points where I need help from others.


*** Related work
The observation of non-linearity of research notes in many disciplines
is of course a well known issue. Some of the popular solutions to the
problem is the use of wikis and blogs (see
https://en.wikipedia.org/wiki/Open_research,
https://en.wikipedia.org/wiki/Open_notebook_science). While blogs
facilitate publication and open discussion of research

Theorists labbook package - comments and help solicitation

[Peter Novak]

Hello LyX users and developers,
my name is Peter Novak and since around 2001 I am a (passionate) user of
LyX (as also documented by my bug reports and feature requests at
http://www.lyx.org/trac/search?q=walkmanyi), though I did not read the
LyX-users mailing lists till now.

To scratch one of many itches of my professional life, I created an
unpolished quick-hack LaTeX/LyX package aimed at creation and
manipulation of lab books for theorists. I include a motivation for
writing the package below and discuss it in the accompanying notes to
the package accessible from here:
http://www.aronde.net/theolabbook.tar.gz (readme.pdf/lyx) file.

Hereby I would like to solicit comments from the LyX users community,
which includes also many research professionals, especially in applied
mathematics and computer science, which is what I care for myself. The
best outcome of this announcement for me would be getting help with
improvements of the package - these are also briefly discussed in the
readme notes to the package.

Below, I am including the motivation for writing the package, which
(hopefully) illuminates the problem I want to solve. In the case
somebody finds this kind of work useful, I would be happy to give back
something to the LyX community as I am definitely grateful to the LyX
team for providing this great tool I rely on in my every-day work since
many years.

Best regards,

Peter.



*** Motivation
Keeping a research lab-book is a daily bread for many researchers, such
as experimental physicists. It helps them to keep track of their
experiments, equipment, results, as well as capture their ideas about
the stuff they work on. Typically a researcher, or a team, keeps one
lab-book per project. This suits the typical workflow of experimental
research, where the evolution of a project can be captured as a (more,
or less) linear stream of notes in a lab book.

Scientists in more theoretical disciplines, such as (applied)
mathematics, or in computer science often deal with several intertwined
and related, yet distinct topics at once. In a consequence the evolution
of their thoughts from inception to a finished paper is often rather
non-linear, rather meandering stream of ideas and notes, which are
difficult to order linearly before the idea/project is ripe enough and
finally “clicks in”. Yet, due to this non-linearity, researchers in
theoretical fields are perhaps even more in a need to capture their
research notes so that they do not get lost. There is definitely a need
for flexible tools and workflows to help theorists capture, organize and
expose their ideas and research notes.

Theolabbook is an attempt to solve this problem for users which center
their daily life around TeX related tools, which are especially useful
when one deals with mathematics. The central requirements driving the
development of the theolabbook package are the following:

1.- notes should be media-rich in terms to the extent TeX allows. That is,
should easily include math, pictures, figures, etc.;
2.- notes can be scribbled in a linear fashion, their order should be
irrelevant;
3.- the package should provide tools for rapid and simple organization
and re-organization of the set of notes, result of which is primarily a
document, the lab-book instance;
4.- the editing of the notes should be as simple as possible, yet as good
as possible. This is a no-brainer, LyX is the editor of choice;
5.- the package should facilitate also publishing of the notes on the web
to support the open notebook research
(https://en.wikipedia.org/wiki/Open_notebook_science).

As of publishing this document, the package implements requirements 1-3
(supported only in Unix environments, for reasons, see the internal
philosophy of the package in the readme document), to a large extent
also 4 and completely lacks support for 5.

By publishing the package as is together with the readme ntroductory
text, my hope is to firstly, receive comments, suggestions, and
criticism from interested LyX users; and secondly, solicit help with
improvements, improving upon the implementation of the requirement 4 and
working out 5.

The rest of the readme document is structured as follows: after a brief
discussion of related work and existing tools for the problem of
capturing and organization of a non-linear stream of notes, I explain
the guts of the theolabbook package, provide a step-by-step installation
instructions, explain included examples and finally discuss its
shortcomings and points where I need help from others.


*** Related work
The observation of non-linearity of research notes in many disciplines
is of course a well known issue. Some of the popular solutions to the
problem is the use of wikis and blogs (see
https://en.wikipedia.org/wiki/Open_research,
https://en.wikipedia.org/wiki/Open_notebook_science). While blogs
facilitate publication and open discussion of research

Re: Pass LyX comments through eLyXer?

[Guenter Milde]

On 2011-12-06, Richard Heck wrote:
 On 12/06/2011 11:54 AM, Steve Litt wrote:
 On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?

 Code for the document header can be added via Local Layout, e.g.:

 AddToHTMLPreamble
 style type=text/css
 // css commands here
 /style
 EndPreamble

 You can put whatever you like there. JavaScript, meta tags, whatever.

I see. 

However, it strikes me as an unbalanced approach.

With the local module GUI in plaxe, maybe we should either

* remove the LaTeX preamble (and use Local Layout with AddToPreamble
  instead), or
* add a HTML Preamble tab

so that the output options are treated equal.

Günter

Re: Pass LyX comments through eLyXer?

[Liviu Andronic]

On Wed, Dec 7, 2011 at 9:28 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2011-12-06, Richard Heck wrote:
 On 12/06/2011 11:54 AM, Steve Litt wrote:
 On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?

 Code for the document header can be added via Local Layout, e.g.:

 AddToHTMLPreamble
     style type=text/css
         // css commands here
     /style
 EndPreamble

 You can put whatever you like there. JavaScript, meta tags, whatever.

 I see.

 However, it strikes me as an unbalanced approach.

 With the local module GUI in plaxe, maybe we should either

 * remove the LaTeX preamble (and use Local Layout with AddToPreamble
  instead), or
 * add a HTML Preamble tab

This second approach seems better. Since we natively support both
LaTeX and HTML output, and apparently both have a potential need for a
Preamble, then it stands to reason to have two different Preambles via
a 'tab' or a 'combobox': HTML output doesn't use the LaTeX Preamble
and vice versa.

Regards
Liviu


 so that the output options are treated equal.

 Günter




-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Pass LyX comments through eLyXer?

[Guenter Milde]

On 2011-12-06, Richard Heck wrote:
 On 12/06/2011 11:54 AM, Steve Litt wrote:
 On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?

 Code for the document header can be added via Local Layout, e.g.:

 AddToHTMLPreamble
 style type=text/css
 // css commands here
 /style
 EndPreamble

 You can put whatever you like there. JavaScript, meta tags, whatever.

I see. 

However, it strikes me as an unbalanced approach.

With the local module GUI in plaxe, maybe we should either

* remove the LaTeX preamble (and use Local Layout with AddToPreamble
  instead), or
* add a HTML Preamble tab

so that the output options are treated equal.

Günter

Re: Pass LyX comments through eLyXer?

[Liviu Andronic]

On Wed, Dec 7, 2011 at 9:28 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2011-12-06, Richard Heck wrote:
 On 12/06/2011 11:54 AM, Steve Litt wrote:
 On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?

 Code for the document header can be added via Local Layout, e.g.:

 AddToHTMLPreamble
     style type=text/css
         // css commands here
     /style
 EndPreamble

 You can put whatever you like there. JavaScript, meta tags, whatever.

 I see.

 However, it strikes me as an unbalanced approach.

 With the local module GUI in plaxe, maybe we should either

 * remove the LaTeX preamble (and use Local Layout with AddToPreamble
  instead), or
 * add a HTML Preamble tab

This second approach seems better. Since we natively support both
LaTeX and HTML output, and apparently both have a potential need for a
Preamble, then it stands to reason to have two different Preambles via
a 'tab' or a 'combobox': HTML output doesn't use the LaTeX Preamble
and vice versa.

Regards
Liviu


 so that the output options are treated equal.

 Günter




-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Pass LyX comments through eLyXer?

[Guenter Milde]

On 2011-12-06, Richard Heck wrote:
> On 12/06/2011 11:54 AM, Steve Litt wrote:
>> On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

>>> As LyX now offers native HTML export,
>>> is there an equivalent to Document>Settings>LaTeX preamble
>>> for "raw" HTML code in the document header?

> Code for the document header can be added via Local Layout, e.g.:

> AddToHTMLPreamble
> 
> // css commands here
> 
> EndPreamble

> You can put whatever you like there. JavaScript, meta tags, whatever.

I see. 

However, it strikes me as an unbalanced approach.

With the "local module" GUI in plaxe, maybe we should either

* remove the "LaTeX preamble" (and use Local Layout with AddToPreamble
  instead), or
* add a "HTML Preamble" tab

so that the output options are treated equal.

Günter

Re: Pass LyX comments through eLyXer?

[Liviu Andronic]

On Wed, Dec 7, 2011 at 9:28 AM, Guenter Milde  wrote:
> On 2011-12-06, Richard Heck wrote:
>> On 12/06/2011 11:54 AM, Steve Litt wrote:
>>> On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:
>
 As LyX now offers native HTML export,
 is there an equivalent to Document>Settings>LaTeX preamble
 for "raw" HTML code in the document header?
>
>> Code for the document header can be added via Local Layout, e.g.:
>
>> AddToHTMLPreamble
>>     
>>         // css commands here
>>     
>> EndPreamble
>
>> You can put whatever you like there. JavaScript, meta tags, whatever.
>
> I see.
>
> However, it strikes me as an unbalanced approach.
>
> With the "local module" GUI in plaxe, maybe we should either
>
> * remove the "LaTeX preamble" (and use Local Layout with AddToPreamble
>  instead), or
> * add a "HTML Preamble" tab
>
This second approach seems better. Since we natively support both
LaTeX and HTML output, and apparently both have a potential need for a
Preamble, then it stands to reason to have two different Preambles via
a 'tab' or a 'combobox': HTML output doesn't use the LaTeX Preamble
and vice versa.

Regards
Liviu


> so that the output options are treated equal.
>
> Günter
>



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Pass LyX comments through eLyXer?

[Guenter Milde]

On 2011-12-06, Steve Litt wrote:
 Hi Alex,

 I found that my LyX comments don't get through to the finished HTML 
 file, and eLyXer's Options class appears to have no option for passing 
 through LyX comments.

 How difficult would it be to add code so there's an option to convert 
 LyX comments to !-- HTML comments --? Comments would be an excellent 
 way to pass through eBook-only data, without it showing up in a book 
 printed from the same LyX file.

IMO, LyX notes are just for LyX - they are also stripped from the LaTeX.

OTOH, Comments (InsertNoteComment) are put as comments in the LaTeX and
should be put in the HTML, too.

In the *.lyx file, comments look like:

\begin_inset Note Comment
status open

\begin_layout Plain Layout
a comment
\end_layout

\end_inset


 If it's too hard to do, or if there's not enough time to do it, I can 
 probably make a small program to scoop out the specific comment that 
 passes the eBook metadata, and give that information to the post-
 processor. The post-processor already adds pagefeeds to every h1 
 item in the HTML file and captures the Title, Author and Date but 
 doesn't print them.


As LyX now offers native HTML export,
is there an equivalent to DocumentSettingsLaTeX preamble
for raw HTML code in the document header?

Günter

Re: Pass LyX comments through eLyXer?

[Alex Fernandez]

Hi, Steve and Guenter,

On Tue, Dec 6, 2011 at 10:46 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2011-12-06, Steve Litt wrote:
 Hi Alex,

 I found that my LyX comments don't get through to the finished HTML
 file, and eLyXer's Options class appears to have no option for passing
 through LyX comments.

 How difficult would it be to add code so there's an option to convert
 LyX comments to !-- HTML comments --? Comments would be an excellent
 way to pass through eBook-only data, without it showing up in a book
 printed from the same LyX file.

 IMO, LyX notes are just for LyX - they are also stripped from the LaTeX.

 OTOH, Comments (InsertNoteComment) are put as comments in the LaTeX and
 should be put in the HTML, too.

 In the *.lyx file, comments look like:

 \begin_inset Note Comment
 status open

 \begin_layout Plain Layout
 a comment
 \end_layout

 \end_inset

Sounds reasonable. Steve, are you willing to try out a test version? I
can send it to you privately.

Alex.

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:
 On 2011-12-06, Steve Litt wrote:
  Hi Alex,
  
  I found that my LyX comments don't get through to the finished
  HTML file, and eLyXer's Options class appears to have no option
  for passing through LyX comments.
  
  How difficult would it be to add code so there's an option to
  convert LyX comments to !-- HTML comments --? Comments would
  be an excellent way to pass through eBook-only data, without it
  showing up in a book printed from the same LyX file.
 
 IMO, LyX notes are just for LyX - they are also stripped from the
 LaTeX.
 
 OTOH, Comments (InsertNoteComment) are put as comments in the
 LaTeX and should be put in the HTML, too.

They're not. What I used was (in 2.0), 

Insert-Note-Comment

I then ran eLyXer, and the resulting HTML file didn't contain the 
comment.


 
 In the *.lyx file, comments look like:
 
 \begin_inset Note Comment
 status open
 
 \begin_layout Plain Layout
 a comment
 \end_layout
 
 \end_inset

Yes, that's just what it looked like in Vim.

Thanks

SteveT

Steve Litt
Author: The Key to Everyday Excellence
http://www.troubleshooters.com/bookstore/key_excellence.htm
Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

Can we please move elyxer discussion to the elyxer mailing list? This is
the LyX list.

Richard

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?
 
 Günter

LyXHTML was much worse. I put in the following comment:

===
ebook
cover=”./bigtitle.jpg”
publisher=”Troubleshooters.Com”
===

Here was the output from LyXHTML:

==
!-- class=note_commenta id='magicparlabel-41888' /
ebook!-- Output Error: Closing tag `div' when other tags are open, 
namely: --!-- Output Error: !-- --/!--!-- Output Error: 
LyX_parsep_tag --/div

div class=plain_layouta id='magicparlabel-41892' /
cover=rdquo;./bigtitle.jpgrdquo;/div

div class=plain_layouta id='magicparlabel-41899' /
publisher=rdquo;Troubleshooters.Comrdquo;!-- Output Error: Tried to 
close `!--' when tag was not open. Tag discarded. --!-- Output 
Error: Tags still open in closeFontTags(). Probably not a problem,
but you might want to check these tags: --!-- Output Error: div --
!-- Output Error: No paragraph separation tag found in 
endParagraph(). --/div
==

The other thing is, from my understanding, unlike eLyXer which enables 
you to specify a .css file on the command line, the only way to 
specify a .css file in LyX's native LyXHTML is to define it within the 
layout file. First of all, in this book I have no layout file -- it's 
document class Book plain and simple. But second of all, even if I 
did, what I'd want is for the layout file to determine the PDF 
appearance, with the .css determining the flowing text eBook 
appearance.

Thanks

SteveT

Steve Litt
Author: The Key to Everyday Excellence
http://www.troubleshooters.com/bookstore/key_excellence.htm
Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

Can I ask again that off-topic threads be moved to an appropriate
mailing list?

On 12/06/2011 12:06 PM, Steve Litt wrote:
 On Tuesday, December 06, 2011 05:15:38 AM Alex Fernandez wrote:
 Hi, Steve and Guenter,

 On Tue, Dec 6, 2011 at 10:46 AM, Guenter Milde mi...@users.sf.net 
 wrote:
 On 2011-12-06, Steve Litt wrote:
 Hi Alex,

 I found that my LyX comments don't get through to the finished
 HTML file, and eLyXer's Options class appears to have no option
 for passing through LyX comments.

 How difficult would it be to add code so there's an option to
 convert LyX comments to !-- HTML comments --? Comments would
 be an excellent way to pass through eBook-only data, without it
 showing up in a book printed from the same LyX file.
 IMO, LyX notes are just for LyX - they are also stripped from the
 LaTeX.

 OTOH, Comments (InsertNoteComment) are put as comments in the
 LaTeX and should be put in the HTML, too.

 In the *.lyx file, comments look like:

 \begin_inset Note Comment
 status open

 \begin_layout Plain Layout
 a comment
 \end_layout

 \end_inset
 Sounds reasonable. Steve, are you willing to try out a test
 version? I can send it to you privately.

 Alex.
 Abso-Lutely, but I just had another thought. After seeing how LyXHTML 
 handled comments, I'm beginning to wonder if the metadata not already 
 provided in LyX (Title, Author and Date) should simply be put in a 
 tiny XML file.

 Doing it separately kinda sorta makes sense when you think about it. 
 In my opinion, the LyX file should always be about how it looks in 
 PDF, with another file(s) providing looks/metadata in a flowing text 
 eBook. Actually, it might end up with three files, one for Kindle, one 
 for iPad, and one for Nook, and one for Open ePad (yeah, I have 
 trouble counting :-).

 If you already have something that passes through comments, I'll be 
 glad to test it today or in the next few days. Such a thing is 
 probably a good thing in general. However, if you're doing it just for 
 this specific thing, I'm thinking maybe hold off until all of us give 
 it more thought.

 I'm most of the way through a post processor for eLyXer-derived HTML 
 files that turns them into everything needed to make a Kindle. My 
 script is ugly, probably crashy in other circumstances, limited in 
 what situations it can handle, featureless, and pre-pre-alpha, but 
 when I get it working it can at least serve as a platform for 
 discussions on how to do it right the next time.

 Thanks for eLyXer. When you're making a Kindle book, it's the coolest 
 thing since sliced cheese.


 SteveT

 Steve Litt
 Author: The Key to Everyday Excellence
 http://www.troubleshooters.com/bookstore/key_excellence.htm
 Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

On 12/06/2011 11:54 AM, Steve Litt wrote:
 On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?

Code for the document header can be added via Local Layout, e.g.:

AddToHTMLPreamble
style type=text/css
// css commands here
/style
EndPreamble

You can put whatever you like there. JavaScript, meta tags, whatever.

 Günter
 LyXHTML was much worse. I put in the following comment:

 ===
 ebook
 cover=”./bigtitle.jpg”
 publisher=”Troubleshooters.Com”
 ===

 Here was the output from LyXHTML:

 ==
 !-- class=note_commenta id='magicparlabel-41888' /
 ebook!-- Output Error: Closing tag `div' when other tags are open, 
 namely: --!-- Output Error: !-- --/!--!-- Output Error: 
 LyX_parsep_tag --/div

 div class=plain_layouta id='magicparlabel-41892' /
 cover=rdquo;./bigtitle.jpgrdquo;/div

 div class=plain_layouta id='magicparlabel-41899' /
 publisher=rdquo;Troubleshooters.Comrdquo;!-- Output Error: Tried to 
 close `!--' when tag was not open. Tag discarded. --!-- Output 
 Error: Tags still open in closeFontTags(). Probably not a problem,
 but you might want to check these tags: --!-- Output Error: div --
 !-- Output Error: No paragraph separation tag found in 
 endParagraph(). --/div
 ==

There's some bug here involving multi-paragraph comments. I'll sort it out.

 The other thing is, from my understanding, unlike eLyXer which enables 
 you to specify a .css file on the command line, the only way to 
 specify a .css file in LyX's native LyXHTML is to define it within the 
 layout file. 

A recent patch from Rob Oakes will change this, in the sense that the
CSS will be written to a separate file. You can then modify it at will,
or replace it completely, as you wish. There's no need to specify anything.

 First of all, in this book I have no layout file -- it's 
 document class Book plain and simple. 

Then you do have a layout file: book.layout. And what it is doing can be
modified in different ways: You can write a module that you load with
the file, or you can enter your custom layout information into Local
Layout. Presumably, you'd want to do it as a module in this sort of
case, for re-usability. Or, as I said, you can do CSS separately. It's
entirely up to you.

 But second of all, even if I 
 did, what I'd want is for the layout file to determine the PDF 
 appearance, with the .css determining the flowing text eBook 
 appearance.

There's a misunderstanding here. In the PDF case, what the layout file
determines is what LaTeX gets output. Then pdflatex (or whatever) gets
run on that file, and you get a PDF. In the XHTML case, the layout file
determines what CSS gets output. Then the browser (or whatever)
determines how the whole thing gets displayed. The LaTeX-oriented parts
of the layout file are inactive when XHTML is output, just as the
XHTML-oriented parts of the layout file are inactive when LaTeX is output.

So the layout controls what gets output in both cases. But of course the
CSS is what's determining how the eBook appears, but as the LaTeX
determines how the PDF appears.

Richard

Re: Pass LyX comments through eLyXer?

[Alex Fernandez]

Hi Steve,

On Tue, Dec 6, 2011 at 6:06 PM, Steve Litt sl...@troubleshooters.com wrote:
 Abso-Lutely, but I just had another thought. After seeing how LyXHTML
 handled comments, I'm beginning to wonder if the metadata not already
 provided in LyX (Title, Author and Date) should simply be put in a
 tiny XML file.

 Doing it separately kinda sorta makes sense when you think about it.
 In my opinion, the LyX file should always be about how it looks in
 PDF, with another file(s) providing looks/metadata in a flowing text
 eBook. Actually, it might end up with three files, one for Kindle, one
 for iPad, and one for Nook, and one for Open ePad (yeah, I have
 trouble counting :-).

 If you already have something that passes through comments, I'll be
 glad to test it today or in the next few days. Such a thing is
 probably a good thing in general. However, if you're doing it just for
 this specific thing, I'm thinking maybe hold off until all of us give
 it more thought.

OK, I will wait to hear from you.

 I'm most of the way through a post processor for eLyXer-derived HTML
 files that turns them into everything needed to make a Kindle. My
 script is ugly, probably crashy in other circumstances, limited in
 what situations it can handle, featureless, and pre-pre-alpha, but
 when I get it working it can at least serve as a platform for
 discussions on how to do it right the next time.

Ideally, that post-processor should be integrated within eLyXer to
generate EPUB or Kindle documents. I would be glad to add new options:
  $ elyxer.py --epub input.lyx output.html
or, for Kindle:
  $ elyxer.py --kindle input.lyx output.azw
(if that is indeed the extension for Amazon Kindle). The problem I
found when I looked into supporting EPUB was the definition of the
format itself: the supposedly open validator rejected a lot of the
constructs which eLyXer uses in its output, but they worked fine in
e.g. Calibre to generate a full EPUB document.
  http://en.wikipedia.org/wiki/EPUB#Validation
Perhaps newer versions of the specification have improved in that respect.

 Thanks for eLyXer. When you're making a Kindle book, it's the coolest
 thing since sliced cheese.

Thanks :)  I have copied the eLyXer-users list, if you want to discuss
eLyXer-specific stuff we can continue the discussion over there.

Alex.

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 03:06:37 PM you wrote:
 Can I ask again that off-topic threads be moved to an appropriate
 mailing list?

Unless it's the LyX project's position that LyX's only function is to 
build PDF and Docbook, then this is very ontopic. As more and more 
books are written to a flowable text reader, LyX will become a more 
and more obvious choice. The HTML post-processor I discussed is one 
very easy, very modular, and very unobtrusive way to write the same 
book to both PDF/paper and Kindle, at least to the degree that such a 
thing can be done and still read. Building books for Kindle, iPad and 
Nook will probably become one of LyX's main uses in the future.

On or off topic is a relative thing. I have absolutely no interest in 
Sweave or Lilypond but don't I call them offtopic, because people use 
them to output information via LyX.

I could move this discussion over to the eLyXer list, or maybe a list 
specifically about flowable text authoring, but understand that doing 
so will remove most LyX-listers from input into the eventual flowable 
text making techniques with LyX, and understand that debugging will be 
more complex as people have to reach across mailing lists to determine 
in whose fiefdom the problem resides.

SteveT

Re: Pass LyX comments through eLyXer?

[Rob Oakes]

I for one would like for the topic to remain here. I don't follow the 
discussion on the eLyXer list, but knowing what developments happen with this 
topic are useful for things I'm working on. Especially if whatever Steve and 
Alex create can be adapted to work with the native XHTML modifications I'm 
trying to make.

To move it in a new direction, what tags are most important to Kindle? In what 
ways could the native LyX output be refined (I can create layouts/modules that 
fix these for testing purposes)? Where does the current implementation cause 
problems and for what reasons? (I'm currently looking into the situations 
raised by Steve.)

I've been delving into various ePub resources and I'm cleaning up the HTML 
based on HTML5 best practices, but it would be useful to know where else I can 
focus my attention.

Cheers,

Rob

Re: Pass LyX comments through eLyXer?

[Richard Heck]

On 12/06/2011 04:38 PM, Steve Litt wrote:
 On Tuesday, December 06, 2011 03:06:37 PM you wrote:
 Can I ask again that off-topic threads be moved to an appropriate
 mailing list?
 Unless it's the LyX project's position that LyX's only function is to 
 build PDF and Docbook, then this is very ontopic. 

Do you think the LyX list is also good for discussion of the details of
the ps2pdf converter? Or for reporting bugs with it?

Richard

Re: Pass LyX comments through eLyXer?

[Alan L Tyree]

On 07/12/11 09:41:13, Richard Heck wrote:
 On 12/06/2011 04:38 PM, Steve Litt wrote:
  On Tuesday, December 06, 2011 03:06:37 PM you wrote:
  Can I ask again that off-topic threads be moved to an appropriate
  mailing list?
  Unless it's the LyX project's position that LyX's only function is
 to 
  build PDF and Docbook, then this is very ontopic. 
 
 Do you think the LyX list is also good for discussion of the details
 of
 the ps2pdf converter? Or for reporting bugs with it?

No, but I don't think it is the same.

If LyX is to develop into a serious e-book editor, then this is a very 
LyX related discussion. Even users such as myself who are in no 
position to contribute directly to the development have an interest in 
how this develops. Mere users can eventually have an input into this 
development.

It is not just a discussion about converters or bugs. It relates to how 
LyX will look and behave in the future. I agree with Steve and others 
that LyX could become major tool for writing e-books. As such, the 
discussion doesn't seem to me to be off topic.

Cheers,
Alan

 
 Richard
 
 



-- 
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:172...@iptel.org

Re: Pass LyX comments through eLyXer?

[Richard Heck]

On 12/06/2011 05:55 PM, Alan L Tyree wrote:
 On 07/12/11 09:41:13, Richard Heck wrote:
 On 12/06/2011 04:38 PM, Steve Litt wrote:
 On Tuesday, December 06, 2011 03:06:37 PM you wrote:
 Can I ask again that off-topic threads be moved to an appropriate
 mailing list?
 Unless it's the LyX project's position that LyX's only function is
 to 
 build PDF and Docbook, then this is very ontopic. 

 Do you think the LyX list is also good for discussion of the details
 of the ps2pdf converter? Or for reporting bugs with it?
 No, but I don't think it is the same.

 If LyX is to develop into a serious e-book editor, then this is a very 
 LyX related discussion. Even users such as myself who are in no 
 position to contribute directly to the development have an interest in 
 how this develops. Mere users can eventually have an input into this 
 development.

 It is not just a discussion about converters or bugs. It relates to how 
 LyX will look and behave in the future. I agree with Steve and others 
 that LyX could become major tool for writing e-books. As such, the 
 discussion doesn't seem to me to be off topic.

I agree with Steve, as well, that LyX could become such a tool. But that
is not what this discussion has been about. This discussion, as the
subject makes very clear, has been about elyxer, and about a very
specific question Steve had about it.

If people want to have a general discussion about how to make LyX a good
tool for writing e-books, then let's have that discussion. And let's
have it in such a way that it has something to do with LyX, which none
of this discussion so far has. Indeed, various of us have already been
having that discussion---but it is, frankly, a discussion for the devel
list, which many non-developers read and contribute to, for exactly the
reason you mention: because users' input is welcome and needed. This
list is for issues with LyX itself, or for questions about how to use
it, etc.

Richard

Re: Pass LyX comments through eLyXer?

[Guenter Milde]

On 2011-12-06, Steve Litt wrote:
 Hi Alex,

 I found that my LyX comments don't get through to the finished HTML 
 file, and eLyXer's Options class appears to have no option for passing 
 through LyX comments.

 How difficult would it be to add code so there's an option to convert 
 LyX comments to !-- HTML comments --? Comments would be an excellent 
 way to pass through eBook-only data, without it showing up in a book 
 printed from the same LyX file.

IMO, LyX notes are just for LyX - they are also stripped from the LaTeX.

OTOH, Comments (InsertNoteComment) are put as comments in the LaTeX and
should be put in the HTML, too.

In the *.lyx file, comments look like:

\begin_inset Note Comment
status open

\begin_layout Plain Layout
a comment
\end_layout

\end_inset


 If it's too hard to do, or if there's not enough time to do it, I can 
 probably make a small program to scoop out the specific comment that 
 passes the eBook metadata, and give that information to the post-
 processor. The post-processor already adds pagefeeds to every h1 
 item in the HTML file and captures the Title, Author and Date but 
 doesn't print them.


As LyX now offers native HTML export,
is there an equivalent to DocumentSettingsLaTeX preamble
for raw HTML code in the document header?

Günter

Re: Pass LyX comments through eLyXer?

[Alex Fernandez]

Hi, Steve and Guenter,

On Tue, Dec 6, 2011 at 10:46 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2011-12-06, Steve Litt wrote:
 Hi Alex,

 I found that my LyX comments don't get through to the finished HTML
 file, and eLyXer's Options class appears to have no option for passing
 through LyX comments.

 How difficult would it be to add code so there's an option to convert
 LyX comments to !-- HTML comments --? Comments would be an excellent
 way to pass through eBook-only data, without it showing up in a book
 printed from the same LyX file.

 IMO, LyX notes are just for LyX - they are also stripped from the LaTeX.

 OTOH, Comments (InsertNoteComment) are put as comments in the LaTeX and
 should be put in the HTML, too.

 In the *.lyx file, comments look like:

 \begin_inset Note Comment
 status open

 \begin_layout Plain Layout
 a comment
 \end_layout

 \end_inset

Sounds reasonable. Steve, are you willing to try out a test version? I
can send it to you privately.

Alex.

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:
 On 2011-12-06, Steve Litt wrote:
  Hi Alex,
  
  I found that my LyX comments don't get through to the finished
  HTML file, and eLyXer's Options class appears to have no option
  for passing through LyX comments.
  
  How difficult would it be to add code so there's an option to
  convert LyX comments to !-- HTML comments --? Comments would
  be an excellent way to pass through eBook-only data, without it
  showing up in a book printed from the same LyX file.
 
 IMO, LyX notes are just for LyX - they are also stripped from the
 LaTeX.
 
 OTOH, Comments (InsertNoteComment) are put as comments in the
 LaTeX and should be put in the HTML, too.

They're not. What I used was (in 2.0), 

Insert-Note-Comment

I then ran eLyXer, and the resulting HTML file didn't contain the 
comment.


 
 In the *.lyx file, comments look like:
 
 \begin_inset Note Comment
 status open
 
 \begin_layout Plain Layout
 a comment
 \end_layout
 
 \end_inset

Yes, that's just what it looked like in Vim.

Thanks

SteveT

Steve Litt
Author: The Key to Everyday Excellence
http://www.troubleshooters.com/bookstore/key_excellence.htm
Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

Can we please move elyxer discussion to the elyxer mailing list? This is
the LyX list.

Richard

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?
 
 Günter

LyXHTML was much worse. I put in the following comment:

===
ebook
cover=”./bigtitle.jpg”
publisher=”Troubleshooters.Com”
===

Here was the output from LyXHTML:

==
!-- class=note_commenta id='magicparlabel-41888' /
ebook!-- Output Error: Closing tag `div' when other tags are open, 
namely: --!-- Output Error: !-- --/!--!-- Output Error: 
LyX_parsep_tag --/div

div class=plain_layouta id='magicparlabel-41892' /
cover=rdquo;./bigtitle.jpgrdquo;/div

div class=plain_layouta id='magicparlabel-41899' /
publisher=rdquo;Troubleshooters.Comrdquo;!-- Output Error: Tried to 
close `!--' when tag was not open. Tag discarded. --!-- Output 
Error: Tags still open in closeFontTags(). Probably not a problem,
but you might want to check these tags: --!-- Output Error: div --
!-- Output Error: No paragraph separation tag found in 
endParagraph(). --/div
==

The other thing is, from my understanding, unlike eLyXer which enables 
you to specify a .css file on the command line, the only way to 
specify a .css file in LyX's native LyXHTML is to define it within the 
layout file. First of all, in this book I have no layout file -- it's 
document class Book plain and simple. But second of all, even if I 
did, what I'd want is for the layout file to determine the PDF 
appearance, with the .css determining the flowing text eBook 
appearance.

Thanks

SteveT

Steve Litt
Author: The Key to Everyday Excellence
http://www.troubleshooters.com/bookstore/key_excellence.htm
Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

Can I ask again that off-topic threads be moved to an appropriate
mailing list?

On 12/06/2011 12:06 PM, Steve Litt wrote:
 On Tuesday, December 06, 2011 05:15:38 AM Alex Fernandez wrote:
 Hi, Steve and Guenter,

 On Tue, Dec 6, 2011 at 10:46 AM, Guenter Milde mi...@users.sf.net 
 wrote:
 On 2011-12-06, Steve Litt wrote:
 Hi Alex,

 I found that my LyX comments don't get through to the finished
 HTML file, and eLyXer's Options class appears to have no option
 for passing through LyX comments.

 How difficult would it be to add code so there's an option to
 convert LyX comments to !-- HTML comments --? Comments would
 be an excellent way to pass through eBook-only data, without it
 showing up in a book printed from the same LyX file.
 IMO, LyX notes are just for LyX - they are also stripped from the
 LaTeX.

 OTOH, Comments (InsertNoteComment) are put as comments in the
 LaTeX and should be put in the HTML, too.

 In the *.lyx file, comments look like:

 \begin_inset Note Comment
 status open

 \begin_layout Plain Layout
 a comment
 \end_layout

 \end_inset
 Sounds reasonable. Steve, are you willing to try out a test
 version? I can send it to you privately.

 Alex.
 Abso-Lutely, but I just had another thought. After seeing how LyXHTML 
 handled comments, I'm beginning to wonder if the metadata not already 
 provided in LyX (Title, Author and Date) should simply be put in a 
 tiny XML file.

 Doing it separately kinda sorta makes sense when you think about it. 
 In my opinion, the LyX file should always be about how it looks in 
 PDF, with another file(s) providing looks/metadata in a flowing text 
 eBook. Actually, it might end up with three files, one for Kindle, one 
 for iPad, and one for Nook, and one for Open ePad (yeah, I have 
 trouble counting :-).

 If you already have something that passes through comments, I'll be 
 glad to test it today or in the next few days. Such a thing is 
 probably a good thing in general. However, if you're doing it just for 
 this specific thing, I'm thinking maybe hold off until all of us give 
 it more thought.

 I'm most of the way through a post processor for eLyXer-derived HTML 
 files that turns them into everything needed to make a Kindle. My 
 script is ugly, probably crashy in other circumstances, limited in 
 what situations it can handle, featureless, and pre-pre-alpha, but 
 when I get it working it can at least serve as a platform for 
 discussions on how to do it right the next time.

 Thanks for eLyXer. When you're making a Kindle book, it's the coolest 
 thing since sliced cheese.


 SteveT

 Steve Litt
 Author: The Key to Everyday Excellence
 http://www.troubleshooters.com/bookstore/key_excellence.htm
 Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

On 12/06/2011 11:54 AM, Steve Litt wrote:
 On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

 As LyX now offers native HTML export,
 is there an equivalent to DocumentSettingsLaTeX preamble
 for raw HTML code in the document header?

Code for the document header can be added via Local Layout, e.g.:

AddToHTMLPreamble
style type=text/css
// css commands here
/style
EndPreamble

You can put whatever you like there. JavaScript, meta tags, whatever.

 Günter
 LyXHTML was much worse. I put in the following comment:

 ===
 ebook
 cover=”./bigtitle.jpg”
 publisher=”Troubleshooters.Com”
 ===

 Here was the output from LyXHTML:

 ==
 !-- class=note_commenta id='magicparlabel-41888' /
 ebook!-- Output Error: Closing tag `div' when other tags are open, 
 namely: --!-- Output Error: !-- --/!--!-- Output Error: 
 LyX_parsep_tag --/div

 div class=plain_layouta id='magicparlabel-41892' /
 cover=rdquo;./bigtitle.jpgrdquo;/div

 div class=plain_layouta id='magicparlabel-41899' /
 publisher=rdquo;Troubleshooters.Comrdquo;!-- Output Error: Tried to 
 close `!--' when tag was not open. Tag discarded. --!-- Output 
 Error: Tags still open in closeFontTags(). Probably not a problem,
 but you might want to check these tags: --!-- Output Error: div --
 !-- Output Error: No paragraph separation tag found in 
 endParagraph(). --/div
 ==

There's some bug here involving multi-paragraph comments. I'll sort it out.

 The other thing is, from my understanding, unlike eLyXer which enables 
 you to specify a .css file on the command line, the only way to 
 specify a .css file in LyX's native LyXHTML is to define it within the 
 layout file. 

A recent patch from Rob Oakes will change this, in the sense that the
CSS will be written to a separate file. You can then modify it at will,
or replace it completely, as you wish. There's no need to specify anything.

 First of all, in this book I have no layout file -- it's 
 document class Book plain and simple. 

Then you do have a layout file: book.layout. And what it is doing can be
modified in different ways: You can write a module that you load with
the file, or you can enter your custom layout information into Local
Layout. Presumably, you'd want to do it as a module in this sort of
case, for re-usability. Or, as I said, you can do CSS separately. It's
entirely up to you.

 But second of all, even if I 
 did, what I'd want is for the layout file to determine the PDF 
 appearance, with the .css determining the flowing text eBook 
 appearance.

There's a misunderstanding here. In the PDF case, what the layout file
determines is what LaTeX gets output. Then pdflatex (or whatever) gets
run on that file, and you get a PDF. In the XHTML case, the layout file
determines what CSS gets output. Then the browser (or whatever)
determines how the whole thing gets displayed. The LaTeX-oriented parts
of the layout file are inactive when XHTML is output, just as the
XHTML-oriented parts of the layout file are inactive when LaTeX is output.

So the layout controls what gets output in both cases. But of course the
CSS is what's determining how the eBook appears, but as the LaTeX
determines how the PDF appears.

Richard

Re: Pass LyX comments through eLyXer?

[Alex Fernandez]

Hi Steve,

On Tue, Dec 6, 2011 at 6:06 PM, Steve Litt sl...@troubleshooters.com wrote:
 Abso-Lutely, but I just had another thought. After seeing how LyXHTML
 handled comments, I'm beginning to wonder if the metadata not already
 provided in LyX (Title, Author and Date) should simply be put in a
 tiny XML file.

 Doing it separately kinda sorta makes sense when you think about it.
 In my opinion, the LyX file should always be about how it looks in
 PDF, with another file(s) providing looks/metadata in a flowing text
 eBook. Actually, it might end up with three files, one for Kindle, one
 for iPad, and one for Nook, and one for Open ePad (yeah, I have
 trouble counting :-).

 If you already have something that passes through comments, I'll be
 glad to test it today or in the next few days. Such a thing is
 probably a good thing in general. However, if you're doing it just for
 this specific thing, I'm thinking maybe hold off until all of us give
 it more thought.

OK, I will wait to hear from you.

 I'm most of the way through a post processor for eLyXer-derived HTML
 files that turns them into everything needed to make a Kindle. My
 script is ugly, probably crashy in other circumstances, limited in
 what situations it can handle, featureless, and pre-pre-alpha, but
 when I get it working it can at least serve as a platform for
 discussions on how to do it right the next time.

Ideally, that post-processor should be integrated within eLyXer to
generate EPUB or Kindle documents. I would be glad to add new options:
  $ elyxer.py --epub input.lyx output.html
or, for Kindle:
  $ elyxer.py --kindle input.lyx output.azw
(if that is indeed the extension for Amazon Kindle). The problem I
found when I looked into supporting EPUB was the definition of the
format itself: the supposedly open validator rejected a lot of the
constructs which eLyXer uses in its output, but they worked fine in
e.g. Calibre to generate a full EPUB document.
  http://en.wikipedia.org/wiki/EPUB#Validation
Perhaps newer versions of the specification have improved in that respect.

 Thanks for eLyXer. When you're making a Kindle book, it's the coolest
 thing since sliced cheese.

Thanks :)  I have copied the eLyXer-users list, if you want to discuss
eLyXer-specific stuff we can continue the discussion over there.

Alex.

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 03:06:37 PM you wrote:
 Can I ask again that off-topic threads be moved to an appropriate
 mailing list?

Unless it's the LyX project's position that LyX's only function is to 
build PDF and Docbook, then this is very ontopic. As more and more 
books are written to a flowable text reader, LyX will become a more 
and more obvious choice. The HTML post-processor I discussed is one 
very easy, very modular, and very unobtrusive way to write the same 
book to both PDF/paper and Kindle, at least to the degree that such a 
thing can be done and still read. Building books for Kindle, iPad and 
Nook will probably become one of LyX's main uses in the future.

On or off topic is a relative thing. I have absolutely no interest in 
Sweave or Lilypond but don't I call them offtopic, because people use 
them to output information via LyX.

I could move this discussion over to the eLyXer list, or maybe a list 
specifically about flowable text authoring, but understand that doing 
so will remove most LyX-listers from input into the eventual flowable 
text making techniques with LyX, and understand that debugging will be 
more complex as people have to reach across mailing lists to determine 
in whose fiefdom the problem resides.

SteveT

Re: Pass LyX comments through eLyXer?

[Rob Oakes]

I for one would like for the topic to remain here. I don't follow the 
discussion on the eLyXer list, but knowing what developments happen with this 
topic are useful for things I'm working on. Especially if whatever Steve and 
Alex create can be adapted to work with the native XHTML modifications I'm 
trying to make.

To move it in a new direction, what tags are most important to Kindle? In what 
ways could the native LyX output be refined (I can create layouts/modules that 
fix these for testing purposes)? Where does the current implementation cause 
problems and for what reasons? (I'm currently looking into the situations 
raised by Steve.)

I've been delving into various ePub resources and I'm cleaning up the HTML 
based on HTML5 best practices, but it would be useful to know where else I can 
focus my attention.

Cheers,

Rob

Re: Pass LyX comments through eLyXer?

[Richard Heck]

On 12/06/2011 04:38 PM, Steve Litt wrote:
 On Tuesday, December 06, 2011 03:06:37 PM you wrote:
 Can I ask again that off-topic threads be moved to an appropriate
 mailing list?
 Unless it's the LyX project's position that LyX's only function is to 
 build PDF and Docbook, then this is very ontopic. 

Do you think the LyX list is also good for discussion of the details of
the ps2pdf converter? Or for reporting bugs with it?

Richard

Re: Pass LyX comments through eLyXer?

[Alan L Tyree]

On 07/12/11 09:41:13, Richard Heck wrote:
 On 12/06/2011 04:38 PM, Steve Litt wrote:
  On Tuesday, December 06, 2011 03:06:37 PM you wrote:
  Can I ask again that off-topic threads be moved to an appropriate
  mailing list?
  Unless it's the LyX project's position that LyX's only function is
 to 
  build PDF and Docbook, then this is very ontopic. 
 
 Do you think the LyX list is also good for discussion of the details
 of
 the ps2pdf converter? Or for reporting bugs with it?

No, but I don't think it is the same.

If LyX is to develop into a serious e-book editor, then this is a very 
LyX related discussion. Even users such as myself who are in no 
position to contribute directly to the development have an interest in 
how this develops. Mere users can eventually have an input into this 
development.

It is not just a discussion about converters or bugs. It relates to how 
LyX will look and behave in the future. I agree with Steve and others 
that LyX could become major tool for writing e-books. As such, the 
discussion doesn't seem to me to be off topic.

Cheers,
Alan

 
 Richard
 
 



-- 
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:172...@iptel.org

Re: Pass LyX comments through eLyXer?

[Richard Heck]

On 12/06/2011 05:55 PM, Alan L Tyree wrote:
 On 07/12/11 09:41:13, Richard Heck wrote:
 On 12/06/2011 04:38 PM, Steve Litt wrote:
 On Tuesday, December 06, 2011 03:06:37 PM you wrote:
 Can I ask again that off-topic threads be moved to an appropriate
 mailing list?
 Unless it's the LyX project's position that LyX's only function is
 to 
 build PDF and Docbook, then this is very ontopic. 

 Do you think the LyX list is also good for discussion of the details
 of the ps2pdf converter? Or for reporting bugs with it?
 No, but I don't think it is the same.

 If LyX is to develop into a serious e-book editor, then this is a very 
 LyX related discussion. Even users such as myself who are in no 
 position to contribute directly to the development have an interest in 
 how this develops. Mere users can eventually have an input into this 
 development.

 It is not just a discussion about converters or bugs. It relates to how 
 LyX will look and behave in the future. I agree with Steve and others 
 that LyX could become major tool for writing e-books. As such, the 
 discussion doesn't seem to me to be off topic.

I agree with Steve, as well, that LyX could become such a tool. But that
is not what this discussion has been about. This discussion, as the
subject makes very clear, has been about elyxer, and about a very
specific question Steve had about it.

If people want to have a general discussion about how to make LyX a good
tool for writing e-books, then let's have that discussion. And let's
have it in such a way that it has something to do with LyX, which none
of this discussion so far has. Indeed, various of us have already been
having that discussion---but it is, frankly, a discussion for the devel
list, which many non-developers read and contribute to, for exactly the
reason you mention: because users' input is welcome and needed. This
list is for issues with LyX itself, or for questions about how to use
it, etc.

Richard

Re: Pass LyX comments through eLyXer?

[Guenter Milde]

On 2011-12-06, Steve Litt wrote:
> Hi Alex,

> I found that my LyX comments don't get through to the finished HTML 
> file, and eLyXer's Options class appears to have no option for passing 
> through LyX comments.

> How difficult would it be to add code so there's an option to convert 
> LyX comments to ? Comments would be an excellent 
> way to pass through eBook-only data, without it showing up in a book 
> printed from the same LyX file.

IMO, LyX notes are just for LyX - they are also stripped from the LaTeX.

OTOH, Comments (Insert>Note>Comment) are put as comments in the LaTeX and
should be put in the HTML, too.

In the *.lyx file, comments look like:

\begin_inset Note Comment
status open

\begin_layout Plain Layout
a comment
\end_layout

\end_inset


> If it's too hard to do, or if there's not enough time to do it, I can 
> probably make a small program to scoop out the specific comment that 
> passes the eBook metadata, and give that information to the post-
> processor. The post-processor already adds pagefeeds to every  
> item in the HTML file and captures the Title, Author and Date but 
> doesn't print them.


As LyX now offers native HTML export,
is there an equivalent to Document>Settings>LaTeX preamble
for "raw" HTML code in the document header?

Günter

Re: Pass LyX comments through eLyXer?

[Alex Fernandez]

Hi, Steve and Guenter,

On Tue, Dec 6, 2011 at 10:46 AM, Guenter Milde <mi...@users.sf.net> wrote:
> On 2011-12-06, Steve Litt wrote:
>> Hi Alex,
>
>> I found that my LyX comments don't get through to the finished HTML
>> file, and eLyXer's Options class appears to have no option for passing
>> through LyX comments.
>
>> How difficult would it be to add code so there's an option to convert
>> LyX comments to ? Comments would be an excellent
>> way to pass through eBook-only data, without it showing up in a book
>> printed from the same LyX file.
>
> IMO, LyX notes are just for LyX - they are also stripped from the LaTeX.
>
> OTOH, Comments (Insert>Note>Comment) are put as comments in the LaTeX and
> should be put in the HTML, too.
>
> In the *.lyx file, comments look like:
>
> \begin_inset Note Comment
> status open
>
> \begin_layout Plain Layout
> a comment
> \end_layout
>
> \end_inset

Sounds reasonable. Steve, are you willing to try out a test version? I
can send it to you privately.

Alex.

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:
> On 2011-12-06, Steve Litt wrote:
> > Hi Alex,
> > 
> > I found that my LyX comments don't get through to the finished
> > HTML file, and eLyXer's Options class appears to have no option
> > for passing through LyX comments.
> > 
> > How difficult would it be to add code so there's an option to
> > convert LyX comments to ? Comments would
> > be an excellent way to pass through eBook-only data, without it
> > showing up in a book printed from the same LyX file.
> 
> IMO, LyX notes are just for LyX - they are also stripped from the
> LaTeX.
> 
> OTOH, Comments (Insert>Note>Comment) are put as comments in the
> LaTeX and should be put in the HTML, too.

They're not. What I used was (in 2.0), 

Insert->Note->Comment

I then ran eLyXer, and the resulting HTML file didn't contain the 
comment.


> 
> In the *.lyx file, comments look like:
> 
> \begin_inset Note Comment
> status open
> 
> \begin_layout Plain Layout
> a comment
> \end_layout
> 
> \end_inset

Yes, that's just what it looked like in Vim.

Thanks

SteveT

Steve Litt
Author: The Key to Everyday Excellence
http://www.troubleshooters.com/bookstore/key_excellence.htm
Twitter: http://www.twitter.com/stevelitt

Re: Pass LyX comments through eLyXer?

[Richard Heck]

Can we please move elyxer discussion to the elyxer mailing list? This is
the LyX list.

Richard

Re: Pass LyX comments through eLyXer?

[Steve Litt]

On Tuesday, December 06, 2011 04:46:28 AM Guenter Milde wrote:

> As LyX now offers native HTML export,
> is there an equivalent to Document>Settings>LaTeX preamble
> for "raw" HTML code in the document header?
> 
> Günter

LyXHTML was much worse. I put in the following comment:

===
ebook
cover=”./bigtitle.jpg”
publisher=”Troubleshooters.Com”
===

Here was the output from LyXHTML:

==



cover=./bigtitle.jpg


publisher=Troubleshooters.Com
==

The other thing is, from my understanding, unlike eLyXer which enables 
you to specify a .css file on the command line, the only way to 
specify a .css file in LyX's native LyXHTML is to define it within the 
layout file. First of all, in this book I have no layout file -- it's 
document class Book plain and simple. But second of all, even if I 
did, what I'd want is for the layout file to determine the PDF 
appearance, with the .css determining the flowing text eBook 
appearance.

Thanks

SteveT

Steve Litt
Author: The Key to Everyday Excellence
http://www.troubleshooters.com/bookstore/key_excellence.htm
Twitter: http://www.twitter.com/stevelitt