thats usually because of the variable word length - take UTF16 for example where each character is either 2 or 4 bytes
-
-
Replying to @Raven_Luni @qntm
It makes a bit more complicated as you have to A example 4 bytes at a time to tell which is the case and B make sure you dont go past 0
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni @qntm
alot of thse knocked up scripts either wont check the encoding or dont support all of them
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni
"Naïve" has six characters, counting the combining umlaut. Naïvely reversing character by character results in "ev̈iaN". Accent's moved
1 reply 0 retweets 1 like -
Replying to @qntm
hehe I remember my dad made that joke when bottled water because a thing (evian) :p Anyway it looks like the unlaut is a separate code
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni @qntm
and theyve simply reversed the codes not taking into account that the one for the umlat is a prefix
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni @qntm
and thats became not because - I have become my own autocorrect (i dont use it and still type whole wrong words) :P
1 reply 0 retweets 0 likes -
-
Replying to @Raven_Luni @qntm
N a i .. v e - its after the i here e v .. i a N - its after the v here
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni @qntm
more accurately the .. is most likely the high byte of a UTF-8 2 byte code for i (in little endian format).
2 replies 0 retweets 0 likes
In this instance there are two characters, the lower-case "i" and the umlaut. The choice of encoding isn't really significant to the problem
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.