X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Tue, 10 Aug 2021 22:43:18 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	"karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] subscripts in schematics text
In-Reply-To:	<20210810192733.0805A83DF0CF@turkos.aspodata.se>
Message-ID:	<alpine.DEB.2.21.2108102238150.4764@nimbus>
References:	<20210810192733 DOT 0805A83DF0CF AT turkos DOT aspodata DOT se>
User-Agent:	Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1701398008-1628628198=:4764
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Tue, 10 Aug 2021, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> Is there any better way to make subscripts than "just" placing two
> text objects in a way that "happens" to produce the desired result ?

For the more common characters, you could use Unicode subscripts and 
superscripts (as in, “I²C”):

https://en.wikipedia.org/wiki/Unicode_subscripts_and_superscripts

--8323329-1701398008-1628628198=:4764--

- Raw text -