From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with special characters in filenames
Date: Wed, 18 Mar 2020 20:54:28 +0100 [thread overview]
Message-ID: <20200318205428.6dec3cb9@gmx.net> (raw)
In-Reply-To: <CADLDEKtQdEPVwiKiYHrjpRc6On4sMhHbDRSU4UWq9wnmx2xEEg@mail.gmail.com>
Hello Juerg,
On Sat, 14 Mar 2020 13:03:07 +0100, Juerg Haefliger <juergh@gmail.com> wrote:
> Hi,
>
> I have filenames with umlauts (special German characters) that are
> displayed as '??' in busybox shell. I've tried the below config
> changes to get those umlauts to display properly but it's not
> working. What am I missing?
Maybe
$ export LANG=en_US.utf8
or
$ export LANG=de_CH.utf8
Regards,
Peter
>
> Thanks
> ...Juerg
>
> - BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
> +BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
> +# BR2_ENABLE_LOCALE_PURGE is not set
> +BR2_GENERATE_LOCALE="en_US de_CH"
>
> busybox config fragment:
> CONFIG_LOCALE_SUPPORT=y
> CONFIG_UNICODE_SUPPORT=y
> # CONFIG_UNICODE_USING_LOCALE is not set
> CONFIG_FEATURE_CHECK_UNICODE_IN_ENV=y
> CONFIG_SUBST_WCHAR=63
> CONFIG_LAST_SUPPORTED_WCHAR=767
> CONFIG_UNICODE_COMBINING_WCHARS=y
> CONFIG_UNICODE_WIDE_WCHARS=y
> # CONFIG_UNICODE_BIDI_SUPPORT is not set
> # CONFIG_UNICODE_NEUTRAL_TABLE is not set
> # CONFIG_UNICODE_PRESERVE_BROKEN is not set
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2020-03-18 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 12:03 [Buildroot] Problems with special characters in filenames Juerg Haefliger
2020-03-18 19:54 ` Peter Seiderer [this message]
2020-03-20 6:23 ` Juerg Haefliger
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=20200318205428.6dec3cb9@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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