tag:blogger.com,1999:blog-11788780.post563148726532207252..comments2023-12-29T13:22:33.104-08:00Comments on JJinuxLand: MySQL: Encoding Helljjinuxhttp://www.blogger.com/profile/03270879497119114175noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-11788780.post-51291265495443704092009-03-05T23:10:00.000-08:002009-03-05T23:10:00.000-08:00Wow, awesome comments! Thanks, guys.Wow, awesome comments! Thanks, guys.jjinuxhttps://www.blogger.com/profile/03270879497119114175noreply@blogger.comtag:blogger.com,1999:blog-11788780.post-56462573480202500482009-03-05T09:32:00.000-08:002009-03-05T09:32:00.000-08:00there is a related thingie that i have noted even ...there is a related thingie that i have noted even some web frameworks get wrong—the ambiguity in encoding of URLs as sent by the browser. firefox2, for one, likes to send out URLs in the system encoding (or so i guess) where possible and to switch to UTF-8 when not possible. <BR/><BR/>this is why typing http://example.com/ä will give me http://example.com/%E4 in the browser address bar, but typing http://example.com/äЖ will give me http://example.com/%C3%A4%D0%96 where ä is %C3%A4. neat, eyh? means you have to have at least one fallback encoding scheme ready for when UTF-8 fails. <BR/><BR/>the nasty thing here is that (1) there is to my knowledge no way for the client to include information about URL encoding used; (2) you can only have one fallback encoding scheme that is activated by UTF-8 decoding failure—schemes like Latin-1 do not have a big chance to throw an exception on string.decode; (3) what fallback scheme to use will depend on the geolocation of the majority of your clients; (4) since URLs are typically rather short pieces of text, a heuristic encoding detection (such as the ones browser employ for web pages) should be difficult to impossible to implement; (5) if the secondary URL encoding is really governed by system settings it may prove exceedingly difficult to testdrive whatever setup you choose. <BR/><BR/>all told, it's sort of a shame that in 2009 we still have technology that shows erratic %4D%75%6D%62%6F%4A%75%6D%62%6F instead of readable text. this should have been in the past by now.flowhttps://www.blogger.com/profile/18342392935682557868noreply@blogger.comtag:blogger.com,1999:blog-11788780.post-5067023776145476032009-03-05T07:37:00.000-08:002009-03-05T07:37:00.000-08:00In Spanish sureñas is female plural for "southern"...In Spanish sureñas is female plural for "southern". Spanish adjectives don't need a filler noun. (for instance "little" by itself functions like "little one") so without context its safe to assume "women" for a regional adjective like "sureñas"<BR/><BR/>"southside southern women"<BR/><BR/> I further guess its latin women.rgzhttps://www.blogger.com/profile/00299003818364105534noreply@blogger.com