-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Closed
Labels
Description
Explain the problem.
#7562's move to babel has forced me to confront its use in the default template
Several issues arise in using babel over polyglossia
- Language loading from babel has some problems that I haven't been able to fully trace. Suffice to say that the wiki advice to pass
provide=*does not work well enough to just dump the entire used-language list in it. What works consistently for me is to use\babelprovide[langopts]{lang}. Note that some of these (especially arabic, hebrew) might want to pass per-language options, cf end of the linked page and 1.23 in manual) -
lang: he-ILdoesn't work underlualatex, complaining ofRight-to-Left Support Error: use TeX--XeT or e-TeX engine.. If the global language setting (indocumentclass) is removed, (andmainpassed to the main language's\babelprovide), this is no longer a problem. - RTL languages need
babelto be passed abidiparameter, set todefaultunderxelatexandbasicunderlualatex.pdflatexisn't supported bybabelhere. Note this also means thebidipackage doesn't need to be invoked explicitly. - Per-language fonts aren't supported. Worse, the
header-includesexpansion in the default template occurs beforebabelis imported, so a simple\babelfontinvocation cannot be added inheader-includes. However, if a single font covers all uses, this can be mitigated by just settingmainfont.
Pandoc version?
Self-built 6742e77 (2.14.2)
Reactions are currently unavailable