Re: KeepEmpty 1 for sections?
On Wed, Dec 02, 2015 at 06:55:27AM +, Guenter Milde wrote: > On 2015-12-01, Scott Kostyshak wrote: > > I don't actually care if we make the change. I was just curious why > > things are how they are. > > Currently, if you remove the content of a "section paragraph", the > complete paragraph is deleted. With keepempty, you would have to remove the > paragraph "by hand" (selecting and ...). Good point. > As the above use-case is rather the exception (some would even say a > mis-use), I vote against KeepEmpty for sections. OK Scott signature.asc Description: PGP signature
Re: KeepEmpty 1 for sections?
On 2015-12-01, Scott Kostyshak wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> On Tue, Dec 01, 2015 at 09:54:37PM +0100, Jean-Marc Lasgouttes wrote:
>> What is the use case ? It looks useless to me.
> It was an exam. The desired output was
> 1
> Here is a question.
> 2
> Here is another question.
> ...
> I don't actually care if we make the change. I was just curious why
> things are how they are.
Currently, if you remove the content of a "section paragraph", the
complete paragraph is deleted. With keepempty, you would have to remove the
paragraph "by hand" (selecting and ...).
As the above use-case is rather the exception (some would even say a
mis-use), I vote against KeepEmpty for sections.
Instead, use the "classical" workaround with either a protected space, an
empty group, a LyX-note, or a comment to keep the paragraph:
\section{\ }
\section{ } % the space in here is not 000A but 00A0NO-BREAK SPACE
\section{{}}
\section{%
}
Günter
Re: Why don't we use layout2layout to update local layout?
On 11/30/2015 06:04 AM, Scott Kostyshak wrote: > On Sun, Nov 29, 2015 at 08:35:32PM -0500, Richard Heck wrote: >> On > 11/29/2015 06:29 PM, Uwe Stöhr wrote: >>> Am 29.11.2015 um 22:13 schrieb Richard Heck: >>> There is no reversion in layout2layout, so this is not possible. That's why I suggested issuing a warning. >>> >>> That is bad. You see that my argumentation against backward >>> compatibility is sadly true - it costs us much manpower. >>> >>> In fact we need to keep the LocalLayout at version 7 (as it was) >>> because if we promise backwards compatibility then the user is free to >>> export e.g. to LyX 1.5.x, right? >> >> No, I don't see it that way. The question isn't whether it's OK to use >> local layout of higher versions. The question is whether we should >> *routinely* update the format for a new release. If there was some >> reason to do so---for example, you want to make use of some feature only >> available with later formats---then that'd be differfent. > > Seems like a good policy. We should have this (and the reasoning) in > Development.lyx. Since I've removed local layout from almost all the doc files, this is less pressing. Richard
Re: Why don't we use layout2layout to update local layout?
On 12/01/2015 07:14 PM, Kornel Benko wrote: > Am Dienstag, 1. Dezember 2015 um 18:31:49, schrieb Scott Kostyshak > >> On Mon, Nov 30, 2015 at 09:08:11AM +0100, Kornel Benko > wrote: >>> Am Montag, 30. November 2015 um 02:38:48, schrieb Uwe Stöhr Am 30.11.2015 um 02:35 schrieb Richard Heck: > Note also that the use of higher formats does NOT mean the document > cannot be exported. It means one will have to do manual fixup of local > layout, to reduce the format number to something appropriate. But people > who are messing with local layout will be able to handle this. It's a > super-user feature. OK. But we use it in the docs. To solve the situation there, we could instead use the logical markup module and get rid of the LocalLayout. I will do this but cannot figure out how to use this module. regards Uwe >>> >>> For now please revert. The tests do not cover wrong lyx 1.6 export, because lyx >>> passes even with wrong output. >>> >From my side it is a blocker for 2.2. >> >> Did Richard's patches fix this or is there still a problem? > > In lib/doc only ja/Additional.lyx is left with 'Format 57', all other are '35' or '7'. > I'd say OK, don't know better. Fixed. rh
Re: [PATCH] Re: Regression in lyx2lyx box alignment
Am 30.11.2015 um 12:59 schrieb Uwe Stöhr: Sure. I'll file a bug report that this is not forgotten. Done: http://www.lyx.org/trac/ticket/9885 Regards Uwe
Re: [patch] use inkscape for EMF and WMF was: [LyX/master] installer: install Qt plugin DLLs correctly
Am 30.11.2015 um 21:39 schrieb Alex Vergara Gil: In Windows when you press Ctrl+C in an Office graphics you obtain an emf file in your pastebin, so when trying to place it in LyX you will be unsuccessful, so I always has to put it into mspaint and save it as png. So it would be a good idea to have a native automatic transformation from emf to eps. Since years the LyX installer installs metafile2eps as printer. So this printer should do the conversion for you so that you should already be able to copy emf from the pastebin directly to LyX. if this is not the case, please open a LyX bug report. (the change discussed here will first become active for LyX 2.2.0) thanks and regards Uwe
Re: [patch] use inkscape for EMF and WMF was: [LyX/master] installer: install Qt plugin DLLs correctly
Am 30.11.2015 um 22:30 schrieb Georg Baum: 1) ImageMagick has a raster image kernel, it would be a huge effort to add vector graphics capabilities, and I doubt that this is even a goal of the ImageMagick authors Well, it can convert from and to PDF and EPS via Ghostscript libraries keeping the vector information. 2) metafile2eps does not contain the conversion code. The conversion code is in windows itself, which makes it unsuitable for ImageMagick (it is cross platform). To understand why that is the case one needs to know a bit of the wmf/emf file formats. They are not like most file formats, where the contents is stored as individual objects (e.g. a green rectangle of a certain size). Instead, the contents is stored as a transcript of windows API calls to create the desired objects. This makes id dead easy for developers to support wmf/emf export and display on windows: For export you call the same routine that draws your vector graphic on screen, but with a different so called "device context" that is associated with a EMF file. To display a EMF file you call a windows API function to "replay" it. However, if you want to convert the contents into your own data structures, you basically have to replicate a lot of drawing logic from windows. The same is true if you want to export to an EMF file without calling windows API functions. Interesting. Many thanks! I am still wondering why metafile2eps required admin permissions (I assume because it has to be installed as printer). This restriction annoyed me and users too. I mean I spent much time to get LyX to be installable without admin permissions and non-admin LyX users could not benefit from Metafile2eps. Now I got feedback that Metafile2eps makes problems on some Win 10 PCs (I don't have Win 10 to test). Thus I had to make a decision. Since metafile2eps is not part of LyX, I thought it is up to me what so support via the installer. At least until now nobody commented my third-party specific installer changes. But to keeping the vector information is easy: Inkscape Attached is a patch This is indeed great news! Some years ago this was not possible. I just tried, it works even on linux, although some more adavanced EMF features are only available in the very latest inkscape version (which I do not have yet). The patch looks good to me. If this is in I am have no objections to remove metafile2eps from the installer anymore. OK, I put in in. regards Uwe
Re: [LyX/master] build.bat: add -DLYX_ENABLE_EXPORT_TESTS=ON and add a note about Ninja
Am 02.12.2015 um 00:55 schrieb Scott Kostyshak: build.bat: add -DLYX_ENABLE_EXPORT_TESTS=ON and add a note about Ninja Uwe can you now run the export tests? Peter once added this to my build script so it should not harm to have it in git too. However it doesn't seem to have an effect. (but now I have a completely clean git tree ;-) ) regards Uwe
Re: Why don't we use layout2layout to update local layout?
Am Dienstag, 1. Dezember 2015 um 18:31:49, schrieb Scott Kostyshak > On Mon, Nov 30, 2015 at 09:08:11AM +0100, Kornel Benko wrote: > > Am Montag, 30. November 2015 um 02:38:48, schrieb Uwe Stöhr > > > > > Am 30.11.2015 um 02:35 schrieb Richard Heck: > > > > > > > Note also that the use of higher formats does NOT mean the document > > > > cannot be exported. It means one will have to do manual fixup of local > > > > layout, to reduce the format number to something appropriate. But people > > > > who are messing with local layout will be able to handle this. It's a > > > > super-user feature. > > > > > > OK. > > > But we use it in the docs. To solve the situation there, we could > > > instead use the logical markup module and get rid of the LocalLayout. I > > > will do this but cannot figure out how to use this module. > > > > > > regards Uwe > > > > For now please revert. The tests do not cover wrong lyx 1.6 export, because > > lyx > > passes even with wrong output. > > From my side it is a blocker for 2.2. > > Did Richard's patches fix this or is there still a problem? In lib/doc only ja/Additional.lyx is left with 'Format 57', all other are '35' or '7'. I'd say OK, don't know better. > Scott Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] build.bat: add -DLYX_ENABLE_EXPORT_TESTS=ON and add a note about Ninja
On Wed, Dec 02, 2015 at 12:42:44AM +0100, Uwe Stöhr wrote: > commit 3fc47f2a5cff8e5d3a0cfd7d0c007e557d552146 > Author: Uwe Stöhr > Date: Wed Dec 2 00:42:40 2015 +0100 > > build.bat: add -DLYX_ENABLE_EXPORT_TESTS=ON and add a note about Ninja Uwe can you now run the export tests? They take a long time to run, but if you just run them overnight it should not waste much of your time (only your computer's!). What are the results you get (i.e. the failed tests)? Scott signature.asc Description: PGP signature
Re: KeepEmpty 1 for sections?
On Tue, Dec 01, 2015 at 09:54:37PM +0100, Jean-Marc Lasgouttes wrote: > What is the use case ? It looks useless to me. It was an exam. The desired output was 1 Here is a question. 2 Here is another question. ... I don't actually care if we make the change. I was just curious why things are how they are. Scott signature.asc Description: PGP signature
Re: Why don't we use layout2layout to update local layout?
On Mon, Nov 30, 2015 at 09:08:11AM +0100, Kornel Benko wrote: > Am Montag, 30. November 2015 um 02:38:48, schrieb Uwe Stöhr > > Am 30.11.2015 um 02:35 schrieb Richard Heck: > > > > > Note also that the use of higher formats does NOT mean the document > > > cannot be exported. It means one will have to do manual fixup of local > > > layout, to reduce the format number to something appropriate. But people > > > who are messing with local layout will be able to handle this. It's a > > > super-user feature. > > > > OK. > > But we use it in the docs. To solve the situation there, we could > > instead use the logical markup module and get rid of the LocalLayout. I > > will do this but cannot figure out how to use this module. > > > > regards Uwe > > For now please revert. The tests do not cover wrong lyx 1.6 export, because > lyx > passes even with wrong output. > From my side it is a blocker for 2.2. Did Richard's patches fix this or is there still a problem? Scott signature.asc Description: PGP signature
Re: Why don't we use layout2layout to update local layout?
On Mon, Nov 30, 2015 at 12:55:33PM +0100, Uwe Stöhr wrote: > > To use logicalmkup, ust go to Edit> Text Style. The various choices > (Noun, etc) are listed there. > > Thanks. I was looking for the styles in the Insert menu. By the way, I answered this same question here: https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg190954.html Did you get my message? It seems that many messages I send to you, you do not get or do not respond to. I remember there was a problem with SPAM before. Did you solve that problem? Should I always add you to the CC? I assumed that you would follow the thread since you participated in it, but I guess I should not assume that? Scott signature.asc Description: PGP signature
Re: [PATCH] Re: Spell checking
On Mon, Nov 30, 2015 at 10:32:49AM +0100, Jean-Marc Lasgouttes wrote: > Le 27/11/2015 15:08, Kornel Benko a écrit : > >It is OK. > > OK, I was not sure about the meaning of the smiley. > > Scott, OK? Yes. We might need to tweak it eventually to get it "perfect" but it seems like a clear improvement to me and Kornel agrees. Thanks, Scott signature.asc Description: PGP signature
Re: Just Noticed...
On Mon, Nov 30, 2015 at 02:15:38PM -0500, Richard Heck wrote: > https://www.brown.edu/information-technology/software/catalog/lyx Nice. It might be nice to have it listed here also: https://www.brown.edu/information-technology/software/free-alternatives-brown-licensed-software Scott signature.asc Description: PGP signature
Re: merging of po files done? Send email to translators?
On Sun, Nov 29, 2015 at 08:17:50PM +0100, Georg Baum wrote: > > All other are more uptodate than in branch. > > Thanks, there was indeed a bug. Now it shows 0 updates for sk.po. So is the merging indeed complete or still not yet? Scott signature.asc Description: PGP signature
Re: [PATCH] Re: Regression in lyx2lyx box alignment
Le 29/11/2015 23:55, Uwe Stöhr a écrit :
Am 29.11.2015 um 22:26 schrieb Jean-Marc Lasgouttes:
This separation between box alignment and paragraph alignment does not
exist in LaTeX. This is a creation that you propose.
Yes, because LyX doesn't allow you to choose between e.g. \begin{center}
or \centering.
So the right solution would be to add a checkbox 'compact alignment' (or
'tight' or whatever) so that the alignment functions without extra
spacing are used, right?
That would work and replace advantageously the noTrivlistCentering that
I do not like much. We could imagine to have a insetlayout property that
sets the default value for the 'compact' property depending on the inset.
This is not 2.2 material, though.
JMarc
Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file
Guillaume Munch wrote: > We could leave this aside for the moment no? Are you afraid that it would > cast the situation in stone and somebody who comes up with a good solution > won't be able to implement it anymore? I was just sharing my thoughts. Pavel
Re: Renaming revertedTests
Am Montag, 30. November 2015 um 12:56:22, schrieb Guenter Milde > On 2015-11-28, Kornel Benko wrote: > ... > Why do you use a filter chain? Because some filter are more general than others. First filter is the most general. > Wouldn't it be easier to maintain separate filters? > > Currently, an unreliable test must get an entry in "revertedTests" AND > "unreliableTests". If the problem is solved, both entries should be removed > again (but after removing the one from revertedTests we will not be flagged > to remove the other entry as well). This has changed, that is not true anymore. And my previous description was wrong too, probably because my memory is shading. > We have 2 options: > > a) put all in one file "invertedTests" and use the new subtag mechanism: It is renamed now, a multiple subtag mechanism is implemented. ... > I am not happy with the naming "suspicious" (we know for sure there is a > problem and the test fail). > > I am not happy with the naming "suspended" (what is its use case?)¹ > This one are tests which are failing, but we cannot do anything on them. See .*pdf4_texF Many other tests with the same signature are not failing. You don't need to remove it from 2 lists, only from 'suspiciousTests'. 'Suspended' is only a subfilter which does not effect tests not in 'suspicious'. > > Günter > > ¹ I know I once proposed this category, but I wanted something different from > what became implemented. I made a table which shows how labels are assigned. See lib/doc/Development.lyx, at the end of subsection '3.4 Export test filtering'. Kornel signature.asc Description: This is a digitally signed message part.
Re: [PATCH] Re: Spell checking
Le 27/11/2015 15:08, Kornel Benko a écrit : Am Freitag, 27. November 2015 um 13:23:04, schrieb Jean-Marc Lasgouttes Le 27/11/2015 12:28, Kornel Benko a écrit : Back to this problem. What about the following patch? JMarc Yes, that is easy to notice :) Do you mean that it is OK, or too large? JMarc It is OK. OK, I was not sure about the meaning of the smiley. Scott, OK? JMarc
Lyx: Reduce vertical spacing of items [in UI only]
Dear Lyx-Users, I've posted the following question on stackoverflow a couple of days ago and since it is related to customization of Lyx I figure I might post it on the developers list. https://tex.stackexchange.com/questions/279995/lyx-reduce-vertical-spacing-of-items-in-ui-only I like to use lists to structure my ideas before writing them down. To organize these notes it is very convenient to have shortcuts to exchange and change the level of indentation (just as in Emacs Orgmode). Lyx can do this. Unfortunately the vertical space between the items in the UI is quite large, so it takes up too much space and is a little confusing to look at. **Is there any way to reduce the amount of vertical space between these items in the UI?** (preferably to a single space) Just for clarification: I'm not interested to modify the vertical space in the output document, but the way the items are displayed in the Lyx UI. Any suggestions how to modify the Lyx layout files would be quite welcome. Thank you! Henning
Re: [PATCH] Re: Regression in lyx2lyx box alignment
Original Message
From: Jean-Marc Lasgouttes
Sent: Montag, 30. November 2015 10:32
>> Yes, because LyX doesn't allow you to choose between e.g. \begin{center} or
>> \centering.
> So the right solution would be to add a checkbox 'compact alignment' (or
'tight' or whatever) so that the alignment functions without extra
spacing are used, right?
Yes, very good idea! This would help for many different cases.
> This is not 2.2 material, though.
Sure. I'll file a bug report that this is not forgotten.
Regards Uwe
Duplication in Outline display with inactive branches
When a branch is inactivated in alpha2 (on Windows), the Outline display shows duplicated expand/contract boxes, as in the attached png. Activate the branch and the duplication vanishes. I read in the New features in 2.2 that " entries that are disabled (i.e. either in a note or in an inactive branch) are now marked with the symbol ❎". Presumably the empty boxes should display this symbol. Does this point to a missing font package in my latex distribution? Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: using std_regex on Windows leads to 135 compilation errors
Am Dienstag, 1. Dezember 2015 um 22:06:40, schrieb Georg Baum
> Uwe Stöhr wrote:
>
> > Am 29.11.2015 um 22:30 schrieb Kornel Benko:
> >
> >> The problem may also be usage (respective non-usage) of --std=c++11.
> >> I already asked, what to do to allow MSVC to use this flag, but got no
> >> answer. ATM the windows compilation is probably without, setting the
> >> 'LYX_USE_CXX11' to 0
> >>
> >> The changes could be built in
> >> development/cmake/modules/FindCXX11Compiler.cmake:37 ff The actual search
> >> is done at development/cmake/modules/FindCXX11Compiler.cmake:86 ff
> >
> > I would like to test this. Could you please send me a patch to be able
> > to test?
>
> Please try this one. It assumes that you use the build.bat file to compile,
> if you don't, then you need to adjust the call of cmake accordingly.
>
> MSVC 2010 does not need any special flag to compile in C++11 mode, the
> limited subset of C++11 features that it supports is enabled by default. The
> only thing I am not 100% sure about is whether the supported subset is
> enough for LyX, but I believe it is.
There is missing the patch for searching c++11 flags. They are not needed,
but ATM this info is ignored by our script.
Additional to your patch we need probably also the attached:
> Georg
Kornel
signature.asc
Description: This is a digitally signed message part.
diff --git a/development/cmake/modules/FindCXX11Compiler.cmake b/development/cmake/modules/FindCXX11Compiler.cmake
index 7d09f8f..49203e6 100644
--- a/development/cmake/modules/FindCXX11Compiler.cmake
+++ b/development/cmake/modules/FindCXX11Compiler.cmake
@@ -83,6 +83,10 @@ int main() {
# check c compiler
set(SAFE_CMAKE_REQUIRED_QUIET ${CMAKE_REQUIRED_QUIET})
set(CMAKE_REQUIRED_QUIET ON)
+if(MSVC10)
+ set(LYX_USE_CXX11 1)
+ set(CXX11_FLAG "")
+endif()
FOREACH(FLAG ${CXX11_FLAG_CANDIDATES})
SET(SAFE_CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS}")
SET(CMAKE_REQUIRED_FLAGS "${FLAG}")
Re: Why don't we use layout2layout to update local layout?
Original Message From: Richard Heck Sent: Montag, 30. November 2015 04:47 > I've done that, for all the manuals except the Japanese ones. Those use a "Ruby" style that I have no idea what it is. Many thanks! I see that you used Noun while the locallayout used sansserif. Is this correct? > To use logicalmkup, ust go to Edit> Text Style. The various choices (Noun, etc) are listed there. Thanks. I was looking for the styles in the Insert menu. Regards Uwe
Re: A margin-al question
Le 29/11/2015 23:18, Murat Yildizoglu a écrit : Hello, I would like to know if it would be too difficult for you to implement an option that permits us to fix the margin between the text's border and LyX's window border. Currently, there is nearly zero margin, and that is something that slightly annoyed me for many years. I was wondering if the adoption of the new QT would allow for such an option. This is a question comfort rather than usability, but nevertheless... Hi Murat, What is the resolution of your screen (DPI)? At 100dpi, the current margin corresponds to 2.5mm. I have a patch that enforces this length also when the resolution is higher. If you are looking for a much larger margin, then your should have a look at our fullscreen support, which allows to select the margin value. JMarc
Re: [LyX/master] Cmake autotests: Corrected suspiciousTests for new testfile
Am Dienstag, 1. Dezember 2015 um 22:13:17, schrieb Georg Baum > Kornel Benko wrote: > > > # Language nesting, document is OK, fails because of a bug in LyX > > -export/export/languagenesting1_(dvi|pdf(|[23])) > > +# Does no longer fail > > +# export/export/languagenesting1_(dvi|pdf(|[23])) > > +# > > because of af18890ed668c8. Turns out that this document works with 2.1 as > well, and it is not the one I wanted to add. Unfortunately I deleted all > intermediate docs after it was in git, so I have to extract it from the > manual again:-( > Sorry. > Georg Kornel signature.asc Description: This is a digitally signed message part.
Re: file generation after compilation is always executed twice
Am Dienstag, 1. Dezember 2015 um 21:18:59, schrieb Georg Baum > Uwe Stöhr wrote: > > > Am 25.11.2015 um 21:15 schrieb Georg Baum: > > > >> I believe it is the argument /t:ALL_BUILD to msbuild in > >> development/cmake/build.bat. This builds all projects that depend on > >> ALL_BUILD, and I guess that .gmo recreation is included. > > > > Thanks. Yes this is the reason. /t:ALL_BUILD builds the target > > "tex2lyx", then the target "translations" and the "update-gmo". > > This is strange. In the .sln file you sent to me the target ALL_BUILD does > neither depend on "translations" nor on "update-gmo". Also none of the other > targets built by ALL_BUILD do depend on one of those. This would be > consistent with what we see on linux for the "all" target. Are you sure that > you do not use a modified build.bat file? > > I tried to look up in the cmake documentation how the ALL_BUILD (or all, > repsectively) target is constructed, but I could not find it. Kornel, you > you have a hint? I would have to search exactly as you too. I have no clue. > Also, both the MSVC project files and the Linux Makefile > generated by cmake are not very readable. They are clearly not meant to be > understood by humans. Probably. There seems to be only Makefiles calling cmake with scripts named 'Makefile.cmake', 'cmake_clean.cmake', ... , 'cmake_install.cmake'. So, now they are readable only by humans which are good in cmake scripting. > Georg Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] Cmake autotests: Corrected suspiciousTests for new testfile
Kornel Benko wrote: > # Language nesting, document is OK, fails because of a bug in LyX > -export/export/languagenesting1_(dvi|pdf(|[23])) > +# Does no longer fail > +# export/export/languagenesting1_(dvi|pdf(|[23])) > +# because of af18890ed668c8. Turns out that this document works with 2.1 as well, and it is not the one I wanted to add. Unfortunately I deleted all intermediate docs after it was in git, so I have to extract it from the manual again:-( Georg
Re: URL check in our lyx-sources
Am Montag, 30. November 2015 um 18:41:14, schrieb Scott Kostyshak > > > > Error url: "ftp://ftp.edpsciences.org/pub/aa/readme.html"; > > > > lib/doc/Additional.lyx:u7916 > > > > lib/doc/de/Additional.lyx:u8355 > > > > lib/doc/es/Additional.lyx:u7989 > > > > lib/doc/fr/Additional.lyx:u8702 > > > > lib/doc/ja/Additional.lyx:u8355 > > > > When I go to this site in either Chromium or Firefox it works (and the > > site is up-to-date). So our detection has a problem it seems. I checked > > the parsing and it seems to be correct: > > protocol is "ftp" > > host is "ftp.edpsciences.org" > > path is "pub/aa/" > > file is "readme.html" > > > > Not sure what to do. > > This only fails for me sometimes, and I believe it depends on the > internet connection. Kornel, you see this failure right? And when you go > in your browser, it works right? Do you think it is worth it to debug or > should we just forget about it? > > Scott Yes, firefox access is OK. Kornel signature.asc Description: This is a digitally signed message part.
Re: using std_regex on Windows leads to 135 compilation errors
Uwe Stöhr wrote: > Am 29.11.2015 um 22:30 schrieb Kornel Benko: > >> The problem may also be usage (respective non-usage) of --std=c++11. >> I already asked, what to do to allow MSVC to use this flag, but got no >> answer. ATM the windows compilation is probably without, setting the >> 'LYX_USE_CXX11' to 0 >> >> The changes could be built in >> development/cmake/modules/FindCXX11Compiler.cmake:37 ff The actual search >> is done at development/cmake/modules/FindCXX11Compiler.cmake:86 ff > > I would like to test this. Could you please send me a patch to be able > to test? Please try this one. It assumes that you use the build.bat file to compile, if you don't, then you need to adjust the call of cmake accordingly. MSVC 2010 does not need any special flag to compile in C++11 mode, the limited subset of C++11 features that it supports is enabled by default. The only thing I am not 100% sure about is whether the supported subset is enough for LyX, but I believe it is. Georg diff --git a/CMakeLists.txt b/CMakeLists.txt index a87b049..4194a76 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -265,9 +265,14 @@ if(UNIX OR MINGW) endif() else() set(LYX_USE_STD_REGEX 0) -# if(MSVC10) -# set(LYX_USE_STD_REGEX 1) #TODO should we use it in ECMAScript mode? -# endif() + if(MSVC10) + # MSVC 10 has limited C++11 support (which is enabled by default, no switch needed) + set(LYX_USE_STD_REGEX 1) + endif() + if(MSVC12) + # MSVC 12 has less limited C++11 support (which is enabled by default, no switch needed) + set(LYX_USE_STD_REGEX 1) + endif() endif() diff --git a/development/cmake/build.bat b/development/cmake/build.bat index 25baec0..4ff711a 100755 --- a/development/cmake/build.bat +++ b/development/cmake/build.bat @@ -82,14 +82,14 @@ if [%2]==[] ( if "%1%" == "devel" ( REM Build solution to develop LyX - cmake %LYX_SOURCE% -GNinja -G%USED_STUDIO% -DLYX_MERGE_FILES=0 -DLYX_NLS=1 -DLYX_INSTALL=0 -DLYX_RELEASE=0 -DLYX_CONSOLE=FORCE %DEPENDENCIES_DOWNLOAD% + cmake %LYX_SOURCE% -GNinja -G%USED_STUDIO% -DLYX_ENABLE_CXX11=ON -DLYX_MERGE_FILES=0 -DLYX_NLS=1 -DLYX_INSTALL=0 -DLYX_RELEASE=0 -DLYX_CONSOLE=FORCE %DEPENDENCIES_DOWNLOAD% msbuild lyx.sln /p:Configuration=Debug /t:LyX /t:tex2lyx ) if "%1%" == "install" ( REM Build solution to develop LyX REM set -DLYX_MERGE_REBUILD and -DLYX_MERGE_FILES to 1 for a version released with an installer - cmake %LYX_SOURCE% -G%USED_STUDIO% -DLYX_MERGE_REBUILD=0 -DLYX_MERGE_FILES=0 -DLYX_NLS=1 -DLYX_INSTALL=1 -DLYX_RELEASE=1 -DLYX_CONSOLE=OFF %DEPENDENCIES_DOWNLOAD% + cmake %LYX_SOURCE% -G%USED_STUDIO% -DLYX_ENABLE_CXX11=ON -DLYX_MERGE_REBUILD=0 -DLYX_MERGE_FILES=0 -DLYX_NLS=1 -DLYX_INSTALL=1 -DLYX_RELEASE=1 -DLYX_CONSOLE=OFF %DEPENDENCIES_DOWNLOAD% msbuild lyx.sln /p:Configuration=Release /t:ALL_BUILD msbuild INSTALL.vcxproj /p:Configuration=Release )
Re: KeepEmpty 1 for sections?
What is the use case ? It looks useless to me.
JMarc
Le 30 novembre 2015 14:24:37 GMT+01:00, Scott Kostyshak a
écrit :
>I just received a .tex file from a colleague and he uses \section{}.
>
>Is there a reason to not have KeepEmpty 1 for sections?
>
>Scott
KeepEmpty 1 for sections?
I just received a .tex file from a colleague and he uses \section{}.
Is there a reason to not have KeepEmpty 1 for sections?
Scott
signature.asc
Description: PGP signature
Re: Font of LyX manuals
Am 30.11.2015 um 00:09 schrieb Uwe Stöhr : > Am 26.11.2015 um 09:09 schrieb Guenter Milde: > >> No. Many users (including myself) don't use a *complete* TeX distribution > > That makes me wonder. In the world around me everybody uses just click and > go. Why do you fiddle around to get a TeX subset when there is TeXLive that > you can install with a few clicks? (I have TeXLive as well). Fiddling costs > time and that is what people usually don't have. I understood that the default installation without "fiddling" is the subset of TeX. Stephan
Re: Tentative schedule for 2.2.0 release
Le 30/11/2015 10:59, Scott Kostyshak a écrit : On Sun, Nov 29, 2015 at 08:44:34PM +0100, Jean-Marc Lasgouttes wrote: Le 29/11/2015 16:39, Richard Heck a écrit : I'd suggest beta in two weeks if we don't run into any serious problems, then see how that goes. If well, then we can shoot for RC in mid-January. This looks good to me. Uwe will be away in two weeks. The last day he will be able to build an installer is December 11, which to me means we should plan on the last day being December 10, just in case there is a problem. He will be back on January 6. Should we aim then for a beta on December 10? This seems too quick to me, but I'm fine to proceed if this is what others want. Scott Well everybody knows that time freezes for two weeks at the end of December for most people here anyway so it's not a real delay. I am happy to have an accelerated release schedule (I have nothing absolutely necessary to implement before that) but I had made mental plans according to what was announced initially. I have an implementation of http://www.lyx.org/trac/ticket/7790 (which I mentioned among the things that I would like to finish for 2.2.0 when Scott asked about it). I might have a polished version soon, though certainly not before Dec 10th. I am not worried about having this between alpha and beta because I can do at first a set of changes that are innocuous. In case I do not have time (for instance if you want to accelerate the schedule) is it possible to implement the format change (which I feel is stable now) for 2.2.0 and implement the polished visible changes in 2.2.1 or 2.2.2?
Re: file generation after compilation is always executed twice
Uwe Stöhr wrote: > Am 25.11.2015 um 21:15 schrieb Georg Baum: > >> I believe it is the argument /t:ALL_BUILD to msbuild in >> development/cmake/build.bat. This builds all projects that depend on >> ALL_BUILD, and I guess that .gmo recreation is included. > > Thanks. Yes this is the reason. /t:ALL_BUILD builds the target > "tex2lyx", then the target "translations" and the "update-gmo". This is strange. In the .sln file you sent to me the target ALL_BUILD does neither depend on "translations" nor on "update-gmo". Also none of the other targets built by ALL_BUILD do depend on one of those. This would be consistent with what we see on linux for the "all" target. Are you sure that you do not use a modified build.bat file? I tried to look up in the cmake documentation how the ALL_BUILD (or all, repsectively) target is constructed, but I could not find it. Kornel, you you have a hint? Also, both the MSVC project files and the Linux Makefile generated by cmake are not very readable. They are clearly not meant to be understood by humans. Georg
Distribution of commits in lyx-...@lists.lyx.org
Looks like it is not working ATM. Kornel signature.asc Description: This is a digitally signed message part.
Re: Why don't we use layout2layout to update local layout?
Am Montag, 30. November 2015 um 02:38:48, schrieb Uwe Stöhr > Am 30.11.2015 um 02:35 schrieb Richard Heck: > > > Note also that the use of higher formats does NOT mean the document > > cannot be exported. It means one will have to do manual fixup of local > > layout, to reduce the format number to something appropriate. But people > > who are messing with local layout will be able to handle this. It's a > > super-user feature. > > OK. > But we use it in the docs. To solve the situation there, we could > instead use the logical markup module and get rid of the LocalLayout. I > will do this but cannot figure out how to use this module. > > regards Uwe For now please revert. The tests do not cover wrong lyx 1.6 export, because lyx passes even with wrong output. From my side it is a blocker for 2.2. Kornel signature.asc Description: This is a digitally signed message part.
Re: Why don't we use layout2layout to update local layout?
On Sun, Nov 29, 2015 at 08:35:32PM -0500, Richard Heck wrote: > On 11/29/2015 06:29 PM, Uwe Stöhr wrote: > > Am 29.11.2015 um 22:13 schrieb Richard Heck: > > > >> There is no reversion in layout2layout, so this is not possible. That's > >> why I suggested issuing a warning. > > > > That is bad. You see that my argumentation against backward > > compatibility is sadly true - it costs us much manpower. > > > > In fact we need to keep the LocalLayout at version 7 (as it was) > > because if we promise backwards compatibility then the user is free to > > export e.g. to LyX 1.5.x, right? > > No, I don't see it that way. The question isn't whether it's OK to use > local layout of higher versions. The question is whether we should > *routinely* update the format for a new release. If there was some > reason to do so---for example, you want to make use of some feature only > available with later formats---then that'd be differfent. Seems like a good policy. We should have this (and the reasoning) in Development.lyx. Scott signature.asc Description: PGP signature
Just Noticed...
https://www.brown.edu/information-technology/software/catalog/lyx
Re: Why don't we use layout2layout to update local layout?
On 11/29/2015 08:38 PM, Uwe Stöhr wrote: > Am 30.11.2015 um 02:35 schrieb Richard Heck: > >> Note also that the use of higher formats does NOT mean the document >> cannot be exported. It means one will have to do manual fixup of local >> layout, to reduce the format number to something appropriate. But people >> who are messing with local layout will be able to handle this. It's a >> super-user feature. > > OK. > But we use it in the docs. To solve the situation there, we could > instead use the logical markup module and get rid of the LocalLayout. > I will do this but cannot figure out how to use this module. I've done that, for all the manuals except the Japanese ones. Those use a "Ruby" style that I have no idea what it is. To use logicalmkup, ust go to Edit> Text Style. The various choices (Noun, etc) are listed there. Richard
Re: Font of LyX manuals
On 2015-11-29, Uwe Stöhr wrote:
> Am 26.11.2015 um 09:09 schrieb Guenter Milde:
>> No. Many users (including myself) don't use a *complete* TeX distribution
> That makes me wonder. In the world around me everybody uses just click
> and go. Why do you fiddle around to get a TeX subset when there is
> TeXLive that you can install with a few clicks? (I have TeXLive as
> well). Fiddling costs time and that is what people usually don't have.
Wit my Debian system, it is easy to select the sub-packages I really need.
This excludes things like language support for languages I don't understand
or special fonts or document classes I don't want to use.
On Debian, installing LyX recommends a "medium" TeXLive subset
(see https://packages.debian.org/jessie/lyx).
This means you can install LyX also without any TeX (but of course this will
not allow you to compile to PDF or Postscript). You can, however also use it
with a minimal LaTeX installation
https://packages.debian.org/sid/texlive-latex-base
This again recommends (but not requires) the package "lmodern" providing
lmodern.sty.
> In this case I vote for the other solution you proposed:
> ---
> b) use a simplified and "Unicode-clean" preamble code:
...
> +% use Latin Modern fonts if available
> +\IfFileExists{lmodern.sty}{
> + \renewcommand{\rmdefault}{lmr}
> + \renewcommand{\sfdefault}{lmss}
> + \renewcommand{\ttdefault}{lmtt}
> +}{}
...
> -1 requires preamble code
> I vote for this for your argument. We already have preamble code so that
> it shouldn't matter that we will keep it in a changed form.
Fine.
I still believe that it is even better to have less preamble code and make
use of the settings natively supported by LyX.
>> IMO, LM should not be required for the "simple" manuals.
> What is simple? I would load lmodern if available in general, see above.
> if not, the default TeX fonts are used.
>>> Since years also the Intro and Tutorial is using Latin Modern. Only
>>> splash does not use it.
>> However, they use it "optionally" via preamble code. And compiling splash
>> takes ages because first the bitmap fonts need to be generated.
> Interesting; here it is very quick.
There are two possible reasons:
a) bitmap fonts are cached, so this is quick the second time.
b) if installed, the CM-Super font is used as substitute if the request is for
CM with font encoding T1.
both of this does not apply for a new user with a minimal LaTeX installation.
>> I prefer PSNFSS fonts for simple manuals (splash, Intro, Tutorial).
> OK.
>> Please try, e.g., Palatino, Helvetica, Courier and tell about problems.
> What do you mean? They all work here.
Nice.
So my suggestion is:
* use Palatino, Helvetica, Courier for splash, Intro, and Tutorial.
This way you get documents that are guaranteed to compile out of the box
even with a minimal LaTeX installation.
* Other manuals (especially the "heavy" manuals like Math or Additonal)
may use LatinModern via the lyx font-setting -- LM is the
widely accepted "best current practice" for CM-like fonts in 8-bit
encodings.
With 2.2, it is possible to toggle the readonly feature: users without
lmodern.sty but other required packages installed can easily change the
settings to an installed font.
+1 no need for font-selecting preamble code,
+1 consistent look on every site.
Günter
Re: [LyX/master] UserGuide.lyx and Math.lyx: update version number
Uwe Stöhr wrote: > Thanks for this info. I was wondering about this for a while. I think > that we should nevertheless save all files with the current LyX alpha2 > because people might wonder why official LyX files are changed while > they are e.g. only Save As somewhere. I agree. I added support for saving all docs with LyX to updatedocs.py in http://www.lyx.org/trac/changeset/3ab58d155cbb/lyxgit/, but so far nobody volunteered to use this feature and verify that it does not destroy anything. I believe you can save yourself a lot of time if you follow the list more closely, because we try to automate as much as possible, so you do not need to do boring stuff manually. Georg
Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file
Le 30/11/2015 01:15, Pavel Sanda a écrit : Guillaume Munch wrote: You describe a method for this, above, but to me it sounds like a cumbersome way to force-record the state of an inset (for instance, it I agree it is cumbersome, my reasoning was that I would rather impose this complexity on user who is using git & CT than complicating anything for user who just uses CT. We could leave this aside for the moment no? Are you afraid that it would cast the situation in stone and somebody who comes up with a good solution won't be able to implement it anymore? By the way, I forgot the step 1.5) "do a dummy modification" between 1) "save" and 2) "revert", so it's really a 7-step process.
Re: Renaming revertedTests
On 2015-11-28, Kornel Benko wrote: > Originally, this file should have regexes to select export combinations > which fail. Therefore the name 'reverted'. Unfortunately, this name is confusing: we revert a commit but invert a test. > Soon we (Scott and I) found, that some tests worked on Scott's side, > but not on mine (or reverse). > > Now, this file includes many tests which are not at all reverted. The > main purpose is now to select tests which do not pass everywhere even > with full TL/MikTeX installed. > > Günter Milde proposed 'problematicTests'. > > ATM it is the main filter to select suspicious test combinations. We do not just suspect anything in these tests, we list tests where we *know* that these tests fail (at least at one site). OTOH, the term "suspicious" could be used instead of "fragile" for what I proposed as a tag for test combinations that are "unstable" or "working by chance", e.g. unsave export-font combination like XeTeX-texF. > This filters 319 tests (out of 3716 export tests). > From them 270 are inverted (means they always fail) and 49 unreliable > (means that they fail or pass depending on some installed data) > > Our filtering is > > ignoredTests: (small file) > Input: any export combination > Tests selected here are withdrown. > Output: All but selected. > > revertedTests: > Input: Each test which passed 'ignoredTests' > Tests not selected here gets the label 'export'. They should pass. > Output: Tests selected by its regexes. > > suspendedTests: > Input: Each Test selected by 'revertedTests' > Tests selected here gain the label 'suspended' but _not_ 'export' or > 'reverted' > Output: Tests _not_ selected > > unreliableTests: > Input: Each Test _not_ selected by 'suspendedTests' > Tests selected either pass or fail, but that is dependant on system > where the test is run. > Selected tests gain the label 'unreliable' > Not selected tests gain the labels 'reverted' and 'export' Why do you use a filter chain? Wouldn't it be easier to maintain separate filters? Currently, an unreliable test must get an entry in "revertedTests" AND "unreliableTests". If the problem is solved, both entries should be removed again (but after removing the one from revertedTests we will not be flagged to remove the other entry as well). We have 2 options: a) put all in one file "invertedTests" and use the new subtag mechanism: ... # normal inverted tests ... subtag: unreliable ... # unreliable tests ... subtag: suspended ... # suspended tests ... b) change the filtering mechanism: > ignoredTests: (small file) > Input: any export combination > Tests selected here are withdrown. Not selected tests gain the label 'export' > Output: All but selected. > revertedTests: > Input: Each test which passed 'ignoredTests' Selected tests gain the labels 'reverted'. > suspendedTests: Input: Each test which passed 'ignoredTests' Tests selected here gain the label 'suspended' # eventually remove the labels 'reverted' and 'export' > unreliableTests: Input: Each test which passed 'ignoredTests' > Tests selected either pass or fail, but that is dependant on system > where the test is run. > Selected tests gain the label 'unreliable' > Not selected tests gain the labels 'reverted' and 'export' > I think that most files used to filter export tests has appropriate naming. > Remains only 'revertedTests'. > I'd like to rename it to something like 'suspicious', 'suspect' or > 'suspected'-Tests. I am not happy with the naming "suspicious" (we know for sure there is a problem and the test fail). I am not happy with the naming "suspended" (what is its use case?)¹ Günter ¹ I know I once proposed this category, but I wanted something different from what became implemented.
Re: Fwd: LyX 2.2 alpha1
Uwe Stöhr wrote: > I build from the tarball. To do so i create a new branch in my git to > get all paths correct. Can you please explain why you need to do anything in git? I ask because building from a tar ball usually means - unpack tar ball - cd to the unpacked directory - execute build script and I want rto help that you can do it that way. If there is no git involved, then you can be very sure that the build result comes only from the tar ball and not from something in git. If git is involved, then this is not easy to verify. > In this case I compiled it correctly but put the files from the git > master lib folder to the installer instead of the files from the tarball. > The lyx.exe and tex2lyx.exe in the installer are the correct ones (see > the date when LyX is started). So there is no need to release a new > installer. http://www.lyx.org/trac/ticket/9878 is a strong hint that the installer contains at least some files that are not from the tar ball. This bug does also demonstrate why it is so important that the labels of binary and source packages match: If we had known from the beginning that Andrew was not using alpha2, one of the very first things he would have been told is "use alpha2", and then he would have noticed that the bug does not exist in alpha2. Georg
Re: Font of LyX manuals
On 2015-11-29, Uwe Stöhr wrote: > Am 26.11.2015 um 09:09 schrieb Guenter Milde: > In this case I vote for the other solution you proposed: > b) use a simplified and "Unicode-clean" preamble code: ... > I vote for this for your argument. We already have preamble code so that > it shouldn't matter that we will keep it in a changed form. However, it would still be better for maintaining (and as example for good use) to reduce the preamble code if alternatives exist. ... >>> Since years also the Intro and Tutorial is using Latin Modern. Only >>> splash does not use it. >> However, they use it "optionally" via preamble code. And compiling splash >> takes ages because first the bitmap fonts need to be generated. > Interesting; here it is very quick. There may be two reasons: a) the bitmap fonts are cached, so only the first compilation is slow b) the CM-Super fonts are installed. Then they are used as substitution for CM with 8-bit font encodings (like LyX's default T1). Both reasons do not hold for a user trying out Ly with a minimal LaTeX installation. >> I prefer PSNFSS fonts for simple manuals (splash, Intro, Tutorial). > OK. >> Please try, e.g., Palatino, Helvetica, Courier and tell about problems. > What do you mean? They all work here. Fine. Then my suggestion is to set fonts "the LyX way": * Palatino, Helvetica, Courier for splash, Intro, and Tutorial * Latin Modern for the other manuals. Latin Modern is "Current Best Practice" for CM-like fonts with T1 font encoding. Since 2.2, the readonly feature can be toggled -- users who do not have LatinModern installed can change the font setting in LyX. IMO, this is acceptable for manuals that rely on packages outside the set of the "minimal requirements" for a LaTeX installation. +1 No preamble code for font selection. +1 Basic manuals guaranteed to work out of the box also with minimal LaTeX installation. +1 Consistent result on all TeX installations. Günter
Re: LyX 2.2 + Qt 5.5.1 segmentation fault on Fedora 23
Stephan Witt wrote: > Am 19.11.2015 um 04:00 schrieb PhilipPirrip : > >> I had a similar issue a month or so ago, what helped was a clean cloning >> of LyX source. Now even that doesn't work, and it's been like that for 2 >> or 3 weeks. It might be due to newest Qt libraries that came with Fedora >> 23, not sure. Can you read anything from this backtrace? > > I've redirected it to developers list. > >> Reading symbols from ./bin/lyx2.2...done. >> (gdb) run >> Starting program: /build-lyx-Qt5/bin/lyx2.2 >> Missing separate debuginfos, use: dnf debuginfo-install >> glibc-2.22-5.fc23.x86_64 >> [Thread debugging using libthread_db enabled] >> Using host libthread_db library "/lib64/libthread_db.so.1". >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x76305204 in _GLOBAL__sub_I_qprinterinfo.cpp () from >> /lib64/libQtGui.so.4 > > What is that (libQtGui.so.4)? Are you sure your linking with Qt5 at > runtime? In my experience, that backtrace often means a runtime conflict where both qt4 and qt5 are trying to load into the same process (usually crashes quickly) -- Rex
Re: [patch] use inkscape for EMF and WMF was: [LyX/master] installer: install Qt plugin DLLs correctly
Uwe Stöhr wrote: > Am 28.11.2015 um 11:15 schrieb Georg Baum: > >> If there are problems with the installation then please ask on the list >> for help and opinions. > > I am the only Win developer here. My spare time is limited and the > installer consumes a lot of time. > The installer is there to provide a fully functional LyX, no matter if > installed with admin privileges or not. Metafile2eps was not available > without admin privileges. I understand that you do not want to invest time into such installation issues. However, I still think that it is better to discuss such changes on the list first. Nobody knows everything, and even if you do not see any other solution than dropping something from the installer, it is possible that there are others who have a much better idea. For example, I have windows development experience myself. > Besides this, why should I invest my time to get this program working > while it is not part of LyX and not under development for 7 years now? > If emf conversion is important why is metafile2eps not developed > anymore. I already answered that question in the text cited below. > If the creator doesn't have time, he could contribute his code > to e.g. ImageMagick that this program is able to convert keeping the > vector information. No, for two reasons: 1) ImageMagick has a raster image kernel, it would be a huge effort to add vector graphics capabilities, and I doubt that this is even a goal of the ImageMagick authors 2) metafile2eps does not contain the conversion code. The conversion code is in windows itself, which makes it unsuitable for ImageMagick (it is cross platform). To understand why that is the case one needs to know a bit of the wmf/emf file formats. They are not like most file formats, where the contents is stored as individual objects (e.g. a green rectangle of a certain size). Instead, the contents is stored as a transcript of windows API calls to create the desired objects. This makes id dead easy for developers to support wmf/emf export and display on windows: For export you call the same routine that draws your vector graphic on screen, but with a different so called "device context" that is associated with a EMF file. To display a EMF file you call a windows API function to "replay" it. However, if you want to convert the contents into your own data structures, you basically have to replicate a lot of drawing logic from windows. The same is true if you want to export to an EMF file without calling windows API functions. > But to keeping the vector information is easy: Inkscape > Attached is a patch This is indeed great news! Some years ago this was not possible. I just tried, it works even on linux, although some more adavanced EMF features are only available in the very latest inkscape version (which I do not have yet). The patch looks good to me. If this is in I am have no objections to remove metafile2eps from the installer anymore. >> To my knowledge, there was no development needed, and it simply works >> also for newer windows versions, but Enrico can certainly tell more. > > It never "simply" worked. It was not available for those who install LyX > without admin permissions and made troubles when LyX was uninstalled. I meant the converter itself, not the installation. > Interestingly I could not find a single emf file on my PC. I also never > stumbled over this image format at work. > I downloaded now one and it appears that no browser can display this > file format. So I am wondering what program created emf natively. All windows programs that deal with vector graphics I have seen so far can create it, including exotic ones like DynaGeo, where it is the only possibility to export vector graphics. BTW, as fas as LyX is concerned, the differences between emf and wmf do not matter. Georg
Re: [LyX/master] Customization.lyx: update localLayout format
On Sun, Nov 29, 2015 at 12:10:19PM -0500, Richard Heck wrote: > On 11/29/2015 11:26 AM, Kornel Benko wrote: > > Am Sonntag, 29. November 2015 um 17:15:19, schrieb Uwe Stöhr > > >> commit 7499b14b50bf528547c5585cbb0f7e2de11b8a8a >> > > Author: Uwe Stöhr > >> Date: Sun Nov 29 17:15:15 2015 +0100 >> >> > Customization.lyx: update localLayout format >> >> - Japanese > version: also run lyx2lyx >> >> diff --git > a/lib/doc/de/Customization.lyx b/lib/doc/de/Customization.lyx > > So, > manuals are starting to not be exportable to lyx 2.1 format. Very funny. > > I vote for revert, or setting the format to maximal 49. > > We thought we had consensus on this, but now the vote is turning the > other way > > I'm inclined now to think that you and Georg are right, though I was the > one who started this. Actually I think I started it. In any case, I agree that it is best not to update the local layouts without a reason. It might be nice to update them locally just as a test of layout2layout. Scott signature.asc Description: PGP signature
Re: URL check in our lyx-sources
On Fri, Nov 27, 2015 at 01:54:50AM -0500, Scott Kostyshak wrote: > On Thu, Nov 26, 2015 at 07:23:59PM +0100, Kornel Benko wrote: > > > > Error url: "ftp://ftp2.commence.com/pub/freebies/"; > > > lib/doc/Additional.lyx:h7816 > > I asked Uwe and Kornel to confirm a new URL I found in a separate email > thread. s/Kornel/Andrew/. Andrew responded that he did not know. Uwe did not respond. I went ahead and made the change at 19c6a01. > > > > Error url: "ftp://ftp.edpsciences.org/pub/aa/readme.html"; > > > lib/doc/Additional.lyx:u7916 > > > lib/doc/de/Additional.lyx:u8355 > > > lib/doc/es/Additional.lyx:u7989 > > > lib/doc/fr/Additional.lyx:u8702 > > > lib/doc/ja/Additional.lyx:u8355 > > When I go to this site in either Chromium or Firefox it works (and the > site is up-to-date). So our detection has a problem it seems. I checked > the parsing and it seems to be correct: > protocol is "ftp" > host is "ftp.edpsciences.org" > path is "pub/aa/" > file is "readme.html" > > Not sure what to do. This only fails for me sometimes, and I believe it depends on the internet connection. Kornel, you see this failure right? And when you go in your browser, it works right? Do you think it is worth it to debug or should we just forget about it? Scott signature.asc Description: PGP signature
Re: A margin-al question
On Sun, Nov 29, 2015 at 11:18:11PM +0100, Murat Yildizoglu wrote: > Hello, > I would like to know if it would be too difficult for you to implement an > option that permits us to fix the margin between the text's border and > LyX's window border. Currently, there is nearly zero margin, and that is > something that slightly annoyed me for many years. Can you send a screenshot? For me there is a margin. > I was wondering if the adoption of the new QT would allow for such an > option. > This is a question comfort rather than usability, but nevertheless... These questions are important. Best, Scott signature.asc Description: PGP signature
Re: Tentative schedule for 2.2.0 release
On Sun, Nov 29, 2015 at 08:44:34PM +0100, Jean-Marc Lasgouttes wrote: > Le 29/11/2015 16:39, Richard Heck a écrit : > >I'd suggest beta in two weeks if we don't run into any serious problems, > >then see how that goes. If well, then we can shoot for RC in mid-January. > > This looks good to me. Uwe will be away in two weeks. The last day he will be able to build an installer is December 11, which to me means we should plan on the last day being December 10, just in case there is a problem. He will be back on January 6. Should we aim then for a beta on December 10? This seems too quick to me, but I'm fine to proceed if this is what others want. Scott signature.asc Description: PGP signature
Re: [LyX/master] Update format of bind and ui files.
Scott Kostyshak wrote: > Well I had it on my list of things to check and it was also on the list > of things Vincent had told me to check so I don't really have an excuse. > I just missed it. I have added it to my automated script though so I > will not miss it again. BTW can you update wiki for release process in case it differs? Pavel
Re: [patch] use inkscape for EMF and WMF was: [LyX/master] installer: install Qt plugin DLLs correctly
In Windows when you press Ctrl+C in an Office graphics you obtain an emf file in your pastebin, so when trying to place it in LyX you will be unsuccessful, so I always has to put it into mspaint and save it as png. So it would be a good idea to have a native automatic transformation from emf to eps. Regards Alex 2015-11-29 20:34 GMT-05:00, Uwe Stöhr : > Am 30.11.2015 um 01:57 schrieb Andrew Parsloe: > >> When I discovered LyX about ten years ago, I saved my Word 95 documents >> as rtf and used rtf2latex2e to convert them to latex so that they could >> be imported into LyX. The figures in the Word documents were separated >> out by rtf2latex2e into wmf files. > > Interesting. So word is using WMF for RTF. I have to use Word every day > and never noticed this. > > regards Uwe >
Re: merging of po files done? Send email to translators?
> Is the merging complete? If so, should I send an email to the > translators? Does the timing of this email depend on the timing of our > scheduled beta release? I think it is reasonable to send it after you do string freeze (whenever that is). That for example means that ctrl+p shortcut stays unassigned as it is now. Pavel
