mirror of
https://git.lyx.org/repos/lyx.git
synced 2024-11-22 10:00:33 +00:00
6b49b6b129
This makes the defaults of Inset::inheritFont() and Inset::resetFontEdit() compatible. There is no user visible change except for the Chunk inset which does not produce invalid LaTeX after editing operations anymore. This is the safe version for 2.1.0, for later there are still open questions: - All insets with ResetsFont true should be audited: Is this really needed, or do they show similar editing problems as the Chunk inset? - Does inheritFont() need to be customizable in the layout file as well? - Is resetFontEdit() != !inheritFont() needed at all? I did not use change tracking for the docs, since I updated all existing translations.
49 lines
1.3 KiB
Plaintext
49 lines
1.3 KiB
Plaintext
#\DeclareLyXModule[lilypond-book->latex]{LilyPond Book}
|
|
#DescriptionBegin
|
|
#This module adds an inset to enter LilyPond code directly into LyX.
|
|
#It will be processed in the output. See the lilypond.lyx example file.
|
|
#DescriptionEnd
|
|
#Excludes: sweave
|
|
|
|
# Author: Julien Rioux <jrioux@lyx.org>
|
|
|
|
Format 49
|
|
OutputFormat lilypond-book
|
|
|
|
InsetLayout "Flex:LilyPond"
|
|
LabelString LilyPond
|
|
LaTeXType Environment
|
|
LaTeXName lilypond
|
|
LyXType Custom
|
|
Decoration Classic
|
|
Font
|
|
Color latex
|
|
Family typewriter
|
|
EndFont
|
|
LabelFont
|
|
Color latex
|
|
Size Small
|
|
EndFont
|
|
MultiPar true
|
|
CustomPars false
|
|
ForcePlain true
|
|
FreeSpacing true
|
|
PassThru true
|
|
ParbreakIsNewline true
|
|
ForceLTR true
|
|
Spellcheck false
|
|
Argument 1
|
|
LabelString "Options"
|
|
MenuString "LilyPond Options"
|
|
Tooltip "A comma-separated option list (see the LilyPond documentation for available options)."
|
|
Decoration Conglomerate
|
|
Font
|
|
Color black
|
|
Family typewriter
|
|
EndFont
|
|
LabelFont
|
|
Color black
|
|
EndFont
|
|
EndArgument
|
|
End
|