Feature Request (Page 1 of 3)

If you have an account, sign in to associate your post with your account and to subscribe to notifications. If you don’t have an account, you can still use this form as a guest but you won’t receive any notifications.

It can take me a long time to deal with feature requests for free software, and I can’t guarantee that I’ll be able to incorporate your request, but when I do a major update for the particular package or application, I’ll look into it. Please note, this form is for requesting new features. Don’t use it if you simply want to know how to do something. Instead, post your question to a relevant newsgroup, forum or similar site. Before using this form, please consider the following:

Will the feature be useful for multiple documents or is it just specific to your document? If the latter, it’s unlikely to be implemented.
New features add to the overall package load and document build time, therefore there needs to be a trade off between available features and efficient running, so only general use features will be considered.
Can you envisage the feature being activated by a package option or command? In which case, please provide example usage.
Are you asking "please help me with..." or "how do I do...?" If you are, that isn’t a feature request. Please post instead to an appropriate site, such as TeX on StackExchange or The LaTeX Community.
Are you in a desperate, urgent hurry? Don't waste your time using this form. Post to somewhere like TeX on StackExchange or The LaTeX Community. Alternatively, hire a consultant.

Adding a new feature isn’t just a simple matter of inserting a few new lines of code. The package has to be thoroughly tested to ensure the new code doesn’t break existing features. For a package with a high number of options (such as glossaries) this can be quite time consuming.

If the relevant class, package or application isn't listed, then it's not open to feature requests on this site.

glossaries language support: as from version 4.12, the glossaries language support has been separated into independent language modules. You need to install the appropriate language module in addition to installing/upgrading the glossaries package. (You should see a warning message in the transcript if the required module is missing when you build your document.) If you would like a new feature in a language module, please contact the maintainer of that module. If there is no maintainer, you can volunteer using the contact page. Each individual language module is quite small, so please consider volunteering.
Likewise for the datetime2.sty language files.

Please use the GitHub issue tracker for the following:

I’m looking for volunteers to take over the maintenance of the following packages:

I wrote these for other people and don’t use them myself. It would be better if they were developed by someone who actively uses them on a regular basis. If you are willing to take over either of them, contact me and I will notify CTAN.

You may cross-reference another feature request using the “Cross-reference” field on the next page (optional).

The feature request will be checked for spam before being added to the feature tracker.

Since you are not logged in, you will have to periodically check the feature request tracker to find the post.