From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HK_RANDOM_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 26504 invoked from network); 16 Dec 2023 19:43:43 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 16 Dec 2023 19:43:43 -0000 Received: (qmail 5504 invoked by uid 550); 16 Dec 2023 19:43:11 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 5472 invoked from network); 16 Dec 2023 19:43:10 -0000 From: =?UTF-8?q?Pablo=20Correa=20G=C3=B3mez?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=postmarketos.org; s=donut; t=1702755808; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=audl2svwtahvE2PlG+ZPf2mYpXe6id/u03zJGYiiip8=; b=PEk/MlGwJvUeb+S8ara1MZ//DmQWaAD5WnSER+FWoNu3qeyrX+2TO08Oi2090MkBAGxAOD 8M5wjSGmbzE3dJldRcUg0USlNZ9giiNkwGB9s3ZUhziR8bhKKw45Tc2T9BngXxp87XVCcW V2lpWlLh/yhqut96vK4TLtPFaUkTM5M= To: musl@lists.openwall.com Cc: =?UTF-8?q?Pablo=20Correa=20G=C3=B3mez?= Date: Sat, 16 Dec 2023 20:36:42 +0100 Message-ID: <20231216194325.23580-1-pabloyoyoista@postmarketos.org> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: [musl] [PATCH 0/2] Support printing localized RADIXCHAR From: Pablo Correa Gómez 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