Comments for As Thick As Two Short Planks - Mark Fowler's Blog

Comment on Once is Enough by 2shortplanks

2shortplanks — Mon, 16 Jan 2012 17:17:34 +0000

Hello Anonymous whoever you are!

I’m a UTF-8 junkie; I’ve done enough i18n programming to know that you should probably always be using UTF-8 unless you’ve got a very good reason not to (e.g. you need a fixed width binary representation or you’re using a lot of very high bit characters, in which case UTF-32 or its ilk might be better.)

This said, I do prefer to output characters in the ASCII range (even if I am generating UTF-8) and use HTML entities. Until you’ve suddenly had part of your CMS re-written to embed text in emails for inclusion into webmail clients you’ve not known the pain of using character encodings. Another point worth noting is that the output character encoding often influences the character encoding the browser will submit form data back in and care needs to be taken there. In short…there’s no short answer to this.

Comment on Simple Todo List Processing in Perl by 2shortplanks

2shortplanks — Mon, 16 Jan 2012 14:36:16 +0000

That might be an arguably cleaner interface, but it wouldn't actually do what I wanted in terms of altering the original tied file. The filter already exists in List::MoreUtils - it's called part and requires the function to return the number of the array it should place the result into. For example: my ($fail, $pass) = part { /Lion/ } qw(MufasaLion JosieCat PinkPanther SimbaLion)

Comment on Simple Todo List Processing in Perl by Mark Stosberg

Mark Stosberg — Mon, 16 Jan 2012 14:28:12 +0000

I use todo.txt for a text-based TODO handling system: http://todotxt.com/

It has a good number of features, plugins and front-ends which make it pleasant to use

Comment on Simple Todo List Processing in Perl by Gabor Szabo

Gabor Szabo — Mon, 16 Jan 2012 07:42:31 +0000

I am far from being a “clean code experte” so I just wonder if instead of the extract() function, wouldn’t it be cleaner code if there was a filter

my ($pass, $fail) = filter { … } @source;

that would move the success elements in one array ref and the failure elements in another array ref?

Comment on Once is Enough by Anonymous

Anonymous — Mon, 16 Jan 2012 04:46:28 +0000

You teach a tool, but neglected to tell the circumstances when it should not be used and when it should. W3C [tutorial-char-enc] recommends: “Save your pages as UTF-8, whenever you can. … Avoid using character escapes, except for invisible or ambiguous characters.” The details are in [qa-escapes].

http://www.w3.org/International/tutorials/tutorial-char-enc/Overview.en#quicksummary
http://www.w3.org/International/questions/qa-escapes.en

Comment on Once is Enough by realdavorg

realdavorg — Sun, 15 Jan 2012 10:55:46 +0000

Bizarre how it’s being too clever for the numeric entities but exactly the right level of clever for the named entities.

Comment on Once is Enough by 2shortplanks

2shortplanks — Sun, 15 Jan 2012 10:50:28 +0000

WordPress.com is being way too clever here. I’m tempted to move away to a self hosted solution here!

Comment on Once is Enough by realdavorg

realdavorg — Sat, 14 Jan 2012 22:06:10 +0000

And, of course, some times you specifically want double-encoded entities – so that you can show the entities in HTML output, as in the table near the top of this post. But it looks like either you or WordPress are being too clever here, as I’m seeing the third column as the same as the first column.

Comment on Once is Enough by 2shortplanks

2shortplanks — Sat, 14 Jan 2012 00:15:34 +0000

Some of the text in the example at the end of this post is garbled; This is because wordpress seems to not be allowing me to put in the double encoded entities I need to complete the example.

Comment on Once a week, every week by Philippe Bruhat (BooK)

Philippe Bruhat (BooK) — Sat, 07 Jan 2012 23:41:05 +0000

Indeed.

And then you’ll have to compete not only with authors of 2012, but also authors since the beginning of CPAN.

I have a chain that is almost two years long in 2005-2006… ;-)

Anyway, only 20 minutes left to push my first module of 2012 to CPAN. Gotta hurry!