Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 19/01/2017 à 16:04, Jean-Marc Lasgouttes a écrit : Here is what happened 1/ I change randomly (!) the spacing of math equations in the MathRow work 2/ as a consequence the formulas in lib/symbols are often wrong 3/ I fix the problem with arabic test at e832d2e90f 4/ I do a new round of

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On 01/21/2017 07:34 AM, Enrico Forestieri wrote: > On Fri, Jan 20, 2017 at 06:49:29PM -0500, Richard Heck wrote: > >> On 01/20/2017 06:48 PM, Richard Heck wrote: >>> I'll cherry pick it for stable. >> No, I won't > Sorry, I would have to wait for an explicit nod... Sorry, that's not what I

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Fri, Jan 20, 2017 at 06:49:29PM -0500, Richard Heck wrote: > On 01/20/2017 06:48 PM, Richard Heck wrote: > > I'll cherry pick it for stable. > > No, I won't Sorry, I would have to wait for an explicit nod... -- Enrico

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On 01/20/2017 06:48 PM, Richard Heck wrote: > I'll cherry pick it for stable. No, I won't rh

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On 01/20/2017 06:37 PM, Enrico Forestieri wrote: > On Fri, Jan 20, 2017 at 07:53:40PM +0100, Enrico Forestieri wrote: >> On Thu, Jan 19, 2017 at 03:28:25PM -0500, Richard Heck wrote: >>> On 01/19/2017 02:35 PM, Enrico Forestieri wrote: In conclusion, your patch textwidth2.diff is the right

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Fri, Jan 20, 2017 at 07:53:40PM +0100, Enrico Forestieri wrote: > On Thu, Jan 19, 2017 at 03:28:25PM -0500, Richard Heck wrote: > > On 01/19/2017 02:35 PM, Enrico Forestieri wrote: > > > > > > In conclusion, your patch textwidth2.diff is the right thing to do > > > in master. For stable we have

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Thu, Jan 19, 2017 at 03:28:25PM -0500, Richard Heck wrote: > On 01/19/2017 02:35 PM, Enrico Forestieri wrote: > > > > In conclusion, your patch textwidth2.diff is the right thing to do > > in master. For stable we have to make a decision. The alternatives are: > > > > 1) The patch I posted

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On 01/19/2017 02:35 PM, Enrico Forestieri wrote: > On Thu, Jan 19, 2017 at 04:04:15PM +0100, Jean-Marc Lasgouttes wrote: > >> Le 18/01/2017 à 19:23, Enrico Forestieri a écrit : I am not completely sure what this styleName thing does. Is it mac/windows only? >>> No, it is platform

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Thu, Jan 19, 2017 at 04:04:15PM +0100, Jean-Marc Lasgouttes wrote: > Le 18/01/2017 à 19:23, Enrico Forestieri a écrit : > > > I am not completely sure what this styleName thing does. Is it mac/windows > > > only? > > > > No, it is platform independent. For example, if you ask for a font with

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 18/01/2017 à 19:23, Enrico Forestieri a écrit : I am not completely sure what this styleName thing does. Is it mac/windows only? No, it is platform independent. For example, if you ask for a font with name cmsy10, Qt would pick the first cmsy10.ttf it stumbles upon. This would be

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Wed, Jan 18, 2017 at 03:19:31PM +0100, Jean-Marc Lasgouttes wrote: > > I am not completely sure what this styleName thing does. Is it mac/windows > only? No, it is platform independent. For example, if you ask for a font with name cmsy10, Qt would pick the first cmsy10.ttf it stumbles upon.

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 17/01/2017 à 18:01, Enrico Forestieri a écrit : Hello Enroci, Hi JMcra :) :) I often do this typo, but usually I manage to correct it in time. Yes, but I would propose to do that in addition. Nonetheless, my feeling is that this issue is caused by the assumptions of Qt about a given

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Tue, Jan 17, 2017 at 02:51:23PM +0100, Jean-Marc Lasgouttes wrote: > Le 17/01/2017 à 12:19, Enrico Forestieri a écrit : > > This seems to be a Qt issue. QTextLine::naturalTextWidth() should report > > the width of the line occupied by text. If a zero-width character is > > present, it is

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 17/01/2017 à 15:38, Richard Heck a écrit : Thanks for your work on this, both of you. When you decide on a solution, please feel free to commit to stable. OK, thanks. While we are at it, is there some reason why I cannot get an answer there ?

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On 01/17/2017 08:51 AM, Jean-Marc Lasgouttes wrote: > Le 17/01/2017 à 12:19, Enrico Forestieri a écrit : >> This seems to be a Qt issue. QTextLine::naturalTextWidth() should report >> the width of the line occupied by text. If a zero-width character is >> present, it is correctly accounted for,

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 17/01/2017 à 12:19, Enrico Forestieri a écrit : This seems to be a Qt issue. QTextLine::naturalTextWidth() should report the width of the line occupied by text. If a zero-width character is present, it is correctly accounted for, except when it is the only character in the line. That is to

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

On Mon, Jan 16, 2017 at 03:36:07PM -0500, Richard Heck wrote: > Resending as a new thread so it is more visible > > On 01/16/2017 02:04 PM, Scott Kostyshak wrote: > > On Mon, Jan 16, 2017 at 01:13:44PM -0500, Richard Heck wrote: > >> I am seeing display problems in stable with \notin and

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 16/01/2017 à 22:09, Jean-Marc Lasgouttes a écrit : Le 16/01/2017 à 21:29, Richard Heck a écrit : Bisect blames: 24648404b3c85015584b1ca127e257cbecf3342d is the first bad commit commit 24648404b3c85015584b1ca127e257cbecf3342d Author: Jean-Marc Lasgouttes Date: Sun Oct

Re: [CONFIRMED] Display Problem in Stable with \notin, etc.

Le 16/01/2017 à 21:29, Richard Heck a écrit : Bisect blames: 24648404b3c85015584b1ca127e257cbecf3342d is the first bad commit commit 24648404b3c85015584b1ca127e257cbecf3342d Author: Jean-Marc Lasgouttes Date: Sun Oct 23 20:52:01 2016 +0200 Work around issues with Qt5