On 11/07/2010 11:45 PM, Uwe Stöhr wrote:
Am 07.11.2010 21:59, schrieb Richard Heck:
Shouldn't "Use babel" really be a document setting, rather than a
preference?
Yes, definitively. Babel needs to be deactivated for some document
classes and can cause troubles when using XeTeX. XeTeX has its own
babel replacement and it might be possible that both can interfere.
I'll do this.
Uwe, do you know if layouts can disable babel, with e.g.:
Provides babel 1
This is not yet implemented but is easy to do (the same way we do for
natbib in line 734 of LaTeXFeatures.cpp.). If we implement babel as
document option we should also implement this.
It looks like this is already there, in fact.
...
bool const use_babel = features.useBabel() &&
!tclass.provides("babel");
if (use_babel) {
language_options << features.getLanguages();
if (!language->babel().empty()) {
if (!language_options.str().empty())
language_options << ',';
language_options << language->babel();
}
...
rh
