[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070709231221.6ca80ad9@the-village.bc.nu>
Date: Mon, 9 Jul 2007 23:12:21 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Theodore Tso <tytso@....edu>
Cc: Rob Landley <rob@...dley.net>, holzheu@...ux.vnet.ibm.com,
randy.dunlap@...cle.com, jack@...e.cz, kenistoj@...ibm.com,
heiko.carstens@...ibm.com, pavel@....cz, hpa@...or.com,
jengelh@...putergmbh.de, sam@...nborg.org, mtk-manpages@....net,
schwidefsky@...ibm.com, lf_kernel_messages@...ux-foundation.org,
tim.bird@...sony.com, arjan@...radead.org,
auke-jan.h.kok@...el.com, Valdis.Kletnieks@...edu, gregkh@...e.de,
linux-kernel@...r.kernel.org, joe@...ches.com,
Andrew Morton <akpm@...ux-foundation.org>, hansendc@...ibm.com,
davem@...emloft.net
Subject: Re: [Lf_kernel_messages] Re: Documentation of kernel messages
(Summary)
O> Yep, it's going to be up to the translators to keep the message
> catalogs up to date. The gettext folks have figured out ways of doing
> fuzzy string matches, and so if you keep the external database of
> filename, line #, string, hash, and translation(s), when you go to new
> version of the kernel, it's not that hard to make the fuzzy
> translations work.
The tools can extract the strings if marked _() which is easy work to do
and you usually only want to hit a subset of strings anyway [the ones
that occur usually].
Having implemented an encheferizer in a much older kernel its worth it
even for the humour value of a valspeak kernel (plus some people will
never be happy until it says things like
SYS-E-FOO: Incorrect operating system in use
-
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