From: Adam Sampson <azz@us-lot.org>
To: law <lkml@tlinx.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: utf8 or utf-8
Date: Fri, 23 Jan 2004 13:35:06 +0000 [thread overview]
Message-ID: <y2a65f2n5yt.fsf@cartman.at.fivegeeks.net> (raw)
In-Reply-To: <4010108F.2090408@tlinx.org> (lkml@tlinx.org's message of "Thu, 22 Jan 2004 10:03:59 -0800")
law <lkml@tlinx.org> writes:
> Should all references be UTF8 or utf-8?
>From Markus Kuhn's excellent Unicode FAQ:
"The official name and spelling of this encoding is UTF-8, where UTF
stands for UCS Transformation Format. Please do not write UTF-8 in any
documentation text in other ways (such as utf8 or UTF_8), unless of
course you refer to a variable name and not the encoding itself."
<http://www.cl.cam.ac.uk/~mgk25/unicode.html>
--
Adam Sampson <azz@us-lot.org> <http://offog.org/>
prev parent reply other threads:[~2004-01-23 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 18:03 law
2004-01-23 13:35 ` Adam Sampson [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=y2a65f2n5yt.fsf@cartman.at.fivegeeks.net \
--to=azz@us-lot.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome