Date: Fri, 16 Oct 2020 12:34:58 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: sh scripting question Message-ID: <20201016123458.2e7f0eaf74adf4eb1443a69e@sohara.org> In-Reply-To: <20201016132516.71e06c69@archlinux> References: <d50ba2c9-617f-6842-ef89-f5933be8f8b3@hotmail.com> <DB8PR06MB64427D88E17F02711EE657A3F6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016113408.16d58d68@archlinux> <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016132516.71e06c69@archlinux>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Oct 2020 13:25:16 +0200 Ralf Mardorf <ralf-mardorf@riseup.net> wrote: > I can't notice a different philosophy. We agree again. I just wanted to > point out, that our scripts might need to be able to handle some > imported iDroidWindowsCamEmailAttachment file names, at least to some > extend, but we and anybody using systems we might administrate, should > apply a minimum of convention, compatibility, portability. > > Let alone that a apart from little girls nobody tend to name a file > > ***such a cute cat ;)... But somebody might have an NFS or SMB mounted home directory on a workstation set to use Shift-JIS and produce filenames that look really weird from the console. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201016123458.2e7f0eaf74adf4eb1443a69e>