-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Babel-french’s "og=«, fg=»" creates wrong space for "«" in bibliography #48
Comments
For the moment, I solved this issue with: \makeatletter
\renewcommand*{\@frenchquotespace}{}
\makeatother It seems it lets Babel-french automatically manage the insertion of non-breaking space. |
Isn't this a question of picking one or the other method? |
With My MWE is not ideal because this problem shows up in bibliography (or other environments in which we cannot really type everything). |
I'm not seeing a good fix here: it really is an either-or. |
I didn't see this issue before and discovered it by myself (BTW, it isn't an issue with \DeclareQuoteStyle[quotes]{french}
{\og}
{\fg}
{\textquotedblleft}
{\textquotedblright} as shown by the following MWE: \documentclass{article}
\usepackage[main=french]{babel}
\frenchsetup{og=«, fg=»} % Remove these options then no problem!
\usepackage[autostyle]{csquotes}
\DeclareQuoteStyle[quotes]{french}
{\og}
{\fg}
{\textquotedblleft}
{\textquotedblright}
\begin{document}
This « kind » of space. % Good
This «kind» of space. % Good
This \enquote{kind} of space. % Good as well
\end{document} Would be nice if this setting could be implemented in |
Hello,
It seems this configuration (MWE) :
creates a wrong (longer) space, like
This « kind » of space
.It is explained in the French version of Babel-french manual; I added myself the last sentence to the shorter English one (link):
It seems we are exactly in the described case.
If I remove the
og=«, fg=»
options, it works well, but I enable it because I have the characters directly on my keyboard (as well as thin and non-breaking spaces).Don’t hesitate to tell me if it is already known and that I missed a compatibility option somewhere…
Sincerely.
The text was updated successfully, but these errors were encountered: