the Royal Thai Navy's Hydrographic department is in charge of providing a national time server & it looks like they got windows covered at least (yes they devoted more than 1/2 of that page to windows 95/windows ME, no Mac, no Linux--not sure what stats they're running off).
in any case, if you're in Thailand, point your time server at:
and bob's your uncle. i like the idea of having a "local" time server so we swapped tout de suite. works plenty fine. the navy, as usual, did a bang up job.
geez, they've left nothing to complain about ;-)
so be there or be square.
ouch. but hey ok, there was a "download from iTunes" link. so hey ho, off to the iTunes store i go. a buck ninety-nine? a bargain. click the buy button, "content not available in thai store". geez louise. ouch again.
suffice to say i'm fairly disappointed, i was expecting something a bit more global from these fine folks.
ps: none of the links in that flash filler work.
note the release dates:
- 1st episode july 15th
- 2nd episode july 17th
- 3rd episode july 19th
the free airings will get pulled midnight july 20th.
they've got a comic over on mySpace.
everything is, of course, done up in flash.
so remember, if you have a friend that excels in math and science, report them!
you younger folks out there probably should pay particular attention as an NY Times op-ed piece points out that the younger you start binge drinking, the more significant the effects on the goop between your ears.
no matter your age though, exercise is supposed to help. so get on your bike, put on your jogging shoes, head for the gym, etc. and do whatever it takes.
your brain needs the exercise.
maybe romo, brady, et al should take note?
the "moronland" page is kind of unique in that it coins the term Babelfished, as in I wonder if these companies just Babelfished the slogans into another language.
another set of examples why you should use human beings for translation ;-)
and yes, even though it helps "date" me, i am still a fan of Prince's 1999.
from a beer drinker's standpoint, this is a bad thing. the brewery is different, the water is different, the ingredients will probably be sourced differently, geez louise how can it be the same beer? pretty much anyone who is serious about beer knows that commodity beer is usually bad beer and commodity beer is what AB is all about. i don't like any of the AB products, so slapping a rolling rock label on the dish-water slop they normally churn out seems like a sin to me. there's a social impact to this as well. the folks in latrobe, pa. where they make rolling rock, are devastated. it was a big deal for them (well that & the pittsburg steelers training camp, btw why aren't any steeler fans raising a ruckus?). this is just a bad deal all around.
so it's time to leave your watch & wallet at home & wrap up your money & mobile phone in zip-locked baggies. here comes the water :-)
btw you too can help celebrate this holiday, grab a water pistol or bucket of water & dowse everybody in sight ;-)
this is all news to me....i wonder how they advertize windows there? i know we have a good group of turkish coldfusion users, care to shed some light on this guys?
which brings us to the point of this blog entry, this method expects the year argument to be a persian calendar "year" (right now its 1383 in the persian calendar). which i didn't quite grasp at first, as the other calendars (gregorian, buddhist and japanese) with leap years have an isLeapYear method that expects a gregorian year (yes, even the buddhist and japanese calendar classes expect a gregorian year, i imagine this is because these calendars extend the gregorian calendar class). and that's the way i expected the new persian calendar to behave (my own cultural bias--i use the buddhist and gregorian calendars on a daily basis). but it doesn't and why the heck would it? it is a persian calendar after all. so that got me to thinking about the other calendars and the way these "should" work and what other cultural biases have leaked into our code and test harnesses--especially the tests.
first thing i did was to rewrite the i18nIsLeapYear functions across all the calendars to expect a year argument in that calendar's system (it converts to gregorian year as needed and now automagically returns false for calendars lacking the concept of a "leap year").
then i went a hunting for any other places where my cultural bias might have leaked thru....and promptly found it in the getYear function. the getYear function takes a gregorian year value and returns the year in that calendar's system. i was doing that by creating a date:
(and just in case you were wondering, the 2 for the day value is to make sure the date value created fell into that year, given that we're using UTC as the time zone standard for all the calendars). and then setting the calendar object to that date and returning the value for that calendar object's YEAR field:
simple and worked swell for the gregorian, buddhist and japanese calendars because these calendars' year started at the same time. but after looking at the year values of formatted dates from the other calendars i realized that the getYear function was returning horrible nonsense for the other 4 calendars. without realizing it, i'd let my calendar bias creep in and assumed the calendar's were all the same as far as years were concerned. gregorian 2-jan actually falls into different calendar years depending on the calendar (of course, they're different freaking calendars). and the tests were only reporting whether the getYear function "worked" by checking if the year was a positive integer, no eyeball comparisons against the year bits of the formatted date strings. there's a lesson here some where.
so better grab the new code and maybe give the calendars a good poking at to make sure no other cultural bias is left in it.
a lunar calendar was used in japan from the 14th to the 19th century. that calendar had a six day week and those six days were known as rokuyo. and like any other calendar system, each day had a name and a particular meaning (you do know that the english weekdays are named after one of the seven "planets" of ancient times?). and of course, each day had a significance:
- sakigachi good luck in the morning, bad luck in the afternoon
- tomobiki good luck all day, except at noon
- sakimake bad luck in the morning, good luck in the afternoon
- butsumetsu Unlucky all day, as it is the day Buddha died
- taian 'the day of great peace', a good day for ceremonies
- shakku bad luck all day, except at noon
while i'd guess few people would admit to closely adhering to this system, it does invoke some strange "better safe than sorry" behaviors. for instance, some hospital patients in japan won't agree to be discharged on butsumetsu day, as it's regarded as being very unlucky. rather they'd stay the extra 24 hours to be discharged on a lucky taian day.
the calculations for determining rokuyo turn out to be surprisingly difficult. in fact, the only published code i ever saw for this was developed by Eirik Rude, a cf developer (at that time living in japan). the complexity comes from the need to calculate lunar months (remember the old japanese calendar?). since i wanted to integrate this functionality with our existing icu4j-based calendars, i poked thru the lunar calendars (chinese, islamic and hebrew) that i knew about to see if we could use any of these. of course, the old japanese lunar calendar was basically the lunisolar chinese calendar. using Eirik's basic logic and the icu4j library i was able to considerably reduce the code's complexity (the complexity's still there, but i pushed it down into the icu4j java library where smarter people than i have already dealt with it).
the rokuyo testbed is here and the i18n calendars package incorporates this new functionality (pick japanese calendar from the select). and this is a good resource if you want to read more about rokuyo.
and i used to hem and haw over bad traffic/bad weather on election day.
interesting contrast between the "international" coverage by CNN and BBC. CNN laid it on pretty thick with a special report full of their big gun reporters (i guess it was also for the US as well, they had some domestic anchor leading the show, she led into each story with some kind of smarmy/trivializing line, rankled me no end). BBC had some iraqi election coverage (one reporter was parading around empty streets thumping on his flak jacket--like we couldn't see the darned thing against his light colored shirt) but then switched to covering the michael jackson trial. oh my.
ps: "got sand" is an old western (as in cowboy) slang meaning to have guts, courage, or toughness.
the article goes on to claim that welsh is a "great example", citing the existance of welsh porn. i guess they forgot about the irish.
anyway something to think about.
Puijilittatuq? why that's an Inuktitut (eskimo) word meaning "he does not know which way to turn because of the many seals he has seen come to the ice surface". man that's some kind of efficient communication.
Yukpa, Nitak Hollo Chito
Mitho Makosi Kesikansi
En frehlicher Grischtdaag unen hallich Nei Yaahr!
Mele Kalikimaka & Hauoli Makahiki Hou
La Maunia Le Kilisimasi Ma Le Tausaga Fou
Selamat Hari Natal dan Tahun Baru
Selamat Hari Natal
Maligayang Pasko at Manigong Bagong Taon
Chuc Mung Giang Sinh - Chuc Mung Tan Nien
Natale hilare et Annum Nuovo!
Nollaig chridheil agus Bliadhna mhath ur!
Nollaig Shona Daoibh Athbhliain Faoi Mhaise Daoibh
Nollaig chridheil huibh
Nadolig LLawen a Blwyddyn Newydd Dda
Wesolych Swiat i Szczesliwego Nowego Roku
Vrolijk Kerstfeest en een Gelukkig Nieuwjaar!
Joyeux Noël! Bonne Année!
Glædelig Jul og godt nytår
God Jul og Godt Nyttår
Bon nadal i feliç any nou!
Feliz Navidad y Próspero Año Nuevo
Geseende Kerfees en 'n gelukkige nuwe jaar
something i guess i should look into some more.
i've lived in bangkok for more than 20 years and have had my nose rubbed in thailand's culture all the while, my east coast american cultural skin has been rubbed clean off in places. perhaps because of this i don't find it all that hard to get into other cultures while i develop cf applications. its "normal" for me to make an app come out of the gate i18n. but you certainly don't have to live 20 years in some place other than your hometown to get an i18n mindset, all have you to do is not be so "provinicial" and recognize that there's other places in the world than what you have in your frontyard--there are also a lot of messy technical details but that's another story.
in any case, the article's a good read, my ranting aside.