2016-12-13 10:34 GMT+01:00 Guenter Milde <[email protected]>:
> Dear Jürgen,
>
> On 2016-12-13, Jürgen Spitzmüller wrote:
> > Am Montag, den 12.12.2016, 22:12 +0000 schrieb Guenter Milde:
>
> >> Unfortunately, with LuaTeX
> ...
> >> the padding of guillemets seems to be "sticky".
>
> > That's https://github.com/reutenauer/polyglossia/issues/68
>
> Yes, so it is hopefully worked on.
> Especially as we cannot do much to change the situation (except for
> preferring Babel with French + other language).
>
Well, polyglossia maintenance has rather slowed down.
> In any case, I hope we can agree that the combination « “ ” »
> should become a style option.
>
Yes, we do.
> >> Why not using literal Unicode characters in the TeX source for all
> >> non-TeX-font documents:
>
> >> • no difference with Babel
>
> > The specific babel macros (e.g., \og, \fg for French) should be used.
>
> This is not required, if the Babel configuration command
> \frenchbsetup{og=«, fg=»} is included after the \usepackage{babel} call.
> (This works for all input encodings that support » and «, i.e. it is sure
> to
> use for non-TeX fonts.)
>
I think this is a rather new feature.
> > I don't know. Babel does not do it, and nobody seems to care.
>
> At least the polyglossia people cared.
>
I have not found any single complaint about the missing feature in babel.
>
> Whether a workaround or a bug report to Babel-French is better, I don't
> know.
>
>
> Considering
>
> >> > https://github.com/reutenauer/polyglossia/issues/141
>
> and a second bug only concerning Babel:
>
> >> With Babel-French, a narrow no-break space and the Babel-inserted
> >> space around double guillemet add up (!).
> >> With Polyglossia,
> "hard coded narrow no-break spaces" are ignored. (OK)
>
> it seems more safe not to use "hard coded" spaces in the LaTeX source.
>
We don't do that, do we?
Jürgen
>
>
> Günter
>
>
