EM6 does not find notation fonts

Uli · Post by **Uli** » 26 Nov 2012, 00:31

Hi,

Yesterday, I downloaded EM6 for Mac to see if it fits my needs.

Unfortunately, I cannot even start testing the application as it obviously cannot find the notation fonts it needs to display notes. Instead of notes, I only see the "missing fonts" icon of Mac OS X. The fonts themselves seem to be located inside the application bundle just fine. (They did not get installed in /Library/Fonts/, though, should that be what the Installer application is supposed to do.)

This is on Mac OS X 10.8.2; user language is German.

Also note that I'm using HFS+ Case-Sensitive Journaled, so if the path to the fonts that's encoded in the application code had a capitalization error, this would not work on my system, but would work on systems with HFS+ Case-Insensitive Journaled. But that's only a guess ...

(I remember having a look at EM5 several years ago, and IIRC, this version did not have this issue.)

Uli

Post by **Quentin** » 03 Dec 2012, 08:47

Hi Uli,
You got the debugging just right. The problem is the capitalization of the paths, and EarMaster doesn't support HFS+ Case Sensitive partitions. We should definitely add that in the system Requirements of the program, as it will not be possible to our developers to change that aspect of the application unfortunately.

Uli · Post by **Uli** » 03 Dec 2012, 10:08

Quentin wrote:You got the debugging just right. The problem is the capitalization of the paths, and EarMaster doesn't support HFS+ Case Sensitive partitions. We should definitely add that in the system Requirements of the program, as it will not be possible to our developers to change that aspect of the application unfortunately.

Hi Quentin,

Sorry, but I don't understand this. Making an application work on HFS+ Case Sensitive simply means using a consistent capitalization of paths names hardcoded within the application. There is absolutely no reason why a software developer could not avoid writing "/myPath" on one occasion, but "/MyPath" on another.

I'm a Mac OS X software developer myself, so I know what I'm talking about.

I'm sad to learn that you prefer excluding some of your potential customers from using your application to spending maybe 50, but more probably just 15 minutes of work to make path capitalization consistent in your source code.

</sigh>

Uli

Post by **Quentin** » 04 Dec 2012, 07:41

Hi Uli,

It seems that most (all?) of the paths from v5 are supporting case sensitive partitions, so the developers will try to go through all the new paths and do the necessary modifications to support HFS+. Hopefully, it will be available in an update soon.

Uli · Post by **Uli** » 04 Dec 2012, 16:16

Hi Quentin,

Quentin wrote:It seems that most (all?) of the paths from v5 are supporting case sensitive partitions,

Yes, from what I remember when looking at Earmaster 5, I did not experience any issues at all.

I was very busy back then and had no time for really testing Earmaster 5, but things as the font issue now I would have seen even at first glance.

so the developers will try to go through all the new paths and do the necessary modifications to support HFS+. Hopefully, it will be available in an update soon.

That's good news, thank you!