From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: biber: update to 2.16
Date: Mon, 14 Jun 2021 08:15:37 +0200 [thread overview]
Message-ID: <20210614061537.KdRXv5Fiinyv719rcLom_xwdh0J1zsdas5BpxoFokCo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31449@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/31449#issuecomment-860404102
Comment:
Nothing important, let's wait.
```
Revision history for Biber
2.16 (2020-12)
* Better support for Unicode on Windows (10 1803+) with the
--winunicode option
* Option "output_macro_fields" no longer does anything as macro
fields are auto-detected.
* New options "output_no_macrodefs" and "output_all_macrodefs" control
BibTeX macros (@STRING) output for bibtex format output.
2.15 (2020-08)
* Added --output-legacy-dates and --output-field-replace options to
aid in outputting legacy bibtex format in tool and non-tool mode
* UTF-8 filenames supported on Windows
* INCOMPATIBLE CHANGE - datasource globbing now has to be turned on
explicitly with the --glob-datasources option. Globbing causes
some issues with UTF8 encoding detection on some OSes and since it
is a niche requirement, it is turned off by default.
* DEPRECATION WARNING - The BBLXML output format will be removed in
version 4. It is rarely used and complicates test suite maintenance
considerably.
```
next prev parent reply other threads:[~2021-06-14 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 11:19 [PR PATCH] " dkwo
2021-06-14 3:00 ` ericonr
2021-06-14 3:00 ` ericonr
2021-06-14 6:15 ` dkwo [this message]
2021-06-28 12:07 ` [pending perl 5.34] " dkwo
2021-06-28 12:07 ` [PR PATCH] [Closed]: " dkwo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210614061537.KdRXv5Fiinyv719rcLom_xwdh0J1zsdas5BpxoFokCo@z \
--to=dkwo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).