Am Fri, 17 Feb 2023 19:15:36 +0100
schrieb "Jürgen Spitzmüller" :
> Am Freitag, dem 17.02.2023 um 12:22 -0500 schrieb Scott Kostyshak:
> > Indeed. But for example we might want to know if an example or manual
> > fails because of this. I think Jürgen's point is that for a
> > *template*,
> > it ma
Am Freitag, dem 17.02.2023 um 12:22 -0500 schrieb Scott Kostyshak:
> Indeed. But for example we might want to know if an example or manual
> fails because of this. I think Jürgen's point is that for a
> *template*,
> it makes sense not to have it.
>
> > The disadvantage OTOH would be that we would
On Fri, Feb 17, 2023 at 05:39:54PM +0100, Kornel Benko wrote:
> Am Fri, 17 Feb 2023 11:20:44 -0500
> schrieb Scott Kostyshak :
>
> > On Fri, Feb 17, 2023 at 04:52:00PM +0100, Kornel Benko wrote:
> > > Am Fri, 17 Feb 2023 10:24:19 -0500
> > > schrieb Scott Kostyshak :
> > >
> > > > On Fri, Feb 1
Am Fri, 17 Feb 2023 11:20:44 -0500
schrieb Scott Kostyshak :
> On Fri, Feb 17, 2023 at 04:52:00PM +0100, Kornel Benko wrote:
> > Am Fri, 17 Feb 2023 10:24:19 -0500
> > schrieb Scott Kostyshak :
> >
> > > On Fri, Feb 17, 2023 at 10:01:48AM -0500, Scott Kostyshak wrote:
> > > > On Fri, Feb 17,
On Fri, Feb 17, 2023 at 04:52:00PM +0100, Kornel Benko wrote:
> Am Fri, 17 Feb 2023 10:24:19 -0500
> schrieb Scott Kostyshak :
>
> > On Fri, Feb 17, 2023 at 10:01:48AM -0500, Scott Kostyshak wrote:
> > > On Fri, Feb 17, 2023 at 03:42:14PM +0100, Jürgen Spitzmüller wrote:
> > > > Am Freitag, dem
Am Fri, 17 Feb 2023 10:24:19 -0500
schrieb Scott Kostyshak :
> On Fri, Feb 17, 2023 at 10:01:48AM -0500, Scott Kostyshak wrote:
> > On Fri, Feb 17, 2023 at 03:42:14PM +0100, Jürgen Spitzmüller wrote:
> > > Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> > > > I get the fol
On Fri, Feb 17, 2023 at 10:01:48AM -0500, Scott Kostyshak wrote:
> On Fri, Feb 17, 2023 at 03:42:14PM +0100, Jürgen Spitzmüller wrote:
> > Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> > > I get the following (the line number changes depending on the file):
> > >
> > > lyx
On Fri, Feb 17, 2023 at 03:42:14PM +0100, Jürgen Spitzmüller wrote:
> Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> > I get the following (the line number changes depending on the file):
> >
> > lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
> >
> > Is
Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> I get the following (the line number changes depending on the file):
>
> lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
>
> Is this worth fixing?
The bibtex inset in these files does not contain any bib fil
I get the following (the line number changes depending on the file):
lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
Is this worth fixing?
The following ctests are failing:
export/templates/ja/Articles/Japanese_Article_%28JS_Bundle_for_LuaTeX%29_lyx16
(Failed)
export/
On Sun, Jan 13, 2019 at 12:14:57PM -0500, Scott Kostyshak wrote:
> On Sun, Jan 13, 2019 at 09:55:56AM +0100, Enrico Forestieri wrote:
> > On Sat, Jan 12, 2019 at 08:03:26PM -0500, Scott Kostyshak wrote:
> > > For the example file minted-listings.lyx, if I export it with mas
On Sun, Jan 13, 2019 at 09:55:56AM +0100, Enrico Forestieri wrote:
> On Sat, Jan 12, 2019 at 08:03:26PM -0500, Scott Kostyshak wrote:
> > For the example file minted-listings.lyx, if I export it with master to
> > 2.2.x format, when I compile the exported file with LyX 2.2.x or wit
On Sat, Jan 12, 2019 at 08:03:26PM -0500, Scott Kostyshak wrote:
> For the example file minted-listings.lyx, if I export it with master to
> 2.2.x format, when I compile the exported file with LyX 2.2.x or with
> master, I get the following error:
>
> ! Package keyval Error: bg
For the example file minted-listings.lyx, if I export it with master to
2.2.x format, when I compile the exported file with LyX 2.2.x or with
master, I get the following error:
! Package keyval Error: bgcolor undefined.
Scott
signature.asc
Description: PGP signature
On Sun, Oct 07, 2018 at 05:18:23PM +0200, Jean-Marc Lasgouttes wrote:
> I have removed this feature in 2.4.0. The feature is already hidden in 2.3.
Sounds good. Thanks for doing that.
Scott
signature.asc
Description: PGP signature
Le 09/02/2018 à 19:19, Scott Kostyshak a écrit :
On Tue, Feb 06, 2018 at 10:15:30PM +, Scott Kostyshak wrote:
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 i
The 2.2.x branch is now closed so I can prepare the release of 2.2.4.
I'll send another note when binaries are available.
Richard
On Tue, Feb 06, 2018 at 10:15:30PM +, Scott Kostyshak wrote:
> 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
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
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
On Mon, Feb 05, 2018 at 08:40:09AM +, Jean-Marc Lasgouttes wrote:
> Le 05/02/2018 à 09:22, Stephan Witt a écrit :
> > Am 05.02.2018 um 03:07 schrieb Scott Kostyshak :
> > >
> > > On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
> > >
> > > > I cannot reproduce it either. Let’s se
Le 05/02/2018 à 09:22, Stephan Witt a écrit :
Am 05.02.2018 um 03:07 schrieb Scott Kostyshak :
On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
I cannot reproduce it either. Let’s see how it goes with the pixmap cache
disabled.
Joel and Stephan, can you reproduce with pixmap e
Am 05.02.2018 um 03:07 schrieb Scott Kostyshak :
>
> On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
>
>> I cannot reproduce it either. Let’s see how it goes with the pixmap cache
>> disabled.
>
> Joel and Stephan, can you reproduce with pixmap enabled?
Yes, I can reproduce with
On Sun, Feb 4, 2018 at 10:32 PM, Scott Kostyshak wrote:
> Would it make sense for Joel or
> Stephan (if he could reproduce) to do a bisect to figure out what caused
> the problem so we can figure out a fix for 2.3.x branch?
Let me know how I can help. If asked to do a bisect, it would be helpf
On Sun, Feb 04, 2018 at 10:17:27PM -0700, Joel Kulesza wrote:
> On Sun, Feb 4, 2018 at 7:07 PM, Scott Kostyshak wrote:
>
> > On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
> >
> > > I cannot reproduce it either. Let’s see how it goes with the pixmap
> > cache disabled.
> >
> > Joel
On Sun, Feb 4, 2018 at 7:07 PM, Scott Kostyshak wrote:
> On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
>
> > I cannot reproduce it either. Let’s see how it goes with the pixmap
> cache disabled.
>
> Joel and Stephan, can you reproduce with pixmap enabled?
>
Yes, I can reproduce.
On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
> I cannot reproduce it either. Let’s see how it goes with the pixmap cache
> disabled.
Joel and Stephan, can you reproduce with pixmap enabled?
Scott
signature.asc
Description: PGP signature
Hi Stephan,
The math font problem is not an urgent problem now since one can just turn
off the pixel map caching.
Regarding the blurry image, the problem you mentioned with low resolution
image generated by the Mac built-in image converter engine can be easily
fixed. I added a rule "sips -Z 600 -
On Sat, Feb 03, 2018 at 10:22:42PM +, Stephan Witt wrote:
> I cannot reproduce it either. Let’s see how it goes with the pixmap cache
> disabled.
+1.
> > Does anyone have suggestions for especific environment variables that
> > Zhexuan could test to see if it fixes things? e.g., could the
>
Am 03.02.2018 um 20:39 schrieb Scott Kostyshak :
>
> On Sat, Feb 03, 2018 at 07:31:15PM +, Joel Kulesza wrote:
>> On Sat, Feb 3, 2018 at 11:51 AM, Zhexuan Gong wrote:
>>
>>> Hi Scott,
>>>
>>> Yes please see attached for a minimum lyx file that produces the math font
>>> issue, and two scree
Le 03/02/2018 à 21:45, Zhexuan Gong a écrit :
Just found that turning off the pixel map caching fixed the math font
problem on 2.3.0rc2. However, 2.2.3 works fine even with pixel map
caching on.
I might have broken the Pixmap cache, since I have no way to test it on
linux. I will take a look
Just found that turning off the pixel map caching fixed the math font
problem on 2.3.0rc2. However, 2.2.3 works fine even with pixel map caching
on.
On Sat, Feb 3, 2018 at 1:42 PM, Zhexuan Gong wrote:
> It could be the macOS version then. I'm using the latest macOS 10.13.3.
> There must be somet
On Sat, Feb 3, 2018 at 1:42 PM, Zhexuan Gong wrote:
> It could be the macOS version then. I'm using the latest macOS 10.13.3.
> There must be something different with the 2.3.0rc2, because 2.2.3 works
> perfectly.
>
I recall there being some other issues with 10.12 (which I'll test tonight;
head
It could be the macOS version then. I'm using the latest macOS 10.13.3.
There must be something different with the 2.3.0rc2, because 2.2.3 works
perfectly.
On Sat, Feb 3, 2018 at 12:31 PM, Joel Kulesza wrote:
> On Sat, Feb 3, 2018 at 11:51 AM, Zhexuan Gong
> wrote:
>
>> Hi Scott,
>>
>> Yes plea
On Sat, Feb 03, 2018 at 08:08:03PM +, Joel Kulesza wrote:
> I don't recall having done so and don't see any QT variables set:
>
> 9997 jkulesza@tempest[~]> env | grep QT
> 9998 jkulesza@tempest[~]>
OK thanks for checking.
Scott
signature.asc
Description: PGP signature
On Sat, Feb 3, 2018 at 12:39 PM, Scott Kostyshak wrote:
>
> Does anyone have suggestions for especific environment variables that
> Zhexuan could test to see if it fixes things? e.g., could the
> environment variables QT_AUTO_SCREEN_SCALE_FACTOR, QT_SCALE_FACTOR, and
> QT_SCREEN_SCALE_FACTORS be
On Sat, Feb 03, 2018 at 07:31:15PM +, Joel Kulesza wrote:
> On Sat, Feb 3, 2018 at 11:51 AM, Zhexuan Gong wrote:
>
> > Hi Scott,
> >
> > Yes please see attached for a minimum lyx file that produces the math font
> > issue, and two screenshots using Lyx 2.2.3 stable and 2.3.0rc2. The 2.2.3
> >
On Sat, Feb 03, 2018 at 06:12:38PM +, Zhexuan Gong wrote:
> Hi Scott,
>
> Thanks for your hard work and for asking me to test again! Unfortunately,
> the Lyx 2.3.0rc2 did not fix the blurry figures on Mac retina display and
> the disappearing tabs I mentioned in the other email either. What's
On Sat, Sep 30, 2017 at 05:38:59PM +, Scott Kostyshak wrote:
> On Wed, Sep 27, 2017 at 05:03:11PM +, Zhexuan Gong wrote:
> > Dear Scott,
> >
> > Thanks for the reply! Yes I'd be happy to test the 2.3.0rc1 to see if the
> > problem persists.
> >
> > Best,
> >
> > Zhexuan
>
>
> Dear Zhex
On 01/25/2018 02:18 AM, Scott Kostyshak wrote:
> On Wed, Dec 20, 2017 at 05:34:44PM +, Richard Heck wrote:
>
>> Presumably need to do something similar here. I'll have a look.
> Ping. I don't think this is urgent but since I think it's a regression
> it would be nice to make sure it's nothing t
On Wed, Dec 20, 2017 at 05:34:44PM +, Richard Heck wrote:
> Presumably need to do something similar here. I'll have a look.
Ping. I don't think this is urgent but since I think it's a regression
it would be nice to make sure it's nothing too bad.
Scott
signature.asc
Description: PGP signat
On 12/20/2017 01:43 AM, Scott Kostyshak wrote:
> On Sun, Oct 15, 2017 at 05:27:30PM +, Richard Heck wrote:
>> On 10/15/2017 12:52 PM, Scott Kostyshak wrote:
>>> On Sun, Oct 15, 2017 at 04:17:21PM +, Richard Heck wrote:
commit de2a58d986739bccb83615e8515d715ebf1b5821
Author: Richar
On Sun, Oct 15, 2017 at 05:27:30PM +, Richard Heck wrote:
> On 10/15/2017 12:52 PM, Scott Kostyshak wrote:
> > On Sun, Oct 15, 2017 at 04:17:21PM +, Richard Heck wrote:
> >> commit de2a58d986739bccb83615e8515d715ebf1b5821
> >> Author: Richard Heck
> >> Date: Thu Jun 30 14:53:19 2016 -040
On 10/15/2017 12:52 PM, Scott Kostyshak wrote:
> On Sun, Oct 15, 2017 at 04:17:21PM +, Richard Heck wrote:
>> commit de2a58d986739bccb83615e8515d715ebf1b5821
>> Author: Richard Heck
>> Date: Thu Jun 30 14:53:19 2016 -0400
>>
>> Fix bug #8782.
>>
>> We need to invalidate the BibT
On Sun, Oct 15, 2017 at 04:17:21PM +, Richard Heck wrote:
> commit de2a58d986739bccb83615e8515d715ebf1b5821
> Author: Richard Heck
> Date: Thu Jun 30 14:53:19 2016 -0400
>
> Fix bug #8782.
>
> We need to invalidate the BibTeX cache when undoing or redoing. I do
> not like h
about this topic, so my view is: It's fine for
2.2.x when all of the people contributing to this thread are happy with it.
I can confirm that, if I force clang++ as compiler, LyX 2.2.x happily
compiles with Qt4. Therefore, I propose to do nothing.
JMarc
On 10/04/2017 05:37 PM, Jean-Marc Lasgouttes wrote:
> Le 04/10/17 à 20:09, Enrico Forestieri a écrit :
>> Sorry. I didn't notice that you were talking about 2.2.x. Yes, you are
>> probably right.
>>
>> Richard, is the attached patch Ok?
>
> Actually, the
Le 04/10/17 à 20:09, Enrico Forestieri a écrit :
Sorry. I didn't notice that you were talking about 2.2.x. Yes, you are
probably right.
Richard, is the attached patch Ok?
Actually, the patch does not change my situation. It seems that this
ancient gcc does not know about __thread.
Ho
ms that the nice ifdef that try to define thread-local types are not
>>>>> correct for this old os version.
>>>>
>>>> I would be surprised if this is true. The code would be miscompiled in
>>>> several other places, then.
>>>>
>>&g
os version.
> >>
> >> I would be surprised if this is true. The code would be miscompiled in
> >> several other places, then.
> >>
> >> The other possibility is that the error is real, while the info at
> >> http://forum.dlang.org
ces, then.
>>
>> The other possibility is that the error is real, while the info at
>> http://forum.dlang.org/post/mailman.3439.1452269142.22025.digitalmars-d-b...@puremagic.com
>> is wrong.
>
> Sorry. I didn't notice that you were talking about 2.2.x. Yes, you are
&g
mailman.3439.1452269142.22025.digitalmars-d-b...@puremagic.com
> is wrong.
Sorry. I didn't notice that you were talking about 2.2.x. Yes, you are
probably right.
Richard, is the attached patch Ok?
--
Enrico
diff --git a/src/Paragraph.cpp b/src/Paragraph.cpp
index 48d0e1737f..4ced96ff0f
On Tue, Oct 03, 2017 at 10:19:52PM +0200, Jean-Marc Lasgouttes wrote:
> I get:
>
> ../../stable/src/Paragraph.cpp: In member function ‘void
> lyx::Paragraph::latex(const lyx::BufferParams&, const lyx::Font&,
> lyx::otexstream&, const lyx::OutputParams&, int, int, bool) const’:
> ../../stable/src/P
I get:
../../stable/src/Paragraph.cpp: In member function ‘void
lyx::Paragraph::latex(const lyx::BufferParams&, const lyx::Font&,
lyx::otexstream&, const lyx::OutputParams&, int, int, bool) const’:
../../stable/src/Paragraph.cpp:2378: error: thread-local storage not
supported for this target
On Wed, Sep 27, 2017 at 05:03:11PM +, Zhexuan Gong wrote:
> Dear Scott,
>
> Thanks for the reply! Yes I'd be happy to test the 2.3.0rc1 to see if the
> problem persists.
>
> Best,
>
> Zhexuan
Dear Zhexuan,
Great, thanks for being willing to test! You can subscribe to
lyx-announce [1] if y
Dear Scott,
Thanks for the reply! Yes I'd be happy to test the 2.3.0rc1 to see if the
problem persists.
Best,
Zhexuan
On Wed, Sep 27, 2017 at 12:44 PM, Scott Kostyshak wrote:
> On Mon, Sep 25, 2017 at 06:21:20PM +, Zhexuan Gong wrote:
> > Dear Lyx developers,
> >
> > It looks like this
On Mon, Sep 25, 2017 at 06:21:20PM +, Zhexuan Gong wrote:
> Dear Lyx developers,
>
> It looks like this problem is still not fixed in the latest Lyx 2.2.3 Mac
> version. Has anyone been working on this?
>
> Thanks a lot!
>
> Zhexuan
Dear Zhexuan,
Thank you for your persistence! I think tha
retina display in Lyx 2.2 Mac
To: lyx-us...@lists.lyx.org
Dear Lyx developers,
I've just installed the official release of Lyx 2.2 Mac version. Thanks a
lot for your team's hard work! It's really awesome and the text in the
workspace is super sharp right now. However, the display of i
Le 05/07/2017 à 10:14, Jean-Pierre Chrétien a écrit :
If I follow your usual way, I should now copy these changes in the French,
German, Japanese and Spanish docs.
As the subject says, I guess I should first load the foreign 2.2.x doc files in
2.3.0dev and push them in master as 2.3 doc
Le 05/07/2017 à 07:46, Scott Kostyshak a écrit :
On Wed, Jul 05, 2017 at 01:50:19AM +0200, Uwe Stöhr wrote:
The translations can be done. I stored all changes I made at the usual
changelog files in the docs folder.
Thanks, Uwe! I sent the email for translations and asked them to finish
withi
Le 05/07/2017 à 09:08, Uwe Stöhr a écrit :
Hi Scott,
I try to find time for Lyx on Thursday evening. I totally lost contact to LyX,
sorry.
Uwe, if you are overbooked, I said I could take care until you find time to come
back to LyX.
Currently I've made a recollection of what is changed in
Hi Scott,
I try to find time for Lyx on Thursday evening. I totally lost contact to LyX,
sorry.
Regards Uwe
Original Message
From: Scott Kostyshak
Sent: Mittwoch, 5. Juli 2017 07:46
To: Uwe Stöhr
Cc: lyx-devel@lists.lyx.org; Jean-Pierre Chrétien
Subject: Re: Copying translations from 2.2.x
On Wed, Jul 05, 2017 at 01:50:19AM +0200, Uwe Stöhr wrote:
> The translations can be done. I stored all changes I made at the usual
> changelog files in the docs folder.
Thanks, Uwe! I sent the email for translations and asked them to finish
within two weeks.
Scott
signature.asc
Description:
The translations can be done. I stored all changes I made at the usual
changelog files in the docs folder.
Original Message
From: Scott Kostyshak
Sent: Mittwoch, 5. Juli 2017 00:04
To: lyx-devel@lists.lyx.org; Uwe Stöhr
Cc: Jean-Pierre Chrétien
Subject: Re: Copying translations from 2.2.x
On Fri, Jun 30, 2017 at 11:15:29PM -0400, Scott Kostyshak wrote:
> Uwe, I am going to send an email to the translators. My big question to
> you (or anyone else) is: am I supposed to wait for the docs to be
> prepared before sending the email so that the translators can work on
> translating the d
! This is very helpful.
> Here is what I understand to be done:
> * for the English documentation
> - check if the recent 2.2.x changes have been ported to master (from the
> master Changelog files, I understand that this has been done for
> Customization, EmbeddedObj
On Fri, Jun 30, 2017 at 01:24:52AM +0200, Uwe Stöhr wrote:
> El 25.06.2017 a las 22:52, Scott Kostyshak escribió:
>
> > I just wanted to make sure you saw my above questions.
>
> Hi Scott,
>
> I was too busy to follow LyX. I won't have time to take care for the docs
> for LyX 2.3. So I hereby re
ation
- check if the recent 2.2.x changes have been ported to master (from the
master Changelog files, I understand that this has been done for Customization,
EmbeddedObjects, Math and UserGuide);
- check what is new in the 2.3 docs by parsing the change tracking markers,
and report it
El 25.06.2017 a las 22:52, Scott Kostyshak escribió:
I just wanted to make sure you saw my above questions.
Hi Scott,
I was too busy to follow LyX. I won't have time to take care for the
docs for LyX 2.3. So I hereby resign as docs maintainer for LyX 2.3.
When I find time I will work on the
On Sat, Jun 10, 2017 at 01:27:02PM -0400, Scott Kostyshak wrote:
> On Sat, Jun 10, 2017 at 10:29:04AM +0200, Uwe Stöhr wrote:
> > Hi Scott, I am still away for another week. I already transferred the po
> > files from 2.2.x to master for all active translations .
>
> Great,
so as not to lay a trap for the developers who are going to come
after me.
"to maintain the code after me" (avoiding any unintentional double
meaning due to my uncolloquial English).
Le 08/06/2017 à 26:72, Enrico Forestieri a écrit :
> On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
>
>> Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
>>> commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
>>> Author: Enrico Forestieri
>>> Date: Mon Jun 5 23:14:48 2017 +0200
>>>
On Tue, Jun 20, 2017 at 02:45:19AM +0200, Guillaume MM wrote:
> Le 08/06/2017 à 02:07, Enrico Forestieri a écrit :
> > On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
> >
> > > Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
> > > > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
On Tue, Jun 20, 2017 at 02:45:19AM +0200, Guillaume MM wrote:
> Le 08/06/2017 à 02:07, Enrico Forestieri a écrit :
> > On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
> >
> > > Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
> > > > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
Le 08/06/2017 à 02:07, Enrico Forestieri a écrit :
On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
Author: Enrico Forestieri
Date: Mon Jun 5 23:14:48 2017 +0200
Fix bugs #9
Kornel Benko wrote:
> So what is Uwe doing when he is re-merging? Probably calling
> development/tools/mergepo.py.
No. The workhose for remerging translations from the source code is
po/lyx_pot.py. mergepo.py is only for merging between two branches without
ptoducing huge nonsense diffs.
> I a
Am Sonntag, 11. Juni 2017 um 08:55:11, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Am Samstag, 10. Juni 2017 um 10:41:43, schrieb Georg Baum
> >>
> >> I would suggest to use git correctly instead of fixing broken line ends
> >> again and again, producing huge nonsense diffs. We had this disc
Kornel Benko wrote:
> Am Samstag, 10. Juni 2017 um 10:41:43, schrieb Georg Baum
>>
>> I would suggest to use git correctly instead of fixing broken line ends
>> again and again, producing huge nonsense diffs. We had this discussion
>> several times in the past.
>>
>
> Maybe a problem in merging
Which translation updates do you expect? It seems that they are pretty much
> in sync.
I just expected that there was something that I or someone else had to
do. I didn't know it had already been done.
> I get the attached diff when running
>
> python -tt development/tools/mergep
On Sat, Jun 10, 2017 at 10:29:04AM +0200, Uwe Stöhr wrote:
> Hi Scott, I am still away for another week. I already transferred the po
> files from 2.2.x to master for all active translations .
Great, thank you!
> So please don't touch the po files in master.
OK.
> The tr
Am Samstag, 10. Juni 2017 um 10:41:43, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Am Sonntag, 4. Juni 2017 um 10:33:02, schrieb Scott Kostyshak
> >
> >> On Sun, Jun 04, 2017 at 12:17:27PM +0200, Kornel Benko wrote:
> >>
> >> > > Unless someone has a different idea, I will replace the Windo
Kornel Benko wrote:
> Am Sonntag, 4. Juni 2017 um 10:33:02, schrieb Scott Kostyshak
>
>> On Sun, Jun 04, 2017 at 12:17:27PM +0200, Kornel Benko wrote:
>>
>> > > Unless someone has a different idea, I will replace the Windows
>> > > linebreaks with non-Windows linebreaks, update the strings on ma
ain.
>
> After Kornel's fixes to the Windows linebreaks, I tried mergepo.py again
> but it did not update any translations.
>
> Any other ideas?
Which translation updates do you expect? It seems that they are pretty much
in sync. I get the attached diff when running
python
Hi Scott, I am still away for another week. I already transferred the po files
from 2.2.x to master for all active translations . So please don't touch the po
files in master. The translators will be informed that they only need to
translate the giles in master for LyX 2.3.
Regard
On Sat, Jun 03, 2017 at 08:07:39PM -0400, Scott Kostyshak wrote:
> On Mon, May 29, 2017 at 11:09:55PM -0400, Scott Kostyshak wrote:
> > Uwe,
> >
> > Do you have time to copy the translations from 2.2.x to master? From
> > what I understand, you've done this in t
On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
> Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
> > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
> > Author: Enrico Forestieri
> > Date: Mon Jun 5 23:14:48 2017 +0200
> >
> > Fix bugs #9598 and #10650
> > ---
>
> > +//
Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
Author: Enrico Forestieri
Date: Mon Jun 5 23:14:48 2017 +0200
Fix bugs #9598 and #10650
---
+// gcc < 4.8.0 and msvc < 2015 do not support C++11 thread_local
+#if defined(__GNUC__) && ((_
n that again after
> merging translations from 2.2.x.
>
> Scott
OK.
Kornel
signature.asc
Description: This is a digitally signed message part.
On Wed, Jun 07, 2017 at 10:20:58AM +0200, Kornel Benko wrote:
> With 'make layouttranslations1' I get this change to lib/layouttranslations
I think you can push that. But we will have to run that again after
merging translations from 2.2.x.
Scott
Am Dienstag, 6. Juni 2017 um 15:53:13, schrieb Scott Kostyshak
> On Sat, Jun 03, 2017 at 08:07:39PM -0400, Scott Kostyshak wrote:
>
> > Unless someone has a different idea, I will replace the Windows
> > linebreaks with non-Windows linebreaks, update the strings on master,
> > and try the mergepo
On Sat, Jun 03, 2017 at 08:07:39PM -0400, Scott Kostyshak wrote:
> Unless someone has a different idea, I will replace the Windows
> linebreaks with non-Windows linebreaks, update the strings on master,
> and try the mergepo.py call above again.
After Kornel's fixes to the Windows linebreaks, I t
Am Sonntag, 4. Juni 2017 um 10:33:02, schrieb Scott Kostyshak
> On Sun, Jun 04, 2017 at 12:17:27PM +0200, Kornel Benko wrote:
>
> > > Unless someone has a different idea, I will replace the Windows
> > > linebreaks with non-Windows linebreaks, update the strings on master,
> > > and try the merge
On Sun, Jun 04, 2017 at 12:17:27PM +0200, Kornel Benko wrote:
> > Unless someone has a different idea, I will replace the Windows
> > linebreaks with non-Windows linebreaks, update the strings on master,
> > and try the mergepo.py call above again.
>
> I made a perl-script for this purpose (creat
Am Samstag, 3. Juni 2017 um 20:07:39, schrieb Scott Kostyshak
> On Mon, May 29, 2017 at 11:09:55PM -0400, Scott Kostyshak wrote:
> > Uwe,
> >
> > Do you have time to copy the translations from 2.2.x to master? From
> > what I understand, you've done this in the pa
1 - 100 of 804 matches
Mail list logo
