mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Eric Pruitt <eric.pruitt@gmail.com>
To: musl@lists.openwall.com
Subject: Updating Unicode support
Date: Mon, 22 Jan 2018 17:54:49 -0800	[thread overview]
Message-ID: <20180123015446.vera7ocpvgaqvkss@sinister.lan.codevat.com> (raw)

NOTE: When I first started writing this email, I didn't realize musl's
Unicode property table had recently been updated, but I noticed
<https://git.musl-libc.org/cgit/musl/commit/?id=c72c1c5> when I was
looking up commit IDs to cite. I'm leaving most of the verbiage below
unchanged since I think it adds useful context.

The Unicode property data used by musl has not been updated in quite
some time, and due to changes introduced in recent publications of the
Unicode standard, musl's width data is incorrect for many symbols --
notably emoji. This can lead to rendering glitches in terminals when
some applications are not built with musl; for example, my terminal
emulator is dynamically linked against a version of GNU libc that
supports Unicode 9 (released June 21, 2016) whereas musl's table was
lasted updated in 2011 or 2012 (commit 1b0ce9a).

To resolve this problem, I wrote a drop-in replacement for musl's
wcwidth(3) implementation that uses utf8proc
(https://github.com/JuliaLang/utf8proc) as the source of truth. You can
find the code for this at
<https://github.com/ericpruitt/static-unix-userland/blob/42cbdbb/utf8proc-wcwidth/utf8proc-wcwidth.c>.
I am wondering if the musl developers would consider accepting a patch
that implements optional / configurable support for utf8proc. The
utf8proc-wcwidth.c file I linked to includes some additional code
unrelated to musl making it possible to use the file as an LD_PRELOAD
library. The LD_PRELOAD stuff would **not** be include in the proposed
patch. I'm also investigating implementing the Unicode Collation
Algorithm (https://unicode.org/reports/tr10/) for wcscoll(3); would that
be of interest?

Thanks,
Eric


             reply	other threads:[~2018-01-23  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  1:54 Eric Pruitt [this message]
2018-01-23 23:38 ` Rich Felker
2018-01-24  0:51   ` Eric Pruitt
2018-01-24  6:26     ` Eric Pruitt
2018-01-24 21:45       ` Rich Felker
2018-01-24 22:22         ` Eric Pruitt
2018-01-24 21:48       ` Rich Felker
2018-01-24 22:25         ` Eric Pruitt
2018-01-24 22:53           ` Eric Pruitt
2018-01-24 23:32             ` Rich Felker

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=20180123015446.vera7ocpvgaqvkss@sinister.lan.codevat.com \
    --to=eric.pruitt@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).