Re: [PATCH] LyX HiDPI support in OS X with Qt 5
> There are some reports on the users list about LyX not finding standard > classes. > AFAIK, all the users reporting this problem are Yosemite users. > > There is some feedback that this is helpful: > http://tex.stackexchange.com/questions/203810/lyx-2-x-document-class-not-available-mac-os-x-10-10-yosemite-pb-3 Actually I do not have these problems with LyX 2.1.2. Even with Yosemite, LyX 2.1.2 fully works for me. The problems I mentioned before only appear with the new retina build. I am starting the retina version from the Desktop rather than the Application folder, but I would be surprised if this mattered. I should probably also note that I have an additional python installation (Python 2.7.6 via Anaconda 1.9.1) which is pointed to by the name “python” (set in my bash startup file).
Re: [PATCH] LyX HiDPI support in OS X with Qt 5
Stephan Witt gmx.net> writes: > > Here is a first version for an evaluation of the feature: > > https://dl.dropboxusercontent.com/u/27842660/ LyX-2.2.0dev-a09eaf44%2Bqt5-x86_64-cocoa.dmg > https://dl.dropboxusercontent.com/u/27842660/ LyX-2.2.0dev-a09eaf44%2Bqt5-x86_64-cocoa.dmg.sig > Thanks for your great work! I just tried out your built and had the following experience: I opened a document pertaining to a book project and I got the following error message for every file included in the project: The selected document class Book (Standard Class) requires external files that are not available. The document class can still be used, but the document cannot be compiled until the following prerequisites are installed: book.cls See section 3.1.2.2 (Class Availability) of the User's Guide for more information. I also got the following error message: Changes will not be highlighted in LaTeX output, because neither dvipost nor xcolor/ulem are installed. Please install these packages or redefine \lyxadded and \lyxdeleted in the LaTeX preamble. Included pdf-graphics are not displayed in LyX (Error converting to loadable format). Nevertheless, I could edit my document and compiling the document worked without a hitch, despite LyX complaining about book.cls. My system is as follows: OSX 10.10 Yosemite, TexLive-2013 I also had installed some special layouts in my Library, and they did work as well.
Regression: macro display issues with 2.1 RC1 (Mac)
I have partially repeatable display issues concerning macros.
In old documentssome formulas display (some) macros as an empty boxes with blue
frames. For instance, I head defined \varexp to be \mathrm{e}. This macro is
sometimes displayed as a non-cursive e (as it should be) and sometimes as an
empty box with a blue frame. I even saw different displays in the same
formula. As far as I can tell, all my macros are affected. Sometimes I can
manage to replace the empty box by retyping the macro, sometimes not. If I
save and close the document and then re-open again, the retyped macro will
display as a box again.
This is the behavior of an existing child document, which is part of a rather
complex book project. I have tried to create a new, simple document to display
this issue. But I cannot consistently reproduce it. When I open my simple
document I sometimes see boxes and sometimes I see the macros. Sometimes some
macros are displayed as boxes and others are displayed correctly. The issue
seems to arise whether or not I am using child documents. Having said this, I
believe that it arises more often with child documents.
These issues are not present in Lyx 2.1 beta 2.
I also noticed a second issue. I am working with automatic preview enabled.
This works with my old documents, even when I am using LyX 2.1 RC1. However,
it does not seem to work with the new documents I created today, regardless of
whether i am using LyX 2.1 beta 2 or LyX 2.1 RC1. Since it is a while since I
created a new LyX document I do not know whether this is a new issue or an old
one.
I am using OSX Mavericks and the binaries posted by the LyX Project.
Regards, Marcus
Re: bug report
I can confirm the observation of Dan: Insert > Special Character > Symbols dialog box is completely devoid of symbols. This is on Mac OS 10.9 with the 2.1.0beta2 Mac binary produced by the LyX team Regards, Marcus > On Tue, Dec 31, 2013 at 12:29 AM, DWL wrote: > > Hi, > > > > Searched the bug tracker wiki. Couldn't find this one. It's major, at least > > to me. > > > > LyX Version: 2.1.0beta2 > > OS: Macintosh 10.6.8 > > Package came from the pre-compiled disc image on LyX website. > > > > Symptom: Insert > Special Character > Symbols dialog box is completely > > devoid > > of symbols. Every Category is blank. I've attached one screen cap as an > > example. > > I cannot reproduce on Ubuntu 13.10. I agree that this is serious if > other mac users can reproduce. Is there any terminal output? If not, > maybe try starting LyX with -dbg info and see if there's any useful > messages. > > Scott >
Re: Bug #8445
I apologize, this was false alarm. I must have inadvertently tested on beta 1 rather than beta 2. Anyway, I re-downloaded the mac-binary for beta 2 and can confirm that it works as advertised. Marcus On 2013-11-18 , at 22:44, Scott Kostyshak wrote: > From what I understand, that patch is already in LyX 2.1 beta 2. If it > does not work for you, post any information on the ticket. > > Scott > > On Mon, Nov 18, 2013 at 5:45 PM, Marcus Kriele wrote: >> From the bug tracker I understand that Jürgen Spitzmüller has a patch for >> #8445 which is supposed to go into LyX 2.1. However, I still see this bug >> in 2.1 beta 2 (OSX Mavericks). Would it be possible to fix it for the next >> beta? >> Marcus >> PS. Thanks for all your great work on LyX, which I find is a truly >> outstanding program
Bug #8445
From the bug tracker I understand that Jürgen Spitzmüller has a patch for #8445 which is supposed to go into LyX 2.1. However, I still see this bug in 2.1 beta 2 (OSX Mavericks). Would it be possible to fix it for the next beta? Marcus PS. Thanks for all your great work on LyX, which I find is a truly outstanding program
Re: #7301: Issues with svmono.layout
Yes, #7506 is invalid and I just marked as as such. On 2011-9-23 19:32 , 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): OK thanks for your explanation. So as long as backward compatibility is respected it is acceptable for branch. It's a design decision that I will have to remember and live with. The idea about the release notes is good. One could also mention that forward compatibility is possible if users copy the new layouts to their user directory. By the way your commits might also have fixed #7506, please check.
Re: #7301: Issues with svmono.layout
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
Re: #7301: Issues with svmono.layout
Richard, I had hoped that Uwe would reply as he made the final changes. The files I had submitted were exensively tested and their last version did not have any issues with old sv files. I had also tested Uwe's last modifications. His version also appeared to work well with old sv files, so the new sv layout files should be fit for branch. Regards, Marcus On 2011-9-5 15:44 , 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 +--- Changes (by rgheck): * keywords: patch fixedintrunk => fixedintrunk Comment: Now that 2.0.1 is out these can go to branch. I just want to check and make sure that none of these changes are the sorts of things that would require lyx2lyx. I.e., all documents that use the old sv* files will still compile with these ones, and will look the same. Right? I can commit to branch when that is confirmed.
Re: Instant preview does not work for lyx 2.0.1 for OSX
I have now identified what caused my problem. I can easily work around
the issue as it relates to some preamble code that I do not need.
However, the issue points to strange side effects.
I was looking at child documents of a master document. The preamble of
the master document contains the line
\def\Master {}
each of the preambles of the child documents contains the lines
\ifx \Master\undefined
\input{../Preambles/Preamble_Standard}
\input{../Preambles/Preamble_tikz}
\fi
In both LyX 2.0.0 and LyX 2.0.1 the "view master document" command
produces a correct pdf file. However, instant preview does not work for
LyX equations. If I delete the lines "\ifx ... \fi" in the preamble of a
child document and then save and reload the child document, then instant
preview for LyX equations works again in this child document. For LyX
2.0.0 it does not matter whether these lines are present or not. In both
LyX 2.0.0 and LyX 2.0.1 instant preview works for included graphics
whether these lines are present or not.
Re: Instant preview does not work for lyx 2.0.1 for OSX
Sorry, I should have been more precise. Instant preview for included graphics (I have now tested jpg, pdf, eps) does work for me. What does not work is instant preview for equations which are typeset in LyX. I am using OSX 10.7.1 Regards, Marcus
Instant preview does not work for lyx 2.0.1 for OSX
Instant preview does not seem to work with the 2.0.1 cocoa binary for Mac OSX. I have re-downloaded the last 2.0.0 version of the binary and instant preview works flawlessly with this older version. Therefore my problem does not seem to be caused by my lyx settings, unless I missed a change of lyx settings which would be required for 2.0.1. Regards, Marcus
Re: RFI: label prefix not actualized when section heading type is changed
I seem to remember that I had recently changed a label in a document with several children and the references in other children have automatically been updated correctly. However, even if updating across children works at all times, there would be pitfalls in co-authored docuements. For instance, you may co-author a book where each chapter is a child. If the co-author changes a label on his/her machine, his/her references in other child documentsget updated but not yours. So if you include the updated chapter from your co-author, references in your version would get orphaned. This is a real problem as you would usually work concurrently on different chapters.I believe that this is a serious argument against automated updating of labels. In addition, my 10 year+ experience with Microsoft Word indicates that auto labels do not work well. I don't think I ever wrote a word document with auto labels where all the references worked out of the box. In fact, this problem caused me to use LyX or LaTeX whenever possible, even when I was working in a "Word-only" environment. Regards, Marcus
Re: Springer layout files
I noticed two additional bugs in the style preface (for svmono):
1) The style Preface has been assigned to the category "For Authors".
This could be appropriate for the class svmult but not for svmono. I
propose to use the category "FrontMatter"
2) Preface has an optional argument just as Foreword. But this is not
supported in LyX
I still don't get the sense of this optional argument. Can you please
make a proposal for the note?
Proposal:
The style "Foreword" has an optional argument that overrides the default
text ("Foreword" in English, "Geleitwort" in German etc.). For
instance, a book in a series may contain a foreword by the authors and
an addition foreword by the editor of the book series. In this case,
the author could use the style "Foreword" without optional argument and
the editor could use the style "Foreword" with the the optional argument
"Foreword by the Editor". The style "Preface" also supports an optional
argument that overrides the default text. For instance, the 2nd edition
of a book could contain a preface and still retain the preface to the
first edition. For the latter, one would use the style "Preface" with
the optional argument "Preface to the First Edition".
The problem is that Springer redefines a lot in their cls-files. As
consequence Title* fails when hyperref is used. I disabled it in the
file and it works now.
Should there be a note that warns the reader? I would imagine that most
authors would turn on hyperref to make their pdfs more versatile.
Regards, Marcus
Re: Springer layout files
On 2011-7-15 13:06 , Uwe Stöhr wrote: This is not necessary. Before LyX was able to display the number also within LyX, we used a normal "#" to indicate that in the output will be a number. Colored labels indicate that they are only hints what to do and don't appear in the output. But in this case you get a number in the output. Thanks, good to know Ideally, one would replace "[label of Prob]" by the actual counter of the problem but I could not do this. This is not possible. Implementing such a feature in LyX would require a lot of work (the prob is in a subdocument of a master file and the sol too, moreover th3ey are in different chapter with different styles, that's why also LaTeX needs several runs to get the number). So I don't think that it is worth it. okay I have attached an example. This is because you didn't use the argument. The Sol style required an optional argument (the argument is not optional as the nae says, but in case of Sol mandatory). But I described that in the template files. Yes, I should have been clearer. My intention was to show potential problems if the user does not know that there is an optional argument. In any case, your changes address my concern. Thanks and regards, Marcus
Re: Springer layout files
On 2011-7-13 22:35 , Uwe Stöhr wrote:
Am 11.07.2011 23:35, schrieb Marcus Kriele:
However, I would change the label of the
sol environment: Currently it is an automatically generated counter
that may have nothing to do with
the counter of the corresponding problem. I find this misleading.
To what should I change it, a string plus the counter? If yes, what
string?
I do not think that a counter should be created for Sol. In the attached
document I have give examples why a counter would be problematic. I am
proposing something like this:
Style Sol
LabelString "Sol [label of Prob]"
LabelFont
Color Blue
EndFont
End
This label is ugly but gives the user a hint what to do. I chose the
color blue to indicate that this label is different from the actual
output. Ideally, one would replace "[label of Prob]" by the actual
counter of the problem but I could not do this. (I tried " LabelString
"Sol \ref{#1}" " but LyX ignored the part \ref{#1}.)
In addition, if the solutions are
written in the same order as the problems then in LyX it appears that
each solution references the
correct problem. However, the output gives question marks as the
references are not given
explicitly.
I don't get them with the template files. How can I get them?
I have attached an example.
I would prefer a label like "sol [label of problem]". While this
looks very different
from the output, it would reduce the likelihood of user error.
So you mean I should change the name of the style (the one in LyX's
style-combobox). If so, I'll do this as you suggested. But this is
independent of the label you see in your text when using Sol. How
should I change it. To avoid confusions, it is perhaps better if you
send me a patch how you would like to have it and I put it in. OK?
Sorry, I meant the label in the text window, not the LyX Style
combobox. I think that your choice in the combobox is okay. I have
given above a proposal for the label in the text.
(Btw. It is really time that I start documenting all the new LyX 2.0
features if even I don't know them all.)
In my opinion, the documentation is excellent and one of the strengths
of LyX. I am sure that it is an awful lot of work to keep it up to date
but I am also sure that many users will be grateful for this.
Regards,
Marcus
#LyX 2.0 created this file. For more info see http://www.lyx.org/
\lyxformat 413
\begin_document
\begin_header
\textclass svmono
\begin_preamble
\usepackage{type1cm}
\usepackage{multicol} % used for the two-column index
\usepackage[bottom]{footmisc} % places footnotes at page bottom
%\makeindex % used for the subject index
% please use the style svind.ist with
% your makeindex program
\end_preamble
\options graybox,envcountchap,sectrefs
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman times
\font_sans helvet
\font_typewriter courier
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered true
\pdf_bookmarksopen true
\pdf_bookmarksopenlevel 1
\pdf_breaklinks false
\pdf_pdfborder true
\pdf_colorlinks false
\pdf_backref false
\pdf_pdfusetitle true
\papersize default
\use_geometry false
\use_amsmath 1
\use_esint 1
\use_mhchem 1
\use_mathdots 1
\cite_engine basic
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Chapter
Examples for Solution Environments in svmono
\end_layout
\begin_layout Section
Problems
\end_layout
\begin_layout Prob
\begin_inset CommandInset label
LatexCommand label
name "prob:First-Prob-Environment"
\end_inset
First Prob Environment
\end_layout
\begin_layout --Separator--
\end_layout
\begin_layout Prob
\begin_inset CommandInset label
LatexCommand label
name "prob:Second-Prob-Environment"
\end_inset
Second Prob Environment
\end_layout
\begin_layout Section
Solutions
\end_layout
\begin_layout Sol
First solution.
My intent is to give the solution to Problem
\begin_inset CommandInset ref
LatexCommand ref
reference "prob:First-Prob-Environment"
\end_inset
.
I have not given the (required) optional argument, but it looks as if LyX
understands m
Re: Springer layout files
I have tested the new layouts and templates for svmono, svjour3, and
svmult. In these new versions, the proof, solution and problem
environments work for me. However, I would change the label of the sol
environment: Currently it is an automatically generated counter that
may have nothing to do with the counter of the corresponding problem. I
find this misleading. In addition, if the solutions are written in the
same order as the problems then in LyX it appears that each solution
references the correct problem. However, the output gives question
marks as the references are not given explicitly. I would prefer a
label like "sol [label of problem]". While this looks very different
from the output, it would reduce the likelihood of user error.
I also have a few additional comments:
svmono:
1) Minor -- Master document has not been set. I propose to do so for
each include file
How can I do this?
For each document that is to be included: Documents -> Settings... ->
Document Class, check "Select default master document", browse for the
master document. This may result in an absolute path, but you can edit
this path to make it relative. (I only tested this on mac).
4) Medium -- chapter.lyx: References to LaTeX should be replaced by
references to LyX, e.g,
"Furtheron please use the LaTeX automatism for all your
cross-references and citations." There are
several instances of such references.
The references to LaTeX are still present. I think that this would
confuse some users as the references are managed within the LyX GUI.
Some users may conclude that they would have to use LaTeX-commands in
ERT insets to get cross referencing to work.
6) Medium -- appendix.lyx: The section A.1 is too short to illustrate
the Style "Running Section".
The same problem arises in section 1 of chapter.lyx
I think that the user will understand how it works from the other
"running" environments like author and title. Expanding the template
with senseless text won't help much since it is a template, not an
example. When the user writes his text, he will automatically expand
it to see the short section heading in the page title.
fair enough
9) Medium -- foreword.lyx: Optional argument has not been explained
I don't understand this option. If I need another heading, I can
directly change it, why do I need an optional heading for this?
The user would need to use the extrachap command which might not be
obvious to her/him. Perhaps one could document the usage in a comment
note? Same for preface.
I also corrected for "solution" the argument from mandatory to
optional as it appears to be a bug in the Springer templates that they
used a mandatory argument. Their docs and also the logic tells that it
must be an optional one.
I agree
svjour3:
There are two citations to non-existing bibliography entries,
"Abernethy2003" and "Pellacini:2005:LAH"
svmult:
1) title*
In svmult_author.lyx the title* style does not work. Both as an
embedded document and as a stand-alone document you simply get "*" as
the title and the given title ("Contribution Title") is ignored. I
couldn't get this style to work either.
The intended behavior is to produce the title in the output without the
line "chapter 1". It does work with their latex templates.
If you do not have an idea how to do implement title*, I would propose
to delete our title* style and to write a note that we do not support
it. After all, the whole problem is appears to be caused by Springer
hacking the LaTeX title and chapter commands in a way that is not
compatible with the idea of a mark-up language.
(Something minor: title is in the "Section" category while "Title*" is
in the FrontMatter category. While this does reflect the purpose of
title and title *, it would probably be better to present these styles
side by side. )
2) Author
The format in LyX is indistinguishable from the standard format or at
least very similar. I propose to add an italic label "Author: "
similar to the style "Institute".
Other bugs:
I think that the relative path to the pictures
"../../examples/CV-image.png" should read "../examples/CV-image.png".
If this is the case then this bug was originally introduced by me. My
apologies. This applies to svmono_chapter.lyx (twice),
svmono_appendix.lyx, svjour3.lyx (twice), svmult_author.lyx (twice),
svmult_appendix.lyx
Regards, Marcus
Re: Springer layout files
Uwe,
great that you could fix the numbering!
I have tested your templates and I found the following issues (Mac, LyX
2.0.0):
svmono_book.lyx:
1) Minor -- Master document has not been set. I propose to do so for
each include file so that "View master document" and "Update master
document" can be used from each include file immediately. After the
first run LyX knows the master document.
2) Minor -- chapter.lyx, equation eq:10: An equation array style has
been used improperly. The whole equation is in the left column, rather
than spread out over all 3 columns
3) Very Minor -- chapter.lyx, equation eq:10, second line: Okay, this
is quite pedantic and not really a LyX problem:
\vec{a}\cdot\vec{b}=\vec{c} should be replaced by
\vec{a}\cdot\vec{b}=c as the scalar product of two vectors is a scalar
rather than a vector. Having said this, this small error is actually due
to Springer, and I am not sure whether we want to correct it.
4) Medium -- chapter.lyx: References to LaTeX should be replaced by
references to LyX, e.g, "Furtheron please use the LaTeX automatism for
all your cross-references and citations." There are several instances
of such references.
5) Major -- chapter.lyx, Section 1.3.1.1: Neither "Proof" Style nor
"Proof(smartQED)" Style works. "Proof(QED)" does not work either.
6) Medium -- appendix.lyx: The section A.1 is too short to illustrate
the Style "Running Section". The same problem arises in section 1 of
chapter.lyx
7) Minor -- appendix, eqution eq:A01: Same as issues 2) and 3).
8) Medium -- Glossary: No documentation of how the style "Extrachap"
(or the style "extrachap") is to be used. These styles are non-obvious
variants of "Chapter*". Documentation is included in my testfile
"SVmono_testfile.lyx".
9) Medium -- foreword.lyx: Optional argument has not been explained
10) Major -- solution.lyx: The solution style does not work correctly.
It should be numbered (without label "solution") where the numbers are
the corresponding problem numbers. The corresponding problems are given
via references in the optional arguments.
svjour3.lyx:
11) The optional arguments of problem and solution are not supported
correctly.
General:
12) I think you should take credit for your improvements in the header
of the inc and layout files.
For some reason, the three proof environments do not work any more nor
do the solution environments. They did work with my old layout files.
I cannot pinpoint the issues but the following may help to find the bugs:
1) Make in my layout files the following changes:
1a) insert the InTitle flag in my "Title running" style
1b) uncomment the line "RequiredArgs1" in my "Sol" style.
2) in solution.lyx correct the two optional arguments so that they
contain the reference label of the corresponding problems ("prob:prob1"
and "prob:prob2" instead of "probl" and "prob2").
Then your svmono_book.lyx template compiles with my layouts and produce
the correct output.
Specific comments:
1) You have replaced the theorem type environments by the standard
theorem include file, in which
theorem-like environments are defined via \newtheorem.
No, I have not done this because this won't compile and the springer
classes define their own theorem environments.
Where do you see that I have done this? I also wrote you about my
solution in the last mail. So I'm a bit confused now.
Sorry, this was my mistake. I mixed up theorem.inc and
theorem-without-preamble.inc
2) Springer provides two different solution environments, "sol" and
"solution", in their classes
smono.cls and svmult.cls.
I will add "solution" when I review the new layout and include for
svmult. Currently, these files are only reviewed for svmono and svjour.
("sol" is also possible for svmono (it compiles) but the output
consists of question marks and "sol" is not used in the offical
template, only "solution".)
The environment "sol" appears to be preferred and generates a counter
(without any additional label) while the environment "solution"
provides the label "Solution"
together with a counter. Consequently, the styles "Sol" and
"Solution_(theorem-like)"
But your LaTeX code you created via the layout file was for both
environments the same. That's why I removed one of them. It was a bug
in your layout.
It was done on purpose but admittedly not very elegant. Observe that I
redefine some environments in some layout files so that this "double-up"
does not survive in any layout. Anyway, I am not at all opposed to
change this implementation detail. Perhapsit would be best to
explicitly define the solution and problem environments in each layout
file separately?
What environment you think is missing in the new template files? (I
have not listed every possible theorem environment because this is not
necessary - the user will get the idea from the 3 examples I have in
the files.)
I think that the environments are sufficient.
Re: Springer layout files
Uwe, I have not tested the files yet but I have looked through your changes. I find some of these changes problematic as they impair functionality: 1) You have replaced the theorem type environments by the standard theorem include file, in which theorem-like environments are defined via \newtheorem. While this looks much neater it will lead to subtle problems: The .cls files provided by Springer define all these theorem-like environments from scratch using a variation of \newtheorem which is also provided by Springer in the .cls files. Using your include-solution we would be changing the LaTeX content of the .cls file. This is not what the user expects and could lead to problems when articles or books are submitted to Springer. What is more, the typical user would not be aware of these changes. In addition, as Springer uses different LaTeX names, import of Springer LaTeX files would not work well if we would be using our standard theorem include file. 2) Springer provides two different solution environments, "sol" and "solution", in their classes smono.cls and svmult.cls. The environment "sol" appears to be preferred and generates a counter (without any additional label) while the environment "solution" provides the label "Solution" together with a counter. Consequently, the styles "Sol" and "Solution_(theorem-like)" theorems do provide different environments. This is not the case in the class you have looked at, and if I remember correctly, Springer even provides classes in which the environment "sol" has the same implementation as environment "solution" in the smono.cls class. Matters are analogous for the environments "prob" and "problem". It would therefore not be correct to delete one of these environments. The set of layout files I had provided should work correctly in all cases. Please observe that in most layout files some styles are disabled or overwritten so that the layout file is a proper reflection of the class file. Having said this, I am aware that my implementation is a bit clumsy and could benefit from some polish. Our existing template files do not correspond closely to the official example files. Having said that, the official example files are not very useful as they do explain latex specific constructs that are not interesting for LyX users but do not explain all environments provided by the class file. My test files might be more useful as a template as they show all environments and commands in action. Please note that I have not defined any environment or command that is not provided in the corresponding Springer class file. Regards, Marcus
Re: Springer layout files
Hi Uwe, thanks for the work you are putting in to improve my changes! On 2011-6-17 24:35 , Uwe Stöhr wrote: I had a look and fixed this. (You forgot to define the counters.) I created now a new file which contains all theorem environments of classes which already define them, like the sv*** classes. Thanks! - defining the column and side number in svcommon is no good idea since a book might have 2 columns and 2 sides, while an article is only 1-sided. Some articles have 1, some 2 columns. I therefore removed this definition I agree that my implementation was not elegant. However, I have tested all classes, including 1 and 2-column text for articles. According to my testing there were no problems with my original implementation. - Definitions like "LeftMargin "TOC title:xxx"" are problematic. The strings will be translatd. Assume that for "TOC" there is e.g. no corresponding abbreviation in German and it will therefore be translated to "Inhaltsverzeichnis" which is much longer. Thanks for pointing this out. I completely ignored localization. If you have a better naming idea, could you please change the files accordingly? - for titlerunning and authorrunning the InTitle flag was missing. This is necessary that LyX don't end the title when these commands are inserted Thanks. I did not notice this issue. - svcommons contained Style Sol and Style Solution_(theorem-like). From its definition both lead to the same LaTeX/PDF output. So we only need one of them. The same was for Style Problem. I therefore removed the doubled Styles. Springer is very inconsistent with its classes and they managed to use different names for identical environments in different classes. In addition, they use the same name for different environments. So you will see that some environments have been redefined in the class specific layout files. I have actually searched the .cls files to find out what names they have used in every instance. Could you please revert your deletions so that the LyX classes are consistent with the corresponding LaTeX classes? I committed my changes to SVN trunk: http://www.lyx.org/trac/changeset/39126 and also adapted the svjour3.lyx template file according to the latest version of the official svjour3 example LaTeX-file. Please test. Sorry, I am not a developer and do not know how SVN & changesets work. Could you send me the files via email? I would then do some testing if you would find this helpful. I did not yet have a look at svmono and svmult. I will do this the next days. Please see the *testfile*.lyx files that I had uploaded to the bug report 7301 Our template files for these classes are of course still compilable after my changes but I guess they need to be adapted for the latest versions of the official LaTeX example files. Do you want to do this? Perhaps my test files could serve as template files. The advantage would be that they use all features. regards Uwe
Re: Springer layout files
Please see the class specific test files that I had uploaded to bug report #7301. They should contain every feature that is supported. Hopefully this reduced the amount of time necessary for further testing. I had also uploaded updated template files. Regards, Marcus On 2011-6-17 9:43 , Uwe Stöhr wrote: Am 17.06.2011 14:18, schrieb Richard Heck: Thanks, Uwe, for having a close look at these. I guess this stuff should be ported to branch, but probably not until 2.0.2, Yes, we need more testing before this can go to branch. svcommon is used for 3 different classes and I only reviewed 1 in detail. regards Uwe
Re: More Flex Copying Issues
Uwe, please see my comments below. Marcus On 2011-6-16 18:53 , Uwe Stöhr wrote: Am 16.06.2011 19:41, schrieb Marcus Kriele: > The following issues still persist: > > 2) "Short title" for optional arguments does not work. This is intentional in order to guarantee > backward compatibility. I don't understand. If the current classes support this, we must support it too. Older versions don't use optional arguments and are therefore still compilable. These LaTeX classes have always supported optional arguments but the LyX layouts did not. In my testing I got the impression that correcting this issue could prevent old documents from compiling if they use the ERT work-around. > One can use ERT instead of "Short title". (By the way, wouldn't it be > advisable to change the GUI? For a new user it would be hard to guess the general meaning of > "Short title".) The problem is that it is in LaTeX's sense an optional argument, but the average user don't care about the LateX internals. In most cases, they use it as short title. Personally, I think that our users will understand when we explain in the UserGuide that in case of a section an option argument means short title. Short titles are only one usage while we have about 100 others in our layout files. I agree. In fact, it took me a while to figure out that "short title" has a more general usage. > 3) Numbering of theorems within LyX does not work. I tried to copy the implementation of the > theorem-sec.module but LyX does not pick up the correct \thetheorem value. You need to define a counter. I'll have a look. Thanks. I did but I must have done something wrong. > 4) Book authors may need the LaTeX commands \sidecaption and \sidecaption[t] for the correct > placement of figure captions. tex2lyx does not know \sidecaption[t]. Why do we need tex2lyx here? In general using sidecap with LyX is possible and I described this in sec. 3.10 "Caption Placement" of the EmbeddedObjects manual. I had the issue that I tried to import a LaTeX document that used "\sidecaption[t]". The optional argument "[t]" was interpreted as text. This import error may be hard to notice. The LyX document compiles but obviously not as intended. --- The class svjour is obsolete. The current version is svjour3. I therefore declared it obsolete in http://www.lyx.org/trac/changeset/39115 OK? I agree that this class is obsolete. I simply tried to support the class in case some people are still using it or wish to compile old documents I don't know enough about this declaration to comment on whether it is okay. regards Uwe
More Flex Copying Issues
Richard, svglobal3.layout is one of the Springer layout files which I had updated (#bug 7301). The issue should not exist in my corrected files that I had posted in the bug report and sent to you as a zipped archive. Marcus
Re: #7506: CopyStyle for inset layout does not work
On 2011-4-29 7:07 , LyX Ticket Tracker wrote: #7506: CopyStyle for inset layout does not work Comment(by rgheck): I'll have to check this with current trunk. But I'm guessing that the issue is just that the new layouts were not named properly, yet the layout format is beyond where lyx2lyx will fix this. The problem is that old layout files do not work anymore because the CopyStyle directive does not work with the legacy naming convention for inset layout styles.
License permission
I hereby grant permission to license my contributions to LyX under the Gnu General Public License, version 2 or later. Marcus Kriele To date I have only fixed some sv* layout files (Bug 7301) which is targeted for 2.0.1.
Re: Bug #7301: New layout for Springer (smono.layout, smult.layout, sjour3.layout)
On 2011-4-26 14:58 , Richard Heck wrote: On 04/26/2011 02:09 PM, Marcus Kriele wrote: I have found that LyXHTML chokes on the table of contents. If the table of contents is removed in my example files then LyXHTML produces valid HTML files that can be read by Firefox 4. Hmm. Well, I should check that out for sure. This is with one of your test files? Could you add that info to the bug report so I don't forget it? Yes, svmono_test.layout, for instance. I have added this info to the bug report. Can these layouts be included in Version 2.0.1 as they stand? I'll have a look at all of this once 2.0.0 is out. If there's no backwards compatibility issue, then they could go into 2.0.x. If you want to commit other improvements to 2.1.x, that would be fine, too. That would be nice. Would it also be possible to add in 2.0.1 to the file that provides LyX latex import with info about LaTeX commands the info about \sidecaption, sidecaption[t]? For 2.1 I would like to address the small issues that were necessitated by the backward compatibility. But I would like to wait with this until the alpha or early beta phase of 2.1. Marcus
Re: Bug #7301: New layout for Springer (smono.layout, smult.layout, sjour3.layout)
I have produced a new version of the layout files, the test files, and the templates. It has been posted to the bug tracker. This new version is now fully backward compatible. However, the style abstract now behaves differently as the current implementation is broken. The following price has been paid for backward compatibility: 1) The style preface has a different behavior from the analogous style foreword. Import into LyX does not work well as the style defines its own LaTex command. 2) The style Sol uses ERT in order to pass an argument. The only reason for this implementation is backward compatibility. 3) Some Styles are implemented as insets even though they define paragraph styles. I have found that LyXHTML chokes on the table of contents. If the table of contents is removed in my example files then LyXHTML produces valid HTML files that can be read by Firefox 4. Can these layouts be included in Version 2.0.1 as they stand? Marcus PS: Surprising advantage of LyX over plain LaTeX: References to chapter numbers are incorrect in LaTeX files that use svmult.cls, probably due to the way Springer is messing with he \title command. However, if one imports the offending LaTeX file into LyX, the chapter references suddenly work.
Re: Bug #7301: New layout for Springer (smono.layout, smult.layout, sjour3.layout)
Here is a list of backward incompatibilities and issues with the existing layouts -- svglobal3.layout, (Original Layout, to be replaced by svjour3.layout) Original template Issues: a) Insets Keywords, PACS, Subclass: I do not know how to insert these inserts. (They are not listed in the "Custom Insets" menu). Their output is not as expected. Each Inset should start a new paragraph with a label bold label "Keywords", "PACS", "Mathematics Subject Classification (2000)". However, only the content of the inset is output in standard text. It appears as if these insets are treated as "undefined". This is due to the fact that the layout uses CopyStyle. However, contrary to our documentation, CopyStyle does not work for insets. (I did not find a bug report. Is it a but in the documentation or in the layout implementation?). Other original layout Issues: None Backward incompatibility issues: 1) The insets Keywords, PACS, Subclass are replaced by paragraph styles. In addition, Subclass has been renamed to MSC. 2) The layout file is not found automatically because I have renamed it. -- svmono.layout Original template issues: b) Uses Style "Subparagraph" which is not defined. (replaced by default) Other original layout issues: c) Style "Headnote": latex command "\headnote" not defined in current LaTeX class d) Style "Author Running": latex command "\authorrunning" not defined in current LaTeX class e) Style "Running Title": latex command "\runningtitle" not defined in current LaTeX class f) Style "Mail": latex command "\mail" not defined in current LaTeX class g) Style "Offprints": latex command "\offprints" not defined in current LaTeX class h) Style "Acknowledgements": latex environment "acknowledgements" not defined in current LaTeX class (Style "Acknowledgement") (without "s") does work) i) Style "Abstract": In the output he first letter of the abstract text is printed next to the label, then there is a line break. This is due to the fact that the Style is defined for an environment but the class file provides a command. j) Style "Problem": Implements the provided environment "prob" rather than the provided environment "problem". In addition, the display in Lyx resembles the environment "problem" rather than the implemented environment "prob". k) Style "Solution":Implements the provided environment "sol" rather than the provided environment "solution". In addition, the display in Lyx resembles the environment "solution" rather than the implemented environment "sol". The environment "sol" has one required argument in which the name of a label reference label is to be provided. While one can access "short title", this does not work. One has to provide the label in ERT. l) Style "Description": Does not support an optional argument that is supported by the latex class. Backward compatibility issues: 3) Styles "Preface" and "Foreword": Originally they could be overwritten. This does not work any more. 4) Style "Abstract": Error corrected, but the next paragraph is printed with another abstract label. 5) Styles "Problem" and "Solution": Now a different environment. The ERT in the Solution environment is not interpreted as a label but simply printed. -- svmult.layout Original template issues: m) Subparagraph: same as b) for svmono.layout Other original layout issues: n) Abstract: same as i) for svmono.layout Backward incompatibility 6) Style "List of Abreviations & Symbols": Not supported. This is a legacy style that is still supported by the class file but not mentioned in the current class documentation which proposes an alternative method. 7) Inset "Inst": Not supported. Not supported. This is a legacy style that is still supported by the class file but not mentioned in the current class documentation which proposes an alternative method. 8) Style "Running LaTeX Title": Renamed to "Running Title" 9) Style "Author running": Renamed to "Running Author" 10) Style "minitoc": Not Supported. 11) Style " Title*": Not Supported. With respect to the backward incompatibility I would like to propose the following for 2.01: 1) Change Styles back to insets, change name MSC back to Subclass 2) Use the name "svglobal3.layout" rather than "svjour3.layout" 3) This is a bug. I should restore the original functionality 4) Live with the incompatibility as the original implementation does not work anyway. (I suspect that it would work with old springer class files but I feel that we should not support every old version of every class file) 5) Live with the incompatibility. The existing implementation of svmono.layout is inconsistent with the existing implementation of smult.layout and svglobal3.layout, anyway. Alternatively, I could restore the old behavior. In your opinion, would be the lesser of the two evils? 6) Implement the style but have the LyX label text in red and add "[deprecated]" to the LyX Label 7) Implement the inset but have the LyX
Bug #7301: New layout for Springer (smono.layout, smult.layout, sjour3.layout)
I have prepared replacement layout files for Springer monographs
(svmono.layout), Springer contributed books (svmult.layout), Springer
journals (svjour3.layout). I also prepared a file svcommon.inc that is
read by all three layout files. They do not depend on any current
layout files. These layout files support more features than the
existing layout files (with the same names) and are mimicking the output
in LyX more closely than the current files. In addition, some current
layout files are not fully compatible with the current LaTeX classes
used by Springer.
There are two further existing layout files for Springer Journals,
svglobal.layout and svjog.layout. They support obsolete Springer LaTeX
classes. (The layout svglobal3.layout supports the current class
svjour3.cls and would be replaced by svjour3.layout). These two layout
files depend on svjour.inc and could be maintained separately from my
replacements.
Limitations of the new layouts:
1) They are not fully backward compatible.
2) LyXHTML output does not work well. Testfiles for svmono.layout and
svmult.layout generate errors ("This page contains the following errors:
error on line 1452 at column 8: Opening and ending tag mismatch: div
line 0 and body Below is a rendering of the page up to the first
error.") The error is caught at the end of the file. The HTML file
opens in Chrome and Safari but not in Firefox 4. Rendering is
imperfect, in particular, default text is rendered in a large bold
Font. The testfile for svjour3.layout did not generate error messages.
Output is better but far from perfect.
3) I have not implemented every latex tweak that is documented in
Springer's reference guides. As it is, the style drop-down list is
already very large and requires some scrolling.
4) Book authors may need the LaTeX commands \sidecaption and
\sidecaption[t] for the correct placement of figure captions. tex2lyx
does not know \sidecaption[t]. Georg wrote this command would be
imported correctly if it was registered in the file
"lib/synlib/syntax.default". As I am not a developer, could someone do
this who has write access?
There are test files for all implemented features and I have updated the
Template files to work with the new layouts.
I would be happy if someone could test these layouts, both for errors
and usability.It would also be great if someone could fix the HTML
issues as I have no experience with HTML markup. The files have been
uploaded to the bug report #7301.
Would you need a mail that I give GPL permission for my contributions or
is this only required for real code?
Marcus
Re: Additional layout question and tex2lyx problems
Thanks! I have filed a bug (#7468) for those cases where there should be support from the layout file. I believe that the layout was known to tex2lyx since the created LyX document used formatting that I had defined in the same layout file. Marcus
Additional layout question and tex2lyx problems
I am trying to support a command with argument for run-in headings: It produces a small vertical skip without indent and then writes the text in the argument in a bold font. Is it possible to mimic this behavior in LyX? I experimented with the "LabelType Manual" directive but could not get it to work as I also need to pass the label text as an argument. At this time I am simply using a static label to indicate the style but this is of course not a very good solution. Answering myself: A better solution is implemented in the standard Style "Author". In LyX the argument appears on a line by itself (rather than running into the text). This behavior is a little different from the output but probably more in line with wysiwym than a faithful representation.
Additional layout question and tex2lyx problems
I am trying to support a command with argument for run-in headings: It produces a small vertical skip without indent and then writes the text in the argument in a bold font. Is it possible to mimic this behavior in LyX? I experimented with the "LabelType Manual" directive but could not get it to work as I also need to pass the label text as an argument. At this time I am simply using a static label to indicate the style but this is of course not a very good solution. I also ran into various problems with tex2lyx when I tried to import tex-documents with LaTeX-commands that use required or optional arguments and that are supported in the layout. Are such problems well known or should I file a bug report? tex2lyx also failed to import an unsupported command with optional argument: in \sidecaption[t] the optional argument was imported as regular text. (LyX 2.0.0 RC3 and OSX) Marcus
Re: Layout questions
On 2011-4-18 9:12 , Jean-Marc Lasgouttes wrote: Then the question is to know whether this is annoying enough to deserve a new tag :) It might be also that the indenting depends on the question of outputting or not an empty line after environments... JMarc It is certainly a very minor annoyance. If it does not deserve a new directive, then I would prefer leaving the old behavior as it is rather than changing the scope of NextNoIndent to all paragraph environments, as the latter could have unwanted consequences for other layout classes. Marcus
Re: Layout questions
Le 17/04/11 18:27, Marcus Kriele a écrit : Actually, when I come to think of it, I might have tried to use NextNoIndent where the following paragraph was not the default style. So it would be helpful to add to the description that NextNoIndent only has an effect if the following paragraph has default style. Would it be useful for sv classes? In which cases? We could change LyX code to fit output better. JMarc In svmono it depends on the specific style of the following style. Immediately after a theorem like environment the styles Svgraybox and Default are not indented in the output but Petite is indented. As it stands, in LyX the Default style is not indented but the other two styles are. I believe that other latex classes would also exhibit inconsistent behavior. If it is not too difficult to implement, the best solution could be to add a logical layout directive "AdhereToPreviousNextNoIndent" with default values "1" for Default and "0" for all other Styles in case the directive is not explicitly present. Marcus
Re: Layout questions
On 04/16/2011 04:12 PM, Richard Heck wrote: On 04/16/2011 03:59 PM, Julien Rioux wrote: On 16/04/2011 3:40 PM, Marcus Kriele wrote: I am trying to address bug #7301 concerning the Springer layout files, I'll fix the docs Actually, when I come to think of it, I might have tried to use NextNoIndent where the following paragraph was not the default style. So it would be helpful to add to the description that NextNoIndent only has an effect if the following paragraph has default style. Marcus
Re: Layout questions
On 04/16/2011 04:12 PM, Richard Heck wrote: On 04/16/2011 03:59 PM, Julien Rioux wrote: On 16/04/2011 3:40 PM, Marcus Kriele wrote: I am trying to address bug #7301 concerning the Springer layout files, On looking at this now, I see that NextNoIndent should work the way Marcus describes. Here is the relevant code, from TextMetrics::leftMargin(): // This happens after sections in standard classes. The 1.3.x // code compared depths too, but it does not seem necessary // (JMarc) if (tclass.isDefaultLayout(par.layout()) && pit> 0&& pars[pit - 1].layout().nextnoindent) parindent.erase(); So in fact what this does is suppress the indentation if the current paragraph is Standard (or whatever the default is) and the previous paragraph had NextNoIndent. Marcus, did you try the NextNoIndent thing and it didn't work, or was the documentation too confusing for you even to try it? I'll fix the docs. Thanks, I must have done something wrong when I tried it yesterday. The description in the documentation is clear, and I could get it to work now. Marcus
Re: Layout questions
Sat, 16 Apr 2011 13:00:04 -0700Julien Rioux
On 16/04/2011 3:40 PM, Marcus Kriele wrote:
3) I am implementing support for a part sectioning command that prints
some additional text on the next (otherwise empty) page.
In the environment that contains the additional text I do not obtain the
parindents in LyX, though the output is properly indented.
I don't understand your question. This looks like just a sectioning
(or partitioning) command so why would it have paragraph indents?
It is a variation of the normal part sectioning. Normally the page
following \part{...} is blank. This style allows the author to write
some text on this following page. In svmono.cls there is an environment
partbacktext that messes with the LaTeX-pagination in order to achieve
this. The LaTeX usage would be as follows:
\begin{partbacktext}
\part{Part title}
Text which should appear on the following page. This text could span
several paragraphs.
\end{partbacktext}
The layout that I copied into my original message implements this
construction. However my implementation has the bug that indentation is
not indicated in LyX.
4) svmono contains an environment svgraybox that provides a gray
background. I am aware that currently the background color cannot be
controlled by layouts. I have therefore chosen sans font in order to
indicate this environment, simply because this font is rarely used. Does
anyone have a better idea?
LyX already provides coloured boxes so you could just stick to these.
I am trying to provide a LyX implementation of each environment and
command that is offered in svmono.cls. A book author can then simply
export to latex in order to obtain a files that are ready for submission
to Springer.
Marcus
Layout questions
I am trying to address bug #7301 concerning the Springer layout files,
and the following 4 questions have arisen:
1) NextNoIndent prevents the following paragraph (whether of the same or
a different layout) from being indented. Is there a possibility to
restrict this behavior such that in only applies if the next paragraph
has a different layout?
Use case: A definition may consist of several paragraphs which should be
indented. However, the first paragraph in Standard layout following the
definition should not be indented.
2) In the svmono class the \part command is typeset right-ragged, where
the first line consists of Part x and the second line of the name of the
part. (Same as chapter but right-ragged rather than left-ragged).
For the Part layout I cannot obtain the line break after the part
number, even though it is easy to obtain this form for the Chapter
layout (just include: Align Right). The reason for this behavior is the
line "LabelCounter part". If I change it to "LableCounter chapter", I
obtain the right ragged line break, but the counter is messed up, of
course. Redefining "Counter part" does not have an effect. If I
redefine "Counter chapter" in analogy to "Counter part" (as provided in
stdcounters.inc), the Chapter layout still exhibits the line break.
Any idea what I am doing wrong?
3) I am implementing support for a part sectioning command that prints
some additional text on the next (otherwise empty) page. My current
implementation is as follows:
Style PartBacktext
Category Section
MarginDynamic
LabelString "Part \thepart"
LabelType Counter
TocLevel 0
LabelCounter part
LabelsepM
NeedProtect 1
ParIndent MM
TopSep4
BottomSep 4
LaTexTypeEnvironment
LatexNamesvmultpartbacktext
LabelFont
Series Bold
SizeHuge
EndLabelFont
TextFont
SeriesMedium
ShapeUp
Sizenormal
EndTextFont
RequiredArgs1
Preamble
\newenvironment{svmultpartbacktext}[1]{\begin{partbacktext}
\part{#1}}{\end{partbacktext}}
EndPreamble
HTMLTag h1
End
In the environment that contains the additional text I do not obtain the
parindents in LyX, though the output is properly indented.
4) svmono contains an environment svgraybox that provides a gray
background. I am aware that currently the background color cannot be
controlled by layouts. I have therefore chosen sans font in order to
indicate this environment, simply because this font is rarely used.
Does anyone have a better idea?
(I am using the LyX 2.0RC3 binary on OSX.)
Poll for the default icon theme in LyX 2.0
As a user I vote for libreoffice. The icons are very clear and will make it easier for users migrating from OpenOffice or LibreOffice to start with LyX. However, I would like to propose the following small changes: 1) Advanced find/replace: As the magnifying glass is used in LibreOffice for zooming this could confuse newcomers. In addition, a modification of the binocular would indicate the relationship of normal find/replace and advanced find/replace 2) Insert list, insert description The difference between these two icons is very subtle. Could the description items in the description icon be represented by thicker lines? 3) increase indent, decrease indent LibreOffice (newest version) uses different (and I think clearer) icons in their formatting toolbar for Writer. 4) Toggle outline While I think that this icon is very nice, the corresponding icon in LibreOffice appears to be the navigator icon (a compass). Using the compass would improve discoverability for LibreOffice/OpenOffice users. Regards, Marcus
Re: changeset/35060 - color regressions
I think that math corners and math background serve different purposes. Math corners do not only indicate the outline of the whole formula but also the outline of frame elements within this formula. This is the reason why I use them. I believe that the purpose of math background is to show at a first glance where math is used. Math corners are relatively subtle and could be overlooked. Having said this, I personally do not find math background helpful. Even if math corners are removed, I would not make use of math background. But I would not be surprised if other users are fond of math background but not of math corners. I am sure I could find a use case for any existing color options, even though some use cases would not be very strong (such as my own use case for math corners). Your idea to introduce transparency and to make transparency the default for most colors is excellent and much better than my own proposal of ordering the existing colors in a hierarchical way! Regards, Marcus On 2010-9-2 10:17 , Jean-Marc LASGOUTTES wrote: Marcus Kriele writes: Yes, I do. As I am using LaTeX preview, math corners are only visible to me when I activate a formula. They serve as additional visual support, because they indicate which corners (in another part of the activated formula) would "light up" as math frame when my cursor is moved into this position. math frame (which indicates the active portion of the formula) is much more important, of course. I agree that math corners are not a "must have". They are a "nice to have" which some users such as myself are actually using. What I wonder is whether we need both the inactive math corners and the math background. This seems a bit overkill. JMarc
Re: changeset/35060 - color regressions
Yes, I do. As I am using LaTeX preview, math corners are only visible to me when I activate a formula. They serve as additional visual support, because they indicate which corners (in another part of the activated formula) would "light up" as math frame when my cursor is moved into this position. math frame (which indicates the active portion of the formula) is much more important, of course. I agree that math corners are not a "must have". They are a "nice to have" which some users such as myself are actually using. Regards, Marcus On 2010-8-31 12:19 , Jean-Marc LASGOUTTES wrote: Marcus Kriele writes: - remove math corners (The default is already the default background and is most probably never changed by users.) In my opinion this would make lyx less usable. I have enabled math corners (dark grey, math background light gray) because they help me to navigate in complex formulas. In addition, I have set math frame to a contrast color (red)). The math corners here are those displayed when the formula is _not_active. Do you use them? JMarc
Re: changeset/35060 - color regressions
Dear all, As an enthusiastic user of LyX I would like to weigh in on the discussion about colors. Uwe Stöhr wrote: I propose ... - remove math corners (The default is already the default background and is most probably never changed by users.) ... In my opinion this would make lyx less usable. I have enabled math corners (dark grey, math background light gray) because they help me to navigate in complex formulas. In addition, I have set math frame to a contrast color (red)). One wish for enhancement I have would be to be able to set the background color of the math frame independently from math background. Would this be possible? In general, I do not find that the many color options are a problem and I believe that for each color option there are users to whom it is important. I would rather propose a grouping of color options into classes (e.g. background class) and give the user the ability to change the colors belonging to a class simultaneously. The individual color options belonging to the class (e.g, for "class background: background, math background, listing background, ...) could then be assessed through a drill down functionality that allows the user to override the class color. Such a hierarchical system would help making the color options less imposing to beginners and at the same time would preserve the current customizability for more advanced users. best regards, Marcus
Binary 1.5 beta 3 for Mac
The beta 3 for mac binary does not display the times font which is selected in preferences but instead a sans serif font. In addition, the size of math preview larger than it should be. This seems to be a problem with the binary itself since the problem persists if I use the local lyx-1.5svn preference directory in ~/ Libarry/Application Support which contains the preference and customization files for the beta 2 binary. This also shows that it is not a LyX installer problem. The beta 2 binary itself continues to work flawlessly on my computer (intel mac). Regards, Marcus
