Hi! I've modified my version of Typogrify to support the use of the long s in initial and medial positions. I've attached the patch against 6.x-1-dev.

CommentFileSizeAuthor
typogrify_long_s.patch5.62 KBpukku
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pukku’s picture

There is a bug with the new way of doing settings that I just discovered, which prevents the ligature for ſt from being properly saved. I'm not sure exactly where, but I think something is trying to use it un-entitied, vs. something using it entitied. The way of handling ligatures is not quite flexible enough for this.

I'm not sure exactly how to best proceed. The rest of the patch is still valid though.

mikl’s picture

Status: Active » Needs work

This looks fairly good, but remember that Drupal uses Unicode, so there's really no reason to escape ſ and ſt as HTML entities, especially since it causes problems with the strings that are escaped when they make their way through the translation system, and it causes problems with parsing here and there. I've actually been planning to change all the HTML entities in unicode-conversion.php to use the real UTF-8 characters instead.

The problem with the ſt ligature is probably that the way the configuration currently works is by using the plain text version of the string to be converted as the array key, which may be problematic if you have HTML entities in there. Try if using 'ſt' instead of '& #383;t'