IETF Logo Mail Archive

[Tools-discuss] xml2rfc: boldface in Noto Sans

Carsten Bormann <cabo@tzi.org> Mon, 22 September 2025 07:58 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@mail2.ietf.org
Delivered-To: tools-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3A32F669EFC7 for <tools-discuss@mail2.ietf.org>; Mon, 22 Sep 2025 00:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.989
X-Spam-Level:
X-Spam-Status: No, score=-3.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=tzi.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YVBw83GMS5k for <tools-discuss@mail2.ietf.org>; Mon, 22 Sep 2025 00:58:09 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2E623669EFBD for <tools-discuss@ietf.org>; Mon, 22 Sep 2025 00:58:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1758527887; bh=QGzBNqTYPzmi73cBN9isgHCdWjoUgVgD8IvCwEXgIsw=; h=From:Date:Subject:To; b=cAmSzSm2pZajh18tae9rkPkoMAAckN4uFiF4yfsmKaOYz1CEngQqpIX6rIJarnZJM jHPR7aWnrGs+o0UIu9hOz1gY1lmgC1WYjFyefajZNubhAxS7wfxpcl7+nqhAPqREHZ 8+/mQiJcSOltjhZhnktqSbejNhYYxJUC1zvVEJdOirdZ+q4vk7RoFuLFXAkL34VGHq au7syUFaLFkbMIpJi0hDpXgSXQW44cAK/16/aHLfYrAmkVMmH6+PdyKfNkva6GXhHT +LDpMOx4wD8hHITXUEcJSCaWv4wrrstD7RGXugzn14e/eiUpQFdS/xIW/lqDnpEIWq UyDaKjkcS2itw==
Received: from [192.168.217.132] (p5dc5df6f.dip0.t-ipconnect.de [93.197.223.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4cVb7z3rXnzDCcs; Mon, 22 Sep 2025 09:58:07 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 780220687.084191-25cf27545852d716c68d8f8a1dfcca97
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Mon, 22 Sep 2025 09:58:07 +0200
Message-Id: <EC4BEFC9-8916-4957-B42D-1581A598F45F@tzi.org>
To: Tools Team Discussion <tools-discuss@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-FromAuthMilter: ok
Message-ID-Hash: MWNRFM7IPSXI2E2AYRZDGXBLNQOEGOL7
X-Message-ID-Hash: MWNRFM7IPSXI2E2AYRZDGXBLNQOEGOL7
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] xml2rfc: boldface in Noto Sans
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/4hvXbctvojOyRhXUxbwFS0yYKko>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

I was trying to make some point more apparent by using <strong> markup.

It turns out that <strong> markup is nearly invisible in the xml2rfc-generated HTML:

https://www.ietf.org/archive/id/draft-ietf-core-yang-sid-pen-01.html#name-example

(New game: Find the boldface :-) 

This is fine in plaintext (where we have “*” fallback) and in PDF (which uses Noto-serif), please see Section 2 of:

https://tzi.org/~cabo/draft-ietf-core-yang-sid-pen.pdf

(This is the same document — I have to generate the PDF separately because the I-D submission interface still doesn’t.)

Note that the variant, somewhat harder to read formatting shown by the i-d-template CI also can show boldface:

https://core-wg.github.io/sid-pen/draft-ietf-core-yang-sid-pen.html#name-example

Is this something that should be fixed?
Or does the RFC editor maybe use CSS different from that used by plain xml2rfc?

Grüße, Carsten

v2.35.0 | Report a Bug | By Email | System Status