One of the redesign deliverables from MBD was an editorial guide for the copy. One aspect of the guide that will be impossible to implement across the site is using HTML entities in text (e.g. for smart quotes and em dashes). I'd like to look at using the Typogrify filter on d.o to automatically do this for us. We don't need to turn on all of its features, just the ones required by our editorial guide. (As a note, it looks like SmartyPants module is unmaintained and deprecated in favor of Typogrify.)

http://drupal.org/project/typogrify

Comments

add1sun’s picture

add1sun commented
Issue tags: +drupal.org redesign

forgot to tag as well

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Why would it be impossible, especially if we try to put in some automation to ensure it?

add1sun’s picture

add1sun commented

My point is that it is impossible without automation, because we will not be able to get thousands of people to consistently type in HTML entities. Typogrify seems to make the most sense, but did you have another plan? I'm not wedded to Typogrify, it just seems like the most apt Drupal module to do the job.

todd nienkerk’s picture

todd nienkerk commented
Assigned: Unassigned » todd nienkerk

Shannon Lucas and I are officially taking this over. We'll research a typography solution, make changes as needed, and report here.

mikl’s picture

mikl
Location Møn
commented

As the maintainer of Typogrify, I'd like to help – please let me know if there's anything I can do :)

mikl’s picture

mikl
Location Møn
commented

I was wondering where this plan is going… I had some e-mail back&forth with Todd concerning some changes that has since been committed and released (see #409784: Reverse em/en-dash options for a more intuitive UI for more information).

The current state of the module is that I consider it to be stable. There are no outstanding bugs, and unless none turn up in the next couple of weeks, I'm going to call it 1.0.

If there's anything else I can do to help, please let me know :)

add1sun’s picture

add1sun commented
Issue tags: -drupal.org redesign

rock on! at this point it will need a security and general "d.o" review and the people with the keys to give it a +1. If we deploy this on D.o, do we need to change anything for existing content, what would be the exact config we'd use for our use case, etc need to be listed out. Then we can toss it on s.d.o and see how she looks.

add1sun’s picture

add1sun commented
Issue tags: +drupal.org redesign, +doctools

ugh, tag fail.

add1sun’s picture

add1sun commented
Assigned: todd nienkerk » add1sun

Adding this back to my radar. I'll install this on the new test docs.drupal.org once I get that rolling - maybe this week.

lisarex’s picture

lisarex commented

Linking this from the Redesign project #661566: Meta issue for Drupal.org webmaster project because this issue was tagged 'drupal.org redesign'

Feel free to move or link from the Blue Cheese theme project instead... :)

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (won't fix)

I think we should do what we can with CSS3 because Drupal.org has an earlier adopter audience.