Re: [rfc-i] What are current rules on non-ascii in documents?

Jean Mahoney <jmahoney@amsl.com> Thu, 15 February 2024 20:07 UTC

Return-Path: <jmahoney@amsl.com>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C73BEC14F691 for <rfc-interest@ietfa.amsl.com>; Thu, 15 Feb 2024 12:07:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLBFr63mkbew for <rfc-interest@ietfa.amsl.com>; Thu, 15 Feb 2024 12:07:22 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6EC4C14F5F8 for <rfc-interest@rfc-editor.org>; Thu, 15 Feb 2024 12:07:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id ADA2F424B455; Thu, 15 Feb 2024 12:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMMUPnckkR3j; Thu, 15 Feb 2024 12:07:22 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 74D5E424B432; Thu, 15 Feb 2024 12:07:22 -0800 (PST)
Message-ID: <5650a472-3f5d-40b9-b5a6-9ae7444df808@amsl.com>
Date: Thu, 15 Feb 2024 14:07:21 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Jean Mahoney <jmahoney@amsl.com>
To: Lars Eggert <lars@eggert.org>, Carsten Bormann <cabo@tzi.org>
Cc: rfc-interest@rfc-editor.org
References: <3C54D12E-89E0-43BF-ADBB-26F66081E55A@tzi.org> <883024E7-ECFE-483E-AAC5-B08BBFB75DA2@bangj.com> <2705E5C9-8F1E-4557-88E0-B328CE784EF0@tzi.org> <5049CA18-4820-4BF6-8A02-5C8EDDD5F6E6@eggert.org>
Content-Language: en-US
In-Reply-To: <5049CA18-4820-4BF6-8A02-5C8EDDD5F6E6@eggert.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/LBOvtyfQX3fsI9wf7K_015eOBnE>
Subject: Re: [rfc-i] What are current rules on non-ascii in documents?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Feb 2024 20:07:26 -0000

Hi all,

On 2/15/24 7:40 AM, Lars Eggert wrote:
> Hi,
> 
> On Feb 15, 2024, at 07:24, Carsten Bormann <cabo@tzi.org> wrote:
>> PS. Now if I knew why my (chromium-based) browser does this:
>>
>> <PastedGraphic-1.png>
>>
>> Looks fine in emacs (using “Hack” font):
> 
> fonts are a big problem here. With some of utftex's more esoteric math notations, the only font that really works is https://juliamono.netlify.app/

[JM] Please note the fonts that may potentially be used in RFCs can be 
found here: https://github.com/ietf-tools/xml2rfc-fonts

Best regards,
Jean


> 
> Lars
> 
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest