lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 27 Oct 2008 16:03:59 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Martin Schwidefsky <schwidefsky@...ibm.com>, Heiko Carstens <heiko.carstens@...ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, Greg Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org Subject: Re: [GIT PULL/RESEND] kernel message catalog patches > And as for the actual explanations: either they need to be totally outside > the kernel (in a project of their own), or they'd need to be "kernel-doc" > style things that are _in_ the source code. Not in Documentation/. Not > separate from the printk() that they are associated with. You really don't want 32 languages in mixed left/right rendering with multiple fonts in your kernel source. At least not with most editing and viewing tools.... User space uses message catalogues and has tools for maintaining them which make using any other format somewhat dumb. They extract strings using _("hello") type wrappers to identify what are translatable strings so if the kernel source has _() macros all the tooling just works and can live outside and way from the kernel. Just needs _() to do the right thing compiled into the kernel and a printk formatting to do the right thing with the result. In truth you don't even need a hash in printk just the ability to make it produce either "Hello my name is 'fred3'" and something like "Hello my name is '%s%d'\0Fred\0\000\000\000\003" The kernel contains the English which should be a pretty passable hash. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists