Dear all,
I would like to propose that we release our LyX 2.3.0 alpha binaries for
Mac and Windows with Qt 5.9.0beta1 and that we release our final LyX
2.3.0 binaries with the final release of Qt 5.9.0.
I think there is an advantage to releasing the final LyX version with
the same Qt x.y version
Dear all,
Is anyone planning to test TL 2017 pretest? It begins 16 April [1]. I am
planning to install it and run all of our export tests. Some will surely
fail. And then it will be a question of whether we need to change our
LaTeX export. Hopefully we will not, but it is good to plan for this
pos
Dear all,
I think there is agreement that master is pretty stable. Besides just a
feeling, I think that this can be confirmed by looking at the trac
tickets with "2.3.0" milestone and tickets with the "regression"
keyword.
I propose the following schedule for the 2.3.0 release process:
alpha
On Sat, Mar 04, 2017 at 07:06:51PM +, José Abílio Matos wrote:
> Now regarding the other issue at hand and looking into history we have that:
>
> 2.2.0 -> 2016.05
> 2.1.0 -> 2014.04
> 2.0.0 -> 2011.04
> 1.6.0 -> 2008.11
> 1.5.0 -> 2007.07
> 1.4.0 -> 2006.03
>
> First the obvious conclusion,
On Sat, Apr 08, 2017 at 03:30:29AM +0200, Uwe Stöhr wrote:
> commit b3b7675f544128ea4bbff564262774533af3598f
> Author: Uwe Stöhr
> Date: Sat Apr 8 03:30:21 2017 +0200
>
> Length.cpp: add new unit representing \baselineskip
>
> - fileformat change
This commit broke the test
chec
On Mon, Apr 10, 2017 at 01:38:49AM +0200, Uwe Stöhr wrote:
> Bug http://www.lyx.org/trac/ticket/10440
> in at least on Windows a major issue.
I agree.
> 5 months ago the user "backbone" presented a patch that fixes the bug for me
> (see attached).
> I don't understand what is wrong wit this patch
On Mon, Apr 10, 2017 at 01:00:07AM +0200, Uwe Stöhr wrote:
> However, I still think that we should not leave the WYSIWYM track in favor
> of WYSIWYG. The number of strokes is not important within LyX. The user
> should see that there will be strokes and that is it.
That's exactly the problem: For
On Sat, Apr 08, 2017 at 08:59:04PM +0200, Stephan Witt wrote:
> Am 06.04.2017 um 03:10 schrieb Scott Kostyshak :
> >
> > On Sat, Apr 01, 2017 at 09:49:13AM +0100, José Abílio Matos wrote:
> >> On Saturday, 1 April 2017 06.16.55 WEST Scott Kostyshak wrote:
> >>> José, any thoughts?
> >>
> >> The c
On Thu, Apr 06, 2017 at 01:46:32PM +0200, Jean-Marc Lasgouttes wrote:
> Le 06/04/2017 à 05:05, Scott Kostyshak a écrit :
> > To make sure I understand, you are against the attached patch because
> > the changes are not as complicated as in the iconv case, right?
>
> No, I would be against the atta
As reported in
http://www.lyx.org/trac/ticket/10270
LyX forbids incorrectly the float placement options.
The attached patch fixed this.
I don't think that a fileformat change is necessary but I could of
course do this.
regards Uwe
src/frontends/qt4/FloatPlacement.cpp | 12 ++--
src/i
El 10.04.2017 a las 00:44, Uwe Stöhr escribió:
And that way I googled around. Googling brings you quickly to the
"Script=Devanagari option. So one doesn't need to be a TeXpert to find
this. One now only needs an input field for that option. When this is
implemented I can update our Wiki pages
Bug http://www.lyx.org/trac/ticket/10440
in at least on Windows a major issue.
5 months ago the user "backbone" presented a patch that fixes the bug
for me (see attached).
I don't understand what is wrong wit this patch and all further patches
do not work.
Therefore the patch should go in if
El 06.04.2017 a las 11:10, Jean-Marc Lasgouttes escribió:
That is not how it works. Actually, I propose to add a rule to our
coding rules that says that no code which does not take in account zoom
and DPI when drawing should be accepted (with the usual exceptions, of
course).
I have not hear
El 07.04.2017 a las 22:19, Guillaume MM escribió:
- 411
- 351
+ 480
+ 350
One should need to rely on the indicative pixel size which does not take
into account the platform, dpi and language. This probably indicates
that the ui file is broken.
I don't understand. I have not
El 09.04.2017 a las 10:27, Jürgen Spitzmüller escribió:
In any case, such features need to be implemented at the beginning of
new development cycles, since they need testing and improvement, not at
the end of cycles.
I don't understand. We are talking about 3 simple line edits. As you can
see
Am Freitag, den 07.04.2017, 00:44 +0200 schrieb Uwe Stöhr:
> Since many years LyX misses the feature to input options to the font
> loading commands \setmainfont etc. We did not act for 5 years
> because
> you said exactly the same as today that it is not the right time:
> http://www.lyx.org/trac
16 matches
Mail list logo
