All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.de>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: String conversions
Date: Wed, 29 Apr 2009 18:12:32 +0530	[thread overview]
Message-ID: <49F84B38.7080308@suse.de> (raw)
In-Reply-To: <38c3c4860904290533g1a62ed85y12005733d5599c33@mail.gmail.com>

> Steve French <smfrench@gmail.com> wrote:
> 
> In looking at various patches for more accurately sizing the required
> buffer needed for conversions to UTF-8, the following question came up
> more than once.
> 
> Functions which do string copying often null terminate the target
> string (single byte of \0), and size strings one byte larger than
> their string name (for UCS-2 this does not work since the null
> termination is two bytes). � Are there local nls codepages in Linux
> kernel which require double null termination (e.g. DBCS asian code
> pages), and if so how do you tell which ones require "double null
> termination?"

A look at fs/nls and supported charsets suggests that the linux kernel
does not support a pure double-byte charsets. Some of the supported east
asian charsets seem to be a superset of ASCII (for e.g TIS 620, Big5)
and only non-ASCII characters are expressed in 2 bytes.


Thanks,

-- 
Suresh Jayaraman

      parent reply	other threads:[~2009-04-29 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 18:45 String conversions Steve French
     [not found] ` <38c3c4860904290533g1a62ed85y12005733d5599c33@mail.gmail.com>
2009-04-29 12:42   ` Suresh Jayaraman [this message]

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=49F84B38.7080308@suse.de \
    --to=sjayaraman@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@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 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.