bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: bug-gnulib@gnu.org
Subject: u8_strconv_to_locale() misbehaves on OSX (Travis CI runner)
Date: Thu, 8 Feb 2018 16:59:25 +0100	[thread overview]
Message-ID: <bbbc3c3e-ff14-ad5f-5874-dba3d7fb3df6@gmx.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1268 bytes --]

Trying to find out why the to_unicode tests of libidn2 fail since a few
months...

It happens on OSX Travis-CI runner, all the infos I have are

$ clang --version
Apple LLVM version 8.1.0 (clang-802.0.42)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
before_install.1

locale_charset() returns with "UTF-8".

u8_strconv_to_locale() and u8_strconv_from_locale() seem not to work as
expected:


One problem seems to be that u8_strconv_to_locale() outputs decomposed
characters, e.g. u8_strconv_to_locale(bücher.de) returns b"ucher.de.

Hex/u32:

Result: U+0062 U+0022 U+0075 U+0063 U+0068 U+0065 U+0072 U+002e U+0064
U+0065)

Expected: U+0062 U+00fc U+0063 U+0068 U+0065 U+0072 U+002e U+0064 U+0065



The second problem is that characters beyond 255 are translated into ?
(U+003f).


Do you have any hints how to fix these problems ?
I would expect u8_strconv_to_locale() to work in a defined manner on
UTF-8 locales - but maybe I am wrong. I could apply a normalization step
in the test itself, but not sure if that is the correct solution.

For problem 2 I see no solution right now.


With Best Regards, Tim



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-02-08 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 15:59 Tim Rühsen [this message]
2018-02-08 17:05 ` u8_strconv_to_locale() misbehaves on OSX (Travis CI runner) Bruno Haible
2018-02-08 19:22   ` Tim Ruehsen
2024-02-23 18:52     ` Bruno Haible

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bbbc3c3e-ff14-ad5f-5874-dba3d7fb3df6@gmx.de \
    --to=tim.ruehsen@gmx.de \
    --cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).