On 2016-12-07, Jürgen Spitzmüller wrote: > [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 07.12.2016, 17:53 +0000 schrieb Guenter Milde: >> +1 "the right thing" for non-TeX fonts >> +1 "the right thing" for HTML (LyX generates utf8-encoded HTML >> documents) > Macros/HTML tags are not "the wrong thing". However, given that other non-ASCII characters are exported as-is, too using literal characters for typographical quotes makes the generated document's source more consistent and easier to read. Also: +1 get rid of the dependance on "TeX ligatures" with non-TeX fonts >> +1 no need to query "fontenc": Unicode charaters are replaced by >> lib/unicodesymbols - this already works reliably for all quote >> characters >> in question. > Querying fontenc is not really something problematic. However, if we can do without, the code becomes simpler and less error-prone. > I really do not see what we will gain here. * consistency: currently, if a user sees a guillemot « on screen, it can be a literal character or a Quote inset and the LaTeX export can be "«" or "\guillemotleft" (depending on the "inputencoding") "<<" (for Quote inset, even if « is supported by the encoding) * remove code doubling: currently, shortcomings of the OT1 font encoding are handled separately for Quote-inset export and Unicode character export I.e. even if we decide to keep the Quotes inset, export as Unicode characters makes the code simpler and the exported documents more consistent. Günter
