Re: German tutorial.lyx updated
Am 18.05.2016 um 17:58 schrieb mn: Well, together with the above page breaks: The second page is blank but numbered in arabic, then the toc starts in roman numerals. And the remainder gets again arabic page numbering. This is because \frontmatter was not started at the beginning. However, you showed me that preamble code at all doesn't make sense for a tutorial that is designed to learn how LyX work - and not what is possible with LaTeX. So I removed now all preamble code. Then LyX should not offer them in the special character dialog. As I understand this, it should be like: 1. You do not mean that the special char-dialog should be reduced for every possible font. Instead, 2. LyX knows the glyph coverage of a font, at least for those offered through doc-settings/pdflatex and then adjusts the special character dialog accordingly? That might be nice. Yes, this would be nice. But most probably that is not an option since we cannot know the glyphs of all fonts. But maybe I am wrong so having this issue in our bugtracker (marks the bug as enhancement) would be helpful in every case. regards Uwe
Re: German tutorial.lyx updated
Am 16.05.2016 um 14:09 schrieb mn: OK. The ImageMagick that should be called is at 6.9.4. How do I check which path and program/options is used for that from LyX? LyX uses the version that is installed on your system. Maybe you are using an older version of hyph-utf8 and/or babel-german? That should be from MacTex 2015, latest updates applied. OK, then they are up to date. Nevertheless, as long as the page-metaphor is transferred to or kept in PDFs, things like widows and orphans should be avoided still. Sure. This and a few additions to the tutorial are attached. I committed only a few of your changes. Most are just a matter of taste and the user is just learning how LyX works in the Tutorial so that forced page breaks are something he does not yet know. One thing I saw and didn't touch: Footnotes start their numbers afresh in chapters. Again, if this is intended, OK. This is the default. You can of course change this with the command \numberwithin, see the EmbeddedObjects manual. Another point: You changed the info that LyX supports every image format. It really does! (Thanks to ImageMagick and Ghostscript.) Well, I thought that would be a bet on the safe side. You know, _every_ format. A quick check and I cannot find in “identify” the formats for STAD, NeoChrome and ApplePreferred (GS). There seem to be a bit more though. Are these normed image formats? Of course I can invent my own image format and LyX cannot support it. However, some advertising for LyX is not too bad here. You found a bug. Can you please report it in our bug database: http://www.lyx.org/trac/wiki/BugTrackerHome Just to clarify: This symbol seems to be missing in Palatino, Helvetica. Then LyX should not offer them in the special character dialog. thanks and regards Uwe
Re: German tutorial.lyx updated
Am 15.05.2016 um 15:30 schrieb mn:
But isn’t this a justified line-break that you changed them into?
Yes, sorry, I meant changed some ragged into justified line breaks.
I noticed a few instances of this change.
One is hardly noticeable in the output now.
The other one produces a big hole in a line in the corresponding PDF;
because of justification. (in 3.4.2) I reverted that.
Accepted.
One anomaly, e.g. in 5.2.1:
The TeX-logo symbol does not appear in the output.
Here it does, see the attached PDF.
The source for that line reads:
auf
\includegraphics[width=1em]{/Applications/[…]/LyX.app/Contents/Resources/images/ert-insert}
in
Here it reads:
auf \includegraphics[width=1em]{\string"C:/Program Files (x86)/LyX
2.2/Resources/images/ert-insert\string".svgz} in
This produces just an undefineable blob (see attached screenshot)
Opening the file in inkscape shows that the file seems intact.
Then it seem to be an issue with ImageMagick. This program is used by
LyX for the image conversions. It works here with ImageMagick 6.9.3 and
6.9.4.
There where still a few problems with the margins and a few rewordings,
conservatively deemed desireable.
I don't see them. For example in sec. 2.2.1
"Ausschneiden/Kopieren/Einfügen" you added a hyphenation point at
"Bear-beiten" but this is not necessary since the word is automatically
hyphenated at this position, see the attached PDF.
Maybe you are using an older version of hyph-utf8 and/or babel-german?
Most important change: 2.1.1 still referenced direct printing from LyX.
This line seems to be simply removed from English tutorial.
Thanks for spotting. All other language versions of Tutorial were
already updated but not the German one. Background is that the printing
feature was removed for LyX 2.2.
> Given the target audience I think that how to print LyX-documents
> should be mentioned somehow. I propose to guide the user to use the
> PDF-viewer for that (i.e. just ignoring all other options).
I think that this is superfluous. If the users created a PDF he can
print it or not. Everybody knows PDF. (In times of paperless offices
printing is slowly dying out nevertheless.)
Another point: You changed the info that LyX supports every image
format. It really does! (Thanks to ImageMagick and Ghostscript.)
I just committed a new version with your fixes.
Since it was suggested that instead of mathtimes one should use
texttimes to get multiplication in running text:
I tried to change
$\uparrow$ to \textuparrow in 2.1.
This gives slightly better looking (sized) symbols
but awkwardly also the error that:
! Package textcomp Error: Symbol \textuparrow not provided by
(textcomp)font family pplx in TS1 encoding.
(textcomp)Default family used instead.
You found a bug. Can you please report it in our bug database:
http://www.lyx.org/trac/wiki/BugTrackerHome
thanks and regards
Uwe
