From owner-freebsd-questions@freebsd.org Mon Nov 16 19:10:32 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4C67146E863 for ; Mon, 16 Nov 2020 19:10:32 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CZdvC12pKz4V64 for ; Mon, 16 Nov 2020 19:10:30 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm1-x333.google.com with SMTP id 23so515874wmg.1 for ; Mon, 16 Nov 2020 11:10:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=iQbYTSBBmVE1N5KI9fxJJduOZ4HRiTqMSb/OwmlbGxg=; b=P/s0dSLUxMj+iJsQsLIpHZJxprNTARbSu4r7UHk/6icTbERNR5k/G22onSsDabBXQU 4ZtEpiwxW4kUPWZL5ah+Sz+jWcOKcMvliOUKhLcCRZ0yN23GkpDFJqOqdJZwUAURY3Ym wtyX7nFMymdmG2KBmhr4sB+7frRjHtRlZxxnSZIu+BCHVUWqu2zbaTeGGl68qbDHBSJT NH9bRxG6sZhKd2DHdSXrRzXkvsaodtNBygy+lF0lnlb9EsoMhxPIq+ZtQs5C72kGFWFK EzGjOJhfUj4AnBtLLywiBL8SZPiDEohNJdIBC7UzRlHCyDeanubhlYMk21RAr0ODNkR1 qqEg== X-Gm-Message-State: AOAM532wOZ2Hr6BxjLJKU4kuG+OIROBiuk0O04GdIdA2p0oOPNROjoQT DdbkEdJRQrl80+IlypsZ+GC34/FhpjOYxA== X-Google-Smtp-Source: ABdhPJw8bH7x9N2RxWchR0ir91SXUgIckBx6tLiq7xd4sIEoaK4Jf73BEBbQr+Sjzag65AHf39GiYQ== X-Received: by 2002:a1c:ed06:: with SMTP id l6mr359766wmh.67.1605553829294; Mon, 16 Nov 2020 11:10:29 -0800 (PST) Received: from gumby.homeunix.com ([2.220.21.54]) by smtp.gmail.com with ESMTPSA id u23sm299920wmc.32.2020.11.16.11.10.27 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Nov 2020 11:10:28 -0800 (PST) Date: Mon, 16 Nov 2020 19:10:24 +0000 From: RW To: freebsd-questions@freebsd.org Subject: Re: Booting multiple BSDs. Message-ID: <20201116191024.6c366f78@gumby.homeunix.com> In-Reply-To: <20201116124900.be157ef7.freebsd@edvax.de> References: <3c5506c0-9727-4773-43c9-5afe9767ad9f@xsmail.com> <202011161116.0AGBGgLt001902@r56.edvax.de> <20201116124900.be157ef7.freebsd@edvax.de> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd12.1) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4CZdvC12pKz4V64 X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-1.00)[-0.996]; RECEIVED_SPAMHAUS_PBL(0.00)[2.220.21.54:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::333:from]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::333:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::333:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2020 19:10:32 -0000 On Mon, 16 Nov 2020 12:49:00 +0100 Polytropon wrote: > On Mon, 16 Nov 2020 09:45:01 +0000, Thomas Mueller wrote: > > > > > Harry Weaver =20 =20 > > =C3=A2=C2=A2=C2=80=C3=A2=C2=A3=C2=B4=C3=A2=C2=A0=C2=BE=C3=A2=C2=A0=C2= =BB=C3=A2=C2=A2=C2=B6=C3=A2=C2=A3=C2=A6=C3=A2=C2=A0=C2=80 > > =C3=A2=C2=A3=C2=BE=C3=A2=C2=A0=C2=81=C3=A2=C2=A2=C2=A0=C3=A2=C2=A0=C2= =92=C3=A2=C2=A0=C2=80=C3=A2=C2=A3=C2=BF=C3=A2=C2=A1=C2=81 Debian - The univ= ersal operating system > > =C3=A2=C2=A2=C2=BF=C3=A2=C2=A1=C2=84=C3=A2=C2=A0=C2=98=C3=A2=C2=A0=C2= =B7=C3=A2=C2=A0=C2=9A=C3=A2=C2=A0=C2=8B=C3=A2=C2=A0=C2=80 https://www.debia= n.org > > =C3=A2=C2=A0=C2=88 > > which is not what I'm running now. =20 >=20 > Looks like there is still more than one 2-to-1 byte mangling > involved, possibly crossing encoding borders. ... What you saw was misleading, and has nothing to do with why Thomas Mueller didn't see the Debian thing. His client likely just has broken or missing UTF-8 and/or MIME support. There's no excuse for that in 2020. > The original message declares UTF-8 correctly, and also _uses_ > UFT-8 encoded symbols in the signature. The following drawing > should be visible: >=20 > =E2=A2=80=E2=A3=B4=E2=A0=BE=E2=A0=BB=E2=A2=B6=E2=A3=A6 > =E2=A3=BE=E2=A0=81=E2=A2=A0=E2=A0=92=E2=A0=80=E2=A3=BF=E2=A1=81 > =E2=A2=BF=E2=A1=84=E2=A0=98=E2=A0=B7=E2=A0=9A=E2=A0=8B > =E2=A0=88=E2=A0=B3=E2=A3=84 That was visible to me in the post that you quoted from. What happened was that Thomas Mueller pasted UTF-8 into a text/plain body without an explicit character set. The relevant RFC says that this should default to US-ASCII, which means that byte values above 7f are undefined. This include all of the UTF-8 Braille. My client, Claws Mail, identified the text as UTF-8 and displayed it as such. UTF-8 can be identified very reliably is there are enough multibyte characters. Your client, Sylpheed, appears to have assumed the undefined bytes were in ISO 8859-1, a common fallback. On replying, Sylpheed then converted the quoted bogus text to UTF-8 which hopefully this reply preserves.=20 There may be a bit more to this, but any remaining weirdness is most likely caused by Sylpheed. Note that some of the whitespace in the quoted garbage above is from A0 bytes in the original UTF-8 being treated as a "no break space".=20