Re: Email to translators on Sunday, rc2 two weeks after

Am 13.01.2018 um 05:15 schrieb Jean-Pierre: Uwe, could you try the test file attached in https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg203152.html (perform an advanced search & replace of string '{}' in TeX code by letter 'C'). Neither Scott nor me could  reproduce on Linux, but the

Re: [LyX/2.3.x] Revert "de.po: update some translations"

Am 13.01.2018 um 16:22 schrieb Jürgen Spitzmüller: I am indecisive if this is not even better since it would help non-native speakers (I guess we have a lot non-native users who have to use English menus because no translation is available for their language). Why that? Because "Separated

Re: [LyX/2.3.x] Revert "de.po: update some translations"

Am 13.01.2018 um 08:54 schrieb Jürgen Spitzmüller: No. This does not work due to gender: Separierte Rahmen oberhalb (wrong) vs. Separierte Aufzählung oberhalb (correct) Thanks, I understand. or the English string should be changed to msgid "Separated environment (%1$s) Above" msgstr

Re: Email to translators on Sunday, rc2 two weeks after

Am 11.01.2018 um 09:40 schrieb Scott Kostyshak: I would like to email translators on Sunday. Please try to get documentation touchups that should be translated done as soon as you can. I did so and distributed all available changes. If I missed something, please let me know. Instead of

Re: [LyX/2.3.x] Revert "de.po: update some translations"

Am 12.01.2018 um 10:23 schrieb Juergen Spitzmueller: commit e8fb5da776301a7f435314f64ad2388f9114c721 Author: Juergen Spitzmueller Date: Fri Jan 12 10:23:44 2018 +0100 Revert "de.po: update some translations" This reverts commit

Re: lyx-cvs failure notice

Am 10.01.2018 um 09:57 schrieb Pavel Sanda: Change your git config, so your commiter name is not uwesto...@web.de but uwesto...@lyx.org . Many thanks Pavel. I did this now. I see that my lyx.org address is already subscribed to lyx-cvs. I see that all mails from lyx-cvs are automatically

lyx-cvs failure notice

My PC broke and I jot a new one. Therefore I had to setup everything new from scratch. I can commit but now I get for every commit this error message: Hi. This is the qmail-send program at thales.memphis.edu. I'm afraid I wasn't able to deliver your message to the following

Re: compilation error with sk.po

El 02.01.2018 a las 13:55, Jürgen Spitzmüller escribió: Please try again. Hello Jürgen, I wish you too all the best for the new year. Many thanks for your commit, I can now compile. regards Uwe

Re: make check broken in master

El 01.01.2018 a las 12:12, Kornel Benko escribió: Clearly there are 2 dummy_functions.cpp, one in support containing theApp and one in src/tests which doe not :) OK, one of them should be removed. Hi Pavel, I wish you and your family a happy new year. This is the same problem I

compilation error with sk.po

Hi Kornel, I wish you and your family a happy new year. With JMarc's patch I can compile master again but encounter now this: Generating qt4_files Generating layouts_files Generating languages_files Generating latexfonts_files Generating encodings_files Generating ui_files

Re: Beamer usage again

El 01.01.2018 a las 11:06, Scott Kostyshak escribió: I believe that Uwe is not going to be available to build the Windows binary for the next month, so we will not be able to get rc2 out soon anyway. In fact, I think the last day Uwe will be able to work on LyX for a while is on Tuesday. I

Re: new compilation errors in master

El 23.12.2017 a las 08:23, Uwe Stöhr escribió: I regenerated CMake and built LyX from scratch and the problem persists. If I undo the changes to SystemCall*.cpp/.h from commit 165c9e92a400e8fdc00ef3e74eb68b34bfbcc6d5 it compiles fine. I reported this compilation error now: https

Re: LyX on windows performance

Am 23.12.2017 um 20:35 schrieb Jean-Marc Lasgouttes: But, thanks to the nice INSTALL file, I did it (Qt 5.9.3 64bits) for 2.3.x+properpaint branch (I will switch to master soon). Cool. So I am not alone anymore on Windows. LyX is not yet ready for 64bit. This is something we should do for LyX

Re: missing forward to https for lyx.org

Am 24.12.2017 um 08:16 schrieb Christian Ridderström: > IIRC, rewrites isn't done by .htaccess by the main Apache configuration files under /etc/httpd/. OK. I am a beginner with these things. I found the solution with .htaccess by googling and it works. It should work if you replace in

missing forward to https for lyx.org

I noticed that calling http://www.lyx.org does not automatically forward/rewrite to https://www.lyx.org I did this this week for a private website by adding some code to the .htaccess file. Therefore I think that this should be possible for lyx.org as well without troubles. Christian and

Re: new compilation errors in master

I regenerated CMake and built LyX from scratch and the problem persists. If I undo the changes to SystemCall*.cpp/.h from commit 165c9e92a400e8fdc00ef3e74eb68b34bfbcc6d5 it compiles fine. regards Uwe

Re: new compilation errors in master

El 23.12.2017 a las 04:07, Richard Heck escribió: I don't know why that is supposed to be unsafe, but I've fixed it. Thanks. I've sent a separate note about that one. I do not know the test code well enough to fix this myself. You could try adding this to both files: struct App {   

new compilation errors in master

After the recent changes I get 2 compilation errors and 2 warnings: 2 warnings: D:\LyXGit\Master\src\LaTeX.cpp(420): warning C4805: '|=': unsafe mix of type 'bool' and type 'int' in operation [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj] D:\LyXGit\Master\src\LaTeX.cpp(422): warning C4805:

Re: revtex4-1 failing on 2.3.x because of "Repeated entry" in bib

El 19.12.2017 a las 07:57, Scott Kostyshak escribió: The error I get is: Repeated entry---line 2 of file revtex4-1Notes.bib I cannot see a bug in our file. revtex4-1Notes.bib is part of the revtex4 bundle. Therefore it must be reported/fixed there. regards Uwe

Website news

You might have been wondering about all my commits to SVN. I updated the graphical tour which dated from LyX 1.3.x times (sic!): http://www.lyx.org/Walkthrough The good news are that thanks to Yuriy we have now a Russian translation of our website: http://www.lyx.org/WebRu.Home (work in

Re: LyX version 2.3.0rc1 available

El 18.12.2017 a las 22:14, Richard Heck escribió: Please go ahead. Done: http://www.lyx.org/News regards Uwe

Re: LyX version 2.3.0rc1 available

El 18.12.2017 a las 18:23, Scott Kostyshak escribió: I agree, but I don't have SVN access. I have and can do this if you like. However, I think as release manager you should get SVN access. regards Uwe

Re: LyX version 2.3.0rc1 available

El 18.12.2017 a las 02:47, Scott Kostyshak escribió: Public release of LyX version 2.3.0rc1 Many thanks Scott. I expect now more translation updates an also bug reports. I think the RC is also worth it to announce it on our website: https://www.lyx.org/News many thanks and regards Uwe

Re: code check via MSVC warning level 4

El 17.12.2017 a las 02:54, Richard Heck escribió: Yes, but these are usually the result of cases where someone is comparing, say, as size_t variable (a typedef for unsigned int or something) with an int in a for loop, or something of that sort, and the int is never going to be negative. So it's

Re: [patch] use https in in first line of LyX files

El 17.12.2017 a las 01:37, Uwe Stöhr escribió: El 16.12.2017 a las 20:10, Scott Kostyshak escribió: It's fine for 2.3.0. OK, I'll put it in. OK, I rethought this. I fear special cases in lyx2lyx or tex2lyx where I might have missed a thing. Then they might not work correctly just

Re: code check via MSVC warning level 4

El 17.12.2017 a las 02:02, Richard Heck escribió: I noted that when I extend from level /W4 to /Wall I get some additional signed/unsigned mismatch errors. Should I report them as well? Those are usually harmless. I wouldn't worry too much about them. OK. Just for curiosity, why ar they

Re: Language problems ... again

El 16.12.2017 a las 22:33, Scott Kostyshak escribió: Uwe, should I make the Changelog file? What do you prefer? Better mail him directly. He usually responds quickly. thanks and regards Uwe

Re: should LyX for Win install Pygments?

El 16.12.2017 a las 22:30, Scott Kostyshak escribió: However, it's important to note that LyX's Python is exposed to the whole system, so the more Python packages that we support, the more code it is possible for users to run even outside of LyX. This could be viewed as a danger, as discussed

Re: [patch] support for the paratype fonts

El 16.12.2017 a las 23:45, Richard Heck escribió: I know it's late for a format change, but what about including this in 2.3.0? I am opposed to this because this would change strings. I mean the user can simply add \usepackage{paratype} to the preamble to use it for all fonts. I can also

Re: [patch] use https in in first line of LyX files

El 16.12.2017 a las 20:10, Scott Kostyshak escribió: It's fine for 2.3.0. OK, I'll put it in. Usually what I do when changing http to https is to check that the https link is indeed secure. This is what I did. if it is not secure I left it with http. While doing this I detected a lot of

Re: code check via MSVC warning level 4

El 14.12.2017 a las 02:23, Uwe Stöhr escribió: I just polluted the bug tracker with 86 new bug reports with different compiler warnings Many thanks Jean-Marc and Richard for reviewing them. I feared that some developers are annoyed by this. I noted that when I extend from level /W4

Re: [patch] support for the paratype fonts

El 16.12.2017 a las 06:27, Pavel Sanda escribió: I was about to ask the same, please don't break portability of files until 2.3 is out if possible. OK. By the way, why don't we release RC1 right now? Did I miss something? thanks and regards Uwe

[patch] support for the paratype fonts

/FORMAT index 5e0c5bf0cc..f60db64736 100644 --- a/development/FORMAT +++ b/development/FORMAT @@ -7,6 +7,12 @@ changes happened in particular if possible. A good example would be --- +2017-12-xx Uwe Stöhr <uwesto...@web.de> + * Format incremented to 545: s

[patch] use https in in first line of LyX files

I think we should use https wherever possible: https://www.lyx.org/trac/ticket/10945 Attached is a patch that does this. OK to go in? What about LyX 2.3, should we do this there as well or can this be done for 2.3.1? In Buffer.cpp there are with the patch still 2 non-https links, but this

Re: linked email addresses on lyx.org

El 14.12.2017 a las 08:43, Jürgen Spitzmüller escribió: These 2 pages needs to be updated: http://www.lyx.org/Credits http://www.lyx.org/BlanketPermission Done. Thanks. I was looking how this is done and noted that they contain the full email addresses of all of us. Perfect for Spam bots.

should LyX for Win install Pygments?

In https://wiki.lyx.org/LyX/NewInLyX23 I read about support for the Python module Pygments. I don's know what to do for the installer. If the user hasn't installed Python, should I deliver LyX with python containing the Pygments module? If the user has already python installed, should I force

code check via MSVC warning level 4

I just polluted the bug tracker with 86 new bug reports with different compiler warnings. Why?: I am currently helping to get a KDE program to run properly under Windows. When I started I got a lot of crashes and proposed to fix all possible dataloss, signed/unsigned mismatch and

linked email addresses on lyx.org

These 2 pages needs to be updated: http://www.lyx.org/Credits http://www.lyx.org/BlanketPermission I was looking how this is done and noted that they contain the full email addresses of all of us. Perfect for Spam bots. So can't we use just the text of the addresses instead of links? How can

Re: Updated Russian translation

El 12.12.2017 a las 07:37, Юрий Скалько escribió: I hereby grant permission that my contributions to LyX can be released under the license GPL v2 or later. Many thanks Yuriy, I added you now to the LyX credits. regards Uwe

Re: Plan for next announcement

El 12.12.2017 a las 09:05, Stephan Witt escribió: Which Qt-Version did you use for this installer? Qt 5.9.3. I am using this build now for a while and wrote some new LyX documents with it. I have not encountered a problem. regards Uwe

Re: Plan for next announcement

El 10.12.2017 a las 21:28, Scott Kostyshak escribió: One option is just to announce rc1 now. I would announce it right now. Please use build 8 of my RC1 installer. thanks and regards Uwe

Re: [LyX/master] Enable OK/Apply buttons when resetting to class defaults.

El 01.11.2017 a las 19:20, Scott Kostyshak escribió: Go ahead to 2.3.x branch. Although we have not officially released RC1, we have referred to the installers publicly and I have pushed the commit and tag, so there's no going backward now. If any blocker is found, we would have to move to RC2.

Re: Qt5svg.dll problem

El 29.10.2017 a las 18:23, edu Gpl escribió: Thank you. I reinstalled lyx 2.3 beta1. All ok. Hi Hatim, could you please do me the favor and 1. uninstall LyX 2.3beta1 completely (also the user settings!) 2. install LyX 2.3RC1:

Re: off topic: feedback after 3 months with Linux

El 01.11.2017 a las 04:20, Richard Heck escribió: This is a question you could ask of the people at your distro. They made a decision to compile the kernel so that iwlwifi was integrated into it and not a module. Hi Richard, many thanks for your detailed reply. I learned a lot. So I need a

Re: off topic: feedback after 3 months with Linux

El 31.10.2017 a las 03:05, Richard Heck escribió: I realized that Linux's monolithic kernel is a problem. Every device driver needs to be part of the kernel. This is a confusion. Linux supports kernel modules, which are the exact Linux equivalent of a device driver, and which can be installed

Re: off topic: feedback after 3 months with Linux

On 31.10.2017 14:24, Paul A. Rubin wrote: That's curious. I didn't have any problems with Xreader and gender radio buttons in PDF-form.lyx. - open the PDF of PDF-form.lyx with the latest Xreader 1.4.4. - then go to sec. 2.3 and you can see that you cannot select "female". - go to sec. 2.1 to

Re: off topic: feedback after 3 months with Linux

El 31.10.2017 a las 00:08, Paul A. Rubin escribió: That said, I've been happy with my move to Linux Mint. Hi Paul, the problems I encountered are independent of the distribution. The bugs are in the drivers and/or libraries. (I started with the distribution Manjaro then tested OpenSuse,

off topic: feedback after 3 months with Linux

El 30.10.2017 a las 08:29, Scott Kostyshak escribió: > Do you still have access to Linux? Yes. I work with Linux as testing system for 3 months now. Long story short, I am a bit disappointed. Linux is OK for Internet, office and email. But that is it. I mean I even cannot fill out a PDF form

Re: configure.py regression in RC1 compared to beta

El 30.10.2017 a las 08:31, Scott Kostyshak escribió: I'll cherry-pick Jürgen's change regarding WMF -> EPS converter. I don't want the commit that stores text editors in a variable in RC1 (even though I requested that improvement) since it is more of a long-run benefit fix. OK, then only also

Re: configure.py regression in RC1 compared to beta

El 29.10.2017 a las 16:52, Jürgen Spitzmüller escribió: Note that I am traveling. So if it works on the Mac, someone will have to cherry-pick it. I might also not be able to commit soon. So Scott, could you please do this if Stephan gave his OK? Moreover, I propose to commit configure.py

Re: Qt5svg.dll problem

El 29.10.2017 a las 10:02, edu Gpl escribió: I used windows10 + lyx 2.3 beta1. After i update MiKTex, i got this msg: Qt5svg.dll is either not designed to run on windows or it containts an error. Dear Hatim, MiKTeX updated recently their Qt5 dependencies. I might that this causes this

Re: configure.py regression in RC1 compared to beta

El 29.10.2017 a las 08:54, Jürgen Spitzmüller escribió: Any thoughts on whether this should be an rc1 blocker? Yes, it should, if only since we need the rc to test all OSes. +1 Anyway, I have pushed a fix to master. It works on Linux. Great! This works here. best regards Uwe

Re: wmf2eps

El 29.10.2017 a las 09:00, Jürgen Spitzmüller escribió: We currently look for wmf2eps as EMF -> EPS converter. However, this does not seem to work (the converter only supports WMF, not EMF). Is this just by accident (copy-paste from WMF -> EPS)? Can I remove this one? Yes because wmf2eps can

Re: configure.py regression in RC1 compared to beta

El 28.10.2017 a las 19:25, Jürgen Spitzmüller escribió: It should be quoted. You can check via the messages pane. Hi Jürgen, sorry I did not have time to look closer up to now. Nevertheless I cannot see the complete path behind $$p, all I get is this:

Re: configure.py regression in RC1 compared to beta

El 28.10.2017 a las 14:05, Jürgen Spitzmüller escribió: How can we fix this? If it turns out that Inkscape on Windows cannot deal with paths we need to introduce a function for configure.py that returns full path or only file name depending on the OS. I think this is the problem as far as I

configure.py regression in RC1 compared to beta

Hi Stephan, With LyX 2.3.0beta1 I can convert EMF images in LyX file while this fails in RC1. The reason is commit http://www.lyx.org/trac/changeset/350ef993/lyxgit The bug is that the path must not be output for inkscape on Win and apparently also not on Linux. As this seems to be a special

Re: Tars for 2.3.0rc1

El 28.10.2017 a las 02:18, Uwe Stöhr escribió: I found it: the file ReplaceValues.cmake is missing in your tar. the reason is a missing entry in a Makefile. I fixed this now in master: http://www.lyx.org/trac/changeset/3d4358f1/lyxgit regards Uwe

Re: Tars for 2.3.0rc1

El 28.10.2017 a las 02:14, Scott Kostyshak escribió: But Kornel is not to blame here. There is simply a difference in the folder development\cmake between branch and your tar. I found it: the file ReplaceValues.cmake is missing in your tar. regards Uwe

Re: Tars for 2.3.0rc1

El 28.10.2017 a las 02:07, Scott Kostyshak escribió: Kornel, do you have an idea for a fix? But Kornel is not to blame here. There is simply a difference in the folder development\cmake between branch and your tar. regards Uwe

Re: Tars for 2.3.0rc1

El 27.10.2017 a las 20:33, Scott Kostyshak escribió: Here are the tars for 2.3.0rc1:... Hi Scott, I cannot compile from that TAR because ReplaceValues strikes back: Building Custom Rule D:/LyXGit/LyX23/development/cmake/doc/CMakeLists.txt CMake does not need to re-run because

Re: [LyX/master] Fix remaining path

El 27.10.2017 a las 06:02, Scott Kostyshak escribió: I don't see the file for Japanese. Oh, sorry. Yes the file was missing in Japanese. I added them now in master and will do it after RC1 was released also in 2.3.x if you agree. regards Uwe

Re: [LyX/master] Fix remaining path

El 27.10.2017 a las 00:17, Scott Kostyshak escribió: No. it is just a dummy file as example. I think we should at least be consistent, no? A localized version exists for German. Should we remove that then? to correct myself, you are right, it should be translated. And as I can see it is

Re: Freeze 2.3.x on Wednesday for rc1?

El 26.10.2017 a las 08:59, Guenter Milde escribió: I had some off-list discussion with Uwe about the dash-documentation resulting in some changes to his changes to my changes. Currently, I implemented them with change tracking on -- this would need Uwe's revision to accept the changes and

Re: [LyX/master] Fix remaining path

El 26.10.2017 a las 22:32, Scott Kostyshak escribió: Uwe, how should we signal to translators that this DummyTextDocument.txt file should be translated? No. it is just a dummy file as example. However, Kornel's patch to Japanese EmbeddedObjects should go in before 2.3.0 final. regards Uwe

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 23.10.2017 a las 10:55, Kornel Benko escribió: Question: Is it possible to have also the input-textfiles be utf-8 encoded? Here on Windows all changelog files are UTF-8 encoded. As it is now, the script converts them, which I think is OK. OK then. regards Uwe

Re: Japanese docs: incorrect paths?

El 25.10.2017 a las 19:53, Scott Kostyshak escribió: Uwe, do you happen to have time to take a look at what is going wrong? I fixes them now - I hope. Koji, there are now 2 untranslated image captions in sec. 4.6.2. Also, why don't missing images give an error when compiling? This way our

Re: Freeze 2.3.x on Wednesday for rc1?

‎   Original Message   From: Richard Heck Sent: Montag, 23. Oktober 2017 03:35‎ >> http://www.lyx.org/trac/ticket/10556  > someone else would need to +1 that one. Done: +1 Regards Uwe ‎

Re: Freeze 2.3.x on Wednesday for rc1?

El 22.10.2017 a las 20:08, Scott Kostyshak escribió: I would like to propose to freeze the 2.3.x branch at 23:59 UTC on Wednesday, for releasing rc1. +1 I just checked the docs that all changes are now accepted. Trivial things like e.g. http://www.lyx.org/trac/ticket/10775 and

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 22.10.2017 a las 13:43, Uwe Stöhr escribió: great work! Now it works and also the line break issue is now solved. OK, there is a minor issue left: The script is run on ALL files in the doc directories, so also for the changelog and the attic files. Especially for the changelog files

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 21.10.2017 a las 22:41, Guenter Milde escribió: It is in the 2.3 branch now. Should work with both, Python 2 and 3. Hi Kornel and Günter, great work! Now it works and also the line break issue is now solved. many thanks and best regards Uwe

Re: [LyX/2.3.x] Cmake doc creations: Setting environment PYTHONIOENCODING

El 21.10.2017 a las 11:29, Kornel Benko escribió: OK also for 2.2.x Richard? There are issues with this, see my recent post. With LyX 2.2.x we rely on python 2.x and we don't have a problem. Therefore I opt to keep the 2.2.x branch as it is. regards Uwe

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 18.10.2017 a las 15:18, Kornel Benko escribió: There should not be a problem. Hello Kornel, many thanks for the commit. However, in the 2.3.x branch I still get File "C:\Program Files (x86)\Python35-32\lib\encodings\cp1252.py", line 23, in decode return

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 17.10.2017 a las 19:50, Guenter Milde escribió: The following patch makes it work here with Python versions 2.6, 2.7, 3.3, 3.4, and 3.5. Perfect. This fixes the problem for me. TODO: find out which encoding is used for the arguments by CMake The today's CMake changes from Kornel set

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 17.10.2017 a las 09:44, Kornel Benko escribió: Its, because of problems we had with files having set \origin with wrong value. OK. No, I think it is the write which tries to change encoding. With your changes in master today the problem vanished for me. So setting the encoding at the

Re: Beta1 is slow on undo

El 15.10.2017 a las 18:58, Scott Kostyshak escribió: Uwe, can you check the file that racoon attached at [1] to see if you can reproduce... Right after (3) do you see a small delay, compared with when you do the above on 2.2.3? Dear Scott, I get a small delay but it is as long as in LyX

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 16.10.2017 a las 23:38, Kornel Benko escribió: This leads to following output for e.g. Additional.lyx b'#LyX 2.3 created this file. For more info see http://www.lyx.org/' Hmm, but why do we need to modify the doc files? I mean why can't we just use them as they are and omit

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 16.10.2017 a las 11:17, Kornel Benko escribió: Please replace the print statement print(SubstituteDataInLine(line[:-1])) with sys.stdout.write(SubstituteDataInLine(line[:-1])+'\n') This lead to "python UnicodeEncodeError: 'charmap' codec can't encode character" However, I

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 15.10.2017 a las 23:07, Kornel Benko escribió: As I think I proposed in the attached part in other mail. Essentially, there is the change of open(file) to codecs.open(file, 'r', 'UTF-8') Thanks Kornel, unfortunately this does not work. Changing in ReplaceValues.py for

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 14.10.2017 a las 21:09, Kornel Benko escribió: What is the exact directory name of Additional.lyx on your platform? D:\LyXGit\2.3.x\lib\doc (like all other doc files) Check also \origin part of Additional.lyx. it is correctly this: \origin /systemlyxdir/doc/ Can it be that python

Re: compilation of LyX 2.3 fails with Python 3.6.2

Is there some reason we can't use Python 3.5? You bundle this with the application, right? I tried now the latest Python 3.5 and today's 2.3 branch and get this error: Generating Additional.lyx Traceback (most recent call last): File

Re: additional manual - link correction for elyxer

Am 07.10.2017 um 14:19 schrieb Pavel Sanda: Uwe, do we still ship elyxer by default in windows > If yes, is there still some major bug why we can't use our internal HTML export? Yes. Our HTML export is still not usable. I opened some bug reports:

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 03.10.2017 a las 06:27, Richard Heck escribió: This seems a completely different issue. We're encountering an error when reading whatever the input file is. OK, should I report it to our bugtracker? Is there some reason we can't use Python 3.5? You bundle this with the application,

Re: compilation of LyX 2.3 fails with Python 3.6.2

El 02.10.2017 a las 21:24, Richard Heck escribió: The error being reported is that there is an escape sequence "\o", which is presumably produced by this code in CMakeList.txt:... Is the \\o there leading to a \o in argument to the script? Uwe, you could try removing the double backslash in

Re: Plus 1 for non-documentation patches

El 30.09.2017 a las 19:55, Scott Kostyshak escribió: Uwe it's up to you if you want a policy for documentation-related patches. I will be off from Tuesday for one week. I am sorry for that. Therefore I cannot work on a build for RC1 before. Concerning the docs, please commit with change

Re: hyphen and dashes documentation

El 30.09.2017 a las 19:36, Scott Kostyshak escribió: What is the procedure for upload? Uwe, how should Günter proceed? Upload it with change tracking so that the new info can be distributed to the other langue versions as well. Please do so right now if possible because i will be off

compilation of LyX 2.3 fails with Python 3.6.2

Dear colleagues, after a long time I had few hours to work on LyX. I used it to test if our new release will work with Python 3.6. It works so far, except of the following issue. This problem is new, at least the last time I tested in June I did not encounter it: Generating

Re: Any rc1 blockers?

El 12.09.2017 a las 18:49, Scott Kostyshak escribió: Thanks. Uwe, please go ahead. Done. regards Uwe

Re: Any rc1 blockers?

El 10.09.2017 a las 01:38, Uwe Stöhr escribió: Just the patch for http://www.lyx.org/trac/ticket/10679 should go in before. Jürgen found now a fix. Meanwhile I testes LyX 2.3 a lot the last 2 days. It is stable for my needs. Concerning libiconv 1.15, there are not yet opinions. Concerning

Re: iconv warnings

El 10.09.2017 a las 14:18, Uwe Stöhr escribió: I just compiled the current 2.3.x branch to perform some final tests. I noted some avoidable compiler warnings in libiconv, see below I reported the warnings to the email address and got already a reply. They will analyze the signed/unsigned

upgrading to libiconv 1.15 for LyX 2.3

While reporting compiler warnings in libiconv 1.14 I noticed that version 1.15 was released in February this year. So I grabbed the sources from https://ftp.gnu.org/pub/gnu/libiconv/ and updated them in our git master. It compiles fine and works fine here. I don't know about Linux. If it is

iconv warnings

I just compiled the current 2.3.x branch to perform some final tests. I noted some avoidable compiler warnings in libiconv, see below. The question is if we should or could fix this? If we don't do this, does anybody know where I can or should report this? There is a github page:

Re: necessary commit to compile LyX 2.3 on Windows

El 09.09.2017 a las 21:03, Scott Kostyshak escribió: OK to backport to the 2.3.x branch? Yes, Done now. regards Uwe

Re: Any rc1 blockers?

El 08.09.2017 a las 04:30, Scott Kostyshak escribió: I think we should start thinking about rc1. Fine with me. Just the patch for http://www.lyx.org/trac/ticket/10679 should go in before. Then the new 2.3.0 feature of supporting SVG+text files will also work under Windows. regards Uwe

necessary commit to compile LyX 2.3 on Windows

Hi Scott, I just returned and tried to compile master. This way I noted that I could not compile because of missing \origin tags in the Japanese docs. So for the next release tarball of LyX 2.3, this commit must be part of it:

Re: Complaints about LyX on Mac

On 23.08.2017 12:47, Jean-Pierre Chrétien wrote: If a MacOS user has not inskscape nor librsvg installed I don't know macOS but the correct solution should be to check what SVG image conversion program is available on the computer and set ths automatically to the LyX preferences when LyX is

Re: 404 on manuals on lyx.org

El 15.08.2017 a las 11:43, Tommaso Cucinotta escribió: Great! One minor comment: probably the order of manuals might be exactly reversed, Hi Tommaso, thanks for having a look. As it is a Wiki please change it as you like. In the past I already had this sorting: Tutorial UserGuide Math

Re: 404 on manuals on lyx.org

El 13.08.2017 a las 15:04, Uwe Stöhr escribió: damn, I repaired this already few months ago. I also complained about this automatic permission removal at my hoster... it turned out that the Documentation folder even got lost. I set it now again and updated the manuals to LyX 2.2.3: http

Re: today's mythes commits introduced MSVC warnings

El 13.08.2017 a las 09:55, Jürgen Spitzmüller escribió: It's better if you do hat yourself, in case there are questions. https://github.com/hunspell/mythes/issues OK, I will so so. thanks and regards Uwe

Re: 404 on manuals on lyx.org

El 11.08.2017 a las 08:35, Christian Ridderström escribió: I can't do an anonymous login to ftp://ftp.lyx.de. I can do an anonymous login to http://ftp.lyx.de. I am _not_ able to see the subfolder /Documentation/, so it's gone, moved or permissions changed. Hi Christian, damn, I repaired

Re: today's mythes commits introduced MSVC warnings

El 12.08.2017 a las 18:25, Uwe Stöhr escribió: Compiling current master gives me now:... OK, it seems there were in before. Moreover commit http://www.lyx.org/trac/changeset/8c2e5bfc2065d2d320109c0bbd749cd608e4bf6a/lyxgit squashed 2 compiler warnings. So please excuse the noise. Jürgen

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