On 12/02/2011 01:56 PM, Steve Litt wrote:
> On Friday, December 02, 2011 10:30:17 AM Richard Heck wrote:
>> On 12/02/2011 05:12 AM, Steve Litt wrote:
>>> ...I could swear LyX's internal HTML exporter is simply eLyXer,
>>> as it outputs eLyXer messages.
>> The format for the internal exporter is "LyXHTML". This should be
>> in your view and export menus.
>>
>> Richard
> Found it! As long as I have your attention, how do you tell the export
> what CSS file to use?
>
That is all done through layout files. (It's the LyX way.) Much of the
CSS is automatically generated. E.g., if you set up some character style
with boldface text in LyX, then the XHTML output will generate
appropriate CSS:
span.stevestyle {
font-weight: bold;
}
unless told to generate something else. You can customize what is
generated by adding some layout tags to the InsetLayout declaration:
HTMLStyle
span.stevestyle {
font-weight: bold;
background-color: red;
}
EndHTMLStyle
Given the presence of this tag, the default CSS will no longer be
generated (but can be forced via "HTMLForceCSS 1".) But, as I said, if
you just want the obvious thing, LyX will generate it for you. I like
this, because everything is in one place, and you often don't have to do
anything special for XHTML output.
This is why Rob said he was working on layouts for ePub generation.
See section 5.4 of the Customization manual for more.
At present, LyX's XHTML output does not have the ability to split by
chapters and such. I think a more flexible method would be to allow
separate output of child documents. (Right now, LyX just outputs them as
part of the main document.) Then you divide it up how you like. This
shouldn't be too hard. I just haven't had time to do it. Too many other,
more pressing bugs to fix right at the moment.
Richard
