Re: [patch] support for 'solution' in theorems

Uwe Stöhr wrote: > Am 17.11.2015 um 20:05 schrieb Georg Baum: > >> b) If the lyx2lyx conversion from the old to the new format is empty, or >> if tex2lyx does not yet output the changed feature, you do not need any >> further tex2lyx changes. Otherwise, search

Re: [LyX/master] Document the export tests and other tests

Kornel Benko wrote: > Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum >> >> Therefore I would like to create some specific test cases for language >> nesting. Pure export tests would be fine for now, we could still add a >> comparison of the exported .

Re: Bad Exception Crash in Master

Guillaume Munch wrote: > If I may try to explain with my own words (because I really didn't get > your reasoning at first, being far from being a C++ regex expert). > Std::regex and boost::regex do not set the same regex style by default > (perl vs ECMAScript) but both support other styles by

Re: Basic test of alpha1 tar

Kornel Benko wrote: > Now the problem is linking of lyxclient ... > cd /usr/BUILD/BuildLyxGitQtlocal/src/client && /usr/bin/cmake -E > cmake_link_script CMakeFiles/lyxclient2.2.dir/link.txt --verbose=1 > /usr/bin/c++ -Wall -Wunused-parameter --std=c++11 -fno-strict-aliasing > -Wall

Re: Basic test of alpha1 tar

Kornel Benko wrote: > Am Dienstag, 17. November 2015 um 10:32:47, schrieb Scott Kostyshak > >> On Tue, Nov 17, 2015 at 01:12:56PM +0100, Kornel Benko wrote: >> > >> > Is it with autotools really compiling everything? >> > Or only files to be installed? >> >> The following

Re: [LyX/master] Cmake export tests: More tests to be reverted.

Guenter Milde wrote: > On 2015-11-17, Georg Baum wrote: > >>> However, as the "non-ASCII in preamble" warning is a false positive and >>> LaTeX does not have a problem with "unencodable" characters in a >>> comment, it is no problem to leave

Re: Basic test of alpha1 tar

Kornel Benko wrote: > OK, cmake should now work. Thanks, it works fine now! Georg

Re: [patch] support for 'solution' in theorems

Uwe Stöhr wrote: > The attached patch would fix the longstanding bug > > http://www.lyx.org/trac/ticket/6363 > > This would be a fileformat change and that is why Scott wanted to have > this in after alpha 1. The actual file format change is missing, I guess this will be in the final version?

Re: [LyX/master] Cmake export tests: More tests to be reverted.

Guenter Milde wrote: > On 2015-11-16, Kornel Benko wrote: > >> It is not the test script return failure. It is lyx itself interpreting >> latex result. If lyx exit != 0, then there is no choice for the test >> IMHO. > > However, as the "non-ASCII in preamble" warning is a false positive and >

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > Le 08/11/2015 16:16, Georg Baum a écrit : >> >> If I understood Vincent correctly then it would not be a file format >> change IMHO: >> >> As I understood it, he referred to the suggestion that the "track >> changes&qu

Re: synchronizing po file of branch and trunk

Kornel Benko wrote: > Am Sonntag, 15. November 2015 um 19:03:01, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> Kornel Benko wrote: > >> Nice, but a pity that it is not python;-( Many years ago it was decided >> that all scripts should be python, and eve

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Guenter Milde wrote: > On 2015-11-12, Georg Baum wrote: > >> (and the most important reason for me personally is that you can set an >> explicit default format per document: an automatic choice of non-TeX >> would eliminate uncompilable documents if such a

Re: Bad Exception Crash in Master

Richard Heck wrote: > > Recipe: > > 1. Open the User Guide. > 2. Click somewhere in the main text. > 3. Insert > Citation > 4. Enter the search field and type "cap" > 5. Hit search button. > > Error: Software exception Detected > > LyX has caught an

Re: [LyX/master] Assure we use docstring.

Kornel Benko wrote: > Monolithic build on Cmake has still errors. Don't know if it is worth the > effort. I fixed the one from your log. However, I do now get others for each unit test: Linking CXX executable ../../../bin/check_convert cd lyx-2-2-build/src/support/tests && /usr/bin/cmake -E

Re: [PATCH] Bug #9854 "Dataloss after git merge with change tracking"

Guillaume Munch wrote: > That would be a nice enhancement and would be a proper way to solve the > problem of missing \author lines. Independently from this, the latest > version of my patch solves every critical aspect of the problem (that > can be blamed on LyX rather than version control), and

Re: Basic test of alpha1 tar

Works fine here (Debian jessie). Georg

Re: We now include both png and svgz?

Enrico Forestieri wrote: > It is not intended to work that way. If the svgz image is there, it is > not expected that Qt is not able to show it. The double entry are there > only to assure that if there is no svgz then the png can be used instead. > In this way, you are able to override the

Re: synchronizing po file of branch and trunk

Kornel Benko wrote: > Am Freitag, 13. November 2015 um 20:18:46, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> >> I am tempted to write our own merge tool in python.. > > I have a script ready, though it is perl. Nice, but a pity that it is not python;-(

Re: synchronizing po file of branch and trunk

Scott Kostyshak wrote: > This would be nice. If the only way to do things is with manual merging, > I'm happy to spend the time to learn how to do that. But if you think it > is possible to come up with a script that either does the merging > automatically or at least facilitates the merging,

Re: docs with \origin unavailable

Scott Kostyshak wrote: > When running this script, there are some trailing spaces that are > removed after '\author ...'. This does not seem to be a problem: when > LyX saves the file it will just add the trailing spaces back. But if it > is easy it would be nice to not have this extra change (or

Re: [PATCH] Bug #9854 "Dataloss after git merge with change tracking"

Richard Heck wrote: > Like this? Basically yes, but I guess including strfwd.h shoud be enough, and the FIXME shoud of course be removed;-) Georg

hanging xelatex for japanese docs

I observe a considerable slowdown with the tests. Currently I have four xelatex processes for Additional_pdf4, EmbeddedObjects_pdf4, Customization_pdf4 and UserGuide_pdf4. These did not hang a week ago. Georg

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Scott Kostyshak wrote: > I have not followed the #9744 discussion closely or looked at Georg's > recent work, so my following suggestion might be irrelevant now, but in > any case: > > Would it make sense to check the box "Use non-TeX fonts" by > default, and then change the full string from >

Re: hanging xelatex for japanese docs

Kornel Benko wrote: > I tried to compile with "ctest -j12 -R > '(Additional|EmbeddedObjects|Customization|UserGuide)_pdf4'" Here the > summary: 75% tests passed, 14 tests failed out of 56 > > Label Time Summary: > export = 1199.48 sec (52 tests) > reverted = 311.95 sec (10 tests) >

Re: We now include both png and svgz?

Vincent van Ravesteijn wrote: > In any case, the logic is a bit strange. The icon names are defined > with the extension {png,svgz} so that any one matched, and getPixmap > checks whether the file can be loaded or not. However, iconName then > already decides on whether it is png or svgz just

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Guenter Milde wrote: > The current GUI design is inconsistent if you want to export to the most > commen document types: > > 1. DVI TeX fonts for the TeX nostalgic > > 2. PS TeX fonts for fast preview/printing and PS-tricks > > 3. PDF (pdflatex) TeX fonts

Re: [PATCH] Bug #9854 "Dataloss after git merge with change tracking"

Vincent van Ravesteijn wrote: > I doubt whether it is a good thing to start fiddling with the document > when we read in a corrupt file. > > Version control systems can corrupt a file in so many ways.. do we > really want to raise the impression we could read it in properly but > in the mean

Re: Plan for the current testing situation

Guenter Milde wrote: > What is the policy regarding change-tracking for Development.lyx? Not needed: It is not translated. If we want to know latzer who edited a certain part then we can use git. Georg

Re: Tentative schedule for 2.2.0 release

Pavel Sanda wrote: > I agree with JMarc that we could be flexible WRT shortcuting the dates in > case things look good, but I also know that all plans we ever had for our > releases were delayed. Let's see :) Yes, the plans get always delayed. Therefore I'd like a schedule with about 3 weeks

Re: synchronizing po file of branch and trunk

Jean-Marc Lasgouttes wrote: > Le 11/11/15 22:39, Scott Kostyshak a écrit : >>> Branch has less strings than master. (6609 vs. 6817). And not all >>> strings from branch are common with master. >> >> I see. So there is no rule that I can use to do what I want then. I >> guess I will just copy over

Re: docs with \origin unavailable

Scott Kostyshak wrote: > Thanks for volunteering. Please go ahead. This is now finished. While doing this, I noticed that the following items should probably be part of the release check list (don't know which items are already there): - update development/tools/gen_lfuns.py to generate

Re: [LyX/master] Add example using the varwidth package

Guillaume Munch wrote: > commit e17838b11fca51b4ebe6dfcea8ed2b52c41c437a > Author: Guillaume Munch > Date: Thu Nov 12 15:33:25 2015 + > > Add example using the varwidth package Looks like the lib/Makefile.am entry is missing, this it will not be in the tarball. Georg

Re: [PATCH] Bug #9854 "Dataloss after git merge with change tracking"

Guillaume Munch wrote: > * Georg, you told us an old story of "FIXME: UNICODE"s being placed in > the source when the developers decided that docstring would be the only > place where we see Unicode. I am happy to fix these as I go through the > code, but I am not sure that I understood what's

docs with \origin unavailable

Hi, we have currently several documents with \origin unavailable instead of \origin /systemlyxdir/doc/ in master (because of bug 9815). I suggest to save all these files with correct \origin for the alpha, even if there are still problems with 9815. It is probably also a good idea to update

Re: [LyX/master] Store both sets of font selections

Kornel Benko wrote: > The coding for \font_math looks suspicoius with the new format. > \font_math auto"" "default" > It appears in lyx-file after saving. > > Is this intended? No. I somehow overlooked the missing quote. This is fixed now. Thanks also for adjusting the tests! Georg

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Richard Heck wrote: > On 11/07/2015 12:36 AM, Vincent van Ravesteijn wrote: >> >> Is it really a file format change? If we do not change the physical >> appearance of the file format, and if we do not change the document >> output of a certain file, is it then still forbidden to change in a >>

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

RMAT b/development/FORMAT index 7ec9be7..53f9c03 100644 --- a/development/FORMAT +++ b/development/FORMAT @@ -11,6 +11,15 @@ adjustments are made to tex2lyx and bugs are fixed in lyx2lyx. --- +2015-11-08 Georg Baum <georg.b...@post.rwth-aachen.de> + * Format incremented t

Re: 'make check' failing

Scott Kostyshak wrote: > Ah yes indeed. I remember seeing that but did not make the connection. > > Would it help if I did a git bisect? Don't think so. This test is very old, and probably was never executed with C++11 std::regex in gcc before. Someone would have to find out whether the regex

Re: 'make check' failing

Scott Kostyshak wrote: > test-suite.log shows the following: > > >LyX 2.2.0dev: src/frontends/test-suite.log > > ># TOTAL: 1 ># PASS: 0 ># SKIP: 0 ># XFAIL: 0 ># FAIL:

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Richard Heck wrote: > Very minor suggestion: > > +def convert_fontsettings(document): > +" Duplicate font settings " > + > +i = find_token(document.header, "\\use_non_tex_fonts ", 0) > +if i == -1: > +document.warning("Malformed LyX document: No > \\use_non_tex_fonts!") > +

Re: [LyX/master] Copy caveats from RELEASE-NOTES to UPGRADING

Scott Kostyshak wrote: > diff --git a/UPGRADING b/UPGRADING > index 122f92d..1f410ac 100644 > --- a/UPGRADING > +++ b/UPGRADING > @@ -1,6 +1,44 @@ > -How do I upgrade my existing LyX system to version 2.1.x? > +How do I upgrade my existing LyX system to version 2.2.x? >

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Kornel Benko wrote: > Am Sonntag, 8. November 2015 um 14:57:53, schrieb Scott Kostyshak > >> >> I have just a few more items on my checklist (thanks to Vincent for the >> help) before releasing alpha. I am also waiting for access to the FTP >> (my IP needs to be whitelisted).

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > Le 06/11/2015 09:06, Jean-Marc Lasgouttes a écrit : >> Le 06/11/2015 02:31, Guillaume Munch a écrit : >> >> In terms of least surprise, I would add that both msword 2007 and >> libreoffice 5 store the setting in the document and consider the >> document as modified when

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > Le 05/11/2015 20:25, Georg Baum a écrit : >> Guillaume Munch wrote: >> >>> In addition, what appears even more special to me is the number of times >>> when it produces the effects that you mention: the only times when a >>&g

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

Guenter Milde wrote: > Dear Georg, dear all, > > On 2015-11-05, Georg Baum wrote: > >> I started to work on bug 9744 in order tor get better test results, as >> discussed. Attached is a proof of concept for the automatic font >> selection. > > Thanks fo

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Vincent van Ravesteijn wrote: > What actually makes sense is to have a document setting like > "under_version_control". When the user opens such a document (for the > first time?) we turn on change tracking. What has version control to do with change tracking? Georg

[patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

5d4 100644 --- a/development/FORMAT +++ b/development/FORMAT @@ -11,6 +11,12 @@ adjustments are made to tex2lyx and bugs are fixed in lyx2lyx. --- +2015-11-06 Georg Baum <georg.b...@post.rwth-aachen.de> + * Format incremented to 501 + \use_non_tex_fonts true => \use_tex_fo

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Vincent van Ravesteijn wrote: > I think that a regular use-case is that one author writes, and the other > one provides feedback using track changes. Yes, I did not think of that (because I prefer giving feedback on paper, and if I receive feedback then mostly from people who do not use LyX...)

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > Le 04/11/2015 20:06, Georg Baum a écrit : > > My experience with multi-author collaboration and change tracking > differs. The various portions of the document tend to "belong" to one > author and an author uses change tracking depending on wh

Re: [LyX/master] Document the export tests and other tests

Guenter Milde wrote: > Agreed. OTOH, I would prefer to have tests separated from src/, so maybe > > lib/ > src/ > tests/ > unittests/ > export-tests/ > functional/ > tests-scripts > input/ > expected/ # expected output > output/ # just a dir for the output, no content

Re: Plan for the current testing situation

Guenter Milde wrote: > On 2015-11-02, Georg Baum wrote: > >> 1) Fix the first half of bug #9744. This is an easy and safe change > > Actually, "allowing parallel configuration of TeX and non-TeX fonts" is a > precondition for the proposed config value "

Re: [LyX/master] Document the export tests and other tests

Guenter Milde wrote: > On 2015-10-30, Georg Baum wrote: >> Kornel Benko wrote: > >> These directories are clearly not suitable for pure test files, so I'll >> need to add a new one. Would lib/tests be OK? > > If you use such a generic name, it should have sub-di

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > Le 03/11/2015 21:16, Georg Baum a écrit : >> >> I don't think there is an easy solution, because it depends on the use >> case. For example, in our documentation workflows \tracking_changes needs >> to be the same for all users, so this should

Re: RFC: better submenu for tables

Richard Heck wrote: > On 11/04/2015 04:42 AM, Jean-Marc Lasgouttes wrote: >> Le 03/11/2015 01:43, Uwe Stöhr a écrit : >>> If you open the submenu of tables you see many entries. In my opinion >>> too many, at least too many for laptops with small screens. >>> >>> In general I think it should be

Re: Two Shortcut Changes

Richard Heck wrote: > Attached are two patches inspired by bug #9830. The request there was to > make master-buffer-view and master-buffer-update fall back to > buffer-view and buffer-update, since it's annoying to have to use > different shortcuts with different documents, if one is used to

Re: Unit testing

Vincent van Ravesteijn wrote: > On Tue, Nov 3, 2015 at 2:28 PM, Jean-Marc Lasgouttes > wrote: >> >> Hi Vincent, >> >> What is the difference with the tests we current use (I mean the "make >> check" sort). The same but with better interface? The overhead to add a test with

Re: shortcut clash with German locale

Guenter Milde wrote: > Dear LyXers, > > when I open a fresh compiled LyX here (German locale), I get the error > > frontends/qt4/Menus.cpp (735): Menu warning: menu entries "Logos|L" and > "Sichtbares Leerzeichen|L" share the same shortcut. Thanks, this is fixed now. It might happen for

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > > > I am bringing this to the list due to the timing, due to the fact that > it is a file format change, and due to the fact that it looks severe in > the above context. > > I suggest moving these settings to the user preferences. >

Re: Make master-buffer-update (and -view) compile current document when there is no master

Joon Ro wrote: > Hi, > I was wondering if it would be possible to make master-buffer-update (and > -view) compile the current document when there is no master defined. It > will reduce the psychological overhead involved with remembering to press > two different shortcuts to achieve the same goal

Re: bug 9626: new handling of "LyX" is unintuitive

Richard Heck wrote: > On 10/25/2015 07:43 AM, Kornel Benko wrote: >> Am Sonntag, 25. Oktober 2015 um 12:04:36, schrieb Georg Baum >> <georg.b...@post.rwth-aachen.de> >>> PhilipPirrip wrote: >>> >>>> LibreOffice has it as "Special Characters&

Re: lyx2lyx bugs from export tests

Richard Heck wrote: > I think it would be a perfectly reasonable requirement from now on > ---say, starting in the 2.3.x development cycle---that every format > change be accompanied by some kind of test file that illustrates the use > of the new feature (that's what it usually is) and that can

Re: Plan for the current testing situation

Scott Kostyshak wrote: > So in summary, regarding the XeTeX + TeX fonts, I propose the above policy > to start with; and if we find that there really is such a low signal to > noise ratio then we can change our minds and ignore them. But we will > never know what the signal to noise ratio is if

Re: When to court Qt 5.6?

Scott Kostyshak wrote: > I was wrong---Qt 5.6 beta has now been delayed to 12 November. You can > read the short discussion regarding the delay here: > http://permalink.gmane.org/gmane.comp.lib.qt.releasing/1826 > We have a few options as to what we should do about LyX 2.2.0 alpha: > > 1. Wait a

Re: status update on the export tests

Kornel Benko wrote: > Am Sonntag, 1. November 2015 um 21:46:00, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> >> We have a chicken and egg problem here. I started to work on the language >> nesting stuff, and fixing this without introducing regres

Re: status update on the export tests

Kornel Benko wrote: > Optimist (I mean 'usable state'). > I am strongly against such policy. First one has to check if the reason is > really babel/polyglossia conflict. > There are already too many tests inverted, no one cares anymore. We have a chicken and egg problem here. I started to work

Re: lyx2lyx bugs from export tests

Scott Kostyshak wrote: > On Sun, Nov 01, 2015 at 11:52:08AM -0500, Richard Heck wrote: >> On 11/01/2015 11:37 AM, Scott Kostyshak wrote: >> >> >Since you brought it up though, Kornel and I have discussed comparing >> >the .tex files. While we understand that the .lyx files are not expected >>

Re: Compiling LyX on Windows with more recent Visual Studio versions

Peter Kümmel wrote: > For iconv and hunspell one can find some CMakeLists.txt at github, not > ready for MSVC but usable as starting point. AFAIk zlib already ships > with cmake files. > > Would it be an option to add tripped down iconv, hunspell and zlib sources > to lyx and to build them as

Re: [patch] update modernCV layout file

Guenter Milde wrote: > On 2015-10-29, Georg Baum wrote: >> What do you mean by supported? > > I meant the oldest LyX-supported version, in other words the minimal > required version for flawless working with LyX. I see, I misunderstood "supported" as "supported

Re: [patch] update modernCV layout file

Richard Heck wrote: > I guess my question then is what to do shorter term. It seems a bit late > in the 2.2 cycle to do what we imagined above. I don't think we need to do anything short-term. What we learned in this discussion is that adding new styles to an existing layout can cause problems

Re: [LyX/master] Document the export tests and other tests

Kornel Benko wrote: > This is easy, just add them in one of the scanned directories. > To activate, rerun the configuration part (cmake .) > > After this they are accessible with e.g. > ctest -R > > The scanned directories (and subdirectories) are ATM > lib/doc, lib/examples, lib/templates

Re: [LyX/master] Document the export tests and other tests

Kornel Benko wrote: > Am Freitag, 30. Oktober 2015 um 22:33:14, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> Scott Kostyshak wrote: >> >> > Would another approach be to add a label? You can see the current >> > labels we have with: >> &

Re: [LyX/master] Document the export tests and other tests

Scott Kostyshak wrote: > Would another approach be to add a label? You can see the current labels > we have with: > > ctest --print-labels Since we'll need a new directory anyway (I don't think that pure test files which are not installed should show up in any of the listed directories, we

Re: [LyX/master] More updates for the documentation on tests

Scott Kostyshak wrote: > diff --git a/lib/doc/Development.lyx b/lib/doc/Development.lyx > index 0fbf144..d02aa68 100644 > --- a/lib/doc/Development.lyx > +++ b/lib/doc/Development.lyx > @@ -734,7 +734,7 @@ The tex2lyx tests can be run by the commands > status collapsed > > \begin_layout Plain

Re: [LyX/master] More updates for the documentation on tests

Kornel Benko wrote: > Am Freitag, 30. Oktober 2015 um 17:51:10, schrieb Scott Kostyshak > <skost...@lyx.org> >> On Fri, Oct 30, 2015 at 10:44:17PM +0100, Georg Baum wrote: >> > >> > Why the -R? The old version said to run ctest in the tex2lyx test >>

Re: Many tex2lyx failing now on master

Vincent van Ravesteijn wrote: > While running updatetex2lyxtest: > > algo2e.tex": >Ignoring options 'boxed' of package algorithm2e. This should be fixed one day hopefully. > test-insets.tex: >warning : Could not find included file 'Dummy Document.tex'. (2x) >warning : Could not

Re: Minimum compiler version

Peter Kümmel wrote: > In another project I saw speed improvements just > by enabling C++11 (I assume mainly because of the > move semantic). Yes, I guess we all agree that C++11 brings many improvements. > I would even support MSVC only for developers and do the > release with MinGW, would

Re: Many tex2lyx failing now on master

Kornel Benko wrote: > I see. In my installation there is no uniconvertor either. I have it installed, but it is not called by LyX directly (at least seraching for it in the complete 2.2 git folder results in 0 hits). > It is 'convert' calling this, so maybe it is not 'convert' from >

Re: [patch] update modernCV layout file

Uwe Stöhr wrote: > Am 27.10.2015 um 20:32 schrieb Georg Baum: > >> I think LyX would be perfectly suitable for frequent updates in theory, >> and I'd like to see those as well one day. For example, all those small >> new features like the one we are discussing in this t

Re: [patch] update modernCV layout file

Richard Heck wrote: > On 10/28/2015 03:59 PM, Scott Kostyshak wrote: >> On Tue, Oct 27, 2015 at 01:29:51AM +0100, Uwe Stöhr wrote: >>> Am 26.10.2015 um 22:42 schrieb Scott Kostyshak: >>> >>> - There are 2 sorts of layout issues that could violate the rule: >>> 1. Layouts for journals: We often

Re: [patch] update modernCV layout file

Richard Heck wrote: > If we support the added style, then users who both use that style and > use an older version of the package will have non-compilable documents. > So you could have a document that worked perfectly well, you make one > change---use the new style---and now it won't compile.

Re: [LyX/master] Document the export tests and other tests

Scott Kostyshak wrote: > Please let me know if there is anything else specifically that I should > document regarding the export tests. I will try to keep updating this > file. Very good! I have one question: While investigating the language nesting stuff further I found already a nesting bug

Re: check_lstrings fails at Windows

Vincent van Ravesteijn wrote: > The entries that are different from the test_lstrings reference file are > for the inputs > > { > ... > 1.3754937356458394574047e17, > 1.3754937356458394574047e18, > 1.3754937356458394574047e19, > 1.3754937356458394574047e20, > ... > 1e42 > } > > and the outputs

Re: [patch] update modernCV layout file

Guenter Milde wrote: > On 2015-10-29, Scott Kostyshak wrote: >> On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote: >>> On 10/28/2015 03:52 PM, Scott Kostyshak wrote: >>> > >>> >It seems there are a few different ideas. Let me see if I can summarize >>> >them: >>> > >>> >1. A layout

Re: status update on the export tests

Scott Kostyshak wrote: > On Mon, Oct 26, 2015 at 03:33:22PM +, Guenter Milde wrote: > >> I think we have to distinguish several test methods: >> >> a) automatic export tests with lots of "real life" documents (manuals, >>templates, examples) >> >> b) functional tests: import/export of a

Re: [patch] update modernCV layout file

Vincent van Ravesteijn wrote: > On Tue, Oct 27, 2015 at 12:56 AM, Uwe Stöhr wrote: >> Am 26.10.2015 um 16:51 schrieb Stephan Witt: > If things are that easy why can't they be documented? That is why we have the Development.lyx file, no? There ctest is not mentioned.

Re: Many tex2lyx failing now on master

Vincent van Ravesteijn wrote: > Well yes, there is no "env" command on Windows. > > This is used in both "src/tests/CMakeLists.txt" and > "src/tex2lyx/CMakeLists.txt". > > Besides that, running is a nightmare: > - Somehow tex2lyx often deadlocks when outputting errors, This would be a bug in

Re: status update on the export tests

Guenter Milde wrote: > A proper fix would be to use lib/unicodesymbols for the content of the > hypersetup. It has been discussed in the past to use lib/unicodesymbols replacements for the preamble, but there was some important reason not to do it (which I forgot unfortunately). Searching the

Re: [patch] update modernCV layout file

Uwe Stöhr wrote: > I just sent the complete patch. Could you please apply it and test. I am > pretty sure it passes all tests but since i cannot perform them on my > own... I tested it, and the tests pass. This does unfortunately not say much, because we do not have any tex2lyx test that uses

Re: [LyX/master] colored-boxes.lyx: new example file for the tcolorbox.module

Vincent van Ravesteijn wrote: > Op 25-10-2015 om 22:12 schreef Uwe Stöhr: >> Am 25.10.2015 um 11:08 schrieb Georg Baum: >> >>> And if something is wrong with them, we should invest the time and >>> improve >>> our formatted references support, instead of

Re: status update on the export tests

Scott Kostyshak wrote: > OK. Do you agree that this is not a blocker for alpha? Yes. Georg

Re: [LyX/master] Revert the box alignment part of 8010b90c

Uwe Stöhr wrote: > Am 25.10.2015 um 11:05 schrieb Georg Baum: > >> I reverted to get rid of a regression you introduced. If you want more >> details, please read the commit log and the thread I referred to in the >> commit log, since we discussed the possible alt

Re: [patch] update modernCV layout file

Uwe Stöhr wrote: > Am 26.10.2015 um 06:31 schrieb Scott Kostyshak: > >>> I think it is safe enough to support 2 years old features and would >>> therefore like to put it in. >> >> Do we have any policy on this? What have we done in the past? > > No strict one, but the feature should be at least

Re: #9785: lstinline in footnotes

Guillaume Munch wrote: > Dear Uwe, > >> Keywords regression removed >> Status changed from assigned to closed >> Resolution set to wontfix >> Milestone 2.2.0 deleted >> >> >> I don't think that we should support things that break compilation >> with the default settings. > > Then maybe have

Re: status update on the export tests

Scott Kostyshak wrote: > OK. I just want to make sure we define "there are no regressions". These > tests passed before edd37de8. So it is quite possible that documents > that users have that compile with LyX 2.1.x suddenly fail to compile > with LyX 2.2.0 because of edd37de8. In this sense,

Re: [LyX/master] colored-boxes.lyx: new example file for the tcolorbox.module

Scott Kostyshak wrote: > On Fri, Oct 23, 2015 at 10:01:42AM +0200, Jean-Marc Lasgouttes wrote: > >> >It saves some time because I don't need to write all the sime "see >> >sec._" (where _ is a half space) but only "see ". Furthermore one has a >> >larger area to click on in the PDF. personally

Re: [LyX/master] Fix export with polyglossia and uninvert a manual

Scott Kostyshak wrote: > -% increase link area for cross-references and autoname them, > -\AtBeginDocument{\renewcommand{\ref}[1]{\mbox{\autoref{#1 > -\addto\extrasfrench{% > - \renewcommand*{\equationautorefname}[1]{}% > - \renewcommand{\sectionautorefname}{sec.\negthinspace}% > -

Re: bug 9626: new handling of "LyX" is unintuitive

PhilipPirrip wrote: > LibreOffice has it as "Special Characters". Fedora Linux has an > application called "Character Map" that lists characters by, I believe, > unicode blocks. > And all those are just single characters. Symbols, though, can be one or > more: Greek alpha or \LaTeX > Just my 5

Re: [LyX/master] Revert the box alignment part of 8010b90c

Uwe Stöhr wrote: > Hi Georg, > > it is OK with me if you reverted this for good reasons, I only want to > understand why you reverted and how the feature I implemented will be > available now. I reverted to get rid of a regression you introduced. If you want more details, please read the

Re: status update on the export tests

Scott Kostyshak wrote: > The following tests are currently expected to fail because of issues with > nested language handling and polyglossia. Georg, if you still have > interest and time for fixing this type of issue, take a look at these: > > export/doc/nb/Intro_pdf5_systemF >

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

Guenter Milde wrote: > Just to be sure we don't misunderstand: The question is about tests > compiling the documentation "as-is" (i.e. with *TeX fonts*) using > XeTeX. Thanks for the clarification, I think we misunderstood. For XeTeX + TeX fonts I agree. > For me, Development.lyx compiles fine

<    1   2   3   4   5   6   7   8   9   10   >