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: compilation of LyX 2.3 fails with Python 3.6.2

On 2017-10-23, Helge Hafting wrote: > Den 17. okt. 2017 19:50, skrev Guenter Milde: Hej Helge, thank you for looking into this. >> TODO: find out which encoding is used for the arguments by CMake >> (maybe we need the locale encoding) and eventually adapt the argument >> parsing: >>arg

Re: compilation of LyX 2.3 fails with Python 3.6.2

Den 17. okt. 2017 19:50, skrev Guenter Milde: TODO: find out which encoding is used for the arguments by CMake (maybe we need the locale encoding) and eventually adapt the argument parsing: arg = arg.decode('UTF-8') # support non-ASCII characters in arguments Is that sort of thing

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Montag, 23. Oktober 2017 um 00:08:22, schrieb Uwe Stöhr > 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

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 this

Re: compilation of LyX 2.3 fails with Python 3.6.2

On Sun, Oct 22, 2017 at 11:43:50AM +, Uwe Stöhr wrote: > 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

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: compilation of LyX 2.3 fails with Python 3.6.2

Am Samstag, 21. Oktober 2017 um 20:41:57, schrieb Guenter Milde > On 2017-10-21, Kornel Benko wrote: > > Am Samstag, 21. Oktober 2017 um 13:17:55, schrieb Uwe Stöhr > > > >> El 18.10.2017 a las 15:18, Kornel Benko escribió: > > >> To solve this issue I

Re: compilation of LyX 2.3 fails with Python 3.6.2

On 2017-10-21, Kornel Benko wrote: > Am Samstag, 21. Oktober 2017 um 13:17:55, schrieb Uwe Stöhr >> El 18.10.2017 a las 15:18, Kornel Benko escribió: >> To solve this issue I need the attached patch (which is already in >> master). > I would wait for the patch from Günter. It

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Samstag, 21. Oktober 2017 um 13:17:55, schrieb Uwe Stöhr > 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

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

On Wed, Oct 18, 2017 at 01:18:16PM +, Kornel Benko wrote: > > OK to commit to 2.3. branch? > > Scott? Go ahead. Thanks, Scott signature.asc Description: PGP signature

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Mittwoch, 18. Oktober 2017 um 12:18:39, schrieb Guenter Milde > On 2017-10-18, Kornel Benko wrote: > > Am 17. Oktober 2017 um 17:50:51, schrieb Guenter Milde: > >> On 2017-10-17, Kornel Benko wrote: > > > >> TODO: find out which encoding is used for the arguments by

Re: compilation of LyX 2.3 fails with Python 3.6.2

On 2017-10-18, Kornel Benko wrote: > Am 17. Oktober 2017 um 17:50:51, schrieb Guenter Milde: >> On 2017-10-17, Kornel Benko wrote: >> TODO: find out which encoding is used for the arguments by CMake >> (maybe we need the locale encoding) and eventually adapt the argument >> parsing: >>

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Dienstag, 17. Oktober 2017 um 23:36:52, schrieb Uwe Stöhr > 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

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Dienstag, 17. Oktober 2017 um 17:50:51, schrieb Guenter Milde > On 2017-10-17, Kornel Benko wrote: > > > Am Dienstag, 17. Oktober 2017 um 00:20:02, schrieb Uwe Stöhr > > > >> El 16.10.2017 a las 23:38, Kornel Benko escribió: > > ... > > >> so the

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: compilation of LyX 2.3 fails with Python 3.6.2

On 2017-10-17, Kornel Benko wrote: > Am Dienstag, 17. Oktober 2017 um 00:20:02, schrieb Uwe Stöhr > >> El 16.10.2017 a las 23:38, Kornel Benko escribió: ... >> so the SubstituteDataInLine routine does actually not only replace but >> changes the encoding. > No, I think it

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Dienstag, 17. Oktober 2017 um 00:20:02, schrieb Uwe Stöhr > 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

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

Am Montag, 16. Oktober 2017 um 23:28:13, schrieb Uwe Stöhr > 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') > >

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

Am Montag, 16. Oktober 2017 um 01:43:48, schrieb Uwe Stöhr > 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',

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

Am Sonntag, 15. Oktober 2017 um 19:38:45, schrieb Uwe Stöhr > 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

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

Am Samstag, 14. Oktober 2017 um 21:09:05, schrieb Kornel Benko > Am Samstag, 14. Oktober 2017 um 20:38:04, schrieb Uwe Stöhr > > > Is there some reason we can't use Python 3.5? You bundle this with the > > > application, right? > > > > I tried now the latest

Re: compilation of LyX 2.3 fails with Python 3.6.2

Am Samstag, 14. Oktober 2017 um 20:38:04, schrieb Uwe Stöhr > > 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 >

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: compilation of LyX 2.3 fails with Python 3.6.2

On 10/03/2017 06:23 AM, Uwe Stöhr wrote: > 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? Probably, though note that this problem

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

On 10/02/2017 07:48 PM, Uwe Stöhr wrote: > 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?

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: compilation of LyX 2.3 fails with Python 3.6.2

On 10/01/2017 04:58 PM, Uwe Stöhr wrote: > 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

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