Printing umlauts from FreeSerif or FreeSans doesn't work with certain printers

• Jul 5, 2017 - 08:53
Reported version

Printing direktly out of MuseScore a score that contains umlauts (äöüÖÄÜ) in Title, subtitle, composer, lyricist, copyright, system- and staff text, chord symbols or lyrics replaces those charactes with some junk. Not in Rehersal marks, Instrument Change text and Swing text though.

MuseScore 2.0-2.1 (so no regression) and also 3.0 (8fb09aa), Windows 10, on one Printer, but not another. (Works on an "HP Officejet Pro 8620", does not on "HP Color Laserjet CM4540 MFP"

Export to PDF and printing that doesn't have this problem.

(Side issue: it seems files with umlauts in their name can't get attached here)

Attachment Size
umlaut.mscz 8.2 KB



Found that is is not an issue with 1.3, then checked furter into 2.x: It seems FreeSerif being the culprit, using Time New Roman as the font and the problem is gone.

Title Printing umlauts from FreeSerif doesn't work Printing umlauts from FreeSerif or FreeSans doesn't work

same issue with FreeSans


So only with "HP Color Laserjet CM4540 MFP" ?
is the printer driver up to date?

The only proper way to solve this issue is to make a little sample program in Qt, probably 5.9.1 to reproduce the problem and post it in their bug tracker

Well, I've only tested with those 2. And don't have more to test with. I believe the drivers are up-to-date. This first came to me via a choir member, need to find out which printer and OS he's using.

Title Printing umlauts from FreeSerif or FreeSans doesn't work Printing umlauts from FreeSerif or FreeSans doesn't work with certain printers

Yip. Still a case. Printers that don't work are Konica Minolta Bizhub. If the problem is in the printers, how come no problems exist with other software, only with MuseScore and the built in FreeSerif (and obviously FreeSans). I recall that I got FreeSerif installed as a normal font under Windows and it worked. My strong suspicion is not on FreeSerif itself, but on how MuseScore handles a built in font.

If the font is indeed installed, MuseScore won't use the internal one, so this might be the problem?
Does export to PDF and then print that serve as a workaround?

On the other hand, if the problem has nothing to do with the printer, then everyone would see this, and we don't. So it's something about the specific combination of factors here. MuseScore uses Qt to handle most printing, so it could be that Qt is not communicating properly with your particular printer driver with respect to something in this particular font. Whether that's because of a problem in the printer driver, Qt, the font, or MuseScore itself is really impossible to tell without more investigation, and unfortunately, it's tough to investigate a problem that can't be reproduced by any of the developers.

If someone gives me a test file that isn't working for them under a current 2.2 build on Windows 10, I can try to see if the problem affects my printer. The file in the original report works fine for me, though.