ezrakilty wrote:

I'm not sure what this bug means. Perhaps the user double-clicked on a readme.txt in OpenTTD and it displayed in the default way in TextEdit with a proportionally-spaced font. This is not what happens on my 10.6.8 installation. Even if it does happen on some OS configurations, I don't think this is an OpenTTD problem or particularly significant.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4857#comment11825

Rubidium wrote:

This bug is not made by an user, but rather by a developer that knows that nobody made the required code to select a monospaced font when the default font does not have the required characters. Similarly to the behaviour when the non-monospace font have a missing character and one of the system fonts is used, e.g. for Russian.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4857#comment11827

ezrakilty wrote:

Where would these fonts appear? I interpreted the original note as referring to the readme.txt files (and other *.txt files) that appear in the OpenTTD folder. The follow-up here suggests something within the app, but I'm not sure why monospaced fonts would be useful there...

This comment was imported from FlySpray: https://bugs.openttd.org/task/4857#comment11828

Rubidium wrote:

In those readme, changelog and license files. However, some use characters that are not in the "sprite font" and then OpenTTD asks the operating system for an appropriate font. For example when the readme is the translated Russian version, or when there are a few Russian characters in the readme.

For OS X the function that requests the appropriate font does not even attempt to get a monospaced font, and that is the bug. It's fairly simple to reproduce; just add some Russian characters into one of the readme files and view that readme within OpenTTD.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4857#comment11829

Maedhros wrote:

I've got a small patch that seems to work for me on 10.8, though I don't know if I'm using the Monospace() callback in a sensible way. It doesn't work on OS X before 10.5 either, but it might be somewhere to start, at least.

Attachments

• fs4857.diff (0.70 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/4857#comment12026

michi_cc closed the ticket.

Reason for closing: Fixed

In r25663.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4857