Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 2/12/24 03:23, Léo de Souza wrote: On 10/02/2024 01:56, Richard Kimberly Heck wrote: Should be fixed for RC3, at 91bd457a. Riki I confirm that this is fixed in RC3. Thanks a lot. Thanks! Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org

Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 10/02/2024 01:56, Richard Kimberly Heck wrote: > Should be fixed for RC3, at 91bd457a. > > Riki I confirm that this is fixed in RC3. Thanks a lot. Léo -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX master] Fix display of counters for included listings.

On 2/10/24 22:34, Jürgen Spitzmüller wrote: Am Samstag, dem 10.02.2024 um 12:17 -0500 schrieb Richard Kimberly Heck: Oh, shoot. Should I revert it? Or notify people there is one new string? I'd go for the latter. I think an untranslated string is better than a wrong one. Done. Riki --

Re: [LyX master] Fix display of counters for included listings.

Am Samstag, dem 10.02.2024 um 12:17 -0500 schrieb Richard Kimberly Heck: > Oh, shoot. Should I revert it? Or notify people there is one new > string? I'd go for the latter. I think an untranslated string is better than a wrong one. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org

Re: [LyX master] Fix display of counters for included listings.

On 2/10/24 18:21, Pavel Sanda wrote: On Sat, Feb 10, 2024 at 12:17:57PM -0500, Richard Kimberly Heck wrote: On 2/10/24 03:45, Jürgen Spitzmüller wrote: Am Samstag, dem 10.02.2024 um 00:55 + schrieb Richard Kimberly Heck: The branch, master, has been updated. You are aware that this broke

Re: [LyX master] Fix display of counters for included listings.

On Sat, Feb 10, 2024 at 12:17:57PM -0500, Richard Kimberly Heck wrote: > On 2/10/24 03:45, Jürgen Spitzmüller wrote: > >Am Samstag, dem 10.02.2024 um 00:55 + schrieb Richard Kimberly > >Heck: > >>The branch, master, has been updated. > >You are aware that this broke the string freeze, right?

Re: [LyX master] Fix display of counters for included listings.

On 2/10/24 03:45, Jürgen Spitzmüller wrote: Am Samstag, dem 10.02.2024 um 00:55 + schrieb Richard Kimberly Heck: The branch, master, has been updated. You are aware that this broke the string freeze, right? So translators should be informed to update once more before the final release.

Re: [LyX master] Fix display of counters for included listings.

gt; - Log --- > -- > > commit 91bd457a674579e1bc9e61aab19c272cd0d342dd > Author: Richard Kimberly Heck > Date:   Fri Feb 9 19:53:55 2024 -0500 > >     Fix display of counters for included listings. > > diff --git a/lib/layouts/stdcounters

Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 2/7/24 11:57, Richard Kimberly Heck wrote: On 2/7/24 04:41, Léo de Souza wrote: Hello, I would like to report that LyX doesn't show the correct reference in the work area for included listings when the option to do so is active. Environment: I compiled LyX 2.4.0~RC2 on Ubuntu 22.04

Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 2/7/24 04:41, Léo de Souza wrote: Hello, I would like to report that LyX doesn't show the correct reference in the work area for included listings when the option to do so is active. Environment: I compiled LyX 2.4.0~RC2 on Ubuntu 22.04 with Qt6 enabled. Steps to reproduce: 1. Create

Bug report: "Format cross-references in the work area" is incorrect for included listings

Hello, I would like to report that LyX doesn't show the correct reference in the work area for included listings when the option to do so is active. Environment: I compiled LyX 2.4.0~RC2 on Ubuntu 22.04 with Qt6 enabled. Steps to reproduce: 1. Create a new document: File > New 2. O

Re: Warnings when using Listings in a RTL document

Am Sonntag, dem 02.04.2023 um 13:21 +0200 schrieb Jürgen Spitzmüller: > This needs some effort. For the time being, I think we will be better > off with this rather harmless info message. Possible approach attached. -- Jürgen diff --git a/src/Paragraph.cpp b/src/Paragraph.cpp index

Re: Warnings when using Listings in a RTL document

couple of issues: * It should be the LTR environment, not RTL, right? * I don't like the hardcoding of insets. Basically, this is needed will all "display" insets, right? And it will break with "inline" listings (\lstinline), which shouldn't go on an own line I in order to properl

Re: Warnings when using Listings in a RTL document

t(BufferParams const & bparams, // ERT is an exception, it should be output with no // decorations at all && inset->lyxCode() != ERT_CODE) { - if (runparams.use_polyglossia) - // (lua)bidi - os << "\\LRE{"; + if (runparams.use_polyglossia) { + // (

Re: Warnings when using Listings in a RTL document

rams.use_polyglossia) { // (lua)bidi - os << "\\LRE{"; + if (inset->getLayout().name() == "Listings" + || inset->getLayout().name() == "MintedListings") +os << "\n\\begin{RTL}"; + else +os << "\\LRE{&q

Re: Warnings when using Listings in a RTL document

src/Paragraph.cpp @@ -1101,9 +1101,14 @@ void Paragraph::Private::latexInset(BufferParams const & bparams, // ERT is an exception, it should be output with no // decorations at all && inset->lyxCode() != ERT_CODE) { - if (runparams.use_polyglossia) + if (runparams.

Re: Warnings when using Listings in a RTL document

On Wed, Mar 22, 2023 at 01:13:27PM +0100, Jürgen Spitzmüller wrote: > Am Mittwoch, dem 22.03.2023 um 12:54 +0200 schrieb Udicoudco: > > I think in the case of where forceLTR insets will have multiple > > paragraphs, it is better to use > > \begin{RTL}...\end{RTL}, which basically only issues \par

Re: Warnings when using Listings in a RTL document

Am Mittwoch, dem 22.03.2023 um 12:54 +0200 schrieb Udicoudco: > I think in the case of where forceLTR insets will have multiple > paragraphs, it is better to use > \begin{RTL}...\end{RTL}, which basically only issues \par and sets > the > RTL related conditionals > to be false. Thanks for the

Re: Warnings when using Listings in a RTL document

Slight correction, the lines > > \@RTLfalse\beginL{ > \begin{lstlisting} > Hello > \end{lstlisting} > }\endL > should be {\@RTLfalse\beginL \begin{lstlisting} Hello \end{lstlisting} }\endL and the lines > > \@RTLfalse\beginL{ > \par > Hello > \par > }\endL > should be {\@RTLfalse\beginL

Re: Warnings when using Listings in a RTL document

On Tue, Mar 21, 2023 at 9:40 PM Scott Kostyshak wrote: > > On Tue, Mar 21, 2023 at 12:50:06PM +0100, Jürgen Spitzmüller wrote: > > Am Dienstag, dem 21.03.2023 um 11:27 + schrieb Udicoudco: > > > Hello all, > > > > > > Attached a LyX file and its export to LaTeX code. > > > When compiling with

Re: Warnings when using Listings in a RTL document

On Tue, Mar 21, 2023 at 12:50:06PM +0100, Jürgen Spitzmüller wrote: > Am Dienstag, dem 21.03.2023 um 11:27 + schrieb Udicoudco: > > Hello all, > > > > Attached a LyX file and its export to LaTeX code. > > When compiling with XeLaTeX the exported code > > I get the warning: > > > >     \endL

Re: Warnings when using Listings in a RTL document

Am Dienstag, dem 21.03.2023 um 11:27 + schrieb Udicoudco: > Hello all, > > Attached a LyX file and its export to LaTeX code. > When compiling with XeLaTeX the exported code > I get the warning: > >     \endL or \endR problem (0 missing, 1 extra) in paragraph at lines > 26--27 Interestingly,

Warnings when using Listings in a RTL document

you really know what you are doing. \documentclass[english,hebrew]{article} \usepackage{fontspec} \setlength{\parindent}{0bp} \makeatletter %% User specified LaTeX commands. \newfontfamily\hebrewfont{David CLM} \makeatother \usepackage{listings} \usepackage{polyglossia

Re: [LyX/master] Don't force encoding switch for Japanese "listings" auto-strings.

Am Donnerstag, den 18.04.2019, 17:08 +0200 schrieb Kornel Benko: > I don't see this tag in dev/lyxrc.defaults, have you reconfigured? Don't see it either. Must have been caused by parallel bisecting. Sorry for the noise. Jürgen > > Kornel signature.asc Description: This is a digitally

Re: [LyX/master] Don't force encoding switch for Japanese "listings" auto-strings.

gt; > Don't force encoding switch for Japanese "listings" auto-strings. > > > > listings copes with variable-width encodings under platex. > > I'm now getting > > LyX: Unknown tag `\font_encoding' [around line 479 of file ~/.lyx- > dev/lyxrc.defa

Re: [LyX/master] Don't force encoding switch for Japanese "listings" auto-strings.

Am Donnerstag, den 18.04.2019, 15:44 +0200 schrieb Günter Milde: > commit 6dd505c67aff5e529aa6127504d38fa38725a0b6 > Author: Günter Milde > Date: Thu Apr 18 15:20:06 2019 +0200 > > Don't force encoding switch for Japanese "listings" auto-strings. > >

Re: Bug on tex2lyx with listings

Am Samstag, den 11.08.2018, 12:36 +0100 schrieb José Abílio Matos: > On Friday, 10 August 2018 16.55.38 WEST Jürgen Spitzmüller wrote: > > Try this. > > > > Jürgen > > It works, thank you. :-) Very good. Committed. Candidate for stable. Jürgen signature.asc Description: This is a digitally

Re: Bug on tex2lyx with listings

On Friday, 10 August 2018 16.55.38 WEST Jürgen Spitzmüller wrote: > Try this. > > Jürgen It works, thank you. :-) -- José Abílio

Re: Bug on tex2lyx with listings

else if (name == "lstlisting" || name == "minted") { bool use_minted = name == "minted"; - eat_whitespace(p, os, parent_context, false); + // with listings, we do not eat newlines here since + // \begin{lstlistings} + // [foo] + // and + // // \begi

Re: Bug on tex2lyx with listings

On Friday, 10 August 2018 13.58.43 WEST José Abílio Matos wrote: > latex has no problem with it. FWIW I am aware that I am getting into weird corners. :-) To put things into perspective I am parsing a directory with .m files (octave/ matlab) to get the documentation and to generate automatically

Re: Bug on tex2lyx with listings

asically: \begin{lstlisting}% [str] = disp(x) \end{lstlisting} latex has no problem with it. Regards, -- José Abílio\documentclass{scrbook} \usepackage{listings} \lstset{language=Octave} \begin{document} \begin{lstlisting}% [str] = disp(x) \end{lstlisting} \end{document}

Re: Bug on tex2lyx with listings

Am Mittwoch, den 08.08.2018, 08:53 +0100 schrieb José Abílio Matos: > Consider the following tex file: > > \documentclass{scrbook} > \usepackage{listings} > \lstset{language=Octave} > > \begin{document} > \begin{lstlisting} > [x,y] = nice_fun(a,b); > \end{lst

Re: Bug on tex2lyx with listings

Am Mittwoch, den 08.08.2018, 08:53 +0100 schrieb José Abílio Matos: > Is this known? Should I add a new tracker issue? No. Yes, please. Jürgen > > Regards, signature.asc Description: This is a digitally signed message part

Bug on tex2lyx with listings

Consider the following tex file: \documentclass{scrbook} \usepackage{listings} \lstset{language=Octave} \begin{document} \begin{lstlisting} [x,y] = nice_fun(a,b); \end{lstlisting} \end{document} The problem is that when importing tex2lyx reads the [x,y] as an additional arguments

Re: #11203: LyX 2.3, Listings/minted: Document-wide settings yield invalid LaTeX code involving \setminted

tact the minted maintainer to ensure > that in the next release all minted instructions and options are > invoked as intended. He has been very responsive and probably would be > even more so, if contacted by developers. > > BR > > Virgil > > > On Sunday, July 22, 2018 10:36 PM, L

Re: #11203: LyX 2.3, Listings/minted: Document-wide settings yield invalid LaTeX code involving \setminted

to ensure that in the next release all minted instructions and options are invoked as intended. He has been very responsive and probably would be even more so, if contacted by developers. BR Virgil On Sunday, July 22, 2018 10:36 PM, LyX Ticket Tracker wrote: #11203: LyX 2.3, Listings

Re: [LyX/master] Group the switch of encoding for listings in utf8 documents

Am Dienstag, den 01.05.2018, 19:55 +0200 schrieb Enrico Forestieri: > > - os << code << breakln << "\\end{lstlisting}\n"; > > + os << code << "\\end{lstlisting}\n"; > >} > > Jürgen, why this change? Here, breakln ensures that \end{lstlisting} > is issued at the

Re: [LyX/master] Group the switch of encoding for listings in utf8 documents

On Tue, May 01, 2018 at 02:22:12PM +0200, Juergen Spitzmueller wrote: > commit 2009469219dd81ec932f686eb9985829c426732a > Author: Juergen Spitzmueller <sp...@lyx.org> > Date: Tue May 1 14:21:05 2018 +0200 > > Group the switch of encoding for listings in utf8 docume

Re: LyX truncates spacing in Local Layout and in Listings

On 08/29/2017 10:26 AM, Jean-Marc Lasgouttes wrote: > Le 24/08/2017 à 09:25, haim.ros...@gmail.com a écrit : >> This was generated with the file theorems-ams.inc, which has so many >> different leading spaces. > > I convinced myself that theorems-ams.inc is now correct in the UI and > pushed the

Re: LyX truncates spacing in Local Layout and in Listings

Le 24/08/2017 à 09:25, haim.ros...@gmail.com a écrit : This was generated with the file theorems-ams.inc, which has so many different leading spaces. I convinced myself that theorems-ams.inc is now correct in the UI and pushed the patch in master and 2.3.X. Richard, I do not think it is

RE: LyX truncates spacing in Local Layout and in Listings

מאת: Jean-Marc Lasgouttes נשלח: יום רביעי א אלול תשע"ז 13:31 אל: haim.ros...@gmail.com; LyX Mechanics נושא: Re: LyX truncates spacing in Local Layout and in Listings Le 23/08/2017 à 11:55, Jean-Marc Lasgouttes a écrit : > This is what the code tries to do, but there are bugs (see not

Re: LyX truncates spacing in Local Layout and in Listings

Le 23/08/2017 à 11:55, Jean-Marc Lasgouttes a écrit : This is what the code tries to do, but there are bugs (see notes below). [...] [*] the original code only considered spaces, which is of course wrong and should be corrected. [**] a further random change was added to remove all leading tabs

Re: LyX truncates spacing in Local Layout and in Listings

Le 31/07/2017 à 04:27, Richard Heck a écrit : All the leading tabs are deleted by the validation. This disturbs the reading of this content. Is there any solution for this? It works with spaces, but not with tabs. Same problem with the preamble, actually. JMarc, this seems to be because

Re: questions regarding the minted listings support

On 07/27/2017 06:34 AM, Uwe Stöhr wrote: > > Original Message > From: Richard Heck > Sent: Donnerstag, 27. Juli 2017 03:28‎ > >> Uwe, I think you must have missed the month-long discussion > Hi Richard, > > Yes because I was more or less completely off and on to real life ;-) > > However, the

Re: questions regarding the minted listings support

  Original Message   From: Richard Heck Sent: Donnerstag, 27. Juli 2017 03:28‎ > Uwe, I think you must have missed the month-long discussion Hi Richard, Yes because I was more or less completely off and on to real life ;-) However, the win installer for Lyx will noch add any option to the

Re: questions regarding the minted listings support

On 07/26/2017 07:12 PM, Uwe Stöhr wrote: > El 26.07.2017 a las 23:07, Uwe Stöhr escribió: > >> You added a feature but don't want to document properly how it can be >> used? >> With the link I understand now the -shell-escape option but the >> Python part is still not clear to me. > > I got it now

Re: questions regarding the minted listings support

El 26.07.2017 a las 23:07, Uwe Stöhr escribió: You added a feature but don't want to document properly how it can be used? With the link I understand now the -shell-escape option but the Python part is still not clear to me. I got it now to work. I descried the shell option properly and I

Re: questions regarding the minted listings support

El 26.07.2017 a las 14:16, Enrico Forestieri escribió: So please tell me what you mean and how one can use -shell-escape so that I can document it. Sorry, I won't do it. http://brosnanyuen.blogspot.it/2015/09/lxy-and-minted.html You added a feature but don't want to document properly how it

Re: questions regarding the minted listings support

On Wed, Jul 26, 2017 at 01:18:46PM +0200, "Uwe Stöhr" wrote: > > Sorry, is that your understanding of a documentation?: Go on and google > around by yourself idiot! Sorry that you interpreted it like that. > So please tell me what you mean and how one can use -shell-escape so that I > can

Re: questions regarding the minted listings support

> One can use \usepackage{whatever} multiple times when no options are specified. So, unless float was loaded as \usepackage[someoption]{float}, there should be no problem. Yes, but this is my point. We don't know if it was already loaded with an option. Therefore we should only load the package

Re: questions regarding the minted listings support

On Wed, Jul 26, 2017 at 01:11:28AM +0200, Uwe Stöhr wrote: > > 1. You write in the note that one should add these preamble lines: > \usepackage{float} > \floatstyle{plaintop} > The package float is already loaded if the user uses a non-default float > placement for the document. So shouldn't it

Re: questions regarding the minted listings support

On Wed, Jul 26, 2017 at 01:11:28AM +0200, Uwe Stöhr wrote: > 2. You write that > "requires additional software (the pygments python module) and the > -shell-escape option for the LaTeX backend, which allows arbitrary code > execution." > What does that mean? What is the pygments python module?

questions regarding the minted listings support

Hi Enrico, you added as "ef" added info to the EmbeddedObjects manual regarding the minted listings package. (Why "ef" and not a readable name? Please use real names because that makes life easier.) I tried minted out but failed. I have the following problems: 1. Y

Re: [LyX/master] tex2lyx: import minted listings

Am Samstag, 17. Juni 2017 um 19:41:46, schrieb Enrico Forestieri > On Sat, Jun 17, 2017 at 07:23:34PM +0200, Kornel Benko wrote: > > > > > Sorry, forgot to push my previous commit. Now its out, you may commit the > > files. > > I amended your commit at a1e65ad4. > Thanks, I

Re: [LyX/master] tex2lyx: import minted listings

On Sat, Jun 17, 2017 at 07:23:34PM +0200, Kornel Benko wrote: > > Sorry, forgot to push my previous commit. Now its out, you may commit the > files. I amended your commit at a1e65ad4. -- Enrico

Re: [LyX/master] tex2lyx: import minted listings

> <for...@lyx.org> > > > > > > commit 7a9bb851840fe7211cac05cbd898b27143f73559 > > > > > > Author: Enrico Forestieri <for...@lyx.org> > > > > > > Date: Sat Jun 17 02:23:00 2017 +0200 > > > > > > > >

Re: [LyX/master] tex2lyx: import minted listings

; > > > Author: Enrico Forestieri <for...@lyx.org> > > > > > Date: Sat Jun 17 02:23:00 2017 +0200 > > > > > > > > > > tex2lyx: import minted listings > > > > > > > > > > This commit updates tex2lyx in order to als

Re: [LyX/master] tex2lyx: import minted listings

:39:03, schrieb Enrico Forestieri > > > <for...@lyx.org> > > > > commit 7a9bb851840fe7211cac05cbd898b27143f73559 > > > > Author: Enrico Forestieri <for...@lyx.org> > > > > Date: Sat Jun 17 02:23:00 2017 +0200 > > > > > > &

Re: [LyX/master] tex2lyx: import minted listings

a9bb851840fe7211cac05cbd898b27143f73559 > > > Author: Enrico Forestieri <for...@lyx.org> > > > Date: Sat Jun 17 02:23:00 2017 +0200 > > > > > > tex2lyx: import minted listings > > > > > > This commit updates tex2lyx in order to

Re: [LyX/master] tex2lyx: import minted listings

te: Sat Jun 17 02:23:00 2017 +0200 > > > > tex2lyx: import minted listings > > > > This commit updates tex2lyx in order to also import minted listings. > > Do also exist test files? Something like > src/tex2lyx/test/test-minted.l

Re: [LyX/master] tex2lyx: import minted listings

Am Samstag, 17. Juni 2017 um 02:39:03, schrieb Enrico Forestieri <for...@lyx.org> > commit 7a9bb851840fe7211cac05cbd898b27143f73559 > Author: Enrico Forestieri <for...@lyx.org> > Date: Sat Jun 17 02:23:00 2017 +0200 > > tex2lyx: import minted listings >

Re: [LyX/master] Change the name of the "List of listings" for minted

00, Enrico Forestieri wrote: > > > > > > > commit ab47e48dcc525ed30b4e89b782d2ce5c81ca01c5 > > > > Author: Enrico Forestieri <for...@lyx.org> > > > > Date: Sun Jun 11 10:38:44 2017 +0200 > > > > > > > > Change the name of

Re: [LyX/master] Change the name of the "List of listings" for minted

ca01c5 > > > Author: Enrico Forestieri <for...@lyx.org> > > > Date: Sun Jun 11 10:38:44 2017 +0200 > > > > > > Change the name of the "List of listings" for minted > > > > > > I actually checked that minted calls &qu

Re: [LyX/master] Change the name of the "List of listings" for minted

Sun Jun 11 10:38:44 2017 +0200 > > > > Change the name of the "List of listings" for minted > > > > I actually checked that minted calls "List of Listings" the list of > > listings, contrarily to the listings package. > > Most probably, thi

Re: [LyX/master] Change the name of the "List of listings" for minted

On Sun, Jun 11, 2017 at 10:40:34AM +0200, Enrico Forestieri wrote: > commit ab47e48dcc525ed30b4e89b782d2ce5c81ca01c5 > Author: Enrico Forestieri <for...@lyx.org> > Date: Sun Jun 11 10:38:44 2017 +0200 > > Change the name of the "List of listings" for minted

Re: Translation of Listings in layouttranslations (was : [LyX/master] Overtake layout translations from fi.po, ja.po, zh_CN.po)

t; the file and I have a doubt about the translation of > > > > "Listings[[List of Listings]]" > > > > Does this refer to the word "Listings" as it appears in the List of > > Listings (as > > the double brackets indicate usually in the po file), or

Re: Translation of Listings in layouttranslations (was : [LyX/master] Overtake layout translations from fi.po, ja.po, zh_CN.po)

Le 10/06/2017 à 18:55, Jean-Pierre Chrétien a écrit : French does not seem to be concerned by this call, but I reviewed one more time the file and I have a doubt about the translation of "Listings[[List of Listings]]" Does this refer to the word "Listings" as it

Translation of Listings in layouttranslations (was : [LyX/master] Overtake layout translations from fi.po, ja.po, zh_CN.po)

t in respect to pdf-output? French does not seem to be concerned by this call, but I reviewed one more time the file and I have a doubt about the translation of "Listings[[List of Listings]]" Does this refer to the word "Listings" as it appears in the List of Listings (

Re: [LyX/master] Extend minted support to listings as child documents

Thu Jun 8 19:33:54 2017 +0200 > > > > Extend minted support to listings as child documents > > > > This was slipping through the cracks, apparently... > > Scott, after this I think the minted external template can be removed. > See the attached, meant as a replacemen

Re: [LyX/master] Extend minted support to listings as child documents

On Thu, Jun 08, 2017 at 07:35:51PM +0200, Enrico Forestieri wrote: > commit 8fa0e539e52512b80c5c3eac965e3abb98ba484e > Author: Enrico Forestieri <for...@lyx.org> > Date: Thu Jun 8 19:33:54 2017 +0200 > > Extend minted support to listings as child documents >

Re: HTML Output Improvement for Listings

: File: insets/InsetInclude.cpp Method: InsetInclude::xhtml // In the case of listings, we wrap it in precode. if (listing) { xs html::StartTag(pre); xs html::StartTag(code); } (...) if (listing) { xs html::EndTag(code); xs html::EndTag(pre

Re: HTML Output Improvement for Listings

ies, I suggest the following changes: > > > > File: insets/InsetInclude.cpp > Method: InsetInclude::xhtml > > // In the case of listings, we wrap it in . > > if (listing) { > xs << html::StartTag("pre"); > xs << html::StartTag("

HTML Output Improvement for Listings

. Since automatic language detection is already available to these libraries. To allow for easier integration with these libraries, I suggest the following changes: File: insets/InsetInclude.cpp Method: InsetInclude::xhtml // In the case of listings, we

HTML Output Improvement for Listings

automatic language detection is already available to these libraries. To allow for easier integration with these libraries, I suggest the following changes: File: insets/InsetInclude.cpp Method: InsetInclude::xhtml // In the case of listings, we wrap

Re: [LyX master] Fix InsetCaption::getArgument (subfigure problems reported by Kornel, but also listings caption)

Date: Tue Dec 4 17:06:52 2012 +0100 Fix InsetCaption::getArgument (subfigure problems reported by Kornel, but also listings caption) Works now. Thanks Kornel signature.asc Description: This is a digitally signed message part.

Re: [LyX master] Fix InsetCaption::getArgument (subfigure problems reported by Kornel, but also listings caption)

Juergen Spitzmueller <sp...@lyx.org> > Date: Tue Dec 4 17:06:52 2012 +0100 > > Fix InsetCaption::getArgument (subfigure problems reported by Kornel, but > also listings caption) Works now. Thanks Kornel signature.asc Description: This is a digitally signed message part.

Re: [patch] native support for list of listings

Pavel Sanda wrote: BTW Georg, is make ../lib/layoutranslation supposed to update List of Listings translation? It seems not to work here. Yes. But it does not play well wil updates of lib/layoutranslations via git. I.e. if you change a translation, and then pull in a change of lib

Re: [patch] native support for list of listings

Pavel Sanda wrote: > BTW Georg, is make ../lib/layoutranslation supposed to update List of > Listings translation? It seems not to work here. Yes. But it does not play well wil updates of lib/layoutranslations via git. I.e. if you change a translation, and then pull in a change o

Re: [patch] native support for list of listings

Pavel Sanda wrote: Georg Baum wrote: Listings is the default for \lstlistlistingname in listings.sty. IMHO LyX should not change this default as a side effect of the translation mechanism. Each translator is of course free to choose the appropriate term for his language. Ok, please

Re: [patch] native support for list of listings

Pavel Sanda wrote: > Georg Baum wrote: > > "Listings" is the default for \lstlistlistingname in listings.sty. IMHO LyX > > should not change this default as a side effect of the translation > > mechanism. Each translator is of course free to choose the appropr

Re: [patch] native support for list of listings

Georg Baum wrote: Listings is the default for \lstlistlistingname in listings.sty. IMHO LyX should not change this default as a side effect of the translation mechanism. Each translator is of course free to choose the appropriate term for his language. Ok, please go ahead. Pavel

Re: [patch] native support for list of listings

Georg Baum wrote: > "Listings" is the default for \lstlistlistingname in listings.sty. IMHO LyX > should not change this default as a side effect of the translation > mechanism. Each translator is of course free to choose the appropriate term > for his language. Ok, please go ahead. Pavel

Re: [patch] native support for list of listings

Pavel Sanda wrote: Georg Baum wrote: \addto\captions$$lang{\renewcommand{\lstlistlistingname} {_(Listings[[List of Listings]])}} Why don't we use directly List of Listings? All other linstings have this form. Pavel The reason is given in the comment a few lines above the cited line

Re: [patch] native support for list of listings

Pavel Sanda wrote: > Georg Baum wrote: >> \addto\captions$$lang{\renewcommand{\lstlistlistingname} {_(Listings[[List >> of Listings]])}} > > Why don't we use directly "List of Listings"? All other linstings have > this form. Pavel The reason is given in the c

Re: [patch] native support for list of listings

Georg Baum wrote: \addto\captions$$lang{\renewcommand{\lstlistlistingname}{_(Listings[[List of Listings]])}} Why don't we use directly List of Listings? All other linstings have this form. Pavel

Re: [patch] native support for list of listings

Georg Baum wrote: > > \addto\captions$$lang{\renewcommand{\lstlistlistingname}{_(Listings[[List of > Listings]])}} Why don't we use directly "List of Listings"? All other linstings have this form. Pavel

[patch] native support for list of listings

When working on the listings translation I noticed that \lstlistoflistings is not supported by LyX, although almost everything is already there. The attached patch implements this. Is it OK to go in (+ file format change of course)? Georgdiff --git a/lib/layouts/stdinsets.inc b/lib/layouts

[patch] native support for list of listings

When working on the listings translation I noticed that \lstlistoflistings is not supported by LyX, although almost everything is already there. The attached patch implements this. Is it OK to go in (+ file format change of course)? Georgdiff --git a/lib/layouts/stdinsets.inc b/lib/layouts

Re: [patch] fix #8066 for branch - tex2lyx support for listings

with a better approach but the patch improves the import of listings already enormously. Currently listings are not imported and with my patch they are. OK, special cases like % might fail but better than nothing. The new approach can later be backported without problems. I don't understand

Re: [patch] fix #8066 for branch - tex2lyx support for listings

implementation would raise wrong expectations, it may also introduce regressions for listings environments. Anyway, this is my personal opinion, and I am not the one to decide. +1 Uwe, I agree with you that we need verbatim, but pushing a half-baked implementation and ask other people to do

Re: [patch] fix #8066 for branch - tex2lyx support for listings

before it is backported. > > I'm fine with a better approach but the patch improves the import of > listings already enormously. Currently listings are not imported and with > my patch they are. OK, special cases like "%" might fail but better than > nothing. The new approach

Re: [patch] fix #8066 for branch - tex2lyx support for listings

implementation would raise wrong expectations, it may also introduce regressions for listings environments. Anyway, this is my personal opinion, and I am not the one to decide. +1 Uwe, I agree with you that we need verbatim, but pushing a half-baked implementation and ask other people to do

Re: [patch] fix #8066 for branch - tex2lyx support for listings

but the patch improves the import of listings already enormously. Currently listings are not imported and with my patch they are. OK, special cases like % might fail but better than nothing. The new approach can later be backported without problems. I don't understand your concerns because

Re: [patch] fix #8066 for branch - tex2lyx support for listings

) +++ test/test-insets.tex (working copy) @@ -156,6 +156,42 @@ \listoftables +\section{Listings} + +Inline: \lstinline[language={C++}]!int a=5;!\\ +Float: + +\begin{lstlisting}[caption={Example Listing float},label={lst:Example-Listing},language=Python] +# Example listing float +def func(param

Re: [patch] fix #8066 for branch - tex2lyx support for listings

but the patch improves the import of listings already enormously. Currently listings are not imported and with my patch they are. OK, special cases like "%" might fail but better than nothing. The new approach can later be backported without problems. I don't understand your concer

Re: [patch] fix #8066 for branch - tex2lyx support for listings

d::string const & name); /*! * Returns the character of the current token and increments * the token position. Index: test/test-insets.tex === --- test/test-insets.tex (revision 40911) +++ test/test-insets.tex (working copy) @@ -156,6 +156,42 @@ \listoftables +\section{Listings} + +In

Re: [patch] fix #8066 for branch - tex2lyx support for listings

Richard Heck wrote: On 03/05/2012 05:26 PM, Uwe Stöhr wrote: Richard, can the attached patch go to branch? Can someone else comment on this? I don't know tex2lyx at all. I would not put it in branch right now (see my other mail for details). I would rather like to see a better aproach

Re: [patch] fix #8066 for branch - tex2lyx support for listings

Richard Heck wrote: > On 03/05/2012 05:26 PM, Uwe Stöhr wrote: >> Richard, can the attached patch go to branch? >> > Can someone else comment on this? I don't know tex2lyx at all. I would not put it in branch right now (see my other mail for details). I would rather like to see a better aproach

Re: [patch] fix #8066 for branch - tex2lyx support for listings

Le 05/03/2012 23:35, Richard Heck a écrit : On 03/05/2012 05:26 PM, Uwe Stöhr wrote: Richard, can the attached patch go to branch? Can someone else comment on this? I don't know tex2lyx at all. I have my doubts on whether this code is enough to handle verbatim, but since I do not have time

Re: [patch] fix #8066 for branch - tex2lyx support for listings

Le 05/03/2012 23:35, Richard Heck a écrit : On 03/05/2012 05:26 PM, Uwe Stöhr wrote: Richard, can the attached patch go to branch? Can someone else comment on this? I don't know tex2lyx at all. I have my doubts on whether this code is enough to handle verbatim, but since I do not have time

  1   2   3   4   5   6   7   8   9   10   >