Am Mittwoch, den 07.12.2016, 23:09 +0000 schrieb Guenter Milde: > 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
I am not sure we do not need these ligatures in other cases.
> > > +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.
Not in all cases. My documents, for instance, will break, since I have
activated » and « for the use with csquotes, as many csquotes users do:
\MakeAutoQuote{»}{«}
So literal guillemot glyphs change in output depending on the context.
In parallel, I am using the LyX quotes for static quotes, and if I
enter a guillemot there, I expect it to come out as a guillemet in any
case, thus it needs to be output as a macro or ligature.
> > 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)
What is crucial for most LyX users is the output, not the intermediate
LaTeX source.
> * remove code doubling: currently, shortcomings of the OT1 font
> encoding
> are handled separately for Quote-inset export and Unicode character
> export
This is really just a small code junk.
Jürgen
> 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
>
signature.asc
Description: This is a digitally signed message part
