[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b8bc929-2f07-049d-f24c-cb1f1d85bbaa@gmail.com>
Date: Fri, 14 May 2021 12:08:36 +0100
From: Edward Cree <ecree.xilinx@...il.com>
To: David Woodhouse <dwmw2@...radead.org>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Mali DP Maintainers <malidp@...s.arm.com>,
alsa-devel@...a-project.org, coresight@...ts.linaro.org,
dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org,
intel-wired-lan@...ts.osuosl.org, keyrings@...r.kernel.org,
kvm@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-edac@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-hwmon@...r.kernel.org, linux-iio@...r.kernel.org,
linux-input@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-media@...r.kernel.org, linux-pci@...r.kernel.org,
linux-pm@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-sgx@...r.kernel.org, linux-usb@...r.kernel.org,
mjpeg-users@...ts.sourceforge.net, netdev@...r.kernel.org,
rcu@...r.kernel.org
Subject: Re: [PATCH v2 00/40] Use ASCII subset instead of UTF-8 alternate
symbols
> On Fri, 2021-05-14 at 10:21 +0200, Mauro Carvalho Chehab wrote:
>> I do use a lot of UTF-8 here, as I type texts in Portuguese, but I rely
>> on the US-intl keyboard settings, that allow me to type as "'a" for á.
>> However, there's no shortcut for non-Latin UTF-codes, as far as I know.
>>
>> So, if would need to type a curly comma on the text editors I normally
>> use for development (vim, nano, kate), I would need to cut-and-paste
>> it from somewhere
For anyone who doesn't know about it: X has this wonderful thing called
the Compose key[1]. For instance, type ⎄--- to get —, or ⎄<" for “.
Much more mnemonic than Unicode codepoints; and you can extend it with
user-defined sequences in your ~/.XCompose file.
(I assume Wayland supports all this too, but don't know the details.)
On 14/05/2021 10:06, David Woodhouse wrote:
> Again, if you want to make specific fixes like removing non-breaking
> spaces and byte order marks, with specific reasons, then those make
> sense. But it's got very little to do with UTF-8 and how easy it is to
> type them. And the excuse you've put in the commit comment for your
> patches is utterly bogus.
+1
-ed
[1] https://en.wikipedia.org/wiki/Compose_key
Powered by blists - more mailing lists