Special Characters: Ligatures. . .

Permalink 2 users found helpful
Got a site I'm working on that must have an air of advancement, though stated minimally. Got a few things pulled off and it's looking great. However, one of the things I need are some ligatures. I'm using Georgia, and all I really need are the fi (fi) and fl (fl) ligatures. Webkit handles it beautifully straight up w/ this
text-rendering:optimizeLegibility;


I have the fi coded in the theme header and it works great. However, if I add it via c5 content block (using straight HTML input, of course), c5 changes the special character to a question mark as in fin vs. ?n.

Is this my DB encoding? It's utf8_general_ci.
Any ideas out there on this one?

FYI, if you're wondering how I got the HTML special character's code for Georgia, it's a cinch, if you use Font Explorer X 1.2.3 (Free) for font management, or any font manager probably. In FEX, you can find the font, double click the version you need the characters for, and the character set pops up. Select the character you're looking for w/ a double click, and an inspection bar pops out w/ extended info for the character. On of lines is "HTML Code". Hope someone finds that useful.

Thoughts anyone?

Abs0lute
 
TheRealSean replied on at Permalink Reply
TheRealSean
I am having a similar problem trying to display some Russian Characters,
Ill try them here, брат (Thanks tohttp://kanjidict.stc.cx/recode.php)...
HTML code is брат

But I still get the ???? When used in the content block
Did you ever resolve this?
Abs0lute replied on at Permalink Reply
Abs0lute
No, I never got this resolved. It wasn't crucial, so I put it on the backburner and see what kind of responses trickled through.
Hopefully someone will be able to direct us in the right direction.
TheRealSean replied on at Permalink Reply
TheRealSean
I managed to get round it by entering the html directly into the DB within btContentLocal, but I can't seem myself doing that every time the copy is amended.
Abs0lute replied on at Permalink Reply
Abs0lute
I can see your case being much more crucial than mine. I don't see changing it in the db as a viable option. I guess it's something in c5's core that's possibly got a list of available special characters maybe?
Anyone out there more familiar w/ c5's handling of special characters or tinymce's handling of them?
Abs0lute replied on at Permalink Reply
Abs0lute
Not an answer, but for anyone looking into this, here's a great article on custom font-stacks and the little known css attribute "unicode-range".
http://24ways.org/2011/unicode-range...
TheRealSean replied on at Permalink Reply
TheRealSean
I did revisit this problem this year, and noticed my db-encoding was set to latin-swedish,

I set it to unicode UTF-8, and for me I was then able to put in Arabic script,

This was after making sure my document types where all using utf-8