Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 22 Jul 2003 09:18:32 -0400 | From | Greg KH <> | Subject | Re: [Patch] Non-ASCII chars in visor.c messages |
| |
On Tue, Jul 22, 2003 at 03:09:42PM +0200, Jan Kasprzak wrote: > Greg KH wrote: > : > > : > What do you think about it? > : > : I don't think it's really needed. Why change this, syslog can't handle > : this? It works for me... > : > Yes, syslog can handle this, but in order to parse syslog files > you should have your LC_CTYPE set to something Latin-1 compatible > (which UTF-8 is not, and it is the default on many distros). > > Why Latin-1 and not UTF-8? I think UTF-8 is more "correct", while > ASCII is "works for all". Latin-1 is neither "correct" nor "works for all".
So how do you encode that character in UTF-8?
If we are going to print device names, I want to be correct in their usage...
thanks,
greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |