I ran into a weird problem with the \usepackage{datetime2} (with datetime2-english installed). When I run the following code


the date is typeset correctly in both cases (i.e. with the datesep intentionally set to weird values [' &,& '] for demonstration purposes). This shows me, that the en-GB-numeric style seems to be used correctly. Nevertheless, I get three errors

! Package datetime2 Error: Unknown style `en-GB-regional'

and nine warnings

Package datetime2 Warning: No date style `en-GB-regional' defined on input line[...]

The same is true for en-US. However, in both cases there is absolutely no problem when I set useregional=text. Am I doing something wrong or is this a bug?

  • @ChristianHupfer Nope, that makes things worse. The errors disappear, but only because then \today is redefined by babel and for \DTMdisplaydate uses the default instead of en-GB. So both dates are then not in the format I want, and worse not even consistently formatted. In the datetime2 manual this is hinted at and there also datetime2 is always loaded after babel – Manuel Weinkauf Apr 8 '15 at 13:54
  • Imho this is a typo at the end of datetime2-en-GB.ldf. \DTMsetstyle{en-GB-regional} should be \DTMsetstyle{en-GB-numeric} – Ulrike Fischer Apr 8 '15 at 13:55
  • @UlrikeFischer So you think it is a bug the author/maintainer should be informed about? – Manuel Weinkauf Apr 8 '15 at 13:57
  • Yes, write Nicola. – Ulrike Fischer Apr 8 '15 at 13:57

It turned out that this was truly a minor bug. It has now been fixed in v. 1.01 of datetime2-english.

Bug Report

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.