On Sat, Jun 15, 2024 at 10:06:55AM +0200, Kornel Benko wrote:
> I had the impression that 2.4.1-devel branch is dead. Should this not go to
> 2.4.x branch
> instead?
Oops, was on a wrong branch indeed. P
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-
Am Fri, 14 Jun 2024 20:18:42 +
schrieb Pavel Sanda :
> commit b8a22a3667b20aee663ff897e1d24761dc9e1f30
> Author: Richard Kimberly Heck
> Date: Tue Apr 2 12:46:36 2024 -0400
>
> Update doc info for quote-insert
> ---
> src/LyXAction.cpp | 4 +++-
> 1 file cha
On Wed, Jan 04, 2023 at 10:06:13PM +0100, Pavel Sanda wrote:
> On Fri, Dec 30, 2022 at 09:27:32AM +0100, Jürgen Spitzmüller wrote:
> > Am Donnerstag, dem 29.12.2022 um 15:25 -0500 schrieb Scott Kostyshak:
> > > Sounds good. I can do that. Should I do that now or wait (i.e., would
> > > this change
On Fri, Dec 30, 2022 at 09:27:32AM +0100, Jürgen Spitzmüller wrote:
> Am Donnerstag, dem 29.12.2022 um 15:25 -0500 schrieb Scott Kostyshak:
> > Sounds good. I can do that. Should I do that now or wait (i.e., would
> > this change disrupt the ongoing work)?
>
> It's probably better to wait until Jo
On Fri, Dec 30, 2022 at 10:21:31AM +0100, Kornel Benko wrote:
> Am Fri, 30 Dec 2022 09:27:32 +0100
> schrieb "Jürgen Spitzmüller" :
>
> > Am Donnerstag, dem 29.12.2022 um 15:25 -0500 schrieb Scott Kostyshak:
> > > Sounds good. I can do that. Should I do that now or wait (i.e., would
> > > this cha
Am Fri, 30 Dec 2022 09:27:32 +0100
schrieb "Jürgen Spitzmüller" :
> Am Donnerstag, dem 29.12.2022 um 15:25 -0500 schrieb Scott Kostyshak:
> > Sounds good. I can do that. Should I do that now or wait (i.e., would
> > this change disrupt the ongoing work)?
>
> It's probably better to wait until J
Am Donnerstag, dem 29.12.2022 um 15:25 -0500 schrieb Scott Kostyshak:
> Sounds good. I can do that. Should I do that now or wait (i.e., would
> this change disrupt the ongoing work)?
It's probably better to wait until John is done.
--
Jürgen
signature.asc
Description: This is a digitally signe
On Tue, Dec 27, 2022 at 10:54:54AM +0100, Jürgen Spitzmüller wrote:
> Am Montag, dem 26.12.2022 um 16:40 -0500 schrieb Scott Kostyshak:
> > By the way, does Additional.lyx compile for you? I get language
> > errors now. I think a language switch is done inside an argument or
> > something like that
Am Montag, dem 26.12.2022 um 16:40 -0500 schrieb Scott Kostyshak:
> By the way, does Additional.lyx compile for you? I get language
> errors now. I think a language switch is done inside an argument or
> something like that.
There are currently many "\lang american" and "\lang british" switches
in
On Mon, Dec 26, 2022 at 04:50:09PM +0100, Pavel Sanda wrote:
> commit 90dab5d1e9a67f4b263c2c4f92c9d94e43a63a82
> Author: Pavel Sanda
> Date: Mon Dec 26 17:46:55 2022 +0100
>
> Revert doc update for Additional.lyx so maitenance work can continue.
> ---
By the way, d
On Wed, 23 Mar 2022 at 22:54, José Abílio Matos wrote:
> On Wednesday, 23 March 2022 20.12.23 WET Thibaut Cuvelier wrote:
>
> > XHTML 1 dates back from 2001... LyX generates XHTML 5, but the doctype
> is kept
>
> > from XHTML 1 for compatibility issues (some browsers completely change
> their
>
>
On Wednesday, 23 March 2022 20.12.23 WET Thibaut Cuvelier wrote:
> XHTML 1 dates back from 2001... LyX generates XHTML 5, but the doctype is
kept
> from XHTML 1 for compatibility issues (some browsers completely change their
> behaviour based on the doctype). The issue has been discussed on the ma
On Wed, 23 Mar 2022 at 20:02, Lorenzo Bertini
wrote:
> Il 23/03/22 19:03, Thibaut Cuvelier ha scritto:
> > On Wed, 23 Mar 2022 at 18:43, Lorenzo Bertini
> > mailto:lorenzobertin...@gmail.com>> wrote:
> >
> > Running a very simple LyXHTML doc (a section with
Il 23/03/22 19:03, Thibaut Cuvelier ha scritto:
On Wed, 23 Mar 2022 at 18:43, Lorenzo Bertini
mailto:lorenzobertin...@gmail.com>> wrote:
Running a very simple LyXHTML doc (a section with a few paragraphs)
against this validator https://validator.w3.org/check
<https://val
On Wed, 23 Mar 2022 at 18:43, Lorenzo Bertini
wrote:
> Running a very simple LyXHTML doc (a section with a few paragraphs)
> against this validator https://validator.w3.org/check reports some
> errors, I don't really know if we care or not:
>
> 1. value of attribute "di
Running a very simple LyXHTML doc (a section with a few paragraphs)
against this validator https://validator.w3.org/check reports some
errors, I don't really know if we care or not:
1. value of attribute "dir" cannot be "auto"; must be one of "ltr", "
On Fri, Feb 19, 2021 at 05:39:28PM +0100, Thibaut Cuvelier wrote:
> It should be fixed with 358e4ace560f4a6a3a8435ac9959e38a23cb6d56. Does this
> patch also work on your side?
Works well! Thanks for the quick fix.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-dev
It should be fixed with 358e4ace560f4a6a3a8435ac9959e38a23cb6d56. Does this
patch also work on your side?
On Fri, 19 Feb 2021 at 15:58, Thibaut Cuvelier wrote:
> Hi Scott,
>
> Yes, I can reproduce. I am working on a fix.
>
> On Thu, 18 Feb 2021 at 06:18, Scott Kostyshak wrote:
>
>> Thibaut, can
Hi Scott,
Yes, I can reproduce. I am working on a fix.
On Thu, 18 Feb 2021 at 06:18, Scott Kostyshak wrote:
> Thibaut, can you reproduce?
>
> Scott
>
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Thibaut, can you reproduce?
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sat, Sep 05, 2020 at 08:09:54AM +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 03.09.2020, 11:20 -0400 schrieb Scott Kostyshak:
> > To reproduce:
> >
> > 1. Start a new document with master and save it.
> > 2. Copy that file to a new file (we will look at the diff).
> > 3. Open one of th
Am Donnerstag, den 03.09.2020, 11:20 -0400 schrieb Scott Kostyshak:
> To reproduce:
>
> 1. Start a new document with master and save it.
> 2. Copy that file to a new file (we will look at the diff).
> 3. Open one of the files, go to Document Settings, and check the box
>"Suppress default date
To reproduce:
1. Start a new document with master and save it.
2. Copy that file to a new file (we will look at the diff).
3. Open one of the files, go to Document Settings, and check the box
"Suppress default date on front page".
4. Press "Apply".
5. Uncheck "Suppress default date on front pag
On Fri, May 24, 2019 at 05:05:53PM -, Guenter Milde wrote:
> On 2019-05-24, Pavel Sanda wrote:
> > On Fri, May 24, 2019 at 03:55:43PM -, Guenter Milde wrote:
> >> Closing and re-opening the settings shows the "lineno" box ticked again.
>
> > Do you have up-to-date master? P
>
> LyX Versio
On 2019-05-24, Pavel Sanda wrote:
> On Fri, May 24, 2019 at 03:55:43PM -, Guenter Milde wrote:
>> Closing and re-opening the settings shows the "lineno" box ticked again.
> Do you have up-to-date master? P
LyX Version 2.4.0dev
(Friday, 24 May 2019)
Built from git commit hash 09e69f96
Günter
On Fri, May 24, 2019 at 03:55:43PM -, Guenter Milde wrote:
> Closing and re-opening the settings shows the "lineno" box ticked again.
Do you have up-to-date master? P
+0200
>> Introduce doc preference for line numbering.
Here, once line numbering is selected, it cannot be reverted (short of
manually editing the lyx file).
Unselecting works in the settings dialogue but the internal setting is not
changed nor saved. View-Code still shows the line
Am Freitag, den 24.05.2019, 17:19 +0200 schrieb Pavel Sanda:
> Yes, I bisected. When I delete two most right spacers in language
> pane
> the situation gets much better, but was not sure about your
> intentions.
The intention is to keep the combos at a reasonable size. I adapted the
size hint of t
On Fri, May 24, 2019 at 05:16:14PM +0200, Jürgen Spitzmüller wrote:
> Am Freitag, den 24.05.2019, 14:37 +0200 schrieb Pavel Sanda:
> > I'll have a look.
>
> Thanks.
>
> > BTW since 83a62a6d74d we have extremely wide document settings
> > dialog...
> > Was that intention?
>
> No. Are you sure thi
Am Freitag, den 24.05.2019, 14:37 +0200 schrieb Pavel Sanda:
> I'll have a look.
Thanks.
> BTW since 83a62a6d74d we have extremely wide document settings
> dialog...
> Was that intention?
No. Are you sure this commit is to blame?
Jürgen
signature.asc
Description: This is a digitally signed me
On Fri, May 24, 2019 at 10:11:54AM +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 23.05.2019, 15:24 +0200 schrieb Pavel Sanda:
> > commit 7f125f62d2cfeacdb820aee5ef39f86eb82db3ae
> > Author: Pavel Sanda
> > Date: Thu May 23 15:13:27 2019 +0200
> >
> >
Am Donnerstag, den 23.05.2019, 15:24 +0200 schrieb Pavel Sanda:
> commit 7f125f62d2cfeacdb820aee5ef39f86eb82db3ae
> Author: Pavel Sanda
> Date: Thu May 23 15:13:27 2019 +0200
>
> Introduce doc preference for line numbering.
GUI-wise, I'd suggest not to use a chec
On Tue, May 21, 2019 at 06:10:48PM +0200, Pavel Sanda wrote:
> Like the attached.
This is now in.
> It occurred to me that lineno might be used for referencing lines
> in the document as well (and clickable with hyperref), not sure how
> much work would it take to integrate with our label/crossre
On Mon, May 20, 2019 at 04:44:12PM +0200, Pavel Sanda wrote:
> Hi,
>
> I'm not heavy user of lineno package for numbering of the lines
> in the margin, but I regularly need it for submissions and always
> need to google again for preamble two-liner:
> \usepackage{lineno}
> \linenumbers
>
> What a
On Mon, May 20, 2019 at 08:58:19PM -, Guenter Milde wrote:
> On 2019-05-20, Pavel Sanda wrote:
> > Hi,
>
> > I'm not heavy user of lineno package for numbering of the lines
> > in the margin, but I regularly need it for submissions and always
> > need to google again for preamble two-liner:
>
On 2019-05-20, Pavel Sanda wrote:
> Hi,
> I'm not heavy user of lineno package for numbering of the lines
> in the margin, but I regularly need it for submissions and always
> need to google again for preamble two-liner:
> \usepackage{lineno}
> \linenumbers
> What about adding checkbox '[X] Numbe
Hi,
I'm not heavy user of lineno package for numbering of the lines
in the margin, but I regularly need it for submissions and always
need to google again for preamble two-liner:
\usepackage{lineno}
\linenumbers
What about adding checkbox '[X] Number lines', perhaps with field
for additional para
Am Montag, den 10.09.2018, 14:00 +0200 schrieb Kornel Benko:
> Thanks Jürgen. Using the listings-backup with
> # tlmgr restore listings 37534
> and your latest commit, the Arabic files are now compilable again.
and fixed upstream with new bidi release:
https://sourceforge.net/p/persian-tex-d
Am Montag, 10. September 2018 12:42:40 CEST schrieb Jürgen Spitzmüller
:
> Am Sonntag, den 09.09.2018, 11:37 +0200 schrieb Kornel Benko:
> > > Bisect leads to 2d4ac90f.
> > >
> > > Scott
> > >
> >
> > I got something different:
> > 652ca5f578c1
>
> There are two issues involved. One is a c
Am Sonntag, den 09.09.2018, 11:37 +0200 schrieb Kornel Benko:
> > Bisect leads to 2d4ac90f.
> >
> > Scott
> >
>
> I got something different:
> 652ca5f578c1
There are two issues involved. One is a consequence of 2d4ac90f. This
should be fixed now.
The other one is caused by the latest lis
Am Samstag, 8. September 2018 20:04:53 CEST schrieb Scott Kostyshak
:
> On Sat, Sep 08, 2018 at 06:51:09PM -0400, Scott Kostyshak wrote:
> > On Sat, Sep 08, 2018 at 04:29:38PM +0200, Kornel Benko wrote:
> > > I was unable to find the reason.
> >
> > I can reproduce. I can do a bisect if it would
On Sat, Sep 08, 2018 at 06:51:09PM -0400, Scott Kostyshak wrote:
> On Sat, Sep 08, 2018 at 04:29:38PM +0200, Kornel Benko wrote:
> > I was unable to find the reason.
>
> I can reproduce. I can do a bisect if it would help.
Bisect leads to 2d4ac90f.
Scott
signature.asc
Description: PGP signatur
On Sat, Sep 08, 2018 at 04:29:38PM +0200, Kornel Benko wrote:
> I was unable to find the reason.
I can reproduce. I can do a bisect if it would help.
Thanks for all of your help checking the tests, Kornel. I have been
ignoring them. I would like to get back in the habit of regularly
running the t
I was unable to find the reason.
Apart from 'Missing glyph', there are also some messages like
! Package Listings Error: direction textdirection unknown.
l.43 ...ror{Listings}{direction #1 unknown}\@ehc}}
...
Missing character: There is no
in font Scheherazade/OT:s
Am Mittwoch, 16. Mai 2018 00:10:34 CEST schrieb Scott Kostyshak
:
> On Wed, May 02, 2018 at 04:00:12PM +, Scott Kostyshak wrote:
> > On Wed, May 02, 2018 at 01:06:04PM +, Jean-Marc Lasgouttes wrote:
> > > Le 28/04/2018 à 00:06, Scott Kostyshak a écrit :
> > > > On Wed, Apr 25, 2018 at 06:4
On Wed, May 02, 2018 at 04:00:12PM +, Scott Kostyshak wrote:
> On Wed, May 02, 2018 at 01:06:04PM +, Jean-Marc Lasgouttes wrote:
> > Le 28/04/2018 à 00:06, Scott Kostyshak a écrit :
> > > On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
> > >
> > > > it is not 100% reproduc
Le 28/04/2018 à 00:06, Scott Kostyshak a écrit :
On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
it is not 100% reproducible for me. I wonder if valgrind might be useful
to try in this situation.
Attached is a valgrind log. Do the invalid reads provide any clues?
Does this
Le 29 avril 2018 05:31:46 GMT+02:00, Richard Kimberly Heck a
écrit :
>>There's some kind of race condition involved, then, it seems to me. But
>I think the general idea
>JMarc had must be right. It's just that we only get the unfortunate
>paint event sometimes.
>
>
I will take care of this one
On 04/28/2018 11:35 AM, Scott Kostyshak wrote:
> On Sat, Apr 28, 2018 at 01:58:41PM +, Richard Kimberly Heck wrote:
>> On 04/28/2018 07:58 AM, Jean-Marc Lasgouttes wrote:
>>> Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
I'm not good at reading these things, but I do see several
>
On Sat, Apr 28, 2018 at 01:58:41PM +, Richard Kimberly Heck wrote:
> On 04/28/2018 07:58 AM, Jean-Marc Lasgouttes wrote:
> > Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
> >> I'm not good at reading these things, but I do see several
> >> lyx::InsetInclude::~InsetInclude(), which
> >>
On 04/28/2018 07:58 AM, Jean-Marc Lasgouttes wrote:
> Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
>> I'm not good at reading these things, but I do see several
>> lyx::InsetInclude::~InsetInclude(), which
>> would presumably be the inset that's being replaced. So it might be some
>> kind
Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
I'm not good at reading these things, but I do see several
lyx::InsetInclude::~InsetInclude(), which
would presumably be the inset that's being replaced. So it might be some
kind of double delete
issue? Then again, a lot of the log seems to r
On 04/27/2018 06:06 PM, Scott Kostyshak wrote:
> On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
>
>> it is not 100% reproducible for me. I wonder if valgrind might be useful
>> to try in this situation.
> Attached is a valgrind log. Do the invalid reads provide any clues?
I'm not
On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
> it is not 100% reproducible for me. I wonder if valgrind might be useful
> to try in this situation.
Attached is a valgrind log. Do the invalid reads provide any clues?
Scott
==4977== Memcheck, a memory error detector
==4977== Co
On Tue, Apr 24, 2018 at 11:00:46PM +, Richard Kimberly Heck wrote:
> On 04/24/2018 01:10 AM, Scott Kostyshak wrote:
> > I can reproduce on master and on 2.3.x.
> >
> > To reproduce:
> >
> > 1. download the attached 3 documents and put them in the same directory.
> > 2. open master_copy_from.lyx
On 04/24/2018 01:10 AM, Scott Kostyshak wrote:
> I can reproduce on master and on 2.3.x.
>
> To reproduce:
>
> 1. download the attached 3 documents and put them in the same directory.
> 2. open master_copy_from.lyx in one LyX instance
> 3. in the dialog that comes up, click "cancel"
> 4. open maste
On 04/24/2018 01:10 AM, Scott Kostyshak wrote:
> I can reproduce on master and on 2.3.x.
>
> To reproduce:
>
> 1. download the attached 3 documents and put them in the same directory.
> 2. open master_copy_from.lyx in one LyX instance
> 3. in the dialog that comes up, click "cancel"
> 4. open maste
I can reproduce on master and on 2.3.x.
To reproduce:
1. download the attached 3 documents and put them in the same directory.
2. open master_copy_from.lyx in one LyX instance
3. in the dialog that comes up, click "cancel"
4. open master_copy_to.lyx in a *separate* LyX instance
5. highlight the c
On Wed, Feb 21, 2018 at 02:52:23PM +, Jean-Marc Lasgouttes wrote:
> Le 21/02/2018 à 15:46, Pavel Sanda a écrit :
> > Well, the requirements section remain as it was.
> > No one seemed to care about this section, so I though we'll make
> > updated to what will invitable happen to master in 3 yea
Jean-Marc Lasgouttes wrote:
> Well, this is a discussion that we can have. My problem is that ubuntu
> 14.04, which will still be supported for next master (I guess), only has QT
> 5.2. Is this working correctly by our standards?
Why not? They are not going to backport our releases and trying to
Le 21/02/2018 à 15:46, Pavel Sanda a écrit :
Well, the requirements section remain as it was.
No one seemed to care about this section, so I though we'll make
updated to what will invitable happen to master in 3 years...
But I can revert if you want.
Well, this is a discussion that we can have.
Jean-Marc Lasgouttes wrote:
> Le 21/02/2018 ?? 14:47, Pavel Sanda a écrit :
>> commit 8adba3896ce3fa0402ea719ce85140ef6cbdaa1a
>> Author: Pavel Sanda
>> Date: Wed Feb 21 14:47:03 2018 +0100
>> small doc glitches
>> ---
>> INSTALL |4 ++--
>>
El 21.10.2017 a las 11:29, Kornel Benko escribió:
OK also for 2.2.x Richard?
There are issues with this, see my recent post. With LyX 2.2.x we rely
on python 2.x and we don't have a problem. Therefore I opt to keep the
2.2.x branch as it is.
regards Uwe
Am Samstag, 21. Oktober 2017 um 11:21:24, schrieb Kornel Benko
> commit 72122beee885decb251b1634cf4ae3cab9487e17
> Author: Kornel Benko
> Date: Sat Oct 21 11:18:02 2017 +0200
>
> Cmake doc creations: Setting environment PYTHONIOENCODING
>
> 1. This sh
On Sun, Mar 12, 2017 at 11:23:33PM -0400, Scott Kostyshak wrote:
> > > Thanks for the feedback, Günter and Andrew. I propose two questions for
> > > going forward:
> > > (2) Which behavior should be changed?
> > I'm still looking for feedback on the above issue.
>
> If no one has feedback, I'll
On Sat, Jan 21, 2017 at 11:32:27PM -0500, Scott Kostyshak wrote:
> On Mon, Nov 21, 2016 at 09:34:40PM -0500, Scott Kostyshak wrote:
> > On Tue, Nov 22, 2016 at 09:07:35AM +1300, Andrew Parsloe wrote:
> > > On 21/11/2016 6:34 p.m., Scott Kostyshak wrote:
> >
> > > As an occasional user of branches,
On Sun, Feb 19, 2017 at 10:51:24PM +0100, Kornel Benko wrote:
> Am Sonntag, 19. Februar 2017 um 16:05:31, schrieb Scott Kostyshak
>
> > it_Customization.lyx with LuaTeX + system fonts now compiles for me
> > without error after updating TeX Live. Can anyone confirm? If so, we can
> > apply the at
Am Sonntag, 19. Februar 2017 um 16:05:31, schrieb Scott Kostyshak
> it_Customization.lyx with LuaTeX + system fonts now compiles for me
> without error after updating TeX Live. Can anyone confirm? If so, we can
> apply the attached patch.
I see the same. From my pov, apply.
Kornel
sign
..b02b0a8 100644
--- a/development/autotests/invertedTests
+++ b/development/autotests/invertedTests
@@ -257,7 +257,7 @@ export/doc/attic/eu_UserGuide_pdf[25].*
# Files in the attic with non-default output
# (i.e. could be ERT, package incompatiblity, ...)
-export/doc/attic/it_
On Mon, Nov 21, 2016 at 09:34:40PM -0500, Scott Kostyshak wrote:
> On Tue, Nov 22, 2016 at 09:07:35AM +1300, Andrew Parsloe wrote:
> > On 21/11/2016 6:34 p.m., Scott Kostyshak wrote:
>
> > As an occasional user of branches, when I deactivate a branch I expect the
> > state of insets in the branch
On Thu, Sep 22, 2016 at 03:26:32PM +0200, mn wrote:
> With LyX 2.2.1 I experience a strange behavior when trying to reuse old
> preamble-code in newly created documents.
>
> Steps to reproduce.
> Open a new document and then an old one,
> open document settings for the old doc
On 2017-01-11, Kornel Benko wrote:
> Am Montag, 9. Januar 2017 um 21:33:42, schrieb Günter Milde
>
>> The attached file works fine here with ucharclasses under XeTeX.
> Does not compile here because of missing font.
I installed this font via the Debian package "fonts-linex". It has a wide
rang
Am Montag, 9. Januar 2017 um 21:33:42, schrieb Günter Milde
> The attached file works fine here with ucharclasses under XeTeX.
>
Does not compile here because of missing font.
BUT, selecting a Korean font like UnBatang works. Even with empty preamble.
Kornel
signature.asc
Description:
>> Thanks.
>> > Now we have unwanted messages e.g. for the test
>> "export/doc/de/UserGuide_pdf4_texF".
>> > I think, this is unrelated to the last patches.
>> I did a bisect based on the pass/failure of "de/Additional_pdf4_texF"
>> and it
2017-01-11 17:12 GMT+01:00 Scott Kostyshak :
> On Wed, Jan 11, 2017 at 10:27:34AM +0100, Kornel Benko wrote:
>
> > Thanks Jürgen.
> > Committed my patch too.
>
> Thanks.
>
> > Now we have unwanted messages e.g. for the test
> "export/doc/de/UserGuide_pdf4
On Wed, Jan 11, 2017 at 10:27:34AM +0100, Kornel Benko wrote:
> Thanks Jürgen.
> Committed my patch too.
Thanks.
> Now we have unwanted messages e.g. for the test
> "export/doc/de/UserGuide_pdf4_texF".
> I think, this is unrelated to the last patches.
I did a bisect
t;
> > Please commit.
>
> OK. Done.
>
> Jürgen
>
> >
> > Günter
Thanks Jürgen.
Committed my patch too.
Now we have unwanted messages e.g. for the test
"export/doc/de/UserGuide_pdf4_texF".
I think, this is unrelated to the last patches.
LyX's au
Am Dienstag, den 10.01.2017, 20:40 + schrieb Guenter Milde:
> As Kornel provided a use case and I can see other possible uses for
> command-line export of documents, I withdraw my objection.
>
> Please commit.
OK. Done.
Jürgen
>
> Günter
>
signature.asc
Description: This is a digitally s
On Tue, Jan 10, 2017 at 08:40:00PM +, Guenter Milde wrote:
> On 2017-01-10, Jürgen Spitzmüller wrote:
>
> > [-- Type: text/plain, Encoding: quoted-printable --]
>
> > Am Dienstag, den 10.01.2017, 14:10 +0100 schrieb Kornel Benko:
> >> Jürgen, I have a patch ready to push which builds on top o
}
> \newfontfamily\defaultfont{Latin Modern Roman}
> \setTransitionsForCJK{\cjkfont{}}{\defaultfont{}}
>
>
> The attached file works fine here with ucharclasses under XeTeX.
>
> We can either add "cheating" preamble code with
> \@ifpackageloaded{fontspec}{
On 2017-01-10, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Dienstag, den 10.01.2017, 14:10 +0100 schrieb Kornel Benko:
>> Jürgen, I have a patch ready to push which builds on top of your
>> patch.
>> Please commit.
> I don't have the impression there is
Am Dienstag, den 10.01.2017, 14:10 +0100 schrieb Kornel Benko:
> Jürgen, I have a patch ready to push which builds on top of your
> patch.
> Please commit.
I don't have the impression there is general consensus on this.
Jürgen
>
> Kornel
signature.asc
Description: This is a digitally sig
Am Montag, 9. Januar 2017 um 16:33:45, schrieb Jürgen Spitzmüller
> Am Montag, den 09.01.2017, 10:15 -0500 schrieb Scott Kostyshak:
> > Let's first ask Kornel and Günter. Do you think we should turn this
> > option on by default for the tests? I don't know too much about this,
> > but it makes se
either add "cheating" preamble code with
\@ifpackageloaded{fontspec}{
...
}{}
or, with an enhancement ticket for a "font combi GUI", we can invert
export/doc/(|de/|es/|fr/)UserGuide_.*_systemF
in the
Sublabel: lyxbugs
# LyX bugs with a Trac number.
section and add a copy without CJK quotes to the autotests/export/latex/
samples.
Günter
CJK-quotes.lyx
Description: application/lyx
ld we just use a special label? Do you mind
> > doing the work?
>
> I will look into this.
>
Something like attached should work. Contents of the new file
"ignoreMissingGlyphTests" is
"export/doc/UserGuide_(dvi3|pdf4|pdf5)_systemF"
Kornel
diff --g
Am Montag, 9. Januar 2017 um 10:55:06, schrieb Scott Kostyshak
> On Mon, Jan 09, 2017 at 04:50:55PM +0100, Kornel Benko wrote:
>
> > I'd prefer to make the behaviour be document specific. Ignoring errors in
> > tests
> > does not feel right if used in general.
>
> Sounds good to me. Seems like
On Mon, Jan 09, 2017 at 04:50:55PM +0100, Kornel Benko wrote:
> I'd prefer to make the behaviour be document specific. Ignoring errors in
> tests
> does not feel right if used in general.
Sounds good to me. Seems like you and Jürgen agree on this. Kornel,
would it be difficult to incorporate thi
Am Montag, 9. Januar 2017 um 10:15:56, schrieb Scott Kostyshak
> On Mon, Jan 09, 2017 at 03:23:47PM +0100, Jürgen Spitzmüller wrote:
> > Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> > > On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > > > Am Sonntag, de
Am Montag, den 09.01.2017, 10:15 -0500 schrieb Scott Kostyshak:
> Let's first ask Kornel and Günter. Do you think we should turn this
> option on by default for the tests? I don't know too much about this,
> but it makes sense to me because it will help make the tests less
> sensitive to font choic
On Mon, Jan 09, 2017 at 03:23:47PM +0100, Jürgen Spitzmüller wrote:
> Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> > On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > > Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > > > Ignoring the
Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > > Ignoring the
> > > > missing glyphs warning strikes me a better alternative.
> > >
> >
On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > Ignoring the
> > > missing glyphs warning strikes me a better alternative.
> >
> > Perhaps. Does anyone volunteer to do this work?
>
> Please try the attach
Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > Ignoring the
> > missing glyphs warning strikes me a better alternative.
>
> Perhaps. Does anyone volunteer to do this work?
Please try the attached patch. The lyx option
--ignore-error-message missing_glyphs
does what you need
Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > I doubt you will find a free suitable font that is expected to be
> > installed on every user's box so that "a user just clicking "'use
> > non-
> > TeX fonts' and compiling will get the correct result."
>
> Until now we pretty m
On Wed, Dec 28, 2016 at 01:08:44PM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 28.12.2016, 11:41 + schrieb Guenter Milde:
> > I see. But as the tests should correspond to "normal" LyX behaviour,
> > we
> > should rather
> >
> > a) fix the document: we can set a custom non-tex font that
Am Mittwoch, den 28.12.2016, 11:41 + schrieb Guenter Milde:
> I see. But as the tests should correspond to "normal" LyX behaviour,
> we
> should rather
>
> a) fix the document: we can set a custom non-tex font that contains
> the
> missing characters. This way a user just clicking "use non-
On 2016-12-28, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 28.12.2016, 05:20 -0500 schrieb Scott Kostyshak:
>> > Note, though, that the missing glyphs message is a warning, not an
>> > error. We treat it as an error in the GUI, for good reas
On Wed, Dec 28, 2016 at 11:25:51AM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 28.12.2016, 05:20 -0500 schrieb Scott Kostyshak:
> > > Note, though, that the missing glyphs message is a warning, not an
> > > error. We treat it as an error in the GUI, for good reasons (since
> > it
> > > seve
Am Mittwoch, den 28.12.2016, 05:20 -0500 schrieb Scott Kostyshak:
> > Note, though, that the missing glyphs message is a warning, not an
> > error. We treat it as an error in the GUI, for good reasons (since
> it
> > severely can impact the output), but it does not stop LaTeX from
> > processing.
>
On Wed, Dec 28, 2016 at 11:13:59AM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 28.12.2016, 04:27 -0500 schrieb Scott Kostyshak:
> > I know nothing about this so I'll go along with whatever others
> > decide.
> > Günter might have an opinion.
> >
> > If we do implement the above we might wa
1 - 100 of 986 matches
Mail list logo
