From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [OT?] Coding Style
Date: 25 Jan 2001 15:33:00 +0200 [thread overview]
Message-ID: <7uYrAXlHw-B@khms.westfalen.de> (raw)
In-Reply-To: <3A6E2C6E.632CDABF@coppice.org>
In-Reply-To: <3A6E2C6E.632CDABF@coppice.org>
steveu@coppice.org (Steve Underwood) wrote on 24.01.01 in <3A6E2C6E.632CDABF@coppice.org>:
> Unfortunately the C standards people don't seem to realise there are
> languages other than English. C99 had perfect timing to introduce UTF8
> Unicode as acceptable in C source. Alas they missed the boat. I have
> been embedding Chinese in C source for years (mostly Big-5 - UTF8 is
> more likely to be troublesome with existing compilers), and have yet to
> hit a significant problem. It isn't standards compliant, though.
Have you *READ* the C99 standard? According to my copy of ISO/IEC
9899:1999, chinese characters in identifiers are quite legal.
And the source is not defined to be UTF8 because C has never defined the
source to be any specific character set; if your character set does not
include the right characters, use \uXXXX or \Uxxxxxxxx.
MfG Kai
-
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-01-25 15:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 15:41 [OT?] Coding Style Jonathan Earle
2001-01-23 15:58 ` Larry McVoy
2001-01-23 16:00 ` Mike Harrold
2001-01-23 16:14 ` Georg Nikodym
2001-01-23 18:05 ` Christopher Friesen
2001-01-23 18:41 ` Mathieu Chouquet-Stringer
2001-01-23 18:44 ` Georg Nikodym
2001-01-23 18:53 ` James Kelly
2001-01-23 16:32 ` Joe deBlaquiere
2001-01-24 1:14 ` Steve Underwood
2001-01-25 13:33 ` Kai Henningsen [this message]
2001-01-24 5:42 ` Brent Rowland
2001-01-24 5:50 ` Andre Hedrick
2001-01-24 9:58 ` Completely offtopic : " Bernd Petrovitsch
2001-01-25 13:25 ` Kai Henningsen
2001-01-25 19:30 ` Harald Arnesen
2001-01-26 0:20 ` James Stevenson
2001-01-23 17:42 ` John Kodis
2001-01-25 13:38 ` Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2001-01-23 22:22 Jonathan Earle
2001-01-23 16:47 Jesse Pollard
2001-01-24 0:07 ` Stephen Satchell
2001-01-22 21:09 Stephen Satchell
2001-01-22 16:42 ` Mark I Manning IV
2001-01-22 23:56 ` Anton Altaparmakov
2001-01-23 0:01 ` Larry McVoy
2001-01-23 6:37 ` Stephen Satchell
2001-01-23 8:37 ` Helge Hafting
2001-01-23 18:58 ` Alan Olsen
2001-01-22 17:53 Jonathan Earle
2001-01-22 16:04 Jonathan Earle
2001-01-22 16:19 ` Mike Harrold
2001-01-22 16:22 ` Larry McVoy
2001-01-22 18:29 ` Richard B. Johnson
2001-01-22 23:20 ` Admin Mailing Lists
2001-01-23 0:54 ` Werner Almesberger
2001-01-23 12:28 ` Steve Underwood
2001-01-23 16:17 ` Nicolas Noble
2001-01-23 21:16 ` David Benfell
2001-01-23 12:52 ` Andrew Morton
2001-01-23 18:10 ` Stephen Satchell
2001-01-22 17:43 ` Gregory Maxwell
2001-01-20 15:32 Anton Altaparmakov
2001-01-20 16:19 ` [OT?] " profmakx.fmp
2001-01-21 5:10 ` Ragnar Hojland Espinosa
2001-01-21 5:50 ` Admin Mailing Lists
2001-01-21 5:58 ` Mike A. Harris
2001-01-21 7:07 ` Josh Myer
2001-01-21 7:20 ` Alan Olsen
2001-01-21 22:40 ` Mo McKinlay
2001-01-22 0:23 ` Admin Mailing Lists
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=7uYrAXlHw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox