Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Le 06/10/2015 15:29, Kornel Benko a écrit : Hi Kornel, I could send it if I knew how. Sorry, have no experience with that, but willing to learn! # gdb lyx Or as I learnt recently, to properly see the symbols (you'll have to compile with the various devel options ON though): #

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

On Tue, Oct 06, 2015 at 10:41:52AM -0400, PhilipPirrip wrote: > Thanks, Kornel. I'll check these later. I went back in time, September 28 > 18:13 commit 39343d65af worked. Moving forward, will let you know when > things went bad and send you the backtrace. Are you stepping forward one-by-one?

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Am Dienstag, 6. Oktober 2015 um 10:05:15, schrieb PhilipPirrip > On 10/06/2015 06:00 AM, Kornel Benko wrote: > > > Could you please send a backtrace of the crash? > > > Hi Kornel, > I could send it if I knew how. Sorry, have no experience with that, but > willing to learn! >

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Thanks, Kornel. I'll check these later. I went back in time, September 28 18:13 commit 39343d65af worked. Moving forward, will let you know when things went bad and send you the backtrace.

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/2015 18:28, Jean-Marc Lasgouttes a écrit : For the docstring part of the code, I am not sure what code like the following do: -LASSERT(static_cast(*c) < 0x80, return l); -s.push_back(*c); +if (static_cast(*c) < 0x80) +s.push_back(*c); +else +return s +=

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/2015 18:28, Jean-Marc Lasgouttes a écrit : Le 06/10/2015 18:38, Guillaume Munch a écrit : I'm trying to come up with examples where do we actually "need" unicode in the interface. The ellipsis case seems to be trivial indeed. Is it trivial? On my ubuntu libreoffice (where I can

Re: UTF-8 in string literals and translation strings in particular

On 10/06/2015 12:38 PM, Guillaume Munch wrote: Le 06/10/2015 17:13, Pavel Sanda a écrit : Guillaume Munch wrote: Le 04/10/2015 23:20, Guillaume Munch a écrit : Dear list, Has there been some discussion already about allowing UTF-8 in the source code, in particular for translatable strings?

Re: Size of box insets

Le 06/10/2015 00:34, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: Le 03/10/2015 01:27, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: Why not do it in InsetText::Metrics directly? Is it a box-only problem? Hmm, is there another insettext which allows fixing to certain percentage of

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/2015 20:03, Guillaume Munch a écrit : Le 06/10/2015 18:28, Jean-Marc Lasgouttes a écrit : For the docstring part of the code, I am not sure what code like the following do: -LASSERT(static_cast(*c) < 0x80, return l); -s.push_back(*c); +if (static_cast(*c) < 0x80) +

Re: UTF-8 in string literals and translation strings in particular

Guillaume Munch wrote: >> Seriously, I think this is just going to annoy our translators. > > Seriously :) as described in the rationale of my patch, this cannot be more > transparent for translators. Gettext pre-sets the previous translation; > translators just have to do a global

Re: UTF-8 in string literals and translation strings in particular

Jean-Marc Lasgouttes wrote: > Well, actually I am not sure that we use the same ellipsis as in English. You mean as a translator I need to find French version of ellipsis? P

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/2015 21:01, Pavel Sanda a écrit : Guillaume Munch wrote: Seriously, I think this is just going to annoy our translators. Seriously :) as described in the rationale of my patch, this cannot be more transparent for translators. Gettext pre-sets the previous translation; translators

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/15 21:43, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: Well, actually I am not sure that we use the same ellipsis as in English. You mean as a translator I need to find French version of ellipsis? I even remeber of a document that stated that using 3 dots wa better in French,

Some buttons on Maths palette don't work!

Hello everyone, I am testing LyX suitability for my thesis write-up, and I've come across an odd problem: the buttons in submenus on the maths toolbar are _mostly_ unclickable. By that I mean that the first row of the buttons in any given submenu on that palette does not work. It's hard to

Re: Some buttons on Maths palette don't work!

I tried disabling SIP on El Capitan as suggested in https://www.mail-archive.com/lyx-users@lists.lyx.org/msg101934.html This doesn't fix the problem with the symbol palettes -- clicking on the symbols doesn't work. LyX 2.1.4, July 24, 2015, OS X 10.11, MacBook Pro Retina, 15-inch, Mid 2014.

Re: Some buttons on Maths palette don't work!

John Kennan ssc.wisc.edu> writes: > > I tried disabling SIP on El Capitan as suggested in > > https://www.mail-archive.com/lyx-users lists.lyx.org/msg101934.html > > This doesn't fix the problem with the symbol palettes -- > clicking on the symbols doesn't work. > > LyX 2.1.4, July 24,

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Am Dienstag, 6. Oktober 2015 um 00:40:58, schrieb PhilipPirrip > Any experience compiling LyX 2.2.0dev with Qt 5.5.0 (on Fedora 23)? > Mine compiles well, but never starts: Segmentation fault (core dumped). > > This is my run_cmake.sh Could you please send a backtrace of the crash?

Re: UTF-8 in string literals and translation strings in particular

> Le 06/10/2015 21:01, Pavel Sanda a écrit : > I think you might be mixing issues. One thing is allowing to have > UTF-8 string literals especially in translations, another one is > deciding that we now use ? instead of ... in the interface to be > consistent with Qt. To clarify, I'm not against

Re: UTF-8 in string literals and translation strings in particular

After more looking around, I see that Apple recommends the ellispsis character: https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/TerminologyWording.html#//apple_ref/doc/uid/2957-CH15-SW3 Gnome seems to prefer ellipsis character too:

Re: Some buttons on Maths palette don't work!

On Tue, Oct 06, 2015 at 09:32:42PM +, Oliver Frolovs wrote: > Hello everyone, > > I am testing LyX suitability for my thesis write-up, > and I've come across an odd problem: > the buttons in submenus on the maths toolbar > are _mostly_ unclickable. By that I mean > that the first row of

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

On 10/06/2015 06:00 AM, Kornel Benko wrote: Could you please send a backtrace of the crash? Hi Kornel, I could send it if I knew how. Sorry, have no experience with that, but willing to learn! Are the Qt5 libs at runtime the same as the ones with which they are compiled? It's hard

Re: UTF-8 in string literals and translation strings in particular

Guillaume Munch wrote: > Le 04/10/2015 23:20, Guillaume Munch a écrit : >> Dear list, >> >> Has there been some discussion already about allowing UTF-8 in the >> source code, in particular for translatable strings? Is this >> something we long for? >> >> Guillaume >> > Seeing how there is

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/2015 18:38, Guillaume Munch a écrit : I'm trying to come up with examples where do we actually "need" unicode in the interface. The ellipsis case seems to be trivial indeed. Is it trivial? On my ubuntu libreoffice (where I can write the same string to compare), I would say that what

Re: UTF-8 in string literals and translation strings in particular

Well, actually I am not sure that we use the same ellipsis as in English. JMarc Le 6 octobre 2015 18:13:25 GMT+02:00, Pavel Sanda a écrit : >I'm trying to come up with examples where do we actually "need" unicode >in the interface. The ellipsis case seems to be trivial indeed.

Re: UTF-8 in string literals and translation strings in particular

Le 06/10/2015 17:13, Pavel Sanda a écrit : Guillaume Munch wrote: Le 04/10/2015 23:20, Guillaume Munch a écrit : Dear list, Has there been some discussion already about allowing UTF-8 in the source code, in particular for translatable strings? Is this something we long for? Guillaume

Re: Size of box insets

This looks like a good solution. Now that I think about it, what about fixed-width tabular cells ? Do they have the same problem ? Jmarc Le 6 octobre 2015 17:51:26 GMT+02:00, Pavel Sanda a écrit : >I can put it into InsetCollapsable for fixedwidth insets. For insettext >I do

Re: Size of box insets

Jean-Marc Lasgouttes wrote: > The code in IntextText::metrics does: > > // This can happen when a layout has a left and right margin, > // and the view is made very narrow. We can't do better than > // to draw it partly out of view (bug 5890). > if (mi.base.textwidth < 1) >