linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Peter Jones <pjones@redhat.com>,
	linux-kernel@vger.kernel.org, Matthew Garrett <mjg59@coreos.com>,
	Laszlo Ersek <lersek@redhat.com>,
	linux-efi@vger.kernel.org
Subject: Re: [PATCH] lib/ucs2_string: Correct ucs2 -> utf8 conversion
Date: Mon, 15 Feb 2016 11:12:49 +0000	[thread overview]
Message-ID: <20160215111249.GD2591@codeblueprint.co.uk> (raw)
In-Reply-To: <1455318813-30667-1-git-send-email-jandryuk@gmail.com>

(Cc'ing Laszlo and linux-efi)

On Fri, 12 Feb, at 11:13:33PM, Jason Andryuk wrote:
> The comparisons should be >= since 0x800 and 0x80 require an additional bit
> to store.
> 
> For the 3 byte case, the existing shift would drop off 2 more bits than
> intended.
> 
> For the 2 byte case, there should be 5 bits bits in byte 1, and 6 bits in
> byte 2.
> 
> Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
> ---
> 
> Tested in user space, but not in the kernel.  Conversions now match
> python's unicode conversions.
> 
>  lib/ucs2_string.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
 
Thanks Jason. Peter, Laszlo, any comments?

> diff --git a/lib/ucs2_string.c b/lib/ucs2_string.c
> index 17dd74e..f0b323a 100644
> --- a/lib/ucs2_string.c
> +++ b/lib/ucs2_string.c
> @@ -59,9 +59,9 @@ ucs2_utf8size(const ucs2_char_t *src)
>  	for (i = 0; i < ucs2_strlen(src); i++) {
>  		u16 c = src[i];
>  
> -		if (c > 0x800)
> +		if (c >= 0x800)
>  			j += 3;
> -		else if (c > 0x80)
> +		else if (c >= 0x80)
>  			j += 2;
>  		else
>  			j += 1;
> @@ -88,19 +88,19 @@ ucs2_as_utf8(u8 *dest, const ucs2_char_t *src, unsigned long maxlength)
>  	for (i = 0; maxlength && i < limit; i++) {
>  		u16 c = src[i];
>  
> -		if (c > 0x800) {
> +		if (c >= 0x800) {
>  			if (maxlength < 3)
>  				break;
>  			maxlength -= 3;
>  			dest[j++] = 0xe0 | (c & 0xf000) >> 12;
> -			dest[j++] = 0x80 | (c & 0x0fc0) >> 8;
> +			dest[j++] = 0x80 | (c & 0x0fc0) >> 6;
>  			dest[j++] = 0x80 | (c & 0x003f);
> -		} else if (c > 0x80) {
> +		} else if (c >= 0x80) {
>  			if (maxlength < 2)
>  				break;
>  			maxlength -= 2;
> -			dest[j++] = 0xc0 | (c & 0xfe0) >> 5;
> -			dest[j++] = 0x80 | (c & 0x01f);
> +			dest[j++] = 0xc0 | (c & 0x7c0) >> 6;
> +			dest[j++] = 0x80 | (c & 0x03f);
>  		} else {
>  			maxlength -= 1;
>  			dest[j++] = c & 0x7f;
> -- 
> 2.4.3
> 

  reply	other threads:[~2016-02-15 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 23:13 [PATCH] lib/ucs2_string: Correct ucs2 -> utf8 conversion Jason Andryuk
2016-02-15 11:12 ` Matt Fleming [this message]
2016-02-15 12:19   ` Laszlo Ersek

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=20160215111249.GD2591@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=jandryuk@gmail.com \
    --cc=lersek@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@coreos.com \
    --cc=pjones@redhat.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;
as well as URLs for NNTP newsgroup(s).