Texas was a Mexican colony that declared independence then joined a "equal but separate" treaty with the US...
Right. They declared independance because they had let too many settlers in from the US who they failed to obey Mexican law, revolted against the Mexicans, and declared independance. It was the US settlers who revolted, not the Mexicans.
Well, California was techincally it's own country before joining the US. So was Texas...
Texas, as part of Mexico, allowed U.S. settlers into Mexico/Texas on the provision they would abey Mexican law, and try to become citizens. When enough U.S. settlers got there, the revolted against Mexico and declared independance, and THEN the U.S. annexed Texas. Really, totally bad faith on the part of the settlers and U.S. So quit fooling yourself with the "but it was it's own country first" argument, that was solely because of settlers rebeling and kicking out and killing Mexicans.
(BTW, I am not of that ancestry, but I've read a lot about it...)
My favorite new aspect is the cultural assimilation of other cities. For example, if you have a strong cultural identity (basically, borders) - and you are close to cities that don't...they may rebel and join your side...much in the way that several cities/territories that once belonged to Mexico joined up with the U.S.
Bad eample. That was the Mexican American War, where the U.S. pretty much were total bastards and liars and went in and took the territory they wanted. (Texas, New Mexico, Arizona, California, southern parts of Utah and Colorado). Nothing voluntary at all about that. GO read some history...
Drives my wife nuts. I use the arrow keys and pg-up/down keys to navigate while reading a page since I despise the rat. I only move the mouse to:
a) click on a frame backgound so I can use the arrow keys.
b) click on a link I already know I want to go to after reading the page.
Actually, if you have fonts that render the UniHan in a locale-sensitive way, it works perfectly. The UniHan in Japan show the kanji with the proper (culturally) way to draw them with a Japanese font, the UniHan in China show the hanzi correctly culturally, although you need different fonts for Simplified and Traditional, and similarly for Korea.
It is not so different from using different type faces - ie, in old Germany, most this were printed in an gothic-style font that was culturally correct, whereas printing in other countries at the same time used more "roman" based typesetting. However, the old German gothic 't' was unified with the Latin 't' - are we complaining? It is a similar issue.
ISO 10646, the Universal Character Set defines a 31 bit character set (2,147,483,648 character codes), not a 16 bit character set. Unicode 3.0's character set corresponds to ISO 10646-1:2000.
Actually, this is incorrect. Unicode / ISO 10646, when you count the high and low surrogater range of code points, addresses just over 21 bits worth of data - 1,112,063 code points, including private use area.
Why do I know? Been to recent Unicode conferences, have the standard, and I write software for it.
"These letters, like the last nine in Frank Poole, can be rearranged to form an anagram. In this case, the anagram is "No Meat." A wooden horse has no meat on its skeletal framework."
Why just the last nine? After all, all of "Frank Poole" could be "Ankle Proof" or "Freon Polka", obviously what Clarke intended, while the last nine merely give us "Pork Alone." Or "Poor Ankle", or "Penal Rook", or "Nap Looker" or....
While I live in a primarily MS-based company, I am one of the few (2-3 people) who has a Linux box on my desk as well as an NT box. To be quite frank, I have had NT BSOD exactly once in the last year, despite being heavily used for software development (of non-MFC, portable to several Unices & AS/400 C-language based software). The cause: a bad video driver from IBM.
(Caveat: This doesn't make me a Linux hater, it just means that FUD about windows NTs stability (in the desktop market) is usually over exagerrated. I still wouldn't want to use NT as a server due to bad experiences with NT 3.51 back when I was a SysAdmin - Three dinky NT 3.51 boxes took more time to babysit than 8 10-way SparcServer 2000's each with 800GB of disk. SHUDDER )
Of course, in the last 18 months, I have never had my Linux box crash. (RedHat 6.something, kernel 2.2.something).
Of course, I DO have to reboot the bloody NT box every time I install a freaking piece of software, and that really begins to irritate after the umpty-hundredth time.
Funny, I have a cable modem and do not subscribe to cable TV. I generally get 175 - 275 Kbytes per second on download, too (uploads are a full order of magnitude slower). I can't get DSL though. I'm very happy about it - I'm not paying anymore that I was for an extra phone line and my old ISP, either. With them I was lucky to get better than a 9600 baud connetion (with my 57.6 modem, partly because line quality from Qworst really sucked in my neighborhood). Just switched my other phone line over to the cable as well. I'm quite pleased with the quality of the signal.
Slashdot Mirror
In fact, the "animal" company has one, in French, and after inquiring by email, they aren't translating it to English!!!! ARRGHH!
Texas was a Mexican colony that declared independence then joined a "equal but separate" treaty with the US...
Right. They declared independance because they had let too many settlers in from the US who they failed to obey Mexican law, revolted against the Mexicans, and declared independance. It was the US settlers who revolted, not the Mexicans.
So, it is just as forceful of a takeover as ever.
Well, California was techincally it's own country before joining the US. So was Texas...
Texas, as part of Mexico, allowed U.S. settlers into Mexico/Texas on the provision they would abey Mexican law, and try to become citizens. When enough U.S. settlers got there, the revolted against Mexico and declared independance, and THEN the U.S. annexed Texas. Really, totally bad faith on the part of the settlers and U.S. So quit fooling yourself with the "but it was it's own country first" argument, that was solely because of settlers rebeling and kicking out and killing Mexicans.
(BTW, I am not of that ancestry, but I've read a lot about it...)
My favorite new aspect is the cultural assimilation of other cities. For example, if you have a strong cultural identity (basically, borders) - and you are close to cities that don't...they may rebel and join your side...much in the way that several cities/territories that once belonged to Mexico joined up with the U.S.
Bad eample. That was the Mexican American War, where the U.S. pretty much were total bastards and liars and went in and took the territory they wanted. (Texas, New Mexico, Arizona, California, southern parts of Utah and Colorado). Nothing voluntary at all about that. GO read some history...
Drives my wife nuts. I use the arrow keys and pg-up/down keys to navigate while reading a page since I despise the rat. I only move the mouse to:
a) click on a frame backgound so I can use the arrow keys.
b) click on a link I already know I want to go to after reading the page.
0x10ffff = 1,114,111 code points. So, what I said still stands.
This is incorrect, 44,946 surrogates were approved in March as part of Unicode 3.1.0.
Unicode 3.1 and 10646-2 define three new supplementary planes:
Supplementary Multilingual Plane (SMP) U+10000..U+1FFFF (1594 chars)
Supplementary Ideographic Plane (SIP) U+20000..U+2FFFF (43,253 chars)
Supplementary Special-purpose Plane (SSP) U+E0000..U+EFFFF (97 chars)
Or plane 1, 2, and 14. (from the Unicode 3.1 Technical report, #27)
Actually, if you have fonts that render the UniHan in a locale-sensitive way, it works perfectly. The UniHan in Japan show the kanji with the proper (culturally) way to draw them with a Japanese font, the UniHan in China show the hanzi correctly culturally, although you need different fonts for Simplified and Traditional, and similarly for Korea.
It is not so different from using different type faces - ie, in old Germany, most this were printed in an gothic-style font that was culturally correct, whereas printing in other countries at the same time used more "roman" based typesetting. However, the old German gothic 't' was unified with the Latin 't' - are we complaining? It is a similar issue.
You say:
ISO 10646, the Universal Character Set defines a 31 bit character set (2,147,483,648 character codes), not a 16 bit character set. Unicode 3.0's character set corresponds to ISO 10646-1:2000.
Actually, this is incorrect. Unicode / ISO 10646, when you count the high and low surrogater range of code points, addresses just over 21 bits worth of data - 1,112,063 code points, including private use area.
Why do I know? Been to recent Unicode conferences, have the standard, and I write software for it.
"These letters, like the last nine in Frank Poole, can be rearranged to form an anagram. In this case, the anagram is "No Meat." A wooden horse has no meat on its skeletal framework."
....
/me sighs
Why just the last nine? After all, all of "Frank Poole" could be "Ankle Proof" or "Freon Polka", obviously what Clarke intended, while the last nine merely give us "Pork Alone." Or "Poor Ankle", or "Penal Rook", or "Nap Looker" or
This looks like the beginnings of the Caves of Steel to me. So, when will the positronic brain be invented?
While I live in a primarily MS-based company, I am one of the few (2-3 people) who has a Linux box on my desk as well as an NT box. To be quite frank, I have had NT BSOD exactly once in the last year, despite being heavily used for software development (of non-MFC, portable to several Unices & AS/400 C-language based software). The cause: a bad video driver from IBM.
(Caveat: This doesn't make me a Linux hater, it just means that FUD about windows NTs stability (in the desktop market) is usually over exagerrated. I still wouldn't want to use NT as a server due to bad experiences with NT 3.51 back when I was a SysAdmin - Three dinky NT 3.51 boxes took more time to babysit than 8 10-way SparcServer 2000's each with 800GB of disk. SHUDDER )
Of course, in the last 18 months, I have never had my Linux box crash. (RedHat 6.something, kernel 2.2.something).
Of course, I DO have to reboot the bloody NT box every time I install a freaking piece of software, and that really begins to irritate after the umpty-hundredth time.
Not much point. All of them are already on ftp://ftp.gmd.de/if-archive/infocom/ and all the above mirrors also.
I feel obliged to mention another Linux interpreter for Infocom and Inform games that is not mentioned in the referenced pages. Check out:
http://jzip.sourceforge.net/
Funny, I have a cable modem and do not subscribe to cable TV. I generally get 175 - 275 Kbytes per second on download, too (uploads are a full order of magnitude slower). I can't get DSL though. I'm very happy about it - I'm not paying anymore that I was for an extra phone line and my old ISP, either. With them I was lucky to get better than a 9600 baud connetion (with my 57.6 modem, partly because line quality from Qworst really sucked in my neighborhood). Just switched my other phone line over to the cable as well. I'm quite pleased with the quality of the signal.