From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
Jani Nikula <jani.nikula@intel.com>,
ksummit@lists.linux.dev
Subject: Re: Intersphinx ([TECH TOPIC] Kernel documentation)
Date: Sun, 2 Jul 2023 22:46:51 -0400 [thread overview]
Message-ID: <20230703024651.GE1178919@mit.edu> (raw)
In-Reply-To: <CAHk-=wh+BDKMvm97wuqP6_09=oBrEGFkf=Cd_3+W66RvtWM1Tw@mail.gmail.com>
On Sun, Jul 02, 2023 at 11:44:36AM -0700, Linus Torvalds wrote:
> For example, we have this "mkutf8data" program. It can generate our
> utf8data.c file. Allegedly. Nobody ever does. You need the character
> database files to do it.
Well, Gabriel and I have both run it in the past. The main issue is
that the character database files are (a) very large, so we didn't
want to check them into kernel tree, and (b) they get updated on
unicode.org once or twice a year, and most of the time there's no
*point* to update it. Most of the time the Unicode changes are adding
some random Eomji's, or some script that either don't need case
folding, or would only be of interest of some ancient archeologist who
cares about ancient Sumarian (for example), or both.
Most of the time, the only thing we care about case-folding tables.
That's because most installations don't use the Unicode "strict" mode,
since (a) this would annoy Trekkies who want to use the unofficial
Klingon glyphs, which are not recognized by Unicode since they aren't
used by human languages, and (b) in strict mode we would need to take
every single Unicode update when someone wants to use some new emoji
or some new ancient script in filenames.
Cheers,
- Ted
next prev parent reply other threads:[~2023-07-03 2:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:48 [TECH TOPIC] Kernel documentation Jonathan Corbet
2023-06-20 16:02 ` Jani Nikula
2023-06-20 19:30 ` Jonathan Corbet
2023-11-20 12:06 ` Vegard Nossum
2023-11-20 13:50 ` Jonathan Corbet
2023-11-20 14:42 ` Mauro Carvalho Chehab
2023-11-20 14:49 ` Johannes Berg
2023-11-20 20:54 ` Jonathan Corbet
2023-06-29 21:34 ` Intersphinx ([TECH TOPIC] Kernel documentation) Jonathan Corbet
2023-06-30 13:17 ` Jani Nikula
2023-06-30 16:54 ` Theodore Ts'o
2023-06-30 17:11 ` Jonathan Corbet
2023-07-02 1:46 ` Steven Rostedt
2023-07-02 4:56 ` Linus Torvalds
2023-07-02 13:18 ` James Bottomley
2023-07-02 18:32 ` Steven Rostedt
2023-07-02 18:44 ` Linus Torvalds
2023-07-03 2:46 ` Theodore Ts'o [this message]
2023-06-21 11:04 ` [TECH TOPIC] Kernel documentation Thorsten Leemhuis
2023-06-26 14:34 ` Jan Kara
2023-11-11 12:42 ` Vegard Nossum
2023-11-11 15:14 ` Jonathan Corbet
2023-11-20 12:20 ` Vegard Nossum
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=20230703024651.GE1178919@mit.edu \
--to=tytso@mit.edu \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=ksummit@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).