Open user227621 opened 1 year ago
@user227621 You don't necessarily need to specify the language as class option, you could also pass it to the translator package:
\PassOptionsToPackage{ngerman}{translator}
\documentclass{beamer}
\usepackage[ngerman]{babel}
....
@samcarter That also works, but is not intuitive either. If the beamer
class does not support enabling translations by specifying a language option for the babel
package (this is how it works with most other classes), I think there should be an explanation in the beamer user guide on how to specify a language correctly to get all translations.
If a language is specified as a package option for
babel
, some words are correctly translated while others are not:(The correctly translated words are probably handled by
babel
's translation mechanism, while the other words are handled by thetranslator
package.)However, if a language is specified as a class option for
beamer
, all translations are applied correctly:From a user's point of view, this is surprising because the
beamer
user guide does not mention that you have to specify the language as a class option to get correct translations. With other classes you don't have to do this either.Apparently the
translator
package does not check whether a language is set e. g. by thebabel
package, but needs a language option itself. Is this a bug or is this by design? If this is not a bug, I would suggest adding an explanation in thebeamer
user guide on how to specify a language correctly to get all translations.On the other hand, the
translator
user guide statesThis sounds as if
translator
could in principle apply its translations even if the language is only specified as ababel
option by looking at the language at the beginning of the document.