From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: <20180730143104.GB24051@amd> <20180729113749.GA7333@amd> <153271267980.9458.7640156373438016898.stgit@warthog.procyon.org.uk> <153271292330.9458.14583488053811372222.stgit@warthog.procyon.org.uk> <25489.1532953411@warthog.procyon.org.uk> <21165.1532964795@warthog.procyon.org.uk> <20180730173052.GA881@amd> In-Reply-To: <20180730173052.GA881@amd> From: Linus Torvalds Date: Mon, 30 Jul 2018 10:54:19 -0700 Message-ID: Subject: Re: [PATCH 36/38] vfs: Add a sample program for the new mount API [ver #10] To: Pavel Machek Cc: David Howells , Al Viro , linux-fsdevel , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, Jul 30, 2018 at 10:30 AM Pavel Machek wrote: > > Still userland needs a way to understand the errors. Not really. We don't internationalize kernel strings. We never have. Yes, some people tried to do some database of kernel messages for translation purposes, but I absolutely refused to make that part of the development process. It's a pain. For some GUI project, internationalization might be a big deal, and it might be "TheRule(tm)". For the kernel, not so much. We care about the technology, not the language. So we'll continue to give error numbers for "an error happened". And if/when people need more information about just what _triggered_ that error, they are as English-language strings. You can quote them and google them without having to understand them. That's just how things work. Let's face it, the mount options themselves are already (shortened) English language words. We talk about "mtime" and "create". There are places where localization is a good idea. The kernel is *not* one of those places. Linus