View Single Post
Old 06-06-2016, 06:11 AM   #364
chrisridd
Guru
chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.chrisridd ought to be getting tired of karma fortunes by now.
 
chrisridd's Avatar
 
Posts: 983
Karma: 2209358
Join Date: Nov 2011
Location: London, UK
Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3
Quote:
Originally Posted by GeoffR View Post
One new thing I discovered is that the automatic hyphens added by the KePub reader are hyphen, while the ones added by the ePub reader are hyphen-minus. That means that in a font like this where the hyphen-minus is a minus sign, the automatic hyphens in KePub will look different to the hard hyphens used by the publisher, but in the ePub reader they will look the same. With the alt-hyphen font they will look the same in both KePub and ePub.
Interesting, so it sounds like in theory the ACCESS (kepub) engine is more typographically correct than the RMSDK (epub) engine?

OpenType fonts can support "alternate" characters within the font - for example numerals might come in monospaced and proportional versions - and I wonder if that's a good way to include your adjusted hyphen? Adobe documents how to access these alternates in some CSS engines at https://helpx.adobe.com/typekit/usin...ntax.html#salt but whether these work in ACCESS/RMSDK is another question.
chrisridd is offline   Reply With Quote