-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull Quotes Display Enhancement #91
Comments
Regarding pull quotes, you definitely should encode Safari 6 doesn't like non-encoded symbols in CSS. I had the problem on my own site and on browserhacks.com. |
@hugogiraudel So it doesn't matter for Safari 6 even if UTF-8 is supported? |
Seems so. Here is how I did: https://github.com/HugoGiraudel/hugogiraudel.github.com/blob/master/sass/_helpers.scss#L124. |
@hugogiraudel So I went back to Snow Leopard w/Safari 4.0 and it actually does support non-encoded, recognized UTF-8 characters like quotes. This means you don't need \201C as you've been using. You can even go back to the iPhone 3GS and see that it does in fact have support as well. |
Issue on browserhacks.com: 4ae9b8/browserhacks#53 |
Here's an example using Typeplate pull quotes and non-encoded characters in the Windows 7 on IE8 still seems to be a bugger. |
Wow, that's a real shocker to me. I had no idea, I've been using unicode in CSS for ages. Argh. Well, how comfortable are we phasing out IE8 support? Personally, I don't mind :P |
That's interesting, very neat. But the premis is flawed—the content value – Zachary Kain Designer, Developer |
Besides all this hullahbahloo I think the |
Here's the idea to give more variety with pull quotes in terms of quote placement. This would be done by passing a string of the authors choosing which depicts the location of the quotes.
The text was updated successfully, but these errors were encountered: