Bug Tracker

ID:134 🔗
Status:Closed (Can Not Implement)
Category:tracklang
Version:1.41
Cross-ref:135
Date:2019-08-31 17:58:18
Summary:tracklang doesn't work with newer babel (\babelprovide)

Report

(I couldn't find a category for tracklang and so took the glossaries-extra) newer versions of babel allow to declare the languages after the loading of the package with \babelprovide. tracklang doesn't recognize this. babel also knows now a language nil, but tracklang errors with it.

MWE

\documentclass{article}
%\usepackage[nil]{babel}
\usepackage{babel}
\babelprovide[import=fr]{french}
\babelprovide[import=de,main]{german}
\usepackage{glossaries-extra}

\begin{document}

\ForEachTrackedDialect\mylang{\show\mylang}
\languagename
\end{document}

Evaluation

(I've moved this bug report to the new tracklang category but the version given seems to be for glossaries-extra.sty so it's not clear which version of tracklang you are using. I'm guessing it's 1.3.6.)

The mispelt \AddTrackedLangage error is fixed in version 1.3.7, so unknown languages should now trigger a warning rather than an error. This bug is therefore already fixed.

Version 1.3.8 now defines the undetermined “und” language and defines “nil” as a dialect of that language.

As with polyglossia, if tracklang.sty can't pick up the correct localisation from the language package it will need to be passed to tracklang through package options or explicitly tracked using commands provided in tracklang.tex.

Update 2020-03-02: Since babel doesn't currently provide a list of languages that have been loaded with \babelprovide, there's no way for tracklang (or any other package) to simply access that information. I will therefore have to close this as “can't implement” until babel provides an easy way of detecting which languages have been loaded with that command.

Add comment or return to search results.

Watch This Report

If you would like to be notified whenever updates are made to this report, please fill in your email address in the box below and click on "Notify Me of Changes" button. (Please ensure the address is valid.) Your details won't be passed on to third parties in line with this site's Privacy Policy.

If you supply your name, it will be used in the email greeting, which provides a more personal message, otherwise you'll just get a generic greeting. If you have previously supplied your name when signing up for notifications, you don't need to resupply it unless you want to change it.

If you have previously subscribed to notifications for this report, you can unsubscribe by clicking on the "Stop Notification" button.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional.)
E mail:
Confirm E mail:
Confirm Bug ID:

To unsubscribe from all notifications use the notifications page.

Comment

You can append a comment to the report using the form below. Comments are checked first before being added. Any spam or offensive content will be removed first according to this site's Terms of Website Use. Please bear in mind that I develop and maintain free software in my spare time. If you want commerical level support then you can hire a TeX consultant.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional. If provided, it will be shown with the comment.)
Confirm Bug ID:

You can use the following markup:

[pre]Displayed verbatim[/pre]
[tt]monospace text[/tt]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

Click on the Preview button to preview the message.

Return to search results.