linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Eger <eger@havoc.gtf.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UTF-8ifying the kernel source
Date: Fri, 5 Mar 2004 18:24:25 -0500	[thread overview]
Message-ID: <20040305232425.GA6239@havoc.gtf.org> (raw)
In-Reply-To: <20040304100503.GA13970@havoc.gtf.org>

There are now three patches available, and some work left to go.

The first patch hasn't changed, still the trivial ISO Latin-1 => UTF-8.

The second patch takes care of a lot of wrong and/or unneeded non-ASCII.

The third patch concerns 8-bit characters embedded in C strings.
These are almost always output to devfs or proc.  The characters used are
the degrees symbol (for ppc temp. sensors) and mu (for micro-seconds).
I do not want to make a value judgement on what the kernel outputs
to userspace, so I leave the strings the same.  However, C99 makes it
implementation defined how the source character set is translated to
the character set in the compiled binary...  Therefore, I've taken the
raw octets and converted them in the source file to octal constants in
the strings, just to make sure cc doesn't mangle things if you set your
locale differently...

http://www.yak.net/random/linux-2.6.3-utf8-cleanup-auto.diff.bz2
http://www.yak.net/random/linux-2.6.3-utf8-cleanup-wrong.diff
http://www.yak.net/random/linux-2.6.3-utf8-cleanup-cstrings.diff

-dte


Un-needed/wrong non-ASCII characters (patch 2)
==============================================
drivers/video/amifb.c	- +- sign (NOTE: X's .ttf files just don't have it)
Documentation/i2c/i2c-protocol	- NBSP, but why? (made regular space)
arch/i386/kernel/cpu/cyrix.c	- NBSP, but why? (made regular space)
include/linux/802_11.h - why the non-standard dash? (made regular dash)
scripts/docproc.c	- why the bizarre spelling for specific? (fixed)
fs/ext2/xattr.c	- bad ASCII art (made regular pipe - fixed)
fs/ext3/xattr.c	- bad ASCII art (made regular pipe - fixed)
arch/arm/nwfpe/fpopcode.h	- line-drawing characters (fixed)
include/asm-m68k/atarihw.h	- 0x94? no, it's an ö, for Björn
include/asm-m68k/atariints.h	- 0x94? no, it's an ö, for Björn

C strings - (patch 3)
=====================
arch/ppc/platforms/proc_rtas.c	-  a C string w/"degrees": exports to proc
arch/ppc64/kernel/rtas-proc.c	-  a C string w/"degrees": exports to proc
drivers/macintosh/therm_adt7467.c	- temperature reporting (degrees sign)
	- several printk's, output to a devfs interface, MODULE_PARAM_DESC(), 
drivers/mtd/chips/cfi_probe.c	- time reporting (micro sign) 
	- printk's in the DEBUG code
drivers/net/wireless/netwave_cs.c	- module version string 
   (author's name - but it doesn't seem to be *used* for anything...)

BELOW HERE not fixed...

(was going to be fixed w/ patch, but, umm, huh?)
==================================================
arch/v850/kernel/as85ep1.ld	- according to Miles Bader, 
	it's EUC-JP in the comments, and e.g. as85ep1.c uses ISO-2022-JP...
drivers/char/ftape/lowlevel/fdc-isr.c	- WTF? shit in the comments
fs/afs/vlclient.h	- a degrees sign, but why? (author says he'll get it)
drivers/scsi/dc395x.c	- C debug strings... is this chinese traditional?
Documentation/networking/tms380tr.txt	- DOS-style ASCII art 

Other - (i'd convert it, but...)
================================
drivers/pci/pci.ids	- I don't know what program processes this...
drivers/ieee1394/oui.db	- I don't know what program processes this...

Machine / charset specific shite - (does anything need to be done?)
===================================================================
arch/m68k/hp300/hp300map.map	- maps to "char"s.. grr
drivers/char/defkeymap.map	- a map file... maps to "char"s.. grr
drivers/char/qtronixmap.c_shipped	- maps to "char"s.. grr
drivers/char/qtronixmap.map	- maps to "char"s.. grr
drivers/tc/lk201-map.c_shipped	- maps to "char"s.. grr
drivers/tc/lk201-map.map	- maps to "char"s.. grr
drivers/acorn/char/defkeymap-l7200.c	- maps to "char"s.. grr
arch/s390/kernel/ebcdic.c	- comments on a keymap table
drivers/video/console/font_8x16.c	- comments on a keymap table 
drivers/video/console/font_8x8.c	- comments on a keymap table 
drivers/video/console/font_pearl_8x8.c	- comments on a keymap table 
drivers/s390/ebcdic.c	- comments on a keymap table

Noise from userland (this I won't be touching)
==============================================
Documentation/networking/ethertap.txt	- random crap cat'd from /dev/tap0
Documentation/s390/Debugging390.txt	- weird gdb output


  parent reply	other threads:[~2004-03-05 23:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 10:05 [PATCH] UTF-8ifying the kernel source David Eger
2004-03-04 10:19 ` Meelis Roos
2004-03-04 10:32   ` Måns Rullgård
2004-03-04 21:51 ` Alex Belits
2004-03-05  8:26 ` Miles Bader
2004-03-05 20:01   ` H. Peter Anvin
2004-03-05 21:00     ` Mike Fedyk
2004-03-05 21:02       ` H. Peter Anvin
2004-03-05 21:17         ` Måns Rullgård
2004-03-05 21:26           ` Charles Cazabon
2004-03-05 21:20       ` David Eger
2004-03-05 23:24 ` David Eger [this message]
2004-03-05 23:33   ` H. Peter Anvin
2004-03-06 11:08     ` Xavier Bestel
2004-03-06 11:14       ` Måns Rullgård
2004-03-09  0:30       ` H. Peter Anvin
2004-03-09  9:49         ` Xavier Bestel
2004-03-06 13:33   ` Other bizarre thing... backspaces? David Eger
2004-03-06 14:04     ` Måns Rullgård
2004-03-14 16:25       ` Petr Baudis
2004-03-09 12:19   ` [PATCH] UTF-8ifying the kernel source Geert Uytterhoeven
2004-03-05 13:21 paolo ciarrocchi

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=20040305232425.GA6239@havoc.gtf.org \
    --to=eger@havoc.gtf.org \
    --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;
as well as URLs for NNTP newsgroup(s).