It looks like you're new here. Sign in or register to get started.
Simon Cozens said:This whole discussion reminds me of my favourite bit of OpenType code,sub period space space by period spaceIf you think fonts should be opinionated about linguistic conventions, you should probably include that one too.
sub period space space by period space
John Hudson said:We're font makers and this is not a font problem.
D. Epar ted said:
Nobody is stopping anybody from making, popularizing or using dumb, smart or manual quotes, apostrophes, repostrophies or quopostrophies.
John Hudson said:
So go make yourself a custom keyboard layout, and open source it if you'd like other people to adopt it. It isn't difficult, and it's an entirely appropriate solution to what you want to achieve.
Just having a custom keyboard does not solve the problem; I expect a custom keyboard to put a straight quote (i.e. U+0027, APOSTROPHE) in my file if that character corresponds to the key I am hitting. That will not happen unless you disable smart quotes either at the system level or at the application level. On the Macintosh, if you do not disable smart quotes in the system preferences (Keyboard > Text > Use smart quotes and dashes), the substitution automatically occurs in TextEdit, Mail and other OS X applications whatever keyboard you are using (and chosing the straight quote with the character palette does not help either). Word on the Macintosh (I have Office 365 from my employer) does not use the system preferences and you need to deactivate smart quotes from the application preferences if you want to keep control. Keeping control is getting harder and harder as “intelligent software” is making more and more decisions for us.
André G. Isaak said:
the behaviour of your text may be entirely different depending on which font you choose to use.