From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: <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> <20180730143104.GB24051@amd> <20180730180842.GA5544@bombadil.infradead.org> In-Reply-To: <20180730180842.GA5544@bombadil.infradead.org> From: Linus Torvalds Date: Mon, 30 Jul 2018 11:18:53 -0700 Message-ID: Subject: Re: [PATCH 36/38] vfs: Add a sample program for the new mount API [ver #10] To: Matthew Wilcox Cc: Pavel Machek , 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 11:08 AM Matthew Wilcox wrote: > > Have you looked at how gettext() works? It uses the english text as > a search string and replaces it with the localised string. This is > a very common design! I absolutely refuse to have anything to do with gettext in the kernel. gettext() needs help that I'm not willing to give, and that I absolutely refuse to consider as part of any kernel interfaces. Mount options are already English text. Don't try to make it anything else. Just do a git grep '{.*Opt_.*".*".*}' on the kernel, and realize that if you are messing with mount options and things like that, you'd better be able to google the incomprehensible words. Most of them will be incomprehensible even if you're a native speaker. There is not a way in hell that we will ever have gettext() support for any of these things. Linus