On Wed, 5 Feb 2020 16:23:14 +0100 Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> Le 05/02/2020 à 16:05, V K a écrit : > > So it is obvious that Pandoc understands only quotes signs, but > > not, how to say, commands, it doesn't convert all the \og, > > \guillemotleft, \quotesinglbase, \glqq and so on, but perfectly > > convert signs `` '' << etc. Using csquotes package change > > nothing.Maybe I should load other package? > > Hello, > > While there could be a case made for exporting more portable LaTYeX > when the target is a converter, I think that in this case it makes > sense to open a andoc issue asking for support of these extra macros. > > You can see a list of macros used for quotes here: > https://git.lyx.org/?p=lyx.git;a=blob;f=src/insets/InsetQuotes.cpp;h=d34efa48cd4ed07d920c8c4d969f41e9b286da04;hb=HEAD#l337 I know nothing about Pandoc at all, but the preceding URL, which conveniently lands on the exact subroutine appearing to give translations of quote type UTF-8's, seems the perfect place to just add else if (op == "pandoc") or some other branch that outputs the needful for pandoc. If there isn't a variable representing a pandoc-interfacing output, why not make one and at least have it triggered by a LyX command line argument? Once there's such a variable, VK himself could put in the exact best quote representations for Pandoc, I believe 21 in total, put it back in, and bang, problem solved. Perhaps it's pandoc's job to fix this problem. But if it's as simple as I think it is, it's just too easy to do it on the LyX end to wait for pandoc to do their job. SteveT Steve Litt February 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
