Re: Bad Citation Bug in 2.3dev

2017-05-30 Thread Jürgen Spitzmüller
Am Dienstag, den 30.05.2017, 15:11 -0400 schrieb Richard Heck:
> > OK. Thanks. Since this is used as a session setting, we might have
> > the unwanted side-effect that it is now off by default for
> > everybody starting LyX 2.3 with an old document.
>  
> But it was off by default, anyway, I believe, since the default for
> literal is false. That's how I got the non-literal insets that
> started this thread.

I mean the reverse. If people start with an old document, their session
will default them to "literal".

Jürgen

signature.asc
Description: This is a digitally signed message part


Re: Tentative schedule for 2.3.0 release

2017-05-30 Thread Richard Heck
On 05/30/2017 08:39 AM, Jean-Marc Lasgouttes wrote:
> Le 04/05/2017 à 11:26, Stephan Witt a écrit :
 I liked to use it since then for anything Hebrew.
 Performance was quite noticeably improved.
 With Hebrew this was not perfect but much,  much better.
>>>
>>> So we might want to include it. Stephan, what do you think. It would
>>> be nice for 2.2.3 too.
>>
>> I propose to include it (that’s why I CCed the lyx-devel list).
>> It would be good for 2.2.3 probably. I hope to compare it with
>> Instruments soon.
>
> Richard, this is about using QTextlayout caching for MacOS with Qt5.
> Qt5 is supposed to do caching, but it is very inefficient on MacOS
> with ancient Hebrew. OK for 2.2.4?

Sure.

Richard



Re: Bug #10295

2017-05-30 Thread Richard Heck
On 05/29/2017 12:05 PM, Scott Kostyshak wrote:
> On Tue, May 16, 2017 at 10:18:05PM -0400, Richard Heck wrote:
>> Can anyone test the fix for this bug posted at
>>
>> http://www.lyx.org/trac/ticket/10295
>>
>> It'd be nice to have a decent version for beta1.
> I can't reproduce the bug. Can anyone reproduce and then check that
> Richard's patch makes it go away?

JMarc confirmed it. We should try to get this into beta, but I won't be
able to get to it for a day or two.

Richard



Re: Bad Citation Bug in 2.3dev

2017-05-30 Thread Richard Heck
On 05/30/2017 07:04 AM, Jürgen Spitzmüller wrote:
> 2017-05-30 4:54 GMT+02:00 Richard Heck  >:
>
> >> Another question: Should the "literal" flag default to true or
> false?
> >> Having it default to true would be consistent with pre-2.3
> behavior.
> >> People who wanted it otherwise could set it once and then it would
> >> (should) be remembered.
> > The argument for setting it to false was that novices tend to
> run into
> > more severe problems if they enter text that is interpreted as a
> > command and might not know what happens (as opposed to LaTeX
> > literates).
> >
> > For people who are used to the current situation, there will
> certainly
> > a learning process. But on the other hand, the situation was not
> very
> > clear at all, since some dialogs were outputting verbatim texts,
> some
> > not, some partially.
>
> Having the checkbox is fine with me. I just don't want to have to keep
> checking it.
>
> I've committed something along these lines.
>
>
> OK. Thanks. Since this is used as a session setting, we might have the
> unwanted side-effect that it is now off by default for everybody
> starting LyX 2.3 with an old document.

But it was off by default, anyway, I believe, since the default for
literal is false. That's how I got the non-literal insets that started
this thread.

Richard



Re: #10119: Shortcut Control-M

2017-05-30 Thread Luca Brandolini
I forgot to mention that this strange behavior started with LyX 2.2.0 since in 
LyX 2.1.5 the Italian keyboard used to work smoothly.


> Il giorno 30 mag 2017, alle ore 09:58, Luca Brandolini 
>  ha scritto:
> 
> I don’t think this is a Mac OS issue. It seems that the Italian keyboard is 
> designed to produce a question mark in place of 'Ctrl-m’. 
> Luca
> 
> 
>> Il giorno 29 mag 2017, alle ore 18:05, Scott Kostyshak  ha 
>> scritto:
>> 
>> On Mon, May 29, 2017 at 08:19:55AM +0200, Luca Brandolini wrote:
>>> It seems that in Mac OSX Italian keyboard 'Ctrl-m' is mapped to ‘?’.
>> 
>> Do you mean this is independent of LyX? That is, do you think that the
>> issue is LyX's fault or is it a more general issue on Mac OS?
>> 
>>> I have a modified layout of the Italian keyboard in which Ctrl-m is mapped 
>>> to ‘U+D’. With this layout LyX works correctly.
>> 
>> Good to know.
>> 
>> Scott
> 



Re: Tentative schedule for 2.3.0 release

2017-05-30 Thread Jean-Marc Lasgouttes

Le 04/05/2017 à 11:26, Stephan Witt a écrit :

I liked to use it since then for anything Hebrew.
Performance was quite noticeably improved.
With Hebrew this was not perfect but much,  much better.


So we might want to include it. Stephan, what do you think. It would be nice 
for 2.2.3 too.


I propose to include it (that’s why I CCed the lyx-devel list).
It would be good for 2.2.3 probably. I hope to compare it with Instruments soon.


Richard, this is about using QTextlayout caching for MacOS with Qt5. Qt5 
is supposed to do caching, but it is very inefficient on MacOS with 
ancient Hebrew. OK for 2.2.4?


JMarc


Re: Bad Citation Bug in 2.3dev

2017-05-30 Thread Jürgen Spitzmüller
2017-05-30 4:54 GMT+02:00 Richard Heck :

> BibTeX bst files do not control the output of citations, only of
> bibliography references. Right?
>

Right. You'd need to set it on package level (natbib's \setcitestyle or
\bibpunct, for instance or cite.sty's \citemid).


> >> Another question: Should the "literal" flag default to true or false?
> >> Having it default to true would be consistent with pre-2.3 behavior.
> >> People who wanted it otherwise could set it once and then it would
> >> (should) be remembered.
> > The argument for setting it to false was that novices tend to run into
> > more severe problems if they enter text that is interpreted as a
> > command and might not know what happens (as opposed to LaTeX
> > literates).
> >
> > For people who are used to the current situation, there will certainly
> > a learning process. But on the other hand, the situation was not very
> > clear at all, since some dialogs were outputting verbatim texts, some
> > not, some partially.
>
> Having the checkbox is fine with me. I just don't want to have to keep
> checking it.
>
> I've committed something along these lines.
>

OK. Thanks. Since this is used as a session setting, we might have the
unwanted side-effect that it is now off by default for everybody starting
LyX 2.3 with an old document.

Jürgen


>
> Richard
>
>


Re: syntax error in po files due to Windows line endings

2017-05-30 Thread Kornel Benko
Am Montag, 29. Mai 2017 um 23:10:06, schrieb Scott Kostyshak 
> On master when I do (CMake)
> 
> make layouttranslations1
> 
> I get
> 
> OSError: Syntax error in po file 
> /home/scott/lyxbuilds/master/repo/po/ar.po (line 35)
> 
> and indeed there are Windows line endings.
> 
> Scott

Yes, and if corrected in this file, we get errors in ca.po.

The same error as already corrected by Georg more than once.
(See 7fa742d186a188)

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: #10119: Shortcut Control-M

2017-05-30 Thread Luca Brandolini
I don’t think this is a Mac OS issue. It seems that the Italian keyboard is 
designed to produce a question mark in place of 'Ctrl-m’. 
Luca


> Il giorno 29 mag 2017, alle ore 18:05, Scott Kostyshak  ha 
> scritto:
> 
> On Mon, May 29, 2017 at 08:19:55AM +0200, Luca Brandolini wrote:
>> It seems that in Mac OSX Italian keyboard 'Ctrl-m' is mapped to ‘?’.
> 
> Do you mean this is independent of LyX? That is, do you think that the
> issue is LyX's fault or is it a more general issue on Mac OS?
> 
>> I have a modified layout of the Italian keyboard in which Ctrl-m is mapped 
>> to ‘U+D’. With this layout LyX works correctly.
> 
> Good to know.
> 
> Scott