Test your sig here
Lets not stop the flow of hate, post your sig tests here.
EireDOrakaa
15 years ago
Well here goes nothing...
Jetamio
15 years ago
EIRE!!!
EireDOrakaa
15 years ago
Heya me darlin'! Yes I'm finally here *grins* ... Lessa finally wrangled me into it *winks at Lessa*.
How goes it? I'm now trying to figure out how to do things on this site....Gaahhhh..failing miserably. Give me good old pen, inks and paint...I suck at computers!
How goes it? I'm now trying to figure out how to do things on this site....Gaahhhh..failing miserably. Give me good old pen, inks and paint...I suck at computers!
Lessa
15 years ago
Yay Eire! This is the sig test thread you know, right? :)
If you need anything, just ask me, I can probably help.
If you need anything, just ask me, I can probably help.
Aellas
14 years ago
test
yay it works!!
yay it works!!
kendi64
14 years ago
tests
Gongaa
14 years ago
Character encoding test.
☃ ☠ ☃ ☠ ☃ ☠ ☃ ☠ ☃ ☠ ☃
Do you guys see snowmen and skulls and crossbones or question marks / boxes?
Do you guys see snowmen and skulls and crossbones or question marks / boxes?
Dia
14 years ago
snowman and skulls! The combo is pretty cute
pharren
14 years ago
Boxes on whatever Atrix default browser is
Gongaa
14 years ago
Is that your phone? It's probably using Latin1 as its encoding, just like they do in Soviet Russia... ☭
(Actually they used KOI8-R while they were still around. Now they use unicode, too - OR THEY SHOULD, ANYWAY.)
(Actually they used KOI8-R while they were still around. Now they use unicode, too - OR THEY SHOULD, ANYWAY.)
pharren
14 years ago
After looking at Facebook I realized what you were trying to do and consequently just how irrelevant my post was. Boo hoo. I should probably install the Firefox app.
Gongaa
14 years ago
The Facebook post stemmed out of what I was doing here. I was originally snooping around and saw that TAC's default encoding is ISO-8859-1 (i.e. Latin1) and was worried that you guys would see boxes every time I used a Euro sign, so I did the snowmenz / skullz test to see what would happen.
As it turns out, TAC's backend converts characters outside of the Latin1 encoding to their respective html entities before writing them to its database, which lets it get around the encoding thing by sacrificing efficiency by up to 800% on some characters. All modern desktop browsers understand unicode, so displaying the entities' relative bitmaps is no problem. It looks like that's not necessarily the case with phones.
Anyway, I got to digging around the interwebz after that and came across a page with funny unicode characters without displaying their unicode code point, so I cranked up vim, stripped off everything but html entities using:
:%s\&#\d\+;/\=setreg('A', submatch(0), '1')/g|%d _|pu a|0d _
and then taking all that stuff and simultaneously converting it and putting it in a form I like with something like
:%s/&#\(\d\+\);/\=printf("\&#%s;<\/span> = U+%x
\n
\n",submatch(1),submatch(1))
and then I was done!
Moral of the story: vim pwnz *\. (<-- lol)
As it turns out, TAC's backend converts characters outside of the Latin1 encoding to their respective html entities before writing them to its database, which lets it get around the encoding thing by sacrificing efficiency by up to 800% on some characters. All modern desktop browsers understand unicode, so displaying the entities' relative bitmaps is no problem. It looks like that's not necessarily the case with phones.
Anyway, I got to digging around the interwebz after that and came across a page with funny unicode characters without displaying their unicode code point, so I cranked up vim, stripped off everything but html entities using:
:%s\&#\d\+;/\=setreg('A', submatch(0), '1')/g|%d _|pu a|0d _
and then taking all that stuff and simultaneously converting it and putting it in a form I like with something like
:%s/&#\(\d\+\);/\=printf("\&#%s;<\/span> = U+%x
\n
\n",submatch(1),submatch(1))
and then I was done!
Moral of the story: vim pwnz *\. (<-- lol)