public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: nikhil <nikhilar2410@gmail.com>,
	openembedded-core@lists.openembedded.org,  sanak@kpit.com
Cc: ranjitsinh.rathod@kpit.com, Sana Kazi <Sana.Kazi@kpit.com>,
	Sana Kazi <sanakazisk19@gmail.com>
Subject: Re: [OE-core] [meta][dunfell][PATCH] busybox: Make high ASCII chars printable
Date: Wed, 29 Mar 2023 08:20:05 +0100	[thread overview]
Message-ID: <53e7d019d34be7a785e67f67ecc5f2c0dff2ac8e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230329064717.2486576-1-nikhilar2410@gmail.com>

On Wed, 2023-03-29 at 12:17 +0530, nikhil wrote:
> Currently busybox utilty "ls" fails to display filenames contains
> UTF-8 characters and replaces with "?".
> 
> Steps to reproduce:
> bin/busybox touch utf_test-Ü
> bin/busybox ls utf_test-* > sample.log
> bin/busybox cat sample.log
> utf_test-??
> bin/busybox hexdump -C sample.log | grep "c3 9c"
> 
> Therefore, above hexdump command is unable to find matching hex value
> for the umlaute character.
> Hence, change the libbb's printable_string() function to allow high ASCII
> characters so that unicode filenames are displayed correctly.
> This issue is not observed in upstream busybox.
> 
> Signed-off-by: Sana Kazi <Sana.Kazi@kpit.com>
> Signed-off-by: Sana Kazi <sanakazisk19@gmail.com>
> Signed-off-by: Nikhil R <nikhilar2410@gmail.com>
> ---
>  .../270-libbb_make_unicode_printable.patch    | 39 +++++++++++++++++++
>  meta/recipes-core/busybox/busybox_1.31.1.bb   |  1 +
>  2 files changed, 40 insertions(+)
>  create mode 100644 meta/recipes-core/busybox/busybox/270-libbb_make_unicode_printable.patch
> 
> diff --git a/meta/recipes-core/busybox/busybox/270-libbb_make_unicode_printable.patch b/meta/recipes-core/busybox/busybox/270-libbb_make_unicode_printable.patch
> new file mode 100644
> index 0000000000..001d2847fe
> --- /dev/null
> +++ b/meta/recipes-core/busybox/busybox/270-libbb_make_unicode_printable.patch
> @@ -0,0 +1,39 @@
> +busybox: make high ASCII chars printable (#7993)
> +
> +Currently busybox utils like "ls" fail to display filenames containing UTF-8
> +characters, replacing any special characters with "?".
> +
> +Change libbb's printable_string() function to allow high ASCII characters so
> +that unicode filenames are displayed correctls.
> +
> +Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
> +Upstream-Status: Pending [https://git.openwrt.org/?p=openwrt/svn-archive/archive.git;a=patch;h=bbca780ca657d894fc457cac8eaaaec9d414bfc8]
> +

Has the patch been submitted to busybox? The upstream we refer to here
is really busybox. The link to openwrt is helpful but we should limit
to any submission to busybox itself for the purposes of upstream-
status.

Cheers,

Richard



  reply	other threads:[~2023-03-29  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  6:47 [meta][dunfell][PATCH] busybox: Make high ASCII chars printable Nikhil R
2023-03-29  7:20 ` Richard Purdie [this message]
2023-03-29 18:07   ` [OE-core] " Khem Raj
2023-03-30  8:48 ` Michael Opdenacker

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=53e7d019d34be7a785e67f67ecc5f2c0dff2ac8e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Sana.Kazi@kpit.com \
    --cc=nikhilar2410@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ranjitsinh.rathod@kpit.com \
    --cc=sanak@kpit.com \
    --cc=sanakazisk19@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox