Font not recognized on Win11

[Beruce]

When using Music Notation for Windows "Fughetta" on Affinity Designer 2 1.10.6... I found that it is not displayed and processed properly. Maybe there is a trick?

Best regards

 

Beruce

 

FUGHETTA.ttf

[GarryP]

When I preview that font on Windows 10 I get what you can see in my attached screen grab.

However, I have no idea what it is supposed to look like so I can’t tell if the preview is correct or not.

Can you give us an idea of what ‘right’ and ‘wrong’ look like so we can compare them?

[walt.farrell]

Are you creating a file in Designer using that font, or trying to open a PDF that something else created using that font?

[kenmcd]

6 hours ago, Beruce said:

When using Music Notation for Windows "Fughetta" on Affinity Designer 2 1.10.6... I found that it is not displayed and processed properly. Maybe there is a trick?

This is a really old (1995) symbol font (pre-Unicode).

All of the code points assigned are up in the PUA - so the glyphs are not mapped to particular keyboard characters.
The glyphs can be entered using the Glyph Browser.

It could be converted to Unicode using the glyph names.
Then the glyphs would be mapped to the keyboard.
But, that may not do you much good.
All of the glyphs are vertically centered on the baseline.

This font is made to be used with a music notation application.
The only one they mention is Finale, but others may work.
Note that this font does not have everything needed to write music - they state that these fonts (Fughetta and Toccata) are to be used in conjunction with Petrucci and Maestro. They just add "missing" symbols.

There are some music fonts which can be entered using Unicode code-points (e.g. BravuraText), but that is a difficult process (and poorly documented). I have seen some determined users master it with a lot of work. So you could do this with APub or ADesigner.
Note: BravuraText has long-time bugs which they show no interest in fixing.

Best thing to do probably is make the music notation in a dedicated app, export to PDF, and then place that in the Affinity app document.

[Beruce]

I've attached two files that illustrate how differently programs deal with this font. The old cs6 illustrator is very well able to display and use the font. It would be nice if the Designer 2 also worked like this.

Best regards

beruce

notenlinien_illustrator_CS6.svg notenlinien_Designer_2.svg

[walt.farrell]

2 minutes ago, Beruce said:

It would be nice if the Designer 2 also worked like this.

I doubt that the Affinity apps will ever support those old fonts.

[kenmcd]

3 hours ago, Beruce said:

I've attached two files that illustrate how differently programs deal with this font. The old cs6 illustrator is very well able to display and use the font. It would be nice if the Designer 2 also worked like this.

I do not understand what we are supposed to see there.

You can "use" the font in ADesigner, but your input options are limited to the Glyph Browser (or directly entering glyph numbers).
And then all vertical alignment is manual.
Same with the horizontal alignment.
Which I assume is the same in IL.

So I am not sure what your SVGs are supposed to show.

This is another of these old Franken-fonts which were converted from Type1, badly.
It includes conflicting encoding.
Macintosh Roman for Macs (for text).
Windows Symbol for Windows (for symbols).
This makes no sense.
Older applications often understand the old Mac-Roman encoding.
And will often default to it (to work-around all the old bad Type1 conversions like this).
Affinity applications do not understand the old Mac-Roman encoding (only Unicode).

If what you are saying is IL has mapped the characters to the keyboard, this is why.
And as I mentioned above, the font can be converted to Unicode properly.
Then the encoding will also be correct for modern applications and Windows.

So please explain exactly what IL is doing differently.

[stokerg]

Hi @Beruce,

Just want to add, @kenmcdis correct with everything they have stated.  So you would need to use the Glyph browser to work with this font.

As it stands, this isn't a bug and I'll move this thread to the Questions section of the Forums.

[Beruce]

I was expecting something like this discussion 😞 The hints are correct - thank you - but not effective. Because you don't really have to sugarcoat a defect

As a user, I just wanted to find out that the illustrator (including the new Illustrator CS from 2023, by the way) can interpret the Fughetta's characters. So nothing with "old application". I do think that it is not a mistake, but a defect in Designer 2. not having skills.

Therefore, it would only be logical if the "Fughetta" would not be displayed in the designer's font selection if the capabilities described above also do not exist - there may instead be a note that said font is only used via the glyph browser can.

Best regards

beruce

[kenmcd]

1 hour ago, Beruce said:

So nothing with "old application".

What I mean is applications which have been around a long time - old enough that they were forced to deal with the flood of bad Type1 font conversions to TrueType as it was happening. So they still have the old code to deal with it.

LibreOffice also is old enough. I remember the discussions in the LO bug tracker about these Franken-fonts which resulted in them adding code to default to the Mac-Roman encoding to work-around these broken fonts on Windows (which would normally default to the Windows Symbol encoding in the font).

The only "defect" in ADesigner regarding this issue is it does not have the ability to work-around the problems with these old broken fonts from 30 years ago. Adopey apps are definitely better at dealing with old and broken fonts. This is not the only example.

Should not have any problems in Affinity applications with modern Unicode fonts.

Edit: on my phone at the moment, but later today I will PM you a version of the font which has been converted to Unicode - for you to test.

[lacerto]

Obsolete.