Re: Note formatting bug?
On 2019-08-23 02:37, Daniel wrote: On 23/8/19 0:13, Richard Kimberly Heck wrote: On 8/22/19 2:47 PM, Daniel wrote: On 2019-08-22 19:42, Paul A. Rubin wrote: On 8/22/19 1:26 PM, Daniel wrote: Could someone please test the following with the attached document: 1. Open it 2. Select all text 3. Insert LyX note For me all text becomes formatted like a section heading. But bot so if I first create the note and then paste the content into it which seems strange. Daniel Same here (LyX 2.3.3). Paul Thanks for checking. The problem seems to be that the LyX note uses the "Plain Layout" (rather than "Standard" layout) which inherits the layout of the paragraph the inset is placed in. I am not sure there is currently a way to fix this. Note that the first line is section* and the second line is plain. As they were, except for the switch from standard. By default, insets do inherit the font from their parents. But you can change this: InsetLayout Note:Note Font Size normal Shape up Series medium EndFont End I would have expected InsetLayout Note:Note ResetsFont true End to work, but it does not seem to. Riki Thanks. Same here. Adding the first approach to my user dir. That actually solves an annoying behavior. Daniel Patching the note inset makes working with them so much nicer! Should I file a report? Daniel
Re: Note formatting bug?
On 23/8/19 1:38, Scott Kostyshak wrote: On Thu, Aug 22, 2019 at 06:15:00PM -0400, Richard Kimberly Heck wrote: This trick resets the outer layout to standard. But I think the issue was that notes have the big font if they're in headings. I've always found that wrong. I also have found it annoying. Scott I find it annoying too. Maybe the idea behind the original approach was that notes should give a preview of what its content looks like if the note was dissolved? At least for notes that have only one paragraph it has this effects. But this idea breaks down anyway if there are several plain paragraphs in the note. Daniel
Re: Note formatting bug?
On 23/8/19 0:13, Richard Kimberly Heck wrote: On 8/22/19 2:47 PM, Daniel wrote: On 2019-08-22 19:42, Paul A. Rubin wrote: On 8/22/19 1:26 PM, Daniel wrote: Could someone please test the following with the attached document: 1. Open it 2. Select all text 3. Insert LyX note For me all text becomes formatted like a section heading. But bot so if I first create the note and then paste the content into it which seems strange. Daniel Same here (LyX 2.3.3). Paul Thanks for checking. The problem seems to be that the LyX note uses the "Plain Layout" (rather than "Standard" layout) which inherits the layout of the paragraph the inset is placed in. I am not sure there is currently a way to fix this. Note that the first line is section* and the second line is plain. As they were, except for the switch from standard. By default, insets do inherit the font from their parents. But you can change this: InsetLayout Note:Note Font Size normal Shape up Series medium EndFont End I would have expected InsetLayout Note:Note ResetsFont true End to work, but it does not seem to. Riki Thanks. Same here. Adding the first approach to my user dir. That actually solves an annoying behavior. Daniel
Re: Note formatting bug?
On 8/22/19 7:38 PM, Scott Kostyshak wrote: > On Thu, Aug 22, 2019 at 06:15:00PM -0400, Richard Kimberly Heck wrote: > >> This trick resets the outer layout to standard. But I think the issue >> was that notes have the big font if they're in headings. I've always >> found that wrong. > I also have found it annoying. Why doesn't ResetsFont work here? Should it? Or does it do something else, say, indicate something about the LaTeX output? Riki
Re: Note formatting bug?
On Thu, Aug 22, 2019 at 06:15:00PM -0400, Richard Kimberly Heck wrote: > This trick resets the outer layout to standard. But I think the issue > was that notes have the big font if they're in headings. I've always > found that wrong. I also have found it annoying. Scott signature.asc Description: PGP signature
Re: Note formatting bug?
On 8/22/19 6:11 PM, Enrico Forestieri wrote: > On Thu, Aug 22, 2019 at 08:47:43PM +0200, Daniel wrote: >> On 2019-08-22 19:42, Paul A. Rubin wrote: >>> On 8/22/19 1:26 PM, Daniel wrote: Could someone please test the following with the attached document: 1. Open it 2. Select all text 3. Insert LyX note For me all text becomes formatted like a section heading. But bot so if I first create the note and then paste the content into it which seems strange. Daniel >>> Same here (LyX 2.3.3). >>> >>> Paul >>> >>> >> Thanks for checking. The problem seems to be that the LyX note uses the >> "Plain Layout" (rather than "Standard" layout) which inherits the layout of >> the paragraph the inset is placed in. I am not sure there is currently a way >> to fix this. > Insert an ampty ERT before the section. Put everything (including the ERT) > into a LyX note. Now remove the empty ERT. See attached, where the previous > three steps are illustrated. This trick resets the outer layout to standard. But I think the issue was that notes have the big font if they're in headings. I've always found that wrong. Riki
Re: Note formatting bug?
On 8/22/19 2:47 PM, Daniel wrote: > On 2019-08-22 19:42, Paul A. Rubin wrote: >> On 8/22/19 1:26 PM, Daniel wrote: >>> Could someone please test the following with the attached document: >>> 1. Open it >>> 2. Select all text >>> 3. Insert LyX note >>> >>> For me all text becomes formatted like a section heading. But bot so >>> if I first create the note and then paste the content into it which >>> seems strange. >>> >>> Daniel >> Same here (LyX 2.3.3). >> >> Paul >> >> > Thanks for checking. The problem seems to be that the LyX note uses > the "Plain Layout" (rather than "Standard" layout) which inherits the > layout of the paragraph the inset is placed in. I am not sure there is > currently a way to fix this. Note that the first line is section* and the second line is plain. As they were, except for the switch from standard. By default, insets do inherit the font from their parents. But you can change this: InsetLayout Note:Note Font Size normal Shape up Series medium EndFont End I would have expected InsetLayout Note:Note ResetsFont true End to work, but it does not seem to. Riki
Re: Note formatting bug?
On Thu, Aug 22, 2019 at 08:47:43PM +0200, Daniel wrote: > On 2019-08-22 19:42, Paul A. Rubin wrote: > > On 8/22/19 1:26 PM, Daniel wrote: > > > Could someone please test the following with the attached document: > > > 1. Open it > > > 2. Select all text > > > 3. Insert LyX note > > > > > > For me all text becomes formatted like a section heading. But bot so > > > if I first create the note and then paste the content into it which > > > seems strange. > > > > > > Daniel > > Same here (LyX 2.3.3). > > > > Paul > > > > > Thanks for checking. The problem seems to be that the LyX note uses the > "Plain Layout" (rather than "Standard" layout) which inherits the layout of > the paragraph the inset is placed in. I am not sure there is currently a way > to fix this. Insert an ampty ERT before the section. Put everything (including the ERT) into a LyX note. Now remove the empty ERT. See attached, where the previous three steps are illustrated. -- Enrico #LyX 2.3 created this file. For more info see http://www.lyx.org/ \lyxformat 544 \begin_document \begin_header \save_transient_properties true \origin unavailable \textclass article \use_default_options true \maintain_unincluded_children false \language english \language_package default \inputencoding auto \fontencoding global \font_roman "default" "default" \font_sans "default" "default" \font_typewriter "default" "default" \font_math "auto" "auto" \font_default_family default \use_non_tex_fonts false \font_sc false \font_osf false \font_sf_scale 100 100 \font_tt_scale 100 100 \use_microtype false \use_dash_ligatures true \graphics default \default_output_format default \output_sync 0 \bibtex_command default \index_command default \paperfontsize default \use_hyperref false \papersize default \use_geometry false \use_package amsmath 1 \use_package amssymb 1 \use_package cancel 1 \use_package esint 1 \use_package mathdots 1 \use_package mathtools 1 \use_package mhchem 1 \use_package stackrel 1 \use_package stmaryrd 1 \use_package undertilde 1 \cite_engine basic \cite_engine_type default \use_bibtopic false \use_indices false \paperorientation portrait \suppress_date false \justification true \use_refstyle 1 \use_minted 0 \index Index \shortcut idx \color #008000 \end_index \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \paragraph_indentation default \is_math_indent 0 \math_numbering_side default \quotes_style english \dynamic_quotes 0 \papercolumns 1 \papersides 1 \paperpagestyle default \tracking_changes false \output_changes false \html_math_output 0 \html_css_as_file 0 \html_be_strict false \end_header \begin_body \begin_layout Standard \begin_inset ERT status open \begin_layout Plain Layout \end_layout \end_inset \end_layout \begin_layout Section* Section \end_layout \begin_layout Standard Text \end_layout \begin_layout Standard \begin_inset Note Note status open \begin_layout Plain Layout \begin_inset ERT status open \begin_layout Plain Layout \end_layout \end_inset \end_layout \begin_layout Section* Section \end_layout \begin_layout Plain Layout Text \end_layout \end_inset \end_layout \begin_layout Standard \begin_inset Note Note status open \begin_layout Section* Section \end_layout \begin_layout Plain Layout Text \end_layout \end_inset \end_layout \end_body \end_document
Re: Some exports are currently failing on master
On Thu, Aug 22, 2019 at 05:17:18PM +0200, Jürgen Spitzmüller wrote: > Am Donnerstag, den 22.08.2019, 10:44 -0400 schrieb Scott Kostyshak: > > If I accept all changes and then do the above command, I get a > > different > > error: > > > > Paragraph ended before \xthreesent was complete. > > Try again, please. Works well! That fixes four tests. Thanks for the quick fix. There are four other failing tests, but I think two are because of the Polyglossia bug. The other two I think are tests that should be disabled since they have to do with exporting to very old formats. For example, if in master you export the Spanish Linguistics.lyx file to 1.6.x format and then open that exported file in master, it appears to be an incorrect .lyx file. I get a lot of warnings. The first one is the following: The module \begin_local_layout has been requested by this document but has not been found... Can you confirm that it is not worth the time to fix this round-trip-with-1.6.x issue and that we should disable those tests for this document? Thanks, Scott signature.asc Description: PGP signature
Re: Note formatting bug?
On 2019-08-22 19:42, Paul A. Rubin wrote: On 8/22/19 1:26 PM, Daniel wrote: Could someone please test the following with the attached document: 1. Open it 2. Select all text 3. Insert LyX note For me all text becomes formatted like a section heading. But bot so if I first create the note and then paste the content into it which seems strange. Daniel Same here (LyX 2.3.3). Paul Thanks for checking. The problem seems to be that the LyX note uses the "Plain Layout" (rather than "Standard" layout) which inherits the layout of the paragraph the inset is placed in. I am not sure there is currently a way to fix this. Daniel
Re: Note formatting bug?
On 8/22/19 1:26 PM, Daniel wrote: Could someone please test the following with the attached document: 1. Open it 2. Select all text 3. Insert LyX note For me all text becomes formatted like a section heading. But bot so if I first create the note and then paste the content into it which seems strange. Daniel Same here (LyX 2.3.3). Paul
Note formatting bug?
Could someone please test the following with the attached document: 1. Open it 2. Select all text 3. Insert LyX note For me all text becomes formatted like a section heading. But bot so if I first create the note and then paste the content into it which seems strange. Daniel #LyX 2.3 created this file. For more info see http://www.lyx.org/ \lyxformat 544 \begin_document \begin_header \save_transient_properties true \origin unavailable \textclass article \use_default_options true \maintain_unincluded_children false \language english \language_package default \inputencoding auto \fontencoding global \font_roman "default" "default" \font_sans "default" "default" \font_typewriter "default" "default" \font_math "auto" "auto" \font_default_family default \use_non_tex_fonts false \font_sc false \font_osf false \font_sf_scale 100 100 \font_tt_scale 100 100 \use_microtype false \use_dash_ligatures true \graphics default \default_output_format default \output_sync 0 \bibtex_command default \index_command default \paperfontsize default \use_hyperref false \papersize default \use_geometry false \use_package amsmath 1 \use_package amssymb 1 \use_package cancel 1 \use_package esint 1 \use_package mathdots 1 \use_package mathtools 1 \use_package mhchem 1 \use_package stackrel 1 \use_package stmaryrd 1 \use_package undertilde 1 \cite_engine basic \cite_engine_type default \use_bibtopic false \use_indices false \paperorientation portrait \suppress_date false \justification true \use_refstyle 1 \use_minted 0 \index Index \shortcut idx \color #008000 \end_index \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \paragraph_indentation default \is_math_indent 0 \math_numbering_side default \quotes_style english \dynamic_quotes 0 \papercolumns 1 \papersides 1 \paperpagestyle default \tracking_changes false \output_changes false \html_math_output 0 \html_css_as_file 0 \html_be_strict false \end_header \begin_body \begin_layout Section* Section \end_layout \begin_layout Standard Text \end_layout \end_body \end_document
Re: Missing lyxeditor.cmd?
On Thu, Aug 22, 2019 at 11:26 AM Richard Kimberly Heck wrote: > ... > >>> I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the > installation's bin directory appears to be missing lyxeditor.cmd, which is > of course crucial for inverse search. Is this an oversight? Or is it now in > some other directory? > >> We don't distribute this file. > > Huh. Unlike the macOS version, apparently. Why the difference with the > Windows distribution? > > I guess Stephan includes it. Maybe Uwe used to as well? I could include > it, too, I suppose, but I'm not actually a Windows user. We really do > need someone who is to take over Windows packaging. > I'm not really a Windows user either, but I got so irked with recent Mac laptops that I bought the (quite lovely) Dell in a fit of pique. I have to say that, once you get it set up right, LyX under Windows (and Linux) works rather better than it does under macOS. It loads *much *faster and just seems snappier all around; forward/inverse searching in particular is faster and more accurate. (Both startup and forward search on macOS have been glacial under the last few iterations, though they're improved in 2.3.3.) >> According to this page of the wiki: > >> > >> https://wiki.lyx.org/LyX/SyncTeX > >> > >> it's something you need to create yourself. > > The need to create lyxeditor.cmd is only mentioned in the section on > Okular for Windows. That one needs to create it oneself is as far as I can > see not mentioned in the section on configuring SumatraPDF, which is the > PDF viewer I'm using. Might the Keepers of the Wiki consider mentioning the > need to create this script right at the top of the section on SumatraPDF. > > The wiki is, well, a wiki, so anyone can edit it. Oh...right. :-) I'll try to gussy up the sections on LyX+SumatraPDF once the semester is comfortably under way. It could definitely use some work. -chris
Re: Missing lyxeditor.cmd?
On 2019-08-22 18:26, Richard Kimberly Heck wrote: On 8/22/19 12:06 PM, Christopher Menzel wrote: On 22 Aug 2019, at 10:39 AM, Richard Kimberly Heck wrote: On 8/22/19 10:48 AM, Chris Menzel wrote: Gentle LyX folk, I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the installation's bin directory appears to be missing lyxeditor.cmd, which is of course crucial for inverse search. Is this an oversight? Or is it now in some other directory? We don't distribute this file. Huh. Unlike the macOS version, apparently. Why the difference with the Windows distribution? I guess Stephan includes it. Maybe Uwe used to as well? I could include it, too, I suppose, but I'm not actually a Windows user. We really do need someone who is to take over Windows packaging. According to this page of the wiki: https://wiki.lyx.org/LyX/SyncTeX it's something you need to create yourself. The need to create lyxeditor.cmd is only mentioned in the section on Okular for Windows. That one needs to create it oneself is as far as I can see not mentioned in the section on configuring SumatraPDF, which is the PDF viewer I'm using. Might the Keepers of the Wiki consider mentioning the need to create this script right at the top of the section on SumatraPDF. The wiki is, well, a wiki, so anyone can edit it. Riki I still think that the SumatraPDF section in the wiki might just be rolled back. Everything seems to work fine for me without having the lyxeditor.cmd. Daniel
Re: Missing lyxeditor.cmd?
On 8/22/19 12:06 PM, Christopher Menzel wrote: > On 22 Aug 2019, at 10:39 AM, Richard Kimberly Heck wrote: >> On 8/22/19 10:48 AM, Chris Menzel wrote: >>> Gentle LyX folk, >>> >>> I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the installation's >>> bin directory appears to be missing lyxeditor.cmd, which is of course >>> crucial for inverse search. Is this an oversight? Or is it now in some >>> other directory? >> We don't distribute this file. > Huh. Unlike the macOS version, apparently. Why the difference with the > Windows distribution? I guess Stephan includes it. Maybe Uwe used to as well? I could include it, too, I suppose, but I'm not actually a Windows user. We really do need someone who is to take over Windows packaging. >> According to this page of the wiki: >> >> https://wiki.lyx.org/LyX/SyncTeX >> >> it's something you need to create yourself. > The need to create lyxeditor.cmd is only mentioned in the section on Okular > for Windows. That one needs to create it oneself is as far as I can see not > mentioned in the section on configuring SumatraPDF, which is the PDF viewer > I'm using. Might the Keepers of the Wiki consider mentioning the need to > create this script right at the top of the section on SumatraPDF. The wiki is, well, a wiki, so anyone can edit it. Riki
Re: Missing lyxeditor.cmd?
On 22 Aug 2019, at 10:39 AM, Richard Kimberly Heck wrote: > On 8/22/19 10:48 AM, Chris Menzel wrote: >> Gentle LyX folk, >> >> I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the installation's >> bin directory appears to be missing lyxeditor.cmd, which is of course >> crucial for inverse search. Is this an oversight? Or is it now in some other >> directory? > We don't distribute this file. Huh. Unlike the macOS version, apparently. Why the difference with the Windows distribution? > According to this page of the wiki: > > https://wiki.lyx.org/LyX/SyncTeX > > it's something you need to create yourself. The need to create lyxeditor.cmd is only mentioned in the section on Okular for Windows. That one needs to create it oneself is as far as I can see not mentioned in the section on configuring SumatraPDF, which is the PDF viewer I'm using. Might the Keepers of the Wiki consider mentioning the need to create this script right at the top of the section on SumatraPDF. Thanks for the info! -chris
Re: Missing lyxeditor.cmd?
On 8/22/19 10:48 AM, Chris Menzel wrote: > Gentle LyX folk, > > I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the > installation's bin directory appears to be missing lyxeditor.cmd, > which is of course crucial for inverse search. Is this an oversight? > Or is it now in some other directory? We don't distribute this file. According to this page of the wiki: https://wiki.lyx.org/LyX/SyncTeX it's something you need to create yourself. If you do a web search for "lyxeditor.cmd", you'll find some other info along the same lines. Riki
Re: Some exports are currently failing on master
Am Donnerstag, den 22.08.2019, 10:44 -0400 schrieb Scott Kostyshak: > If I accept all changes and then do the above command, I get a > different > error: > > Paragraph ended before \xthreesent was complete. Try again, please. Jürgen signature.asc Description: This is a digitally signed message part
Re: Missing lyxeditor.cmd?
On 22/8/19 16:48, Chris Menzel wrote: Gentle LyX folk, I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the installation's bin directory appears to be missing lyxeditor.cmd, which is of course crucial for inverse search. Is this an oversight? Or is it now in some other directory? Thanks. Chris Menzel I don't have lyxeditor.cmd in the bin directory (or apparently anywhere else) either. But reverse search works just fine. So it seems not true that this file is necessary for it to work. I have SumatraPDF set up according to https://wiki.lyx.org/LyX/SyncTeX#toc1. However, my inverse search command in the SumatraPDF Options is CMD /C (ECHO LYXCMD:revdvi:server-goto-file-row:%f %l) > \\.\pipe\lyxpipe.in Someone named KJO seems to have changed the command there in the summer. Not sure why. Maybe someone can restore it to a working version? Best, Daniel
Re: [LyX/2.3.x] Fix encoding issues with configuration under Python 3.
Am 22.08.2019 um 17:01 schrieb Jürgen Spitzmüller : > > Am Donnerstag, den 22.08.2019, 16:55 +0200 schrieb Stephan Witt: >> The status entry is missing. >> >> I don’t know where to add it… > > I'll do when I push the fix proposed at > https://www.lyx.org/trac/ticket/11642#comment:13 Wouldn’t it be a good idea to record the python version in configure.log? Stephan
Re: [LyX/2.3.x] Fix encoding issues with configuration under Python 3.
Am Donnerstag, den 22.08.2019, 16:55 +0200 schrieb Stephan Witt: > The status entry is missing. > > I don’t know where to add it… I'll do when I push the fix proposed at https://www.lyx.org/trac/ticket/11642#comment:13 Jürgen signature.asc Description: This is a digitally signed message part
Re: [LyX/2.3.x] Fix encoding issues with configuration under Python 3.
Am 21.08.2019 um 23:10 schrieb Günter Milde : > > commit d30da478d4f8ca861ee36ff77f6cc10c6f7bfd2b > Author: Günter Milde > Date: Wed Aug 21 23:20:27 2019 +0200 > >Fix encoding issues with configuration under Python 3. > >Backported from [b9cc642/lyxgit]. > --- > lib/configure.py | 262 -- > 1 files changed, 134 insertions(+), 128 deletions(-) The status entry is missing. I don’t know where to add it… Stephan
Missing lyxeditor.cmd?
Gentle LyX folk, I have installed LyX 2.3.3 on a Dell XPS laptop and, Lo, the installation's bin directory appears to be missing lyxeditor.cmd, which is of course crucial for inverse search. Is this an oversight? Or is it now in some other directory? Thanks. Chris Menzel
Re: Some exports are currently failing on master
On Thu, Aug 22, 2019 at 04:04:57PM +0200, Jürgen Spitzmüller wrote: > Am Donnerstag, den 22.08.2019, 09:38 -0400 schrieb Scott Kostyshak: > > Thanks, a TL update made the important tests pass. There are still > > some > > failures, but I'm not sure if they're worth fixing. Could you please > > let > > me know if the failure should be fixed or if I should disable the > > test > > corresponding to the following round-trip export: > > > > lyx -e lyx23x Linguistics.lyx && lyx -e pdf2 Linguistics.23.lyx > > > > I tested with the English version but I think it also fails for other > > versions. > > I don't think so. Good to know. > > The error I get is: > > > > Paragraph ended before \\digloss was complete. > > > > This might be necessary though, if e.g., we make ERT when exporting > > to > > 2.3.x, and then when converting it back to master's format we should > > not > > expect to take into account the ERT. If this is the case we should > > disable the test. > > This is due to the change tracking marks in that (English) document. > Strikes me too complicated to handle that in the reversion routine. Makes sense. > It > will go away once the changes have been accepted. If I accept all changes and then do the above command, I get a different error: Paragraph ended before \xthreesent was complete. Scott signature.asc Description: PGP signature
Re: Some exports are currently failing on master
Am Donnerstag, den 22.08.2019, 09:38 -0400 schrieb Scott Kostyshak: > Thanks, a TL update made the important tests pass. There are still > some > failures, but I'm not sure if they're worth fixing. Could you please > let > me know if the failure should be fixed or if I should disable the > test > corresponding to the following round-trip export: > > lyx -e lyx23x Linguistics.lyx && lyx -e pdf2 Linguistics.23.lyx > > I tested with the English version but I think it also fails for other > versions. I don't think so. > The error I get is: > > Paragraph ended before \\digloss was complete. > > This might be necessary though, if e.g., we make ERT when exporting > to > 2.3.x, and then when converting it back to master's format we should > not > expect to take into account the ERT. If this is the case we should > disable the test. This is due to the change tracking marks in that (English) document. Strikes me too complicated to handle that in the reversion routine. It will go away once the changes have been accepted. Jürgen signature.asc Description: This is a digitally signed message part
Re: Some exports are currently failing on master
On Tue, Aug 13, 2019 at 07:40:07AM +0200, Jürgen Spitzmüller wrote: > Am Montag, den 12.08.2019, 22:24 -0400 schrieb Scott Kostyshak: > > lib/examples/Modules/Linguistics.lyx > > You might need to check whether your covington version is up to date. > The linguistics module now supports some rather new features and > formats. Thanks, a TL update made the important tests pass. There are still some failures, but I'm not sure if they're worth fixing. Could you please let me know if the failure should be fixed or if I should disable the test corresponding to the following round-trip export: lyx -e lyx23x Linguistics.lyx && lyx -e pdf2 Linguistics.23.lyx I tested with the English version but I think it also fails for other versions. The error I get is: Paragraph ended before \\digloss was complete. This might be necessary though, if e.g., we make ERT when exporting to 2.3.x, and then when converting it back to master's format we should not expect to take into account the ERT. If this is the case we should disable the test. Scott signature.asc Description: PGP signature
Re: Again many failing export tests in lyx2.4
On Thu, Aug 22, 2019 at 09:39:18AM +0200, Jürgen Spitzmüller wrote: > Am Sonntag, den 26.05.2019, 16:25 +0200 schrieb Kornel Benko: > > This is the minimal example. User preamble is empty. Removing any > > part > > from the paragraph makes it compilable. Even setting the whole text > > to English does so. > > This compiles with the development version of polyglossia. That's great news! Thanks for checking. Scott signature.asc Description: PGP signature
Re: Again many failing export tests in lyx2.4
Am Sonntag, den 26.05.2019, 16:25 +0200 schrieb Kornel Benko: > This is the minimal example. User preamble is empty. Removing any > part > from the paragraph makes it compilable. Even setting the whole text > to English does so. This compiles with the development version of polyglossia. It's the bug Scott referred to. Jürgen signature.asc Description: This is a digitally signed message part
Re: Again many failing export tests in lyx2.4
Am Freitag, den 24.05.2019, 20:56 +0200 schrieb Kornel Benko: > LaTeX.cpp (719): Log line: Class scrbook Warning: \float@addtolists > detected! > LaTeX.cpp (719): Log line: (scrbook) Implementation of \ > float@addtolist became > LaTeX.cpp (719): Log line: (scrbook) deprecated in KOMA- > Script v3.01 2008/11/14 and > LaTeX.cpp (719): Log line: (scrbook) has been replaced > by several more flexible > LaTeX.cpp (719): Log line: (scrbook) features of package > `tocbasic`. > LaTeX.cpp (719): Log line: (scrbook) Since Version 3.12 > support for deprecated > LaTeX.cpp (719): Log line: (scrbook) \float@addtolist > interface has been > LaTeX.cpp (719): Log line: (scrbook) restricted to only > some of the KOMA-Script > LaTeX.cpp (719): Log line: (scrbook) features and been > removed from others. > LaTeX.cpp (719): Log line: (scrbook) Loading of package > `scrhack' may help to > LaTeX.cpp (719): Log line: (scrbook) avoid this warning, > if you are using a > LaTeX.cpp (719): Log line: (scrbook) a package that > still implements the > LaTeX.cpp (719): Log line: (scrbook) deprecated \ > float@addtolist interface . > > This is the same warning as for > export/doc/fr/Customization_pdf5_systemF. > We use deprecated (since 2008!) interface. That's listings using the command. Jürgen signature.asc Description: This is a digitally signed message part
Re: Again many failing export tests in lyx2.4
Am Mittwoch, den 21.08.2019, 22:31 -0400 schrieb Scott Kostyshak: > I'm getting something similar on a just-updated TL19 for the English > Customization manual with system fonts and pdf5. Googling leads to > here: > > https://github.com/reutenauer/polyglossia/issues/222 > > Maybe it will just take time for the fix to end up in TL. There's hope. Polyglossia maintenance got some live again in recent weeks, and many long-standing bugs have already been fixed (this one included). Jürgen signature.asc Description: This is a digitally signed message part
