Re: Polyglossia, LuaTeX

2015-06-15 Thread Jürgen Spitzmüller
2015-06-16 8:33 GMT+02:00 Jürgen Spitzmüller : > Alas, I do not have time to check the other ones. > However, it would help a lot if you could check whether any of these documents fail for you with LuaTeX, but _not_ with XeTeX. Jürgen

Re: Polyglossia, LuaTeX

2015-06-15 Thread Jürgen Spitzmüller
2015-06-16 1:23 GMT+02:00 Scott Kostyshak : > On Sun, May 17, 2015 at 04:23:14PM +0200, Jürgen Spitzmüller wrote: > > 2015-05-17 15:48 GMT+02:00 Kornel Benko : > > > > > > > Conclusio: LuaTeX + polyglossia introduces no new problems in the tested > > files. > > Jürgen, the commit broke the followi

Re: [patch] fix bug 7657 - Inkscape detection in configure.py

2015-06-15 Thread Georg Baum
Uwe Stöhr wrote: > Am 09.06.2015 um 20:38 schrieb Georg Baum: > >>> Attached is a better patch that does this. It also extends the fix to >>> for libreoffice. >> >> It still has this complicated quoting. I still do not understand why it >> has to be done this way. > > Could you make a proposal t

Re: [patch] check for uncodbale characters in user preamble (bug #9599)

2015-06-15 Thread Jürgen Spitzmüller
2015-06-15 20:46 GMT+02:00 Georg Baum : > Looks good. Ideally I'd prefer to unify the handling of uncodable symbols a > bit more (currently we have several copies of similar code), but this does > not seem to be easy, so I'd say put it in. > I'll do so. Unifiying is certainly a good idea (for aft

Re: [patch] check for uncodbale characters in user preamble (bug #9599)

2015-06-15 Thread Georg Baum
Jürgen Spitzmüller wrote: > The attached patch checks for uncodable glyphs in the user preamble and > issues a warning if such glyphs are found (like we do in many other > situations). > > Comments? Looks good. Ideally I'd prefer to unify the handling of uncodable symbols a bit more (currently

Re: [patch] fix bug 7657 - Inkscape detection in configure.py

2015-06-15 Thread Guenter Milde
On 2015-06-14, Uwe Stöhr wrote: > could you please do me the favor and make a new patch out of mine? I'm > not good in python but then I get your idea correctly, can test it and > maybe fine-tune it for Windows. Patch uploaded to the bug report. Give it a try. Günter

Re: [LyX/master] configure.py: add support for pandoc and docx

2015-06-15 Thread Jürgen Spitzmüller
2015-06-15 1:15 GMT+02:00 Uwe Stöhr : > Am 14.06.2015 um 17:58 schrieb Jürgen Spitzmüller: > > I investigated: pandoc expects utf8 encoded input files. LyX has to take >> care about that. The pandoc manual suggests to go via iconv: >> > > If Pandoc is too buggy, we can revert the support for it.

Re: [LyX/2.1.x] layouttranslations: Arabic update by Hatim

2015-06-15 Thread Kornel Benko
Am Montag, 15. Juni 2015 um 00:59:06, schrieb Uwe Stöhr > Am 09.06.2015 um 09:07 schrieb Kornel Benko: > > > This is only valid if you use 'make', which you doesn't. > > For you (since you use visual studio + cmake) it should be > > # msbuild /t:layouttranslations1 > > from the build director