From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Perl Unicode-Normalize
Date: Sat, 17 Aug 2019 17:24:00 -0000 [thread overview]
Message-ID: <87a7c7rame.fsf@Rainer.invalid> (raw)
In-Reply-To: <7b057e88-fc87-8761-a473-562f4e3c22fe@cornell.edu> (Ken Brown's message of "Sat, 17 Aug 2019 16:09:19 +0000")
Ken Brown writes:
> The upcoming release of Biber requires Unicode-Normalize-1.26, but we currently
> have 1.25. I know this module is now bundled with perl. Would it be difficult
> for you to update it?
I'd have to start provifding it as an extra package again of course, but
otherwise it should be OK. How imminent is this update?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-17 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 16:43 Ken Brown
2019-08-17 17:24 ` Achim Gratz [this message]
2019-08-17 20:13 ` Ken Brown
2019-08-18 12:50 ` Achim Gratz
2019-08-18 16:24 ` Ken Brown
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=87a7c7rame.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).