Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Raymond Lillard

On 04/26/2012 05:15 AM, Richard Heck wrote:

On 04/25/2012 11:59 PM, Raymond Lillard wrote:

Dear Lyx-Users,

I have looked and read documentation and Googled for
hours and have yet to find answers to two questions.

My Lyx environment:

Lyx 2.1.0svn as of about a week ago.
TexLive2011 + updates also current about a week ago.

I have written a ~100 page document and would like
to accomplish two things. While writing this document
I have been previewing it as a PDF and now have a nice
looking document.

I have been asked to prepare an HTML version of the
document. I have done so and it too looks really nice
with two minor (well maybe 1 1/2) flaws.

The first and most bothersome is that I have placed
some ERT to handle page numbering in the PDF output.

For the cover page:
\thispagestyleempty

and for general page numbering:
\lhead Name: \pagenumberingroman

This ERT appears in my HTML output when view in a
browser.

What are you using to produce the HTML output? LyX's own method should
not do this, and does not do it in the test I just ran.


$ elyxer --version
* eLyXer version 1.2.3 (2011-08-31)

When my document output format is set to HTML I get:
Line 3: * Warning: unsupported new format version 430
Line 149: * Unknown command \thispagestyle
Line 192: * Unknown command \lhead
Line 192: * Unknown command \pagenumbering
Line 262: * Unknown command \pagenumbering
Line 262: * Unknown command \topmargin
on STDERR from elyxer.

These unrecognized commands get passed through as plain
text in the HTML.

Sorry, but LyXHTML is too ugly for my taste.

I'm not clear on these things, but it looks like
Elyxer is not maintained by the Lyx project.  Should
I take silly little problem elsewhere?



I would like to not need to modify the document
depending on the output form. Is this possible?


You could use branches to turn things on and off.


Secondly, I would like the output to be one large
file but with defined page numbers just like the PDF.


I guess I don't really understand this. I'd be happy to add it to LyX's
XHTML output routine, but how does one know where to break the pages?


OK, I made an incorrect assumption when I wrote the above.
I didn't realize the HTML was being created directly from
lyx code.  I was thinking it was going through some common
intermediate format.  Since not, the problem is between me
and elyxer and probably insoluble since neither HTML or
Lyx code have a any concept of a letter sized page.








Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Richard Heck

On 04/26/2012 06:27 PM, Raymond Lillard wrote:


Sorry, but LyXHTML is too ugly for my taste.


How so? Do you mean the visual output or the file structure, or?

Richard



Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Raymond Lillard

On 04/26/2012 04:48 PM, Richard Heck wrote:

On 04/26/2012 06:27 PM, Raymond Lillard wrote:


Sorry, but LyXHTML is too ugly for my taste.


How so? Do you mean the visual output or the file structure, or?


Richard,

I'm not experienced enough at HTML to have an opinion
on file structure.

When I set the document default output to HTML (filtered
through elyxer) the viewed document is more visually
appealing than when set to LyXHTML. Perhaps ugly is too
strong a word here, but I think most people would agree
it looks dated.

I didn't mean to give offense and please don't take my
comment that way.

It has been said that a gentleman never gives offense,
unintentionally.

If you or the Lyx team were offended, then my normal
gentlemanly demeanor has suffered a glitch.

Regards,
Ray


Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Alex Fernandez
Hi Ray,

On Fri, Apr 27, 2012 at 12:27 AM, Raymond Lillard rlill...@sonic.netwrote:

 I'm not clear on these things, but it looks like
 Elyxer is not maintained by the Lyx project.  Should
 I take silly little problem elsewhere?


Sure, you can email me directly. I have received other requests to remove
parsing errors from the output; I should probably do that for the next
version.

OK, I made an incorrect assumption when I wrote the above.
 I didn't realize the HTML was being created directly from
 lyx code.  I was thinking it was going through some common
 intermediate format.  Since not, the problem is between me
 and elyxer and probably insoluble since neither HTML or
 Lyx code have a any concept of a letter sized page.


Yes, your intentions (output numbered by actual paper pages) is quite alien
to eLyXer and even to the HTML format itself. Apart from cutting pages at a
fixed number of words, or doing some troff-like abomination (the kind you
see on RFCs: http://www.rfc-editor.org/rfc/rfc1866.txt), I don't see how
that would even work. The natural way to do what you want would be to cut
the output by sections; and frankly I don't understand why that solution
doesn't cut it for you (pun intended).

Another request I have received, and which I need myself, is to output
section names as page names, the kind of dash-separated-titles that you see
on blog posts. I should take out some time to work on eLyXer!

Alex.


Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Raymond Lillard

On 04/26/2012 05:15 AM, Richard Heck wrote:

On 04/25/2012 11:59 PM, Raymond Lillard wrote:

Dear Lyx-Users,

I have looked and read documentation and Googled for
hours and have yet to find answers to two questions.

My Lyx environment:

Lyx 2.1.0svn as of about a week ago.
TexLive2011 + updates also current about a week ago.

I have written a ~100 page document and would like
to accomplish two things. While writing this document
I have been previewing it as a PDF and now have a nice
looking document.

I have been asked to prepare an HTML version of the
document. I have done so and it too looks really nice
with two minor (well maybe 1 1/2) flaws.

The first and most bothersome is that I have placed
some ERT to handle page numbering in the PDF output.

For the cover page:
\thispagestyleempty

and for general page numbering:
\lhead Name: \pagenumberingroman

This ERT appears in my HTML output when view in a
browser.

What are you using to produce the HTML output? LyX's own method should
not do this, and does not do it in the test I just ran.


$ elyxer --version
* eLyXer version 1.2.3 (2011-08-31)

When my document output format is set to HTML I get:
Line 3: * Warning: unsupported new format version 430
Line 149: * Unknown command \thispagestyle
Line 192: * Unknown command \lhead
Line 192: * Unknown command \pagenumbering
Line 262: * Unknown command \pagenumbering
Line 262: * Unknown command \topmargin
on STDERR from elyxer.

These unrecognized commands get passed through as plain
text in the HTML.

Sorry, but LyXHTML is too ugly for my taste.

I'm not clear on these things, but it looks like
Elyxer is not maintained by the Lyx project.  Should
I take silly little problem elsewhere?



I would like to not need to modify the document
depending on the output form. Is this possible?


You could use branches to turn things on and off.


Secondly, I would like the output to be one large
file but with defined page numbers just like the PDF.


I guess I don't really understand this. I'd be happy to add it to LyX's
XHTML output routine, but how does one know where to break the pages?


OK, I made an incorrect assumption when I wrote the above.
I didn't realize the HTML was being created directly from
lyx code.  I was thinking it was going through some common
intermediate format.  Since not, the problem is between me
and elyxer and probably insoluble since neither HTML or
Lyx code have a any concept of a letter sized page.








Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Richard Heck

On 04/26/2012 06:27 PM, Raymond Lillard wrote:


Sorry, but LyXHTML is too ugly for my taste.


How so? Do you mean the visual output or the file structure, or?

Richard



Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Raymond Lillard

On 04/26/2012 04:48 PM, Richard Heck wrote:

On 04/26/2012 06:27 PM, Raymond Lillard wrote:


Sorry, but LyXHTML is too ugly for my taste.


How so? Do you mean the visual output or the file structure, or?


Richard,

I'm not experienced enough at HTML to have an opinion
on file structure.

When I set the document default output to HTML (filtered
through elyxer) the viewed document is more visually
appealing than when set to LyXHTML. Perhaps ugly is too
strong a word here, but I think most people would agree
it looks dated.

I didn't mean to give offense and please don't take my
comment that way.

It has been said that a gentleman never gives offense,
unintentionally.

If you or the Lyx team were offended, then my normal
gentlemanly demeanor has suffered a glitch.

Regards,
Ray


Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Alex Fernandez
Hi Ray,

On Fri, Apr 27, 2012 at 12:27 AM, Raymond Lillard rlill...@sonic.netwrote:

 I'm not clear on these things, but it looks like
 Elyxer is not maintained by the Lyx project.  Should
 I take silly little problem elsewhere?


Sure, you can email me directly. I have received other requests to remove
parsing errors from the output; I should probably do that for the next
version.

OK, I made an incorrect assumption when I wrote the above.
 I didn't realize the HTML was being created directly from
 lyx code.  I was thinking it was going through some common
 intermediate format.  Since not, the problem is between me
 and elyxer and probably insoluble since neither HTML or
 Lyx code have a any concept of a letter sized page.


Yes, your intentions (output numbered by actual paper pages) is quite alien
to eLyXer and even to the HTML format itself. Apart from cutting pages at a
fixed number of words, or doing some troff-like abomination (the kind you
see on RFCs: http://www.rfc-editor.org/rfc/rfc1866.txt), I don't see how
that would even work. The natural way to do what you want would be to cut
the output by sections; and frankly I don't understand why that solution
doesn't cut it for you (pun intended).

Another request I have received, and which I need myself, is to output
section names as page names, the kind of dash-separated-titles that you see
on blog posts. I should take out some time to work on eLyXer!

Alex.


Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Raymond Lillard

On 04/26/2012 05:15 AM, Richard Heck wrote:

On 04/25/2012 11:59 PM, Raymond Lillard wrote:

Dear Lyx-Users,

I have looked and read documentation and Googled for
hours and have yet to find answers to two questions.

My Lyx environment:

Lyx 2.1.0svn as of about a week ago.
TexLive2011 + updates also current about a week ago.

I have written a ~100 page document and would like
to accomplish two things. While writing this document
I have been previewing it as a PDF and now have a nice
looking document.

I have been asked to prepare an HTML version of the
document. I have done so and it too looks really nice
with two minor (well maybe 1 1/2) flaws.

The first and most bothersome is that I have placed
some ERT to handle page numbering in the PDF output.

For the cover page:
\thispagestyleempty

and for general page numbering:
\lhead Name: \pagenumberingroman

This ERT appears in my HTML output when view in a
browser.

What are you using to produce the HTML output? LyX's own method should
not do this, and does not do it in the test I just ran.


$ elyxer --version
* eLyXer version 1.2.3 (2011-08-31)

When my document output format is set to HTML I get:
Line 3: * Warning: unsupported new format version 430
Line 149: * Unknown command \thispagestyle
Line 192: * Unknown command \lhead
Line 192: * Unknown command \pagenumbering
Line 262: * Unknown command \pagenumbering
Line 262: * Unknown command \topmargin
on STDERR from elyxer.

These unrecognized commands get passed through as plain
text in the HTML.

Sorry, but LyXHTML is too ugly for my taste.

I'm not clear on these things, but it looks like
Elyxer is not maintained by the Lyx project.  Should
I take silly little problem elsewhere?



I would like to not need to modify the document
depending on the output form. Is this possible?


You could use branches to turn things on and off.


Secondly, I would like the output to be one large
file but with defined page numbers just like the PDF.


I guess I don't really understand this. I'd be happy to add it to LyX's
XHTML output routine, but how does one know where to break the pages?


OK, I made an incorrect assumption when I wrote the above.
I didn't realize the HTML was being created directly from
lyx code.  I was thinking it was going through some common
intermediate format.  Since not, the problem is between me
and elyxer and probably insoluble since neither HTML or
Lyx code have a any concept of a letter sized page.








Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Richard Heck

On 04/26/2012 06:27 PM, Raymond Lillard wrote:


Sorry, but LyXHTML is too ugly for my taste.


How so? Do you mean the visual output or the file structure, or?

Richard



Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Raymond Lillard

On 04/26/2012 04:48 PM, Richard Heck wrote:

On 04/26/2012 06:27 PM, Raymond Lillard wrote:


Sorry, but LyXHTML is too ugly for my taste.


How so? Do you mean the visual output or the file structure, or?


Richard,

I'm not experienced enough at HTML to have an opinion
on file structure.

When I set the document default output to HTML (filtered
through elyxer) the viewed document is more visually
appealing than when set to LyXHTML. Perhaps ugly is too
strong a word here, but I think most people would agree
it looks dated.

I didn't mean to give offense and please don't take my
comment that way.

It has been said that a gentleman never gives offense,
unintentionally.

If you or the Lyx team were offended, then my normal
gentlemanly demeanor has suffered a glitch.

Regards,
Ray


Re: HTML Pagination Issues (elyxer)

2012-04-26 Thread Alex Fernandez
Hi Ray,

On Fri, Apr 27, 2012 at 12:27 AM, Raymond Lillard wrote:

> I'm not clear on these things, but it looks like
> Elyxer is not maintained by the Lyx project.  Should
> I take silly little problem elsewhere?
>

Sure, you can email me directly. I have received other requests to remove
parsing errors from the output; I should probably do that for the next
version.

OK, I made an incorrect assumption when I wrote the above.
> I didn't realize the HTML was being created directly from
> lyx code.  I was thinking it was going through some common
> intermediate format.  Since not, the problem is between me
> and elyxer and probably insoluble since neither HTML or
> Lyx code have a any concept of a letter sized page.
>

Yes, your intentions (output numbered by actual paper pages) is quite alien
to eLyXer and even to the HTML format itself. Apart from cutting pages at a
fixed number of words, or doing some troff-like abomination (the kind you
see on RFCs: http://www.rfc-editor.org/rfc/rfc1866.txt), I don't see how
that would even work. The natural way to do what you want would be to cut
the output by sections; and frankly I don't understand why that solution
doesn't cut it for you (pun intended).

Another request I have received, and which I need myself, is to output
section names as page names, the kind of dash-separated-titles that you see
on blog posts. I should take out some time to work on eLyXer!

Alex.