I don't think most Asians care about the word 'Oriental', but of course only the most sensitive are often heard. There was a congressman of Korea descent who made a big fuss about it, I don't remember the details, but the word 'oriental' is formally banned from government documents since.
BTW, the word 'Asia' might also come from the meaning of 'East'. at least wikipedia says so.
Google is going to release a statement that stealing code/data is not evil in China, and Google must fit in local cultures and abide by local laws.
Seriously, this is just pathetic. I am appalled by the Google apologists on slashdot.
Chinese input is a well established market; Google Giant forces itself into the market with a product that is very similar to existing ones and offers no innovation. That is not evil enough? They did this by stealing data and who knows what from others. Mind you that the data is not publicly available, so Google must have committed certain crimes to obtain the data.
For those who don't see what's the big deal: the mapping from ASCII sequence to Chinese character/phrase is not trivial; actually it is what Chinese input is all about.
Why do Americans always want to force their own stupid ideas on other countries? What is next? Eating beef? Meeting girls without parent arrangement? Having names of only two syllables?
It depends on how does the database store the date/time, how does the application translate date/time between user and database, and most importantly, what was the *nature* of the event(?!)
here's an example that survives DST rule change without patching the data:
database: store yyyyMMddHHmmss literally, without any timezone information event: lunch with someone at 12:30 PDT, 3/31/2007
here's another example that also survives:
database: store "number of milliseconds since 1/1/1970 00:00 GMT" event: watch solar eclipse at 10:32 PDT, 3/19/2007
in both examples, the application uses the timezone/DST rules that it knows at the moment.
I don't have to list examples that won't work. And it's almost certain that different systems will have different ideas in interpreting a time they previously agreed upon.
Slashdot Mirror
I don't think most Asians care about the word 'Oriental', but of course only the most sensitive are often heard. There was a congressman of Korea descent who made a big fuss about it, I don't remember the details, but the word 'oriental' is formally banned from government documents since.
BTW, the word 'Asia' might also come from the meaning of 'East'. at least wikipedia says so.
Google is going to release a statement that stealing code/data is not evil in China, and Google must fit in local cultures and abide by local laws.
Seriously, this is just pathetic. I am appalled by the Google apologists on slashdot.
Chinese input is a well established market; Google Giant forces itself into the market with a product that is very similar to existing ones and offers no innovation. That is not evil enough? They did this by stealing data and who knows what from others. Mind you that the data is not publicly available, so Google must have committed certain crimes to obtain the data.
For those who don't see what's the big deal: the mapping from ASCII sequence to Chinese character/phrase is not trivial; actually it is what Chinese input is all about.
they should apply the optimizer on their own pages.
shame on you,
Harinarayan; Venky (Mountain View, CA),
Rajaraman; Anand (Palo Alto, CA),
Ranganathan; Anand (Mountain View, CA)
unless, of course, the computer made you do it.
what about a blog on porns? and a porn of bloggers blogging each other?
why couldn't we have the following TLDs?
t ing
.voyeur
.anal
.anime
.asian
.bdsm
.cum
.fis
.latina
.mature
.panties
.pedo
.redhead
.watersport
I just wanted to make a stereotypical joke on the expense of Indians which I think Indians can take it. Nothing serious.
Why do Americans always want to force their own stupid ideas on other countries? What is next? Eating beef? Meeting girls without parent arrangement? Having names of only two syllables?
It depends on how does the database store the date/time, how does the application translate date/time between user and database, and most importantly, what was the *nature* of the event(?!)
here's an example that survives DST rule change without patching the data:
database: store yyyyMMddHHmmss literally, without any timezone information
event: lunch with someone at 12:30 PDT, 3/31/2007
here's another example that also survives:
database: store "number of milliseconds since 1/1/1970 00:00 GMT"
event: watch solar eclipse at 10:32 PDT, 3/19/2007
in both examples, the application uses the timezone/DST rules that it knows at the moment.
I don't have to list examples that won't work. And it's almost certain that different systems will have different ideas in interpreting a time they previously agreed upon.
Stay home on that day, people!
those farmers deserve the same quality of internet porn as what slashdotters enjoy every night.