In the section 3.1 "Guidelines for contributed languages", the suggestion to use
\bbl@save and \bbl@savevariable is misleading, as these functions don't exist.
The most likely explanation is a mix up with the confusingly close named
\babel@save and \babel@savevariable.
Patch:
--- babel.dtx~ 2022-12-16 09:23:14.948972649 +0100
+++ babel.dtx 2022-12-16 09:23:31.659677473 +0100
@@ -4421,8 +4421,8 @@
also use the new tools for encoded strings, described below.
\item Avoid adding things to |\noextras|\m{lang} except for umlauthigh
and friends, |\bbl@deactivate|, |\bbl@(non)frenchspacing|, and
- language-specific macros. Use always, if possible, |\bbl@save| and
- |\bbl@savevariable| (except if you still want to have access to the
+ language-specific macros. Use always, if possible, |\babel@save| and
+ |\babel@savevariable| (except if you still want to have access to the
previous value). Do not reset a macro or a setting to a hardcoded
value. Never. Instead save its value in |\extras|\m{lang}.
\item Do not switch scripts. If you want to make sure a set of glyphs
In the section 3.1 "Guidelines for contributed languages", the suggestion to use
\bbl@save
and\bbl@savevariable
is misleading, as these functions don't exist. The most likely explanation is a mix up with the confusingly close named\babel@save
and\babel@savevariable
. Patch: