From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Need for more ISO8859 codepages?
Date: 1 Feb 2001 09:39:05 -0800 [thread overview]
Message-ID: <95c6vp$n7t$1@cesium.transmeta.com> (raw)
In-Reply-To: <4755.137.44.4.15.981028098.squirrel@www.sucs.swan.ac.uk>
Followup to: <4755.137.44.4.15.981028098.squirrel@www.sucs.swan.ac.uk>
By author: "Rhys Jones" <linux-kernel@postwales.com>
In newsgroup: linux.dev.kernel
>
> Hello,
>
> Please forgive a semi-newbie post.
>
> About 18 months ago I patched fs/nls/ to include support for the
> Celtic character set, ISO8859-14. I notice that there are still gaps
> in nls, specifically in ISO8859 codepages 10 to 13.
>
> The missing codepages are for Nordic/Icelandic (ISO8859-10), Thai
> (ISO8859-11), and Baltic Rim (ISO8859-13) languages. I'm still trying
> to determine the status of ISO8859-12 at the moment.
>
> Two questions, really. The general one is whether anyone would find
> these codepages useful. If they would, I'm willing to provide the
> patches in due course. More specifically, can anyone tell me why
> ISO8859-10 (Icelandic etc.) is mentioned in Documentation/Configure.help
> whilst nls_iso8859-10.c is missing from the fs/nls directory?
>
Having them around can never be a bad thing.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 11:48 Need for more ISO8859 codepages? Rhys Jones
2001-02-01 17:14 ` Pierre Rousselet
2001-02-01 17:39 ` H. Peter Anvin [this message]
2001-02-03 21:08 ` Nerijus Baliunas
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='95c6vp$n7t$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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.