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

[Uwe Stöhr]

From: Jürgen Spitzmüller Sent: Montag, 15. Juni 2015 10:40‎ (Our new \LyX handling seems to be buggy btw.) In which sense? See my bug report about "unintuitivity". OK, it's not buggy.   Pandoc uses the UTF-8 character encoding for both input and output. If your local character encoding is not UTF-8, you should pipe input and output through iconv: iconv -t utf-8 input.txt | pandoc | iconv -f utf-8 What do you propose? You must take care that the LaTeX files are converted to utf8 before they get passed to pandoc, notwithstanding the encoding selected in LyX.. Yes but what di you propose to achieve this?   (On my PC the encoding for output TeX files is already UTF8.) But you cannot make that a general condition. Sure, I only wanted to say that I cannot test other encodings easily.   I can convert a very simply document consisting of the string "test" only, but then pandoc adds preamble stuff (@path/home/jspitz//) to the ODT document! The same here on my PC. This should be reported to the Pandoc people. I fear there will be many more cases like this. I propose to test this a bit more. If it turns out that pandoc does more harm than good (or requires a more complex integration on our side), revert it. OK. Feel free to revert it before LyX 2.2 if there are too many problems Thanks and regards  Uwe