Re: [Tools-discuss] Serving markdown as text/markdown ➔ mojibake
Tom Pusateri <pusateri@bangj.com> Tue, 04 August 2020 15:29 UTC
Return-Path: <pusateri@bangj.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0D93A0A4E for <tools-discuss@ietfa.amsl.com>; Tue, 4 Aug 2020 08:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id essQ97Mtkm53 for <tools-discuss@ietfa.amsl.com>; Tue, 4 Aug 2020 08:29:27 -0700 (PDT)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EA013A0A5F for <Tools-discuss@ietf.org>; Tue, 4 Aug 2020 08:29:21 -0700 (PDT)
Received: from localhost (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 19F9C16D77; Tue, 4 Aug 2020 11:29:20 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1596554960; bh=tc9MouSG7QprcpUQ0AoIGmU3V64YLZ/C5W6I3kKB4T0=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=dWp+gCwZUSPYHtEoLMkDMchO7USgmLtPfo7RyddUfyO+rJWBbf0bxEBA3gfkk/cN6 BGJk1BAShMi6l0GwQRAQWrNJvAe6yeqPkzcoisi2XLvqdm+Z5fFjsaSDhWPKT1xopB uQ/XKq2CgyLHLqNEWASyeGcdm/eI/dnhy7+UcGQ8hmDeP6zkwhevwakkARd0GooVVQ /tsRs1aC4heWBHAT7IlSsC1JUkReWlWMxuHhJhI7TiRwptoo2V2CattFWcQZu65zjz jrf5m0p3IgrMglisLtppWWc+xabkWkZ6DD3CYTJolA8rVdUFqMa/QxaDX2dJZGZYM9 JKUsLqrCLHpVA==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Tom Pusateri <pusateri@bangj.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 04 Aug 2020 11:29:19 -0400
Message-Id: <7A5D4D76-9251-4B6B-95A0-836D1CBFBFC1@bangj.com>
References: <446911DB-C831-4376-9F3B-C017FF44679B@tzi.org>
Cc: Tools Discussion <Tools-discuss@ietf.org>
In-Reply-To: <446911DB-C831-4376-9F3B-C017FF44679B@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (18A5332f)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/rLUZd-ea1z6Zn6qpoDJU9Gfj10s>
Subject: Re: [Tools-discuss] Serving markdown as text/markdown ➔ mojibake
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2020 15:29:31 -0000
> On Aug 4, 2020, at 10:42 AM, Carsten Bormann <cabo@tzi.org> wrote: > > I get mojibake in https://www.ietf.org/proceedings/interim-2020-maprg-01/agenda/agenda-interim-2020-maprg-01-sessa-00 > > It seems browsers (tested with Safari and Chrome) assume Latin-1 for > > $ curl -sI https://www.ietf.org/proceedings/interim-2020-maprg-01/agenda/agenda-interim-2020-maprg-01-sessa-00 | grep -i content-type: > content-type: text/markdown > > https://www.iana.org/assignments/media-types/text/markdown says: > > Required parameters: > > charset: Per Section 4.2.1 of [RFC6838], charset is REQUIRED. There > is no default value because neither [MDSYNTAX] nor many popular > implementations at the time of this registration do either. > [MDSYNTAX] clearly describes Markdown as a "writing format"; its > syntax rules operate on characters (specifically, on punctuation) > rather than code points. Many Markdown processors will get along > just fine by operating on characters in the US-ASCII repertoire > (specifically punctuation), blissfully oblivious to other > characters or codes. > > Please change > > content-type: text/markdown > into > content-type: text/markdown; charset=utf-8 > > Grüße, Carsten I will look at this one. Tom
- [Tools-discuss] Serving markdown as text/markdown… Carsten Bormann
- Re: [Tools-discuss] Serving markdown as text/mark… Tom Pusateri
- Re: [Tools-discuss] Serving markdown as text/mark… Carsten Bormann
- Re: [Tools-discuss] Serving markdown as text/mark… Robert Sparks