On Fri, 2008-08-15 at 16:05 -0400, Rick Troth wrote: > On Wed, 13 Aug 2008, Rusty Russell wrote: > > Can you hash the format string to generate the id? 6 hex digits should be > > enough, and your tool can check for clashes. As it's bad form to have > > identical strings for different semantics anyway, this seems to make sense. > > I second this suggestion (or propose something like it). > A short hash or even an index into some off-line table > lets the user hit the right page when looking for an explanation. The kmsg id is just that, an index into the table of message for a particular component. > I've been using a similar (and perhaps ugly to some eyes) > numeric message catalog for years (with token substitution and all). > The catalogs can be translated and then replaced with local language > so the users don't have to learn English (or French, or German, > or Japanese, or Chinese). That is what we are trying to achieve as well. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
