View Single Post
Old 07-09-2013, 08:06 AM   #909
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by NiLuJe View Post
To answer knc1

(Don't mind the broken up/right arrows, that's due to the crappy unicode coverage of my custom Sans font)
Thanks!

Looks very usable to me.
(At least the pic doesn't say: "SegFault" anywhere. )

That earns the K2 a: "K2: status" field in the (to be) new button blob template.

PS:
Considering your current country, that font file may be ISO 8859-15 rather than Unicode.
OR
It is just (mis-) using U+00A4 for "replacement character".

Ref:
https://en.wikipedia.org/wiki/Wester...28computing%29

(No, I don't normally have that info on the top of my bookmarks stack - I just happen to be working on a custom Unicode parser this week.)

OR
Your "custom font file" has a Windows ancestry:
https://en.wikipedia.org/wiki/Wester...uting%29#Notes
(Note where Microsoft has re-defined the glyphs used in "iso 8859-1" to be compatible with their systems. I.E: If you can't get it right, change the standard.)

Last edited by knc1; 07-09-2013 at 08:50 AM.
knc1 is offline   Reply With Quote