Georg Baum [Sun, 24 Apr 2016 18:04:05 +0000 (20:04 +0200)]
Merge finnish translations from bug 10084
Jari-Matti provided an updated fi.po in bug 10084, but unfortunately I did not
see that before remerging the strings. Therefore, I did not take the updated
file directly, but downloaded it to /tmp/fi.po and merged the updates with
python ../lyx-2.3-staging/development/tools/mergepo.py -o -l fi -t po /tmp/
The two header changes were done manually. This way, the updated translations
are not hidden in lots of sorting changes. I had to use mergepo.py from 2.3
because the one in master does not treat fuzzy translations correctly.
These wms have trouble with the fix at b5a2f1c7, probably more precisely with
the trick to force the calculation of the actual sizes before the display
(layout->invalidate() and the code around it).
This patch gets rid of the code that forces the calculation. As a consequence,
the minimum sizes are again incorrect the first time the window is shown. They
are only correct the second time the window is shown. Now here is the trick: LyX
remembers the sizes of windows between sessions. Therefore, as soon as the good
minimum size has been set, the good size is remembered for the next
session. Thus, in the following sessions, even though the minimum size is
incorrect the first time, the dialog still opens with the good size. So the user
does not see the problem in practice, apart from the very first time.
Georg Baum [Sun, 24 Apr 2016 08:57:36 +0000 (10:57 +0200)]
Remerge strings except for sv and fr
This is a complete remerge of strings (done with cmake) except for fr.po and
sv.po. Those files had already been remerged after the last string changes,
but they use a different sorting, so I did not want to produce an unneeded
diff.
The differences in the comment lines are a well known problem we have: The
last remerge was done on windows, mine was done on linux.
Stephan Witt [Fri, 15 Apr 2016 09:49:04 +0000 (11:49 +0200)]
Improved fix for #9966
* provide GuiApplication::typewriterSystemFont() to get a fixed font consistently
* enlarge fixed font on Mac because of the too small default Qt system font
* use it in source pane, progress view, log view and document preamble editor
Scott Kostyshak [Thu, 14 Apr 2016 06:16:47 +0000 (02:16 -0400)]
Update ANNOUNCE
This email will be sent regarding RC1. The update adds a note that
Uwe recommends to Windows users, which is to uninstall any previous
pre-release versions before installing this newer release.
Regression at cfeddb929. If a flex inset has no layout upon saving (e.g. if a
module has been deleted) then its name became lost. This checks whether the name
resolution, introduced with the ObsoletedBy tag, comes back empty-handed (which
it will if the layout is not defined). In this case, we do as was done before cfeddb929.
In addition, the use of support::token to strip "Flex:" off the beginning of the
name introduces a regression if somebody used a name containing ":". This
replaces it with support::split.
Georg Baum [Wed, 6 Apr 2016 06:22:59 +0000 (08:22 +0200)]
Fix graph translations for es, pt_BR and pt_PT
This was discussed in the thread "Translations of Math environments in LyX
output for LyX 2.2" at http://www.mail-archive.com/lyx-docs@lists.lyx.org/msg08633.html
and has been reviewed. The problem was that in 2.1, the portuguese translation
was correct in lib/layouttranslations but different in po/pt_PT.po. In fact,
the translation is the same for all three languages spanish, portuguese and
brazilian portuguese.
This is the same as the parbreak separator and is represented on screen
as the old parbreak. Old parbreak separators are converted to latexpar
separators when they are used for introducing blank lines in the
latex output rather than for separating environments.
Instead, parbreak separators are now represented on screen by a
double line. In essence, latexpar and parbreak separators produce
the same output but are represented differently on screen.
The context menu does not account for latexpar separators and only
"true" separators can be turned each into the other one.
Georg Baum [Tue, 5 Apr 2016 06:07:56 +0000 (08:07 +0200)]
Latest brazilian translations from Georger
After some discussion between Georger, Pedro, Pavel and me Georger came to the
conclusion that Mapa is not the correct translation of Chart in this context.
Originally he proposed Gráfico, but since that would be identical to the
translation of Graph we decided that Diagram is better. It is a bit more
general than Gráfico, but it is also used in pt_PT, and the german translation
uses the german equivalent, which is more general as well. Those who need a
Gráfico can still use Graph.
Unfortunately Geoger based the new .po file on the remerged one at 259196e1a6c54, so we have now the situation that pt_BR is remerged, but the
other languages are not.
259196e1a6c54 did a remerge and destroyed the line endings.
No translatuions were changed (the last update by Geoger was already in at 77fc7fe8b6478b).
Guillaume Munch [Wed, 16 Mar 2016 21:47:32 +0000 (21:47 +0000)]
Fix broken layout of the citation dialog (#10019)
7b1107d7 introduced the following inconveniences which are regressions to 2.1:
* The citation dialog can open with vertical scroll bars in the options
* The citation dialog can open with horizontal scroll bars, especially if the
translated text is longer than the original text (e.g. in FR)
* Resizing the dialog is inconvenient because it increases the gap between the
options. This is unlike before when the dialog could let us see more of the
reference list when enlarging.
This is because the QToolbox that the above commit introduced is not natively
aware of the sizes of its page sub-widgets. The widget is not conceived for this
use, where the space is scarce.
Geometry values provided in the ui file (automatically computed by qtcreator I
suppose) somehow gave the illusion that it worked, but relying on such values is
not portable : it does not take into account the specific theme, font sizes and
localization. This explains why it failed on my side and will probably fail in
other settings too.
Luckily, there is a simple way to make QToolbox suitable for the current use,
which is to add the "missing link" which computes its size based on the minimal
sizes of its pages. The result looks very nice and intuitive. It solves all the
aforementioned issues.
New translations for the sectionboxes module.
Improved translations for the names of greek letters, and some other symbols
A few other translated strings as well.
Georg Baum [Wed, 30 Mar 2016 19:49:36 +0000 (21:49 +0200)]
Mark brazilian translations for review
These translations were changed implicitly at ad6ab20bb18: Previously, the
translations were taken from pt. At ad6ab20bb18 all pt_BR translations were
copied from pt_BR.po, so we do still need a review for those that differ from
pt_PT.
Rename Caption:LongTableNoNumber to Caption:Unnumbered
The term LongTable has been deprecated and moreover the renaming makes the interface easier to the eye.
File format updated to 507. (conversion based on jamatos patch)
Layout format updated to 60.
tex2ylx tests updated.
Document EmbeddedObjects.lyx has been updated.
Richard Heck [Sun, 27 Mar 2016 20:54:46 +0000 (16:54 -0400)]
Fix problem reported by Kornel in this thread:
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg193248.html
The static InsetLayout could be initialized before its members were, as
JMarc realized here:
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg193293.html
Georg Baum [Sun, 27 Mar 2016 09:18:33 +0000 (11:18 +0200)]
Grab translations from lib/layouttranslations
These strings were translated manually in lib/layouttranslations, but not in
zh_TW.po. If this is the correct translation for document output, then it is
certainly also correct for the user interface.
Georg Baum [Sun, 27 Mar 2016 09:07:50 +0000 (11:07 +0200)]
Add missing layout translation keys
These have been forgotten by the last update, since bg, ko and sl are not in
po/LINGUAS. I add them here so that it is obvious that these translations are
missing.
Georg Baum [Fri, 25 Mar 2016 09:42:28 +0000 (10:42 +0100)]
Grab translation from lib/layouttranslations
This string was translated manually in lib/layouttranslations, but not in
ar.po. If this is the correct translation for document output, then it is
certainly also correct for the user interface.
Kornel Benko [Sat, 26 Mar 2016 12:06:14 +0000 (13:06 +0100)]
Cmake export tests: Label handling
In collaboration with Günter Milde:
1.) Allow char ':' be part of a ctest-label
2.) Eliminate redundant label naming and directory names
(The testnames should not repeat the directory name)
Fix some display bugs related to end of paragraph markers
There are two regressions that are fixed here:
* empty rows at the end of a paragraph (think after newline at end of
paragraph or empty line in Verbatim) do not have an end-of-par
marker. This is fixed by removing the early return in breakRow and
letting the whole function be executed. This requires to relax an
assertion in Paragraph::fontSpan. It makes sense here to query
position at the end of the paragraph.
* a newline at the end of a paragraph will be followed by and
end-of-par marker. This is fixed by skipping the end-of-par marker
when a new row has been requested.
Georg Baum [Fri, 25 Mar 2016 09:32:53 +0000 (10:32 +0100)]
Explain why po files are needed
lib/layouttranslations contains translations for all strings from layout files
that can appear in document output. These translations are read from .po files
by po/lyx_pot.py (using python polib), so up to date po files are needed.
Georg Baum [Fri, 25 Mar 2016 09:24:46 +0000 (10:24 +0100)]
Make lyx_pot.py python3 compatible
Now it produces the same output if running under python3 (tested with 3.4.2)
or python2 (tested with 2.7.9). python3 always uses unicode strings
internally, so we have to specify the file encoding on opening a file, such
that strings can be converted from and to the file encoding on reading and
writing. Using the io module for file io ensures that the behaviour is the
same for python2 and python3. For python2 we also have to mark string literals
as unicode strings by using the u prefix (which is a noop in python3).
Many thanks to José for review and pointing out all the details.