On 2011-9-22 14:43 , LyX Ticket Tracker wrote:
#7301: Issues with svmono.layout
--------------------+-------------------------------------------------------
Reporter: marcus | Owner: uwestoehr
Type: defect | Status: assigned
Priority: normal | Milestone: 2.0.2
Component: layout | Version: 2.0.0svn
Severity: normal | Keywords: fixedintrunk fixedinbranch
--------------------+-------------------------------------------------------
Comment(by jrioux):
Replying to [comment:12 rgheck]:
I.e., all documents that use the old sv* files will still compile with
these ones, and will look the same. Right?
What about files created with these new sv* files?
These styles are not in 2.0.1:
PartBacktext
Running_Chapter
ChapAuthor
ChapSubtitle
ChapMotto
extrachap
Extrachap
Foreword
Svgraybox
The corresponding commands and environments are supported by
svmono.cls. Now LyX supports them as well. In particular, there will be
fewer errors with tex2lyx conversions. Uwe has documented the
non-obvious styles in his new version of the svmono template.
These styles were renamed:
Problem->Prob
Solution->Sol
Sorry, I overlooked this. Unfortunately, this problem is due to a bug
in the LyX 2.0.1 version of the svmono layout and does not appear to be
fixable:
svmono.cls supports both a "problem" and a "prob" environment but only
the prob environment is documented. Similar for "solution" and 'sol".
In LyX 2.0.1 the style prob has been implemented but it has been called
"Problem". This would confuse svmono users who are transitioning from
LaTeX to LyX as well as users who are relying on the documentation
provided by Springer. We thought that in this case it would be best to
correct the bug in the old LyX layout and to follow Springer's usage.
Old files will still compile but the output will be different. Problems
will simply get "Problem " prepended to the label. Solutions will
get "Solution " prepended to the label but in addition LyX will print
out the reference-label string of the corresponding problem. It should
be obvious to the user how to fix these issue as these styles are
documented in Uwe's template.
Regards, Marcus
