>> Dear Jürgen,
On 2016-12-13, Jürgen Spitzmüller wrote:
> 2016-12-13 10:34 GMT+01:00 Guenter Milde <mi...@users.sf.net>:
>> > 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.
The options are mentioned in the Changelog of frenchb.pdf:
v2.0d \frenchbsetup: Options og and fg changed: limit the definition to
French so that quote characters can be used in German.
Unfortunately, there is no date given, but it is more then 4 years at
minimum.
...
>> it seems more safe not to use "hard coded" spaces in the LaTeX source.
> We don't do that, do we?
No (with one exception)¹. This remark was rather me thinking aloud,
backtracking from the idea to have the same string inserted for all
exports (i.e. with additional space in French).
¹ exception:
// the preceding space is important here
// FIXME: really? (doesn't make a difference
// with recent babel-french)
qstr = " \\fg";
The first line was an error. It is not important here. "Since ages",
Babel said that ordinary space inside double guillements is optional --
babel-french cares for the correct spacing.
Fixing this would also allow to revert 526b6a4afc285
(no special " \\fg" case required).
Günter
