Scott Kostyshak | 4 May 22:39 2016

Update on situation for 2.2.0 release

Dear all,

As new issues have popping up (and will without doubt continue to keep popping
up), I want to give an update of how close I think we are to the next step in
the release process. The two main issues in my mind are:

1. Cannot create shortcuts. This problem is present with Qt 5.6 and on all
platforms. Since we are planning to ship Mac and Windows binaries with Qt 5.6,
this is a show stopper. To follow the progress, see #10075 and our hijacked
thread at [1]. Stephan is helping out and will follow a lead that JMarc
suggested. If that does not work out, then we will contact the Qt mailing list
for help.

2. There is a crash that seems mostly reproducible on OS X. Although it is only
on OS X and only in a particular case, I consider this bug important because it
is a crash and because it might indicate a more widespread underlying bug (e.g.
an uninitialized variable). Even though I cannot reproduce, I can run Valgrind
if someone thought that would be useful. See [2] for more information.

Other issues that are important, but that I do not think will
significantly delay moving to the next release step (once the two issues
above are resolved) are the following:

3. A Python3 compatibility issue at [5]. I don't know whether the best
short-run approach is to ensure that we use Python2 to call the script or to
fix the script to be compatible with Python3. I CC'ed José to see if he has
some wisdom to share.

4. Insert Cross-Reference Causes Crash. See #9992. Unfortunately, no one can
reproduce except the OP, Joel. Joel has been extremely helpful in debugging and
(Continue reading)

Helge Hafting | 4 May 18:42 2016
Picon
Picon

2.2-rc1 Tools->Reconfigure: "SyntaxError"

I did a reconfigure, and looked through the list of discovered stuff. I 
found this oddity:

...

checking for a nomenclature processor...
+checking for "makeindex"...  yes
+Indexing TeX files...
   File "/usr/local/share/lyx-2.2.0dev/scripts/TeXFiles.py", line 56
     so that all files will be created'''
                                        ^
SyntaxError: Missing parentheses in call to 'print'

     done
+checking list of modules...
layouts/test.module
layouts/svar.module
...

I am not sure if this has any ill effects, but it doesn't look good. 
Typo in  TeXFiles.py?

Helge Hafting

Guillaume Munch | 30 Apr 16:55 2016

[patch] Remove the "Keep" checkbox in the outliner panel

Dear list

I propose to remove the "Keep" checkbox in the outliner panel. The panel
would behave as if always checked. This is because the only place where
"not-Keep" currently takes effect has been broken since the updates of
the outliner panel were put on a timer, causing the collapse of the tree
view at inappropriate times. I find that the (not-)keep option has no
clear use, and moreover that getting rid of it
simplifies the outliner.

This is for 2.3-staging and 2.2.2-staging.

Sincerely
Guillaume
Steven Smith | 28 Apr 14:40 2016
Picon

Template folder

I’ve just downloaded LyX after MacTeX and finding my way with the tutorials.  Going through the section on creating a letter, I came to full-stop as on keying ‘New from Template’ all I got was an empty folder.  I tried reconfigure in tools and restarted but still empty.  Any advice?

Steve


Dr Steve Smith
Earth Sciences
Royal Holloway College University of London.
Egham Hill
Egham, Surrey TW20 0EX



Stephan Witt | 27 Apr 07:46 2016
Picon
Picon

Re: #10096: Keyboard shortcut for interword space does not work on Mac

Am 27.04.2016 um 07:43 schrieb LyX Ticket Tracker <trac <at> lyx.org>:
> 
> #10096: Keyboard shortcut for interword space does not work on Mac
> -----------------------+-------------------------
> Reporter:  ksvanhorn  |       Owner:  lasgouttes
>     Type:  defect     |      Status:  new
> Priority:  normal     |   Milestone:
> Component:  general    |     Version:  2.1.4
> Severity:  normal     |  Resolution:
> Keywords:             |
> -----------------------+-------------------------
> 
> Comment (by stwitt):
> 
> The LyX version doesn't matter. The clash of the short cuts can be avoided
> by disabling or changing the Finder short cut or by changing it in LyX.

This reminds me that short cuts cannot be changed in LyX with Qt 5.6.0 -
IMHO a possible show stopper for using Qt 5.6.

Stephan

> 
> -- 
> Ticket URL: <http://www.lyx.org/trac/ticket/10096#comment:3>
> The LyX Project <http://www.lyx.org/>
> LyX -- The Document Processor

Andrew Parsloe | 27 Apr 03:22 2016
Picon

A tiny cedilla anomaly

Having just skimmed through an article on Wikipedia about cedillas, I gather a cedilla is never attached to the letter 'i'. Nonetheless, when I do attach one (using european.kmap,  then ',' followed by 'i'), everything looks fine in the main LyX window but in the Source Pane, LyX format, the cedilla gets attached to the following letter. For instance, writing 'aei̧ou' with a cedilla under the 'i', all is fine in the main LyX window (and the pdf) but when viewed in the Source Pane, the cedilla is located under the 'o'. A quick experiment suggests 'i' is the only letter for which this happens. It doesn't happen in 2.1.4 so it appears to be a (tiny) regression.

(I stumbled on this when checking unicode compatibility of some python code,  trying a fairly random assortment of accents and letters.)

Andrew
LyX Document /* Layout-provided Styles */ div.standard { margin-bottom: 2ex; }

Virus-free. www.avast.com
Joel Kulesza | 26 Apr 22:32 2016
Picon

Table "Set All Lines" Behavior Inquiry

LyX Developers,

I recently submitted a couple tickets (one I believe a bug, another an enhancement request) related to table cell lines.  Before posting another I wanted to poll the list regarding whether the "set all lines" behavior is as-expected.

For example, if I insert a table, select all cells, and click "set all lines" I would expect only the double hline to disappear.  If I instead first "unset all lines" and then "set all lines," I would expect only a simple grid of single lines.  

While I agree that it is LaTeX-like to consider "all lines" with double horizontal delimiters, this type of table formatting isn't very common (nor are double vertical delimiters) and also isn't intuitive based on the button's icon (I would expect a double-lined grid to be shown on the icon).  

As such, I would propose changing the table to mimic the icon (and a more common styling, in my experience).

I'd be interested to hear the community's thoughts.

Thank you,
Joel
Shankar Giri Venkita Giri | 26 Apr 00:30 2016
Picon

Blanket permission

As requested, here is the permission.
 
I hereby grant permission to licence my contributions to LyX under the
GNU
General Public Licence, version 2 or later
mn | 25 Apr 22:08 2016
Picon
Picon

Advanced-Find Panel impedes window management

On Mac OS 10.10, rc1 (new upload):

Some newly introduced misbehaviour?
2.1.4 does not do this:

– open LyX,
– open new blank document (default window size for the editor is quite
small)
– open advanced search window [cmd-shift-F]
– try to resize editor window below.
-> window borders for the editor will resize – but the content area will
remain at the smaller state, the rest goes grey

independent of the above:

(After closing the search panel and/or newly)
– adding some text,
– reopen advanced search panel,
the search panel will be deformed (smaller, some items invisible, most
not, has to be resized by hand)
clicking on the search panel, then on the editor again,
-> the editor window (below?) will become un-resizeable (lower right
corner will go ‘blind‘)

Additionally, it seems that some unnecessary updates are going on in the
GUI. It’s hard to describe:
It looks as if there are some things like icon flashing going on, (most
visible in the rightmost caret for the environment menu-icon).
This happens when clicking the pointer in either the editor or the
While advanced search panel is open, I cannot type anything in the
editor window; everything is directed to the search panel.
(although, after saving this newfile.lyx, editing becomes possible again)

mn

mn | 25 Apr 17:56 2016
Picon
Picon

Same document, different PDFs, dependening on locale settings

When comparing PDFs generated from LyX 2.1.4 with those posted on the
wiki I noticed some weird differences. Looking for an explanation I came
to the following reproducible peculiarity:

now with LyX 2.2rc1, while switching UI-locales:

UI: English, en-UserGuide.lyx; generated PDF reads:
Normal This is the “Normal” font size. It’s also the default size. (key
bindings Control-S N, Control-S 5)
Larger This is the “Larger” font size. (key bindings Control-S Shift-L,
Contro

UI: German, en-UserGuide.lyx; generated PDF reads:
Normal This is the “Normal” font size. It’s also the default size. (key
bindings Kontroll-S N, Kontroll-S 5)
Larger This is the “Larger” font size. (key bindings Kontroll-S Shift-L,
Kontr

UI: English, de-UserGuide.lyx; generated PDF reads:
Normal Dies ist die „normale” Schriftgröße. Dies ist auch die Standard-
größe (Tastenkürzel: Alt+S N oder Alt+S 5)

UI: German, de-UserGuide.lyx; generated PDF reads:
Normal Dies ist die „normale” Schriftgröße. Dies ist auch die Standard-
größe (Tastenkürzel: Alt+S N oder Alt+S 5)

As you can see in the above example, German UserGuide yields the same
characters/words and also better line-breaking regardless of UI-choice.
Further, the English UserGuide produces differing output, dependent on
UI-Choice.
Therefore en-UserGuide violates the margins in different ways.
The “Larger” example shows where the line not only runs out of the
margin but off the page completely.
(My viewer didn’t let me copy more than what is shown above.)

If this locale-switching is indeed a feature of en-UserGuide, then
hunting for margin violations and fixing them manually becomes even more
tedious than it is. What would be a more general solution to this?

mn

Georg Baum | 24 Apr 21:49 2016
Picon
Picon

backporting translations

Richard,

this might be interesting to you: After my latest fixes for mergepo.py in 
2.3-staging it is quite easy to transfer translations between different 
branches. Assuming that you have two different branches, and in both 
branches no strings have been changed after the latest remerge, you can call 
mergepo.py like I did at 04e4d6c4eb3d. Doing this to merge translations from 
master to 2.1 results in a 217kB diff and the attached summary. Note that no 
changed translation has been overtaken (you would need the -o option for 
that), only strings that would be shown untranslated in the old version have 
been updated.

Georg
lyx-2.1$ python -tt ../lyx-2.3-staging/development/tools/mergepo.py -t po ../lyx-2.2/po
Merging lyx-2.2/po/pt_PT.po into lyx-2.1/po/pt_PT.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/ja.po into lyx-2.1/po/ja.po: Updated 50 translations with minimal diff.
Merging lyx-2.2/po/sl.po into lyx-2.1/po/sl.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/bg.po into lyx-2.1/po/bg.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/fr.po into lyx-2.1/po/fr.po: Updated 9 translations with minimal diff.
Merging lyx-2.2/po/id.po into lyx-2.1/po/id.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/fi.po into lyx-2.1/po/fi.po: Updated 297 translations with minimal diff.
Merging lyx-2.2/po/ar.po into lyx-2.1/po/ar.po: Updated 1 translations with minimal diff.
Merging lyx-2.2/po/ia.po into lyx-2.1/po/ia.po: Updated 119 translations with minimal diff.
Merging lyx-2.2/po/cs.po into lyx-2.1/po/cs.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/zh_CN.po into lyx-2.1/po/zh_CN.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/nl.po into lyx-2.1/po/nl.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/el.po into lyx-2.1/po/el.po: Updated 1 translations with minimal diff.
Merging lyx-2.2/po/de.po into lyx-2.1/po/de.po: Updated 9 translations with minimal diff.
Merging lyx-2.2/po/en.po into lyx-2.1/po/en.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/pt_BR.po into lyx-2.1/po/pt_BR.po: Updated 9 translations with minimal diff.
Merging lyx-2.2/po/wa.po into lyx-2.1/po/wa.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/sr.po into lyx-2.1/po/sr.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/ko.po into lyx-2.1/po/ko.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/hu.po into lyx-2.1/po/hu.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/ro.po into lyx-2.1/po/ro.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/tr.po into lyx-2.1/po/tr.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/uk.po into lyx-2.1/po/uk.po: Updated 163 translations with minimal diff.
Merging lyx-2.2/po/ru.po into lyx-2.1/po/ru.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/he.po into lyx-2.1/po/he.po: Updated 569 translations with minimal diff.
Merging lyx-2.2/po/sk.po into lyx-2.1/po/sk.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/da.po into lyx-2.1/po/da.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/nb.po into lyx-2.1/po/nb.po: Updated 50 translations with minimal diff.
Merging lyx-2.2/po/es.po into lyx-2.1/po/es.po: Updated 163 translations with minimal diff.
Merging lyx-2.2/po/pl.po into lyx-2.1/po/pl.po: Updated 2 translations with minimal diff.
Merging lyx-2.2/po/eu.po into lyx-2.1/po/eu.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/gl.po into lyx-2.1/po/gl.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/ca.po into lyx-2.1/po/ca.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/sv.po into lyx-2.1/po/sv.po: Updated 9 translations with minimal diff.
Merging lyx-2.2/po/nn.po into lyx-2.1/po/nn.po: Updated 0 translations with minimal diff.
Merging lyx-2.2/po/it.po into lyx-2.1/po/it.po: Updated 9 translations with minimal diff.
Merging lyx-2.2/po/zh_TW.po into lyx-2.1/po/zh_TW.po: Updated 2 translations with minimal diff.


Gmane