On Tue, May 24, 2022 at 4:41 PM home user <mattisonw@comcast.net> wrote:
On 5/24/22 12:31 AM, Samuel Sieb wrote:
> On 5/23/22 22:45, Tim via users wrote:
>> On Mon, 2022-05-23 at 21:23 -0700, Samuel Sieb wrote:
>>> You're not seeing the whole name.  If you click on them, you'll see
>>> they are different.  Regular and 3 types of condensed.

That's how I knew they were 4 different fonts.

>> Terrible GUI design if it doesn't give you some indication that the
>> name's been truncated.  Are users supposed to around clicking on
>> everything, now?
>
> I don't think it's truncated.  I suspect it's something to do with the
> way the font metadata is defined, but I don't know for sure.  There are
> other fonts where that information is shown, so it's not the font app
> that's hiding it.

Either way, there is a problem here.  Yet I suspect that a bug is not
the way to get this addressed.  This is a significant problem, and will
probably take a serious task/project to fix it.  ...a font clean-up
task/project.  How do I propose it?

Unfortunately, widely used open source fonts often get multiple forks --
some that add support for additional languages, some that "improve" 
details of shapes and metrics.   You end up with a font that is needed
by those who require a certain language but that also cause problems
with some tools or when used in existing documents that don't embed 
fonts due to changes in metrics.
 
Fonts are essentially programs, and like programs, you can have multiple
forks with conflicting goals and coding styles that rely on features outside
the language specification.   

If you use open-source fonts that attempt to replace legacy PostScript 
(Laserwriter 35) fonts you run risks if you try to use them for things that
you couldn't do with the original fonts.

Font creators now often include license clauses to require name
changes for modified versions. 

--
George N. White III