All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Harwood <rharwood@redhat.com>
To: development@efficientek.com
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	dkiper@net-space.pl, darren.kenny@oracle.com, ps@pks.im,
	dja@axtens.net
Subject: Re: [PATCH v2 0/4] Update gnulib and drop patches
Date: Thu, 27 Jan 2022 11:46:04 -0500	[thread overview]
Message-ID: <jlgo83xunxv.fsf@redhat.com> (raw)
In-Reply-To: <20220126205548.7054a4ff@crass-HP-ZBook-15-G2>

[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]

Glenn Washburn <development@efficientek.com> writes:

> Robbie Harwood <rharwood@redhat.com> wrote:
>
>> fix-width.patch has not merged upstream.  A version has been
>> proposed, but would need significant rewrite.  It doesn't seem worth
>> the effort to carry, and once this changeset merges to grub, it
>> becomes easier to increment our gnulib version if something like it
>> ever does merge there.
>
> Thanks Robbie for updating gnulib, this is something I've been wanting
> to get done. If I'm understanding you correctly, fix-width.patch is
> being dropped but there is not replacement for what it did.

All good questions.  To back up for a moment, my original plan had been
to wait longer and see if we could get a better version of that patch
accepted into gnulib.  However, we're accelerated from that now because
us using an old gnulib is holding up other efforts (and according to my
bug mail this morning, is needed to build with newer gcc/glibc).

> How was this patch functionally being used by GRUB? And what will the
> effects be of dropping it? Looking at the patch maybe one of the
> places its used is in GRUB's help command. If so, does that mean that
> line wrapping when printing help will be affected?

Not totally clear, and there's no commit information to help.  Mostly it
seems to change gnulib's width assumption to be multibyte-character
aware.  I think this could cause lines to not wrap early in locales that
are mutibyte-heavy, but I don't actually know, as I don't speak any
languages that meet that criteria.

gnulib upstream pointed out that this is only papering over the problem
though: it won't work for Chinese, for instance.  (It also won't work
for Thai, but there's nothing that anyone can do there.)

I could be wrong, but I'm actually not sure this affects grub at all.
We're not translated, which I think means that every character we put in
a help string will fit in a single byte under UTF-8.

Be well,
--Robbie

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2022-01-27 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 22:09 [PATCH v2 0/4] Update gnulib and drop patches Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 1/4] Use visual indentation in config.h.in Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 2/4] Drop gnulib fix-base64.patch Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 3/4] Drop gnulib no-abort.patch Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 4/4] Update gnulib version and drop all gnulib patches Robbie Harwood
2022-01-27  3:06   ` Glenn Washburn
2022-01-27 15:08     ` Robbie Harwood
2022-01-27  2:55 ` [PATCH v2 0/4] Update gnulib and drop patches Glenn Washburn
2022-01-27 16:46   ` Robbie Harwood [this message]
2022-01-27 17:28     ` Robbie Harwood

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=jlgo83xunxv.fsf@redhat.com \
    --to=rharwood@redhat.com \
    --cc=darren.kenny@oracle.com \
    --cc=development@efficientek.com \
    --cc=dja@axtens.net \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=ps@pks.im \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.