August 10, 2004 at 11:56PM KWiki v2 (alpha) up online!
Today, due to various circumstances, I decided to get my wiki engine up and running properly.
It’s now got StableCopy versioning rather than the EditCopy system it used to use.
In addition, I’ve beefed up the formatting engine a bit. It’s now the same one as I use there. One difficulty I’ve had is that I’ve had to remove plaintext wikiwords. Why? Because ColdFusion 5 has a crappy RegEx engine and having them and marking wikiwords without a corresponding page became too difficult. Oh, to have MX running on the server.
Still, CF5 isn’t all bad. I ran into a nasty problem with CFMX that I never had with the previous versions: if you’re from anywhere even slightly out of the way, beware of your configured locale.
The problem I ran into was with CFDIRECTORY’s DateLastModified query field. In CF5, it’s returned in a relatively sane format: you can use it as a date, and ParseDateTime() and LSParseDateTime() have no problems understanding it.
Not so on CFMX: DateLastModified has some kind of wierd locale-dependant format. Considering there’s functions there if I wanted to format it for my current locale, this seems rather dumb.
If you’re a Yankistani, a Brit, German, blah, blah, blah, you’re fine, but head even a bit out of the way, like here in Ireland, you’ve got problems.
Y’see, on the laptop I use, I’ve got the locale configured as en_IE. It’s a rather sane, reasonable choice seeing as I’m Irish and living here. Now, I also work to GMT/BST, though BST is called IST (Irish Summer Time) here: I think they might begin and end at slightly different times, but nothing major.
Now here’s the rub: CFDIRECTORY produced a date that was nice and easily parsable, and identical to its BST equivalent, except that it has IST at the end rather than BST. I tried LSParseDateTime(), which said what I parsed wasn’t a date (!), and ParseDateTime(), which said that en_IE wasn’t amongst the list of locales it understands (meaning it could parse the date, the locale to which it belonged, but couldn’t be bothered parsing it after that: it could identify the locale, for Dog’s sake!)
I kludged around it by fiddling with the locale settings in the jvm.config file for CFMX to make it think my locale was en_UK (best fit) rather than en_IE.
This little episode does not inspire confidence in me for Macromedia...
No comments.