(a word being the term for 2 or more bytes, not a word like we use)
-
-
Replying to @Raven_Luni
OK, so my statement is mainly about Unicode strings, not reversing encoded bytes in any particular encoding.
1 reply 0 retweets 0 likes -
Replying to @qntm
so what did you mean by 'no concept of string reversal' ?
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni
I mean there's nothing in any version of the Unicode standard which explains how to reverse a string.
1 reply 0 retweets 0 likes -
Replying to @qntm
I wouldt expect to find such a thing in the unicode standard anymore than I woulnt expect to find it in the ASCII or ANSI standards...
2 replies 0 retweets 0 likes -
Replying to @Raven_Luni @qntm
If you want to reverse a string you run a bit of code that loops from the last character to the first - nomatter how its encoded
1 reply 0 retweets 0 likes -
Replying to @Raven_Luni
There's a lot of reasons why this general approach can result in gibberish Unicode. Combining diacritics, ligatures, RTL scripts
1 reply 0 retweets 0 likes -
Replying to @qntm
thats usually because of the variable word length - take UTF16 for example where each character is either 2 or 4 bytes
1 reply 0 retweets 0 likes -
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
"Naïve" has six characters, counting the combining umlaut. Naïvely reversing character by character results in "ev̈iaN". Accent's moved
-
-
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 - 5 more replies
New conversation -
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.