Thread (1 message) 1 message, 1 author, 2017-04-07

Re: [RFC 0/3] netlink: extended error reporting

From: David Miller <hidden>
Date: 2017-04-07 19:55:11
Also in: linux-wireless

From: Johannes Berg <redacted>
Date: Fri, 07 Apr 2017 21:46:46 +0200
On Fri, 2017-04-07 at 12:43 -0700, David Miller wrote:
quoted
I suspect that someone will eventually give us a hard time about the
strings wrt. internationalization. :-) It's solvable at least
partially in userspace I suppose.
I tend to think of the strings more of a debugging aid, but that's a
good point.

Perhaps we should have a macro that has the strings - similar to the
inline function I put into netlink - but if we make that a macro we can
put the strings into a separate section to be able to find them more
easily for later translation, and optionally even omit them entirely
(to satisfy the kernel tinification folks)?
One idea.  We use the macro thing to generate a "netlink.pot" file and
then some userland tree can contain the latest netlink.pot and the
translations.

I'm suggesting it this way because whilst putting the netlink.pot file
in the kernel tree is probably OK, putting all the translation there
might not be.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help