CSS for InsetInfo.

git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@30077 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
Richard Heck 2009-06-12 15:27:29 +00:00
parent 1ad1c51c22
commit 082ec01eef
2 changed files with 23 additions and 5 deletions

View File

@ -11,8 +11,8 @@ Known issues:
These insets are basically done, though there are probably issues here and there, These insets are basically done, though there are probably issues here and there,
and there are even some FIXMEs: and there are even some FIXMEs:
Bibitem, Branch, Collapsable, Footnote, Hyperlink, Label, Line, Note, Bibitem, Branch, Collapsable, Footnote, Hyperlink, Info, Label, Line,
Newline, Newpage, Quotes, Space, SpecialChar Marginal, Note, Newline, Newpage, Quotes, Space, SpecialChar
These insets do nothing for XHTML: These insets do nothing for XHTML:
ERT, OptArg, Phantom ERT, OptArg, Phantom
@ -45,6 +45,7 @@ These insets do not work and are not yet scheduled to work:
InsetIndex and InsetPrintIndex: An "advanced" case. What really would be cool InsetIndex and InsetPrintIndex: An "advanced" case. What really would be cool
would be to collect all of these and then write the index as a series of links would be to collect all of these and then write the index as a series of links
back to the occurrences. But not now. back to the occurrences. But not now.
InsetNomencl and InsetPrintNomencl: Also "advanced".
May need to make use here of TocWidget::itemInset, which should then be moved May need to make use here of TocWidget::itemInset, which should then be moved
to TocBackend. to TocBackend.
@ -61,10 +62,7 @@ These do not yet work and need some attention:
InsetInclude: I think we just want to include it, straightforwardly. Probably will InsetInclude: I think we just want to include it, straightforwardly. Probably will
base this more on the latex() routine, then. Another possibility, maybe with a base this more on the latex() routine, then. Another possibility, maybe with a
flag of some sort, would be to do it as a separate file, to which we link. flag of some sort, would be to do it as a separate file, to which we link.
InsetInfo: Probably skip it.
InsetListings: Probably just output it as <pre>. InsetListings: Probably just output it as <pre>.
InsetMarginal: Fine, but will need CSS.
InsetNomencl and InsetPrintNomencl: Also "advanced".
InsetRef: Presumably, this is an internal link. But what should the text be, and how InsetRef: Presumably, this is an internal link. But what should the text be, and how
should we get it? Probably some validation thing again, where labels tell us where should we get it? Probably some validation thing again, where labels tell us where
they are. Alternatively, we could parse the aux file. they are. Alternatively, we could parse the aux file.

View File

@ -327,6 +327,11 @@ End
InsetLayout Info InsetLayout Info
Decoration conglomerate Decoration conglomerate
HTMLTag span
HTMLAttr class='info'
HTMLStyle
span.info { font-family: sans-serif; }
EndHTMLStyle
End End
InsetLayout Info:menu InsetLayout Info:menu
@ -339,6 +344,11 @@ InsetLayout Info:menu
Font Font
Family sans Family sans
EndFont EndFont
HTMLTag span
HTMLAttr "class='info menu'"
HTMLStyle
span.menu { font-family: sans-serif; }
EndHTMLStyle
End End
InsetLayout Info:shortcut InsetLayout Info:shortcut
@ -351,6 +361,11 @@ InsetLayout Info:shortcut
Font Font
Family sans Family sans
EndFont EndFont
HTMLTag span
HTMLAttr "class='info shortcut'"
HTMLStyle
span.shortcut { font-family: sans-serif; }
EndHTMLStyle
End End
InsetLayout Info:shortcuts InsetLayout Info:shortcuts
@ -363,6 +378,11 @@ InsetLayout Info:shortcuts
Font Font
Family sans Family sans
EndFont EndFont
HTMLTag span
HTMLAttr "class='info shortcut'"
HTMLStyle
span.shortcut { font-family: sans-serif; }
EndHTMLStyle
End End
InsetLayout Box InsetLayout Box