On Tue, Feb 06, 2018 at 08:35:56PM +, Jean-Marc Lasgouttes wrote:
> Le 06/02/2018 à 18:17, Scott Kostyshak a écrit :
> > Absolutely. I think JMarc made a similar suggestion to hide it. I
> > proposed to silently ignore it because by nature of being a release
> > manager I tend to by default sug
Le 06/02/2018 à 18:17, Scott Kostyshak a écrit :
Absolutely. I think JMarc made a similar suggestion to hide it. I
proposed to silently ignore it because by nature of being a release
manager I tend to by default suggest the fewest changes possible now
that we are after rc2.
Note that we already
On Tue, Feb 06, 2018 at 05:49:39PM +, Jürgen Spitzmüller wrote:
> Am Dienstag, den 06.02.2018, 12:17 -0500 schrieb Scott Kostyshak:
> > I'm most worried about a change to the .ui files. We've seen weird
> > platform-specific Qt-version specific behavior with even minor
> > changes
> > to .ui fi
Am Dienstag, den 06.02.2018, 12:17 -0500 schrieb Scott Kostyshak:
> I'm most worried about a change to the .ui files. We've seen weird
> platform-specific Qt-version specific behavior with even minor
> changes
> to .ui files that no one would guess would cause a problem. But it
> might
> be possibl
On Tue, Feb 06, 2018 at 05:07:02PM +, Joel Kulesza wrote:
> On Tue, Feb 6, 2018 at 10:00 AM, Scott Kostyshak wrote:
>
> > If the repair is non-trivial, let's not fix it and
> >
> instead just not act on the pixmap pref. Does that seem like a good plan
> > for 2.3.0?
>
>
> If this is the ro
On Tue, Feb 6, 2018 at 10:00 AM, Scott Kostyshak wrote:
> If the repair is non-trivial, let's not fix it and
>
instead just not act on the pixmap pref. Does that seem like a good plan
> for 2.3.0?
If this is the route taken, would it be acceptable to gray-out/disable the
unchecked checkbox in
On Tue, Feb 06, 2018 at 09:29:08AM +, Jean-Marc Lasgouttes wrote:
> Le 06/02/2018 à 01:57, Scott Kostyshak a écrit :
> > > This is the main question IMO. These days, we cache QTextLayout objects,
> > > which already contain the typeset glyphs.
> >
> > I know nothing about this. If we decide to
On Tue, Feb 06, 2018 at 10:01:02AM +, Jean-Marc Lasgouttes wrote:
> Le 01/02/2018 à 06:20, Scott Kostyshak a écrit :
> > On Wed, Jan 31, 2018 at 11:41:58PM +, Jean-Marc Lasgouttes wrote:
> >
> > > For the rest, it is probably the complete rewrite of math spacing...
> > > But a bisect may p
On Tue, Feb 06, 2018 at 11:47:15AM +, Jürgen Spitzmüller wrote:
> Candidate for 2.3.x.
Go ahead for 2.3.0.
Thanks,
Scott
signature.asc
Description: PGP signature
Am Dienstag, den 06.02.2018, 12:46 +0100 schrieb Juergen Spitzmueller:
> commit 6236bcb653f36336b62d4c48769b2d60ec13a0dc
> Author: Juergen Spitzmueller
> Date: Tue Feb 6 12:45:22 2018 +0100
>
> Add missing connection.
>
> This activates the OK/Apply when a biblatex style file is cha
Scott Kostyshak wrote:
> Can we at least have a hardcoded list of symbols that are not shown
> correctly? e.g. can we show "\oiint" as LaTeX in LyX instead of using
> the broken glyph? I don't know how to do that. In lib/symbols is it
> possible to still load the esint package but not use the glyph
Le 01/02/2018 à 06:20, Scott Kostyshak a écrit :
On Wed, Jan 31, 2018 at 11:41:58PM +, Jean-Marc Lasgouttes wrote:
For the rest, it is probably the complete rewrite of math spacing...
But a bisect may prove useful.
Bisect leads to 4a935ed7.
Are you sure? Enrico, for reference this is th
Le 06/02/2018 à 01:57, Scott Kostyshak a écrit :
This is the main question IMO. These days, we cache QTextLayout objects,
which already contain the typeset glyphs.
I know nothing about this. If we decide to not use the pixmap cache,
would we do a prefs to prefs change at this point in the relea
13 matches
Mail list logo
