Explain then, your email of yesterday where you explain that you said --- Hmmm, what I see are superscript 3, 2 & 1 in that order, followed by a prime. What I now think you meant is :
Instead of a “tick” mark for an apostrophe, I¹d like a mark like you see here: ’ I know of no way of accomplishing that using CSS, but server-side processing might be an (off-list/topic) option. --- On 10/11/15, 11:49 AM, "Philip Taylor" <p.tay...@rhul.ac.uk> wrote: > > >Chris Williams wrote: > >> My larger point was, tread carefully here. Test a lot. Unexpected >> results (as Jeff sees in his simple email to this list) are likely. > >If one has to tread carefully for characters as commonplace and >straightforward as curly quotation marks, what hope has one if one wants >(as I frequently do) to use Vietnamese characters, polytonic Greek >characters, IPA characters and so on ? I really think that, in the 21st >century, one should be able to rely on the receiving client displaying >the the more common elements of the Unicode repertoire correctly. If I >were to want to include Cherokee, Blackfoot, Dene, Cree or Naskapi, for >example, then I would do well to ensure that my intended recipient(s) >had support for such languages. But this should not have to be the case >for mainstream languages, let alone basic punctuation. > >Philip Taylor ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
