From: "Pablo Correa Gómez" <pabloyoyoista@postmarketos.org>
To: musl@lists.openwall.com
Cc: "Pablo Correa Gómez" <ablocorrea@hotmail.com>
Subject: [musl] [PATCH 0/2] Support printing localized RADIXCHAR
Date: Sat, 16 Dec 2023 20:36:42 +0100 [thread overview]
Message-ID: <20231216194325.23580-1-pabloyoyoista@postmarketos.org> (raw)
From: Pablo Correa Gómez <ablocorrea@hotmail.com>
Since we've been discussing about translations, I've been looking a bit
around, and have found some low-hanging fruit, in the form of improving
printf-family output for localized systems.
I've tried to do the same for strtof family of functions, but I was not
completely sure on how to approach that. Forcing the radix char there
has the problem that numeric values as written for programming stop
being supported, and treating equally a "." and the localized case seems
to not be supported by POSIX. Does anybody have any thoughts about this?
Without that, this patch series might be a bit incomplete, since
certain localized printf outputs would not be possible to ingest in
strtof. Although I'm also unequally unsure if that's a requirement
Pablo Correa Gómez (2):
langinfo: add support for LC_NUMERIC translations
printf: translate RADIXCHAR for floating-point numbers
src/locale/langinfo.c | 2 +-
src/stdio/vfprintf.c | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-16 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 19:36 Pablo Correa Gómez [this message]
2023-12-16 19:36 ` [musl] [PATCH 1/2] langinfo: add support for LC_NUMERIC translations Pablo Correa Gómez
2023-12-16 19:36 ` [musl] [PATCH 2/2] printf: translate RADIXCHAR for floating-point numbers Pablo Correa Gómez
2023-12-16 23:10 ` [musl] [PATCH 0/2] Support printing localized RADIXCHAR Rich Felker
2023-12-17 7:26 ` Markus Wichmann
2023-12-17 22:25 ` Pablo Correa Gomez
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=20231216194325.23580-1-pabloyoyoista@postmarketos.org \
--to=pabloyoyoista@postmarketos.org \
--cc=ablocorrea@hotmail.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).