Günter Milde [Mon, 14 Dec 2015 13:14:56 +0000 (14:14 +0100)]
Revert output format setting for Japanese manuals (pdf2 does not work).
The manuals use language "Japanese" wich is tied to "platex"
(automatically set instead of (plain) LaTeX).
For export with other engines, the language must be set to "Japanese (CJK).
For a discussion of alternatives for Japanese with LaTeX , see also
http://www.preining.info/blog/2014/12/writing-japanese-in-latex-part-1-introduction/
Richard Heck [Mon, 30 Nov 2015 22:25:03 +0000 (17:25 -0500)]
There does not appear to be any need to update the entire Buffer
after each entry into mathed. Instead, we just update the TOC for
anything the mathed happens to be inside.
Günter Milde [Thu, 10 Dec 2015 09:40:50 +0000 (10:40 +0100)]
Set default output format for manuals to PDF (pdflatex).
Pdflatex is the recommended export tool for the manuals.
Pdflatex brings the best results for hyperlinking.
Some features (e.g. rotated text) are not available in DVI or PS (dvips).
This does not affect export from command line or autotests
(where this setting is ignored and the format must aways be given explicitely).
This crude caching mecanism is useful in the particular case of a screen with many misspelling dotted lines. In this case, it is necessary to build a QTextLayout in order to know where to put the start/end of the spell line. Since rows typically contains text snippets longer than a word, we may be in a situation where the same QTextLayout is constructed repeatedly.
This commit is useful in this particular use case, and should not be costly in other cases. A better fix would be to remember the QTextLayout associated to each row element. This is a bit more work, so this fix should be sufficient for now.
Additionally, do not paint misspelled marks when painting is disabled.
Scott Kostyshak [Tue, 8 Dec 2015 06:33:41 +0000 (01:33 -0500)]
Explain why we do not update the local layout
We do not update the local layout of our .lyx files because users
would then not be able to export to older formats. For example, if a
2.2.0 user exported a template to 2.1.x format and tried to open the
file in LyX 2.1.x, there would be an error because the file would
contain a local layout whose format is too new. The root reason for
this is that we do not convert layouts to older layout formats.
Georg Baum [Mon, 7 Dec 2015 20:17:33 +0000 (21:17 +0100)]
Explain why rsvg_convert is in front of inkscape
Otherwise it could easily happen that the order is changed, since rsvg_convert
seems to be more picky about invalid files (see http://www.lyx.org/trac/ticket/9891)
Georg Baum [Sun, 6 Dec 2015 10:39:47 +0000 (11:39 +0100)]
Merge translations from 2.1.x branch
The translations have been merged by calling
python development/tools/mergepo.py -n ../lyx-2.1-git/po
cd po; make update-gmo
For some languages it may make sense to merge also changed translations,
but this neds to be decided by the individual translators.
Georg Baum [Sun, 6 Dec 2015 10:27:48 +0000 (11:27 +0100)]
Add option to skip null translations
he.po in branch contains a number of translations where the translation is
identical with the original text (e.g. for encoding names) which look suspicios
to me. Therefore I did not want to merge these and leave the decision to the
translator. No information is lost, since these "translations" can easily be
recreated from the original texts by copy-paste.
Richard Heck [Fri, 4 Dec 2015 02:06:28 +0000 (21:06 -0500)]
Add new ProvideStyle tag, which adds a new style only if it does not already
exist. This will allow for a proper fix for bug #8796, though that may or may
not get fixed before 2.2.0.
Also, change the InStyle tag to ModifyStyle, per a suggestion of Jurgen's.
Kornel Benko [Sat, 5 Dec 2015 18:25:23 +0000 (19:25 +0100)]
Cmake export tests: Allow deeper label nesting.
Previously all labels got the depth '7' while processing 'suspiciousTestss'.
The depth is used to sort how our labels are used to build a test-label.
Say a test gets label a, b, and c, with depth 3, 8 and 2.
The constructed test-label will be "b:a:c"
For new (to be implemented) 'reason-labels' it is more convenient to assign them higher values.
Kornel Benko [Fri, 4 Dec 2015 18:33:39 +0000 (19:33 +0100)]
Cmake export tests: Tutorial.lyx now compilable
suspiciousTests: Remove Tutorial from the regex
suspendedTests: Explicit list of languages needed
ignoredTests: Language-string is separated from other strings only by '/'. '|', '_', '(' and ')'
Fix the pilcrow and the cross in the outliner for Windows and old Ubuntus.
The thin space after the cross is based on aesthetics (in Ubuntu at least) after
trying both with and without a normal space. A thin space is already used for
display in BiblioInfo.cpp, so I presume it is safe.
Ideally, I prefer ❌ (CROSS MARK), whose description fits the purpose, over ✖
(HEAVY MULTIPLICATION X), which looks too bold in the UI. Whereas ✕
(MULTIPLICATION X, successfully tested in Windows by Andrew) looks too dim. But
❌ (CROSS MARK) is next to ❎ (NEGATIVE SQUARED CROSS MARK) so it might be as
problematic as the latter.
Do not output the cross on the author name in the toc of tracked changes.