From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org,
jfs-discussion-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-ntfs-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Steve French <sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
OGAWA Hirofumi
<hirofumi-UIVanBePwB70ZhReMnHkpc8NsWr+9BEh@public.gmane.org>,
Dave Kleikamp <shaggy-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Petr Vandrovec <petr-vPk2MGR0e28uaRcfnNAh7A@public.gmane.org>,
Anton Altaparmakov
<anton-yrGDUoBaLx3QT0dZR+AlfA@public.gmane.org>,
Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Subject: [PATCH 0/8] Support non-BMP characters on UTF-16 filesystems
Date: Wed, 16 May 2012 00:55:48 +0200 [thread overview]
Message-ID: <4FB2DEF4.7030701@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hello, when conducting some automated filesystem tests, I've discovered
that some filesystems are unable to cope with non-BMP characters. While
most usual characters are in BMP, I still think that supporting then is
important. Perhaps, the single most important reason to support them is
that they come up in some personal names. The series has 2 patches to
prepare the ground by changing NLS functions uni2char and char2uni to
work on full unicode_t and another patch for UTF-16 conversion functions.
Remaining 6 patches are for specific filesystems.The filesystems I haven't
fixed are ncpfs and cifs since I don't have the relevant test environment
but it should be easy for someone with one to extend it for them as well.
I've used mainly 2 following characters for test:
茝 Some rare CJK symbol, no idea what it means, picked it up at random.
😁 An emoticon.
I send this explanation and first 2 patches to all concerned parties. Rest
is sent to LKML, linux-fsdevel and relevant filesystem maintaintainer/list only
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org,
jfs-discussion@lists.sourceforge.net,
linux-ntfs-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: Steve French <sfrench@samba.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Dave Kleikamp <shaggy@kernel.org>,
Petr Vandrovec <petr@vandrovec.name>,
Anton Altaparmakov <anton@tuxera.com>, Jan Kara <jack@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH 0/8] Support non-BMP characters on UTF-16 filesystems
Date: Wed, 16 May 2012 00:55:48 +0200 [thread overview]
Message-ID: <4FB2DEF4.7030701@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hello, when conducting some automated filesystem tests, I've discovered
that some filesystems are unable to cope with non-BMP characters. While
most usual characters are in BMP, I still think that supporting then is
important. Perhaps, the single most important reason to support them is
that they come up in some personal names. The series has 2 patches to
prepare the ground by changing NLS functions uni2char and char2uni to
work on full unicode_t and another patch for UTF-16 conversion functions.
Remaining 6 patches are for specific filesystems.The filesystems I haven't
fixed are ncpfs and cifs since I don't have the relevant test environment
but it should be easy for someone with one to extend it for them as well.
I've used mainly 2 following characters for test:
茝 Some rare CJK symbol, no idea what it means, picked it up at random.
😁 An emoticon.
I send this explanation and first 2 patches to all concerned parties. Rest
is sent to LKML, linux-fsdevel and relevant filesystem maintaintainer/list only
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next reply other threads:[~2012-05-15 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 22:55 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-05-15 22:55 ` [PATCH 0/8] Support non-BMP characters on UTF-16 filesystems Vladimir 'φ-coder/phcoder' Serbinenko
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=4FB2DEF4.7030701@gmail.com \
--to=phcoder-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=anton-yrGDUoBaLx3QT0dZR+AlfA@public.gmane.org \
--cc=hirofumi-UIVanBePwB70ZhReMnHkpc8NsWr+9BEh@public.gmane.org \
--cc=jack-AlSwsSmVLrQ@public.gmane.org \
--cc=jfs-discussion-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-ntfs-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=petr-vPk2MGR0e28uaRcfnNAh7A@public.gmane.org \
--cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
--cc=sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=shaggy-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
/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.