Am Samstag, 27. Februar 2016 um 01:35:41, schrieb Scott Kostyshak
> On Fri, Feb 26, 2016 at 01:31:43PM +, Guenter Milde wrote:
> > On 2016-02-26, Scott Kostyshak wrote:
> > > On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> > >> Am Donnerstag, 25. Februar
On 2016-02-26, Kornel Benko wrote:
> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde
>
>> On 2016-02-26, Kornel Benko wrote:
>> >> >> I've updated TL for the first time in a while and now the following 11
>> >> >> tests fail for me:
>> ...
>> The common
> > OK. As this is a long existing polyglossia problem, it may be rather be a
> > font update or some other chagne in your setup or the test setup not
> > related to the TL update.
I was careful to do the following, and nothing in-between:
clean build
ctest
tlmgr update
clean build
ctest
Scott
signature.asc
Description: PGP signature
On Fri, Feb 26, 2016 at 01:31:43PM +, Guenter Milde wrote:
> On 2016-02-26, Scott Kostyshak wrote:
> > On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> >> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak
> >>
> >> > On Wed, Feb 24, 2016 at
t; This is why I argue in
> http://www.lyx.org/trac/ticket/8035#comment:7
> to ignore the polyglossia error: LyX's check for missing characters is more
> accurate and fully sufficient.
And this one was with font change.
> >> Also, the version of polyglossia/gloss-russian.ldf
sufficient.
>> Also, the version of polyglossia/gloss-russian.ldf and the polyglossia
>> changelog might give a hint.
> It is always the newest available for TL15.
OK. As this is a long existing polyglossia problem, it may be rather be a
font update or some other chagne in your setup or the test setup not
related to the TL update.
Günter
Am Freitag, 26. Februar 2016 um 13:26:43, schrieb Guenter Milde
> On 2016-02-26, Kornel Benko wrote:
>
> > [-- Type: text/plain, Encoding: 7bit --]
>
> > Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak
> >
> >> I've updated TL for the
On 2016-02-26, Scott Kostyshak wrote:
> On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
>> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak
>>
>> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
>> > > Am Mittwoch, 24. Februar
On 2016-02-26, Kornel Benko wrote:
> [-- Type: text/plain, Encoding: 7bit --]
> Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak
>
>> I've updated TL for the first time in a while and now the following 11
>> tests fail for me:
>> ctest -R
>>
Am Freitag, 26. Februar 2016 um 03:14:10, schrieb Scott Kostyshak
> On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> > Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak
> >
> > > On Wed, Feb 24, 2016 at 09:51:12PM +0100,
On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak
>
> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde
> > >
Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak
> I've updated TL for the first time in a while and now the following 11
> tests fail for me:
>
> ctest -R
> "MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|
confirmed
>
Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak
> On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde
> >
>
> > > BTW: my version of the "system font" is
I've updated TL for the first time in a while and now the following 11
tests fail for me:
ctest -R
On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde
>
> > BTW: my version of the "system font" is
> >
> > Paket: fonts-font-awesome
> > Zustand: Installiert
> > Automatisch installiert: ja
> >
Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde
> On 2016-02-24, Kornel Benko wrote:
>
> > [-- Type: text/plain, Encoding: 7bit --]
>
> > Am Mittwoch, 24. Februar 2016 um 15:52:48, schrieb Guenter Milde
> >
> >> On 2016-02-24, Kornel
On 2016-02-24, Kornel Benko wrote:
> [-- Type: text/plain, Encoding: 7bit --]
> Am Mittwoch, 24. Februar 2016 um 15:52:48, schrieb Guenter Milde
>
>> On 2016-02-24, Kornel Benko wrote:
> ...
>> > But you have a point, libreoffice doesn't show characters above U+F195
>> >
Am Mittwoch, 24. Februar 2016 um 15:52:48, schrieb Guenter Milde
> On 2016-02-24, Kornel Benko wrote:
...
> > But you have a point, libreoffice doesn't show characters above U+F195
> > in private area.
>
> This may be a limitation of libreoffice, not the font. Maybe some
On 2016-02-24, Kornel Benko wrote:
> Am Mittwoch, 24. Februar 2016 um 09:49:34, schrieb Guenter Milde
>
>> On 2016-02-23, Kornel Benko wrote:
>> > Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde
>> >
>> >> On 2016-02-20, Guenter Milde
Am Mittwoch, 24. Februar 2016 um 09:49:34, schrieb Guenter Milde
> On 2016-02-23, Kornel Benko wrote:
> > Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde
> >
> >> On 2016-02-20, Guenter Milde wrote:
> >> > On 2016-02-20, Kornel Benko
On 2016-02-23, Kornel Benko wrote:
> Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde
>
>> On 2016-02-20, Guenter Milde wrote:
>> > On 2016-02-20, Kornel Benko wrote:
>> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde
>> >>
Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde
> On 2016-02-20, Guenter Milde wrote:
> > On 2016-02-20, Kornel Benko wrote:
> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde
> >>
>
> Dear Kornel,
>
> I hope to have
On 2016-02-20, Guenter Milde wrote:
> On 2016-02-20, Kornel Benko wrote:
>> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde
>>
Dear Kornel,
I hope to have solved the "XeTeX + Awesome" mystery:
>>> >> >> Strange: It works here, both "per hand" and via
Am Montag, 22. Februar 2016 um 23:20:21, schrieb Kornel Benko
> > Did you try? It fails here. (Cf. lyx test file below.)
> >
>
> I tried the lyx file you sent. Luatex has no problem with deactivated 1st
> branch.
> I.e. if '${a}_{\mbox{a}}$' is active.
>
Outch. I had overseen
Am Montag, 22. Februar 2016 um 21:17:44, schrieb Guenter Milde
> On 2016-02-21, Kornel Benko wrote:
> > Am Sonntag, 21. Februar 2016 um 16:07:20, schrieb Guenter Milde
> >
> >> On 2016-02-21, Kornel Benko wrote:
>
> >> >> I investigated a little. Trying
On 2016-02-21, Kornel Benko wrote:
> Am Sonntag, 21. Februar 2016 um 16:07:20, schrieb Guenter Milde
>
>> On 2016-02-21, Kornel Benko wrote:
>> >> I investigated a little. Trying to compile manually (export as luatex,
>> >> use bibtex, use lualatex) I found what is causing
Am Sonntag, 21. Februar 2016 um 16:07:20, schrieb Guenter Milde
> On 2016-02-21, Kornel Benko wrote:
>
> >> I investigated a little. Trying to compile manually (export as luatex,
> >> use bibtex, use lualatex) I found what is causing lualatex/bibtex to
> >> misbehave.
>
>
On 2016-02-21, Kornel Benko wrote:
>> I investigated a little. Trying to compile manually (export as luatex,
>> use bibtex, use lualatex) I found what is causing lualatex/bibtex to
>> misbehave.
>> 1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61,
>> entry Arduengo1994).
Am Sonntag, 21. Februar 2016 um 13:24:02, schrieb Kornel Benko
> Am Samstag, 20. Februar 2016 um 20:52:23, schrieb Guenter Milde
>
> >
> > OTOH, I am pretty sure this has something to do with some of the used
> > LaTeX packages not beeing fit for Xe/LuaTeX.
Am Samstag, 20. Februar 2016 um 20:52:23, schrieb Guenter Milde
>
> OTOH, I am pretty sure this has something to do with some of the used
> LaTeX packages not beeing fit for Xe/LuaTeX. Maybe you can bisect or we
> need to compare the complete list of included packages and
rent modernCV version because of a babel issue
> with Spanish. We found now a solution (the preamble line) and could
> update the file.
OK, then this would be the more accurate description.
I am glad you found a way to clean up the document.
>> Now 2 more testcases fail.
>> 6
Kornel Benko wrote:
>> >> >> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr
>> >> >> > <uwesto...@lyx.org>
>> >> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> >> >> >> A
; <uwesto...@lyx.org>
> >> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> >> >> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> >> >> Date: Fri Feb 19 02:16:36 2016 +0100
>
> >> >> >> Span
t;
>> >> On 2016-02-19, Kornel Benko wrote:
>> >> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr
>> >> > <uwesto...@lyx.org>
>> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> >> >> Au
Author: Uwe Stöhr <uwesto...@lyx.org>
> >> >> Date: Fri Feb 19 02:16:36 2016 +0100
>
> >> >> Spanish modernCV.lyx: update the file and make it compilable
>
> >> > This comment seems misleading. With pdflatex it was compilable also
> >> &
m 02:16:42, schrieb Uwe Stöhr
>> > <uwesto...@lyx.org>
>> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> >> Author: Uwe Stöhr <uwesto...@lyx.org>
>> >> Date: Fri Feb 19 02:16:36 2016 +0100
>> >> Spanish modernCV.lyx: update t
. We found now a solution (the preamble line) and could
update the file.
Now 2 more testcases fail.
6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF
..***Failed 61.93 sec
7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF
eeb33
> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> Date: Fri Feb 19 02:16:36 2016 +0100
>
> >> Spanish modernCV.lyx: update the file and make it compilable
>
> > This comment seems misleading. With pdflatex it was compilable also
> > before
t; <uwesto...@lyx.org>
> > >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> > >> Author: Uwe Stöhr <uwesto...@lyx.org>
> > >> Date: Fri Feb 19 02:16:36 2016 +0100
> >
> > >> Spanish modernCV.lyx: update the file
eeb33
> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> Date: Fri Feb 19 02:16:36 2016 +0100
>
> >> Spanish modernCV.lyx: update the file and make it compilable
>
> > This comment seems misleading. With pdflatex it was compilable also
> >
On 2016-02-19, Kornel Benko wrote:
> Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr
> <uwesto...@lyx.org>
>> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> Author: Uwe Stöhr <uwesto...@lyx.org>
>> Date: Fri Feb 19 02:16:36 2016 +0100
Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr <uwesto...@lyx.org>
> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> Author: Uwe Stöhr <uwesto...@lyx.org>
> Date: Fri Feb 19 02:16:36 2016 +0100
>
> Spanish modernCV.lyx: update the file and make
to git a final review, and Georg also is
> trying to look into an issue that Stephan has reported. After beta I do
> not think developers are planning many non-trivial commits so whether we
> achieve end of February for a final release will depend on what issues
> our beta testers find and on
Jean-Marc Lasgouttes wrote:
> Le 09/02/2016 19:06, Scott Kostyshak a écrit :
>> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
>> index ff4068a..fae083f 100644
>> --- a/lib/doc/LFUNs.lyx
>> +++ b/lib/doc/LFUNs.lyx
>> @@ -102,7 +102,7 @@ The \SpecialChar LyX
>> \end_layout
>>
>>
On Thu, Feb 11, 2016 at 08:49:57PM +0100, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
>
> > Le 09/02/2016 19:06, Scott Kostyshak a écrit :
> >> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
> >> index ff4068a..fae083f 100644
> >> --- a/lib/doc/LFUNs.lyx
> >> +++ b/lib/doc/LFUNs.lyx
> >>
Scott Kostyshak wrote:
> On Wed, Jan 27, 2016 at 06:53:04PM +0100, Guillaume Munch wrote:
>> commit 360742c515fcb74e6b8b5383f2e3002edb2d00cf
>> Author: Guillaume Munch <g...@lyx.org>
>> Date: Wed Jan 27 18:35:10 2016 +0100
>>
>> New LFUN tabular-fea
t;> Date: Wed Jan 27 18:35:10 2016 +0100
> >>
> >> New LFUN tabular-feature: update docs
> >>
> >> Simply run updatedocs.py
> >>
> >> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
> >> index a529a0a..ff4068
Am Donnerstag, 11. Februar 2016 um 23:29:55, schrieb Uwe Stöhr
> diff --git a/development/Win32/packaging/installer/lang/slovak.nsh
> b/development/Win32/packaging/installer/lang/slovak.nsh
> index 64a2879..abfef3e 100644
> ---
Am 12.02.2016 um 01:03 schrieb Kornel Benko:
-#-*-coding: windows-1250;-*-
May I ask, why did you remove this line?
This should not happen. I reverted this now.
thanks and regards
Uwe
Le 09/02/2016 19:06, Scott Kostyshak a écrit :
diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
index ff4068a..fae083f 100644
--- a/lib/doc/LFUNs.lyx
+++ b/lib/doc/LFUNs.lyx
@@ -102,7 +102,7 @@ The \SpecialChar LyX
\end_layout
\begin_layout Date
-2016-01-27
+2016-02-09
\end_layout
We
On Wed, Jan 27, 2016 at 06:53:04PM +0100, Guillaume Munch wrote:
> commit 360742c515fcb74e6b8b5383f2e3002edb2d00cf
> Author: Guillaume Munch <g...@lyx.org>
> Date: Wed Jan 27 18:35:10 2016 +0100
>
> New LFUN tabular-feature: update docs
>
> Simply run up
Uwe Stöhr wrote:
> Am 29.01.2016 um 22:32 schrieb Georg Baum:
>
>> Does anybody give a +1 subsequently for the ACM layout update? If yes, we
>> should update the version numbers of the tex2lyx tests. If not, I propose
>> that Uwe reverts the layout file changes an
Hi Uwe,
I attach the screenshot to this mail. It seems there is no corresponding
strings included in .nsh files.
Best regards,
Koji
On 2016年01月28日 08:26, Uwe Stöhr wrote:
> Am 27.01.2016 um 09:29 schrieb Koji Yokota:
>
>> I browsed the Windows installer for 2.2 alpha a little bit and found the
fixed already in master, so I
cherry-picked the commits (see attached).
So what shall I do with this patch? In my view it improves the
situation. The only reason for not pushing it would be if we revert the
boost update patch.
I did not reply since the original code is from me, so I am obviously
Am 29.01.2016 um 22:32 schrieb Georg Baum:
So what are we going to do now?
The tex2lyx tests are currently failing because of wrong versions (I guess
because Guillaume did resolve them with git and did not regenerate them
after merging his patches with the ACM layout update).
I don't
that tex2lyx gets broken for other files.
I now re-run the tex2lyx tests and it tells me that ALL tests fail. In
fact this is wrong because Guillaume only forgot to update the
fileformat of the tex2lyx test files.
Since tex2lyx itself works fine I doubt that the tex2lyx tests are that
useful
ussed in the other thread, you are correct.
>
> So what are we going to do now?
>
> The tex2lyx tests are currently failing because of wrong versions (I guess
> because Guillaume did resolve them with git and did not regenerate them
> after merging his patches with the
are currently failing because of wrong versions (I guess
because Guillaume did resolve them with git and did not regenerate them
after merging his patches with the ACM layout update).
Does anybody give a +1 subsequently for the ACM layout update? If yes, we
should update the version numbers
Am 27.01.2016 um 09:29 schrieb Koji Yokota:
I browsed the Windows installer for 2.2 alpha a little bit and found the
pane titled "Choose Users" is not translated yet.
Hi Koji,
I cannot find this. Could you please send me a screenshot?
You find the translations for the installer in this Git
On Wed, Jan 27, 2016 at 08:11:09AM +0100, Guillaume Munch wrote:
> Le 27/01/2016 01:58, Uwe Stöhr a écrit :
> >commit c1e0b24304e67ede19f30c2ee7498386bfcf6808
> >Author: Uwe Stöhr <uwesto...@lyx.org>
> >Date: Wed Jan 27 01:58:13 2016 +0100
> >
> > ac
Le 27/01/2016 01:58, Uwe Stöhr a écrit :
@@ -2239,10 +2343,12 @@ convert = [
[501, [convert_fontsettings]],
[502, []],
[503, []],
- [504, [convert_save_props]]
+ [504, [convert_save_props]],
+ [505, [convert_ACM_siggraph]]
Am 27.01.2016 um 18:49 schrieb Guillaume Munch:
Uwe, I am worried about this duplicate application of revert_save_props.
Thanks, I fixed this now.
Please, apply the doc updates in a separate commit because they prevent
us from reading the commit log and spotting such errors.
OK.
regards
was it such a problem for you? Isn't it just to update the
fileformat number and then run the 2 scripts to update the docs and the
tex2lyx files? (Takes here 5 minutes.)
I am nevertheless sorry that I disturbed your work. This was not my
plan. I was simply not following the thread of your patch.
Nevertheless
Le 27/01/2016 01:58, Uwe Stöhr a écrit :
commit c1e0b24304e67ede19f30c2ee7498386bfcf6808
Author: Uwe Stöhr <uwesto...@lyx.org>
Date: Wed Jan 27 01:58:13 2016 +0100
acmsiggraph.layout: update layout for ACM siggraph 0.92
fileformat change: update fileformat for all files
diff
Jean-Marc Lasgouttes wrote:
> Le 25/01/2016 10:58, Kornel Benko a écrit :
>> Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes
>>
>>> Le 22/01/2016 17:15, Kornel Benko a écrit :
>> Even with this patch, I could not compile src/support/ForkedCalls.cpp
xed already in master, so I
>> cherry-picked the commits (see attached).
>
> So what shall I do with this patch? In my view it improves the
> situation. The only reason for not pushing it would be if we revert the
> boost update patch.
I did not reply since the original code is from me,
Le 22/01/2016 22:55, Georg Baum a écrit :
C++11 does not matter for 2.1 IMHO. Compilers will support C++98 much longer
than 2.1 will be relevant, and even if that means to enable it by special
command line options users can pass them to configure.
I guess the TR1 support is finally biting us
Le 22/01/2016 17:15, Kornel Benko a écrit :
Even with this patch, I could not compile src/support/ForkedCalls.cpp with
gcc-4.8.4.
This is in C++11 mode, right?
Yes, it is set by checking if the compiler is able to use this mode.
With autotools we let C++11 mode be disabled by default in
Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes
> Le 22/01/2016 17:15, Kornel Benko a écrit :
> >>> Even with this patch, I could not compile src/support/ForkedCalls.cpp
> >>> with gcc-4.8.4.
> >>
> >> This is in C++11 mode, right?
> >
> > Yes, it is set
Le 21/01/2016 15:42, Jean-Marc Lasgouttes a écrit :
Le 14/01/2016 19:12, Jean-Marc Lasgouttes a écrit :
Le 09/01/2016 00:50, Richard Heck a écrit :
On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I
Le 25/01/2016 10:58, Kornel Benko a écrit :
Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes
Le 22/01/2016 17:15, Kornel Benko a écrit :
Even with this patch, I could not compile src/support/ForkedCalls.cpp with
gcc-4.8.4.
This is in C++11 mode,
Am Freitag, 22. Januar 2016 um 11:27:02, schrieb Jean-Marc Lasgouttes
> Le 21/01/2016 22:40, Richard Heck a écrit :
> > On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> >> I guess it also depends how much space for error we have...
> >> Richard, do you plan to release one
Jean-Marc Lasgouttes wrote:
> This is in C++11 mode, right? By default (c++98) it should just work
> IMO. I do not think that we have firm plans of making lyx 2.1 compile in
> C++11 mode.
C++11 does not matter for 2.1 IMHO. Compilers will support C++98 much longer
than 2.1 will be relevant, and
Le 21/01/2016 22:40, Richard Heck a écrit :
On 01/21/2016 04:07 PM, Pavel Sanda wrote:
I guess it also depends how much space for error we have...
Richard, do you plan to release one intermediate 2.1.x or you just waiting for
the final one?
How far out do we realistically think 2.2.0 is? I
Le 22/01/2016 16:15, Kornel Benko a écrit :
Am Freitag, 22. Januar 2016 um 11:27:02, schrieb Jean-Marc Lasgouttes
Le 21/01/2016 22:40, Richard Heck a écrit :
On 01/21/2016 04:07 PM, Pavel Sanda wrote:
I guess it also depends how much space for error we have...
Richard,
Am Freitag, 22. Januar 2016 um 17:01:11, schrieb Jean-Marc Lasgouttes
> Le 22/01/2016 16:15, Kornel Benko a écrit :
> > Am Freitag, 22. Januar 2016 um 11:27:02, schrieb Jean-Marc Lasgouttes
> >
> >> Le 21/01/2016 22:40, Richard Heck a écrit :
> >>> On
Le 14/01/2016 19:12, Jean-Marc Lasgouttes a écrit :
Le 09/01/2016 00:50, Richard Heck a écrit :
On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.
Fine
On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? I
>> would guess not.
> I guess it also depends how much space for error we have...
> Richard, do you plan to release one intermediate 2.1.x or you
On Thu, Jan 21, 2016 at 04:40:56PM -0500, Richard Heck wrote:
> On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> > Jean-Marc Lasgouttes wrote:
> >> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? I
> >> would guess not.
> > I guess it also depends how much space for error we
Jean-Marc Lasgouttes wrote:
> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? I
> would guess not.
I guess it also depends how much space for error we have...
Richard, do you plan to release one intermediate 2.1.x or you just waiting
for the final one?
Pavel
Le 16/01/16 12:48, Guenter Milde a écrit :
Or we remove this generated file from git (my preference).
This creates problems of its own, since now there are files in
/lib.
JMarc
Le 16/01/2016 10:12, Georg Baum a écrit :
Guillaume Munch wrote:
I believe as well that we should not extend the already long checklist
for format changes. Updatedocs could take care of running gen_lfuns and
then update it to the latest format.
Good idea. I added the generation of LFUNs.lyx
Guillaume Munch wrote:
> I believe as well that we should not extend the already long checklist
> for format changes. Updatedocs could take care of running gen_lfuns and
> then update it to the latest format.
Good idea. I added the generation of LFUNs.lyx, the version updating did
exis
On 2016-01-16, Georg Baum wrote:
> Guillaume Munch wrote:
>> I believe as well that we should not extend the already long checklist
>> for format changes. Updatedocs could take care of running gen_lfuns and
>> then update it to the latest format.
> Good idea. I added the
Le 15/01/2016 20:32, Georg Baum a écrit :
commit 4c3b8bf7c7205e26b28b6562be11105558ec3250
Author: Georg Baum <b...@lyx.org>
Date: Fri Jan 15 21:31:57 2016 +0100
Update LFUNs.lyx to current format
diff --git a/development/tools/gen_lfuns.py b/development/tools/gen_lfuns.py
index 8
Guillaume Munch wrote:
> Is a step in Development.lyx missing?
IIRC we did not decide that yet. IMHO it is not required to update these
files for each format change, but some time ago we decided that for a
release all files should be up to date, and it is in the release checklist.
Georg
Le 15/01/2016 20:50, Georg Baum a écrit :
Guillaume Munch wrote:
Is a step in Development.lyx missing?
IIRC we did not decide that yet. IMHO it is not required to update these
files for each format change, but some time ago we decided that for a
release all files should be up to date
Le 09/01/2016 00:50, Richard Heck a écrit :
On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.
Fine with me, and I see the same warnings.
OK, I pushed
Le 11/01/2016 20:53, Georg Baum a écrit :
The few times I did run that script it worked fine. If you look at a few
files in the diff and see no peculiar change I'd say it is safe to commit.
One thing we should keep in mind is that this would also produce a 3 MB
2.1.4->2.1.5 patch.
Richard, is
Le 09/01/2016 00:50, Richard Heck a écrit :
On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.
Fine with me, and I see the same warnings.
I ran
Jean-Marc Lasgouttes wrote:
> I ran the extract.sh script, and have a 3MB commit. Is that to be
> expected? It compiles without warning (using a small additional fix).
>
> Shall I just push it? Does someone want to see it or have a go at it?
The few times I did run that script it worked fine.
On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
>
> Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
> update it to 1.60? I am getting loads of warnings with gcc 5.1.
Fine with me, and I see the same warnings.
Richard
Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.
JMarc
(in fact we would be happy to have unit
> > > >> tests that abstract away from these issues), our tests caught a
> > > >> regression in l3kernel. I reported the issue here
> > > >> http://tug.org/pipermail/tex-live/2016-January/037586.html
> > >
a
regression in l3kernel. I reported the issue here
http://tug.org/pipermail/tex-live/2016-January/037586.html
after updating to TL 2015 caused a test to go from passing to failing.
Yesterday or today's update fixed the regression.
The test is:
EXAMPLES_export/examples/colored-boxes_pdf5_texF
Scott
.org/pipermail/tex-live/2016-January/037586.html
>> after updating to TL 2015 caused a test to go from passing to failing.
>> Yesterday or today's update fixed the regression.
>> The test is:
>> EXAMPLES_export/examples/colored-boxes_pdf5_texF
> Just checked. Fa
o failing.
> Yesterday or today's update fixed the regression.
>
> The test is:
> EXAMPLES_export/examples/colored-boxes_pdf5_texF
Just checked. Failed.
Updated TL
Check. Passed.
That is nice.
> Scott
Kornel
signature.asc
Description: This is a digitally signed message part.
On Tue, Dec 08, 2015 at 10:41:37AM -0500, Richard Heck wrote:
> On 12/08/2015 01:57 AM, Kornel Benko wrote:
> > Am Dienstag, 8. Dezember 2015 um 07:39:50, schrieb Scott Kostyshak
> >
> >> + The root reason for this is that we do support converting layouts to
> >> older
> > The
On 12/08/2015 01:57 AM, Kornel Benko wrote:
> Am Dienstag, 8. Dezember 2015 um 07:39:50, schrieb Scott Kostyshak
>
>> + The root reason for this is that we do support converting layouts to older
> The root reason for this is that we do *not* support converting layouts to
>
Am Dienstag, 8. Dezember 2015 um 07:39:50, schrieb Scott Kostyshak
> + The root reason for this is that we do support converting layouts to older
The root reason for this is that we do *not* support converting layouts to older
> + layout formats, as we do for the .lyx file
801 - 900 of 9616 matches
Mail list logo