Testing UTF8
2013-10-26 01:55:20.80379+02 by Dan Lyke 18 comments
Ignore me, testing UTF-8: ╭∩╮(-_-)╭∩╮
And more testing:
ლ(╹◡╹ლ), ¯\_(ツ)_/¯, ಠ_ಠ,
(╯°□°)╯︵ ┻━┻)
2013-10-26 01:55:20.80379+02 by Dan Lyke 18 comments
Ignore me, testing UTF-8: ╭∩╮(-_-)╭∩╮
And more testing:
ლ(╹◡╹ლ), ¯\_(ツ)_/¯, ಠ_ಠ,
(╯°□°)╯︵ ┻━┻)
comments in ascending chronological order (reverse):
#Comment Re: made: 2013-10-26 01:55:41.94825+02 by: Dan Lyke
Why does this work in the main section and not in comments?
ââ©â®(-_-)ââ©â®
#Comment Re: made: 2013-10-26 02:08:28.54846+02 by: Dan Lyke
ââ©â®(-_-)ââ©â®
#Comment Re: made: 2013-10-26 02:31:43.762969+02 by: meuon [edit history]
Original: *#9581;∩*#9582;(-_-)*#9581;*#8745;*#9582;
In comments: *#226;*#149;*#173;*#226;*#136;*#169;*#226;*#149;*#174;(-_-)*#226;*#149;*#173;*#226;*#136;*#169;*#226;*#149;*#174;
with * replacing &
Comments post is encoding something differently. UTF8 Gods are laughing. But's not obvious.
#Comment Re: made: 2013-10-27 06:04:24.672553+01 by: spc476
ââ©â®(-_-)ââ©â®
#Comment Re: made: 2013-10-27 06:07:40.069447+01 by: spc476
Hmm ... my guess is that the form action is assuming the input is in ISO-8859-1. What happens if you change the form action to
<form style="margin-left: 0;" action="/archives/viewentry.cgi?id=" accept-charset="UTF-8" method="post" >
#Comment Re: made: 2013-10-28 17:33:05.134832+01 by: meuon
ââ©â(â£_â¢)ââ©â
#Comment Re: made: 2013-10-29 16:41:22.935674+01 by: Dan Lyke
Looks like it's inserting wrong: ââ©â®(-_-)ââ©â®
#Comment Re: made: 2013-10-29 16:48:24.803995+01 by: Dan Lyke
And now? ╭∩╮(-_-)╭∩╮
#Comment Re: made: 2013-10-29 17:01:01.328986+01 by: Dan Lyke [edit history]
╭∩╮(-_-)╭∩╮
#Comment Re: made: 2013-10-30 04:12:36.952629+01 by: spc476
╭∩╮(-_-)╭∩╮
So, what was the problem?
#Comment Re: made: 2013-10-30 16:23:26.985693+01 by: Dan Lyke
Fuuuu... now it's stopped working again?
╭∩╮(-_-)╭∩╮
#Comment Re: made: 2013-10-30 22:33:45.608028+01 by: Dan Lyke
╭∩╮(-_-)╭∩╮
ლ(╹◡╹ლ), ¯\_(ツ)_/¯, ಠ_ಠ,
(╯°□°)╯︵ ┻━┻)
#Comment Re: made: 2013-10-31 01:56:47.651669+01 by: meuon [edit history]
¯\_(ã)_/¯ = Absolutely Brilliant! - Hmm, did not work for me..
#Comment Re: made: 2013-10-31 16:28:05.812327+01 by: Dan Lyke
¯\_(ツ)_/¯
#Comment Re: made: 2013-10-31 16:28:40.538649+01 by: Dan Lyke
Crap. Worked for me. Firefox 17.0.9 SL6/Gnome.
#Comment Re: made: 2013-11-01 18:58:50.786214+01 by: Jack William Bell
Just to give you another test, here is all of the above sent from Google Chrome 18.0.1025.151 on a Macbook running OSX 10.8.3.
ââ©â®(-_-)ââ©â®
á(â¹â¡â¹á), ¯\_(ã)_/¯, ಠ_ಠ,
(â¯Â°â¡Â°ï¼â¯ï¸µ â»ââ»)
#Comment Re: made: 2013-11-01 18:59:37.998559+01 by: Jack William Bell
Note: Did that 'cut and paste'. So maybe the problem is there? It looked OK in the comment box before I sent it.
#Comment Re: made: 2013-11-01 19:53:25.274026+01 by: Dan Lyke
I'll have to find some time to fire up Chrome and see what's happening. The document should be tagged UTF-8, but maybe the form isn't for some reason? The CGI object should be instantiated everywhere with -utf8, which should assume that encoding for everything, but...
And, yeah, I'm using cut-and-paste too.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.