Re: en UserGuide.lyx: quotation marks, ellipses, spelling and dashes

2016-05-08 Thread Uwe Stöhr

Am 04.05.2016 um 16:05 schrieb Jean-Marc Lasgouttes:


Some minor corrections to the usage of dots, single- and double
quotation marks, and dashes. One grammar/spelling/typo.


These should go in too. Uwe?


I just spent 1,5 hours for the German UserGuide review. I will try to 
find time to review also the English one.


regards Uwe


Re: de-UserGuide improvements

2016-05-08 Thread Uwe Stöhr

Am 29.04.2016 um 17:05 schrieb mn:


This refers primarily but not exclusively to German Userguide.


Many thanks for your work! I committed more than 90% of your changes.

One hint: instead of using \times in a formula one can directly insert 
the times symbol via the menu Insert-> Special characters. (This creates 
a \texttimes command.)


A plea: Please modify the files where they are . Just turn on change 
tracking. This assures that the relative image paths are preserved and 
this saves me time.




In this section 3.9.3 the usage of the "-sign differs from the rest of
the doc insofar as it is not enclosed in quotation marks.

It would be nice if there were some hints as to which languages usually
prescribe which style.


It is possible to use the French guillemets also in German texts. So it 
is up to the user to chose a style.
(btw. the Wikipedia has extensive information about the usage of 
quotation marks:

https://en.wikipedia.org/wiki/Guillemet )


The shortcut for creating a single quotation mark in LyX cannot be as
universal as the wording implies.
And it does not use the "-sign!
On Mac with German-keyboard-layout the given shortcut Opt-" gives a
correct closing-double quotation mark
\textquotedblleft{} (“) and LyX does not transform this in any way to
opening or closing single quotation marks.


The german UserGuide should reflect LyX's german-specific shortcuts. 
Could you please send me a proposed correction?


many thanks and best regards
Uwe


Re: improving typography and layout in tutorial.lyx

2016-05-08 Thread Uwe Stöhr

Am 23.04.2016 um 15:25 schrieb mn:


Every doc should have at least another round of chktex applied to them.


I am the doc maintainer and on Windows only and ChkteX was not available 
for Windows (it is now since a few weeks but I did not have the time to 
try it out.
Nevertheless, most issues arose because we changed the fonts for dome 
documents without checking the change in the PDF output.
Nevertheless instead of ChkTeX I prefer the checks of the different 
persons working at the docs. Especially for non-English texts I assume 
that software like ChkTeX will fail in some cases.



Better fonts and uniformity of choices for all the included docs:
Tutorial already uses Palatino, but not true smallcaps.
Activating smallcaps should be always on, if available. (Think “Noun-Style”)


What do you mean with "not true smallcaps"?


Other docs still use LModern and Courier. These should be abolished.


No, we had a discussion about the fonts already and the current font 
choices are the result.



Given the choices available Palatino is probably the best.
Mathdesign Charter is so buggy, you get an error in typesetting
additional.lyx.


Can you please point me to this special issue? I don't see a problem here.


%  URW-Garamond is not that good for reading on screen.

...

Says who. It is normal that everybody has personal preferences but we 
should not judge fonts. Every font has its advantages and disadvantages. 
The most important thing is the task that should be fulfilled with the 
docs: provide information is a way that people understand the features 
of LyX quickly. Things like kerning or if endash or emdash is used is 
therefore not very important. Things that make the docs hardly readable 
like the margin protrudes you discovered in the tutorial are important 
and must be fixed.



Anyway, all the docs should conform to a certain style-guide.


Why? Does this help the users to understand LyX's features. The 
different documents have different maintainers and a different history.
If a users send a new file it is more important for me to look that its 
content is OK rather than to bother him to follow a certain style. For 
some documents an article class is sensible while for others a book 
class is more suitable...



Introducing either ERT: \allowbreak or a ragged linebreak into some
LyX-Code environments to avoid margin violations.


Sure. Please report all those issues here.


Setting the slash-character “/” always compress.


OK. If you send files where this is corrected I will commit your changes.


“Correct” usage of endash,


This is microtypography. I don't think that wen need to take care of 
this. But also here, if you send files where this is corrected, I will 
commit them.



Correct punctuation and usage of … for \dots or \ldots instead of three
fullstops ... .


Same opinion as for endash. OK, we even have a menu entry to insert 
ldots so we should use them if possible. Where did you spot this problem?


regards Uwe


Re: improving typography and layout in tutorial.lyx

2016-05-08 Thread Uwe Stöhr

Am 20.04.2016 um 15:35 schrieb mn:


The current English tutorial.lyx in rc1 does not yield clean PDFs on
three levels:...


Dear MN,

many thanks for your report.
Please use a real name. We all use our real names - as in real life.


These are hopefully improved upon in the attached .lyx-file.


Thanks, your changes are now in.


2. Then there are problems with lines running into the margin:

These are the following: occuring with default a4-papersize.

– Exercise: Fix the section and subsection headings in example_raw.lyx.

– Exercise: Correctly typeset the Quote, LYX-Code, and Verse in
example_raw.lyx

—If you want to know more about this document, then see Section .


These are fixed now. The first one only occurs because we changed the 
font of the document and nobody reviewed it afterwards.



3. In section 3.2 designating paragraphs deviates (only optically?) from
the rest of the document in apparently using indention and skips.
For my own documents I would insert a pagebreak there.


Yes. I have done this now.

regards Uwe