Emperor's new groove has a lot more CG in it than most people realise. I mean, the makority of people realise that the big log falling down the waterfall was quite obvious 3D art, but there were a lot of little things that went by unnoticed: The cart that Pacha pulls around when he goes to see the Emperor, for example, or the bag that Kuzco is dropped in.
Disney seem to have foudn a method of generatign a 3D model, and animate it in a way that looks cartoony. At the very least, the 3D models were used as rough sketches form which to draw the cartoony bits.
Also, Emperor's new groove was coloured entirely digitally.
(I'm getting all this from the second DVD in the special edition of the film, BTW.)
So what happens if I, a resident in Spain, wish to send email via a British mailserver to an American recipient? This is somethign I actually do regularly, as well as recieve email stored on a UK POP account. Where do I pay the tax? Could spammers just get around it by using offshore mailservers in countries that won't bother to put in a tax?
Hell, thinking about it, how would you define the sendign of email? A quick traceroute to my ISP's SMTP server shows that the packets from my machine get to that server via france, the UK, The netherlands, and belgium. This is *before* I even start esending the email. Would I end up having to pay 1 Eurocent to each of these jurisdictions just because my ISP doesn't have a local peering agreement with its ADSL provider?
The internet is a global phenomenon. Stop thinking in terms of US only.
He's right on one thing though, Innovation is desperately needed on the DNS system.
The keyboard I'm currently using has two keys on it which print symbols that are not valid in DNS names. These letters are used quite frequenetly in three of the languages that I can write in. (for the record, that's Ñ and Ç - I wonder if slashdot can cope with them?)
It *is* an annoyance when people find they cannot put the names they wish to use, in some cases the names they've been trading under for many years, because at the time, the designers of the system never imagined that the non english-speaking world would want to join in. Hell, Spain can't use its own name in its main language, España, as a valid domain name, and if you think of the number of companies with names along the lines of "American Autos", "US Robotics" and "CompUSA", then you start to see how limiting it is to the large number of spanish companies that have similar naming schemes.
Saying to spaniards "well, don't use a squiggly n, use a plain one" is not really a viable option - the ñ is a separate letter in its own right, and sometimes words are already in existence in the dictionary that just have an n instead of an ñ, and the meaning changes completely. As an example, the word año, meaning year, could not have as a substitute the word ano, meaning anus.
The same goes for ç in french and catalan, and I wouldn't be surprised if similar problems occured in places like Norway and Turkey, which also have commonly used letters not in the ASCII range.
It's even worse for companies and people in countries with completely different alphabets, such as Greece, The various middle-eastern countries, Russia, China and Japan. The translations between these languagese and the latin alphabet are not always well-defined, and so a domain name can't be thought abotu mnemonically, becasue you're not always sure how those sounds tranlate into a character set that you won't necessarily be very familiar with.
And it's not like we don't have a sensible upgrade path available. With the standardisation of the UTF-8 character set, machines can slowly be upgraded without requiring any changes to support the exisiting domain names. New names will not work globally for a while, but you can be fairly sure that most places outside of US, Canada, Britain, Oz, and NZ will be very quick to upgrade once software is released.
I'm not saying that the realnames software was good, but it did have that very useful trait for foreign companies, and it could possibly have become the defacto DNS for a lot of countries because of that.
I just hope the IETF address this issue before Microsoft step in and do their own thing. The last thing I want to see out there is a Microsoft-owned and -run DNS.
Slashdot Mirror
Was your grandfather a member of the Societas Eruditorum?
Emperor's new groove has a lot more CG in it than most people realise. I mean, the makority of people realise that the big log falling down the waterfall was quite obvious 3D art, but there were a lot of little things that went by unnoticed: The cart that Pacha pulls around when he goes to see the Emperor, for example, or the bag that Kuzco is dropped in.
Disney seem to have foudn a method of generatign a 3D model, and animate it in a way that looks cartoony. At the very least, the 3D models were used as rough sketches form which to draw the cartoony bits.
Also, Emperor's new groove was coloured entirely digitally.
(I'm getting all this from the second DVD in the special edition of the film, BTW.)
So what happens if I, a resident in Spain, wish to send email via a British mailserver to an American recipient? This is somethign I actually do regularly, as well as recieve email stored on a UK POP account. Where do I pay the tax? Could spammers just get around it by using offshore mailservers in countries that won't bother to put in a tax?
Hell, thinking about it, how would you define the sendign of email? A quick traceroute to my ISP's SMTP server shows that the packets from my machine get to that server via france, the UK, The netherlands, and belgium. This is *before* I even start esending the email. Would I end up having to pay 1 Eurocent to each of these jurisdictions just because my ISP doesn't have a local peering agreement with its ADSL provider?
The internet is a global phenomenon. Stop thinking in terms of US only.
Hmm, in other worse, a crytpographically secure version of this?
He's right on one thing though, Innovation is desperately needed on the DNS system.
The keyboard I'm currently using has two keys on it which print symbols that are not valid in DNS names. These letters are used quite frequenetly in three of the languages that I can write in. (for the record, that's Ñ and Ç - I wonder if slashdot can cope with them?)
It *is* an annoyance when people find they cannot put the names they wish to use, in some cases the names they've been trading under for many years, because at the time, the designers of the system never imagined that the non english-speaking world would want to join in. Hell, Spain can't use its own name in its main language, España, as a valid domain name, and if you think of the number of companies with names along the lines of "American Autos", "US Robotics" and "CompUSA", then you start to see how limiting it is to the large number of spanish companies that have similar naming schemes.
Saying to spaniards "well, don't use a squiggly n, use a plain one" is not really a viable option - the ñ is a separate letter in its own right, and sometimes words are already in existence in the dictionary that just have an n instead of an ñ, and the meaning changes completely. As an example, the word año, meaning year, could not have as a substitute the word ano, meaning anus.
The same goes for ç in french and catalan, and I wouldn't be surprised if similar problems occured in places like Norway and Turkey, which also have commonly used letters not in the ASCII range.
It's even worse for companies and people in countries with completely different alphabets, such as Greece, The various middle-eastern countries, Russia, China and Japan. The translations between these languagese and the latin alphabet are not always well-defined, and so a domain name can't be thought abotu mnemonically, becasue you're not always sure how those sounds tranlate into a character set that you won't necessarily be very familiar with.
And it's not like we don't have a sensible upgrade path available. With the standardisation of the UTF-8 character set, machines can slowly be upgraded without requiring any changes to support the exisiting domain names. New names will not work globally for a while, but you can be fairly sure that most places outside of US, Canada, Britain, Oz, and NZ will be very quick to upgrade once software is released.
I'm not saying that the realnames software was good, but it did have that very useful trait for foreign companies, and it could possibly have become the defacto DNS for a lot of countries because of that.
I just hope the IETF address this issue before Microsoft step in and do their own thing. The last thing I want to see out there is a Microsoft-owned and -run DNS.