Q: Monospaced Number Characters in Finder

FWIW, I don't believe any version of OSX used a fixed-width/mono-spaced font in the Finder. Even if numeric characters were mono-spaced you would have the same issue with alphabetical characters mixed in. And, even if everything was mono-spaced there would be a ripple on the right because of different length file names.

I don't seen any wave in El Capitan on my machine

Well that's good.

Your example is for letters.  The question is about number characters.  They are monospaced in El Capitan.  0 and 2 have the same width as 1.  In Sierra they do not.  So things are indeed different in that regard.

I did think we were taking about Sierra.

dialabrain wrote:

 

I did think we were taking about Sierra.

Of course.  But you "don't believe any version of OSX used a fixed-width/mono-spaced font in the Finder".  El Capitan at least used fixed-with numbers.  The OP wishes Sierra did the same.

Not to nitpick but I don't consider a mixed-spaced font a fixed-width/mono-spaced font.

And yes, I understood what he wanted.

Tom,

Just to clarify something. I wouldn't have mentioned monospaced fonts at all except the OP mentioned SF Mono and wondered why Apple didn't make it the system font. Which prompted my reply they've never used a monospaced system font which is true. In my opinion that would look terrible. You can certainly use a monospaced font in Linux very easily but it's not something I could live with. There is a reason books, magazines, pamphlets, flyers etc. aren't printed in monospaced fonts.

okay, I'm done.

Of possible interest, some explanation by Apple contained in the transcript of a presentation at the WWDC in 2015

https://developer.apple.com/videos/play/wwdc2015/804/?time=1688

"But I want to tell you about the spacing of numbers, their widths. By default, on our platforms, numbers are always monospaced, meaning they all have the same width, which is great if you need typeset something like tables, for example. Monospaced numbers are really handy because they make everything align. You can also achieve layouts with, like, multiple columns with them.

However, they are not the only numbers in the San Francisco fonts. We also have what are called proportional numbers, where each number has its own "natural" width. So there are situations where, of course, monospaced numbers are clearly what you want.

For example, like this, when you have proportional numbers, they will actually wiggle around, and monospace numbers actually stay put.

But you may also typeset numbers in static labels, such as when typesetting a date or a phone number or a read count in an inbox or an email address or a URL.

In those cases, really, you want proportional numbers instead. So let's take a -- do a case study with an app like Calendar, which is fairly numbers heavy.

And if you look at how we use numbers in this app and how we typeset them, you will notice that they don't really align with anything else, and they really are in line with other text, meaning they could use -- they should use, and they do use proportional numbers.

So knowing this, we decided to take a big leap here, and change the default of our platforms to actually give you proportional numbers by default and make you opt into monospaced numbers. Now, there is a precedent for this, and that's the Watch, which actually ships with proportional numbers by default.

But it is a big change, and it may affect layout. So because of that, we have provisions in place. If your app is not linked against iOS 10.11 -- sorry, OS X 10.11 and iOS 9, you still get monospaced numbers by default. The system turns on the monospace feature for you."