avoid unicode in the document? Duy Nguyen (30 Aug 2020 01:41 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (30 Aug 2020 08:15 UTC)
Re: avoid unicode in the document? Duy Nguyen (30 Aug 2020 09:17 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (30 Aug 2020 09:42 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (30 Aug 2020 13:07 UTC)
Re: avoid unicode in the document? Arthur A. Gleckler (30 Aug 2020 18:35 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (31 Aug 2020 06:47 UTC)
Re: avoid unicode in the document? Arthur A. Gleckler (31 Aug 2020 07:10 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (31 Aug 2020 07:15 UTC)
Re: avoid unicode in the document? Arthur A. Gleckler (31 Aug 2020 07:30 UTC)
Re: avoid unicode in the document? Duy Nguyen (31 Aug 2020 09:10 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (31 Aug 2020 09:28 UTC)
Re: avoid unicode in the document? Duy Nguyen (31 Aug 2020 10:46 UTC)
Re: avoid unicode in the document? Marc Nieper-Wißkirchen (31 Aug 2020 10:53 UTC)

Re: avoid unicode in the document? Marc Nieper-Wißkirchen 31 Aug 2020 07:15 UTC

Am Mo., 31. Aug. 2020 um 09:10 Uhr schrieb Arthur A. Gleckler
<xxxxxx@speechcode.com>:

>> Regardless of that, srfi.css contains one reference to the "Monaco"
>> font, which seems to be commercial font shipped by Apple for their
>> computers. I don't think that we want that, at least not without
>> giving free fonts for free operating systems preference.
>
>
> That just means that Monaco will be used for that class on Macs.  On free operating systems, free fonts will have first preference.

My issue is more a political one about advertising. It seems we are
supporting the commercial Macs better than the rest of the world
because we suggest a good font just for them. if it leads to SRFIs
looking better on a Mac than on a random computer system, this is not
good.