Here is a minimal example:


Hallo Welt!

And here is the error message:


Package polyglossia Warning: \setlocalhyphenmin useless for unknown language ger
man on input line 6.

Package polyglossia Warning: You asked for `ngerman' but only `german' hyphenati
on is available! on input line 68.

! You can't use `\relax' after \the.
<recently read> \l@german 

l.3 \select@language {german}


Setting \setdefaultlanguage{english} works well.

Thanks Georg

Update: The minimal example above works well if german is replaced by ngerman. Nevertheless, adding the line \usepackage{biblatex} again produces an error. Here is a minimal example:



Hallo Welt!

Here is the error message:


Package biblatex Warning: Upgrade package 'polyglossia' to >v1.42.0 recommended.

! Package biblatex Error: No default polyglossia language defined.

See the biblatex package documentation for explanation.
Type  H <return>  for immediate help.

l.6 \begin{document}


closed as off-topic by moewe, TeXnician, Troy, Mensch, Masroor May 28 '17 at 14:06

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    I added an issue to the polyglossia bug tracker. github.com/reutenauer/polyglossia/issues/129 – Ulrike Fischer Feb 6 '16 at 16:02
  • 3
    using ngerman instead of german avoids the error but doesn't solve the underlying problem. I suggest to use \usepackage[ngerman]{babel} until polyglossia and/or babel is updated (or go back to the previous babel). – Ulrike Fischer Feb 6 '16 at 22:46
  • 2
    I'm still waiting for a polyglossia update ... I raised a ticket there a while ago. – PLK May 29 '16 at 20:36
  • 2
    As of today (October 1, 2016) neither example raises errors, provided in the second one the language call is according to polyglossia rules, that is, german and not ngerman. – egreg Oct 1 '16 at 22:15
  • 4
    I'm voting to close this question as off-topic because the problem can not be reproduced any more. It was due to several bugs in several packages, and the actual problem shifted over time. – moewe May 28 '17 at 13:36