I installed Ubuntu on my Mac. I installed it in Japanese (it was one of the options), installation stage 2 and suddenly all screen messages are scrambled. Great. No way to read what the buttons say. Well, force reboot and start install over. This time in English.
Next thing I find there's no Japanese input system. So I can display Japanese, but not input it. After searching the Ubuntu wiki I learn that Japanese actually isn't really supported (so why is it an installation option then?), but you can install a Japanese input system. Installed it, it works.
Next thing that I find is that for some reason in OpenOffice only about 2/3 of the Japanese characters get displayed properly the rest is replaced with some weird placeholder. Not that crap like this does not happen with the Alpha Java port of OpenOffice call NeoOffice/J for Mac OS X.
All in all Ubuntu might be better than many Linux distros, but compared to OS X it's a joke. Here I can use my OS switched to German and switch between German keyboard layout, US keyboard layout and Japanese input method on-the-fly.
Finally I can't tell you how dead-awful it is when you have a Linux box serving files, and then sitting on a Mac OS X client in all its Unicode glory having to deal with long Japanese filenames on the server (that Windows users put there) and being f***ed, because the "old" AFP protocol can't handle long filenames and going in via SMB doesn't work either, because the filenames being in Japanese cause problems, too.
Apple is not competing with some bloody ROLL YER OWN PC IN THE GARAGE bloke
People who want to do that are not Apple's target group. And you know why? Guess what? Because they're are fuckheads who'll ROLL THEIR OWN PC IN THE GARAGE and won't buy PC from a trusted vendor and pay a bit more to get a neatly looking package that actually works and has a warranty.
If you make those calculations please don't forget to also calculate the cost for the time it'll take you get all the drivers working properly and such things. Also don't forget to include the cost for the time and phonecalls once you need some help, because one or the other piece of hardware won't work as promised and either of the vendors will tell you that it's actually a) Window's fault b) The other hardware's drivers fault c) Your fault
Curiously, I also remember when Netscape began to offer serious cash bounties (~$1,000) for anyone who discovered security holes in their browser. I wish Microsoft would do that.
Microsoft, even with all their money, would be bankrupt in no time if they did that.
But thinking about this what, yes what if the T-Rex's voice was like a giant chicken voice... Imagine a T-Rex sitting on a hill and roaring his low pitched earth shattering Cock-A-Doodledoo into the early morning.
Even if you use PostFactoX to install OS X on unsupported hardware your Mac must have a G3 or later to run OS X. I don't think OS X (even 10.1) will run on a 604.
You might have installed OS X with PostFactoX on a 7500/7600 with a G3 upgrade card, but then it's not a 604 anymore.
Well, that's indeed pretty disappointing (I'm not a programmer, so I was just guessing), though it might not necessarily be Apple's fault, it could have to do with copyright to certain parts of the drivers that doesn't belong to Apple.:-(
Shouldn't a look at the drivers for Airport Extreme in Darwin help there? I know, that drivers in darwin are done quite differently than you'd write them for Linux, but shouldn't it be enough to understand how to basically write drivers for the AirportExtreme card?
The next step will be to get rid of those drivers. They're the ones always screwing up anyway, what better solution than to eliminate the biggest cause of error in driving?
Let's just build cars that drive themselves and everybody start walking to work again. Problem solved.
No it happens with any Japanese page I visit with Camino. Changing encodings doesn't fix the issue. The problem is that Camino for some reason uses the proper characters, but mixes all kinds of different fonts, so the pages looks unbearably ugly. I've experienced this with any version of Camino and I wonder why this is.
It still makes a complete visual mess when trying to display Japanese. It displays some words using different fonts for each character and quirks like this. Makes the page really ugly. I have no idea why that is, because Firefox renders those pages perfectly (as does Safari).
It's a shame because I'd rather use Camino than Firefox. Firefox doesn't use native widgets and still doesn't really look & feel like a fully OS X "native" application (although they're really doing their best to get closer).
See? And that's where it fails. It doesnt work out of the box.
I don't want to start fucking around after I'm finally done with the installation just to get my system to a level I can use it.
I installed Ubuntu on my Mac. I installed it in Japanese (it was one of the options), installation stage 2 and suddenly all screen messages are scrambled. Great. No way to read what the buttons say. Well, force reboot and start install over. This time in English.
Next thing I find there's no Japanese input system. So I can display Japanese, but not input it. After searching the Ubuntu wiki I learn that Japanese actually isn't really supported (so why is it an installation option then?), but you can install a Japanese input system. Installed it, it works.
Next thing that I find is that for some reason in OpenOffice only about 2/3 of the Japanese characters get displayed properly the rest is replaced with some weird placeholder. Not that crap like this does not happen with the Alpha Java port of OpenOffice call NeoOffice/J for Mac OS X.
All in all Ubuntu might be better than many Linux distros, but compared to OS X it's a joke. Here I can use my OS switched to German and switch between German keyboard layout, US keyboard layout and Japanese input method on-the-fly.
Finally I can't tell you how dead-awful it is when you have a Linux box serving files, and then sitting on a Mac OS X client in all its Unicode glory having to deal with long Japanese filenames on the server (that Windows users put there) and being f***ed, because the "old" AFP protocol can't handle long filenames and going in via SMB doesn't work either, because the filenames being in Japanese cause problems, too.
Yeah, and it'll have 64 tits, errr, bits.
I guess that's the 21st Century version of the sack of rice fallig over?
Shows you what all those violent video games are doing to mankind.
When will fuckheads like you ever understand:
Apple is not competing with some bloody ROLL YER OWN PC IN THE GARAGE bloke
People who want to do that are not Apple's target group. And you know why? Guess what? Because they're are fuckheads who'll ROLL THEIR OWN PC IN THE GARAGE and won't buy PC from a trusted vendor and pay a bit more to get a neatly looking package that actually works and has a warranty.
If you make those calculations please don't forget to also calculate the cost for the time it'll take you get all the drivers working properly and such things. Also don't forget to include the cost for the time and phonecalls once you need some help, because one or the other piece of hardware won't work as promised and either of the vendors will tell you that it's actually
a) Window's fault
b) The other hardware's drivers fault
c) Your fault
Have a nice day.
No, for easier pronunciation the "p" has been assimilated.
Microsoft, even with all their money, would be bankrupt in no time if they did that.
Leonid: "Ivan, dis waterr taste like piss"
Ivan: "Wellll, you know..."
Not to forget Locutus of Blimp.
Resistance if futile, you will all be abliminated.
There is, if you happen to be an admin for a bunch of Macs running OS X (clients and servers).
The Egg, of course.
But thinking about this what, yes what if the T-Rex's voice was like a giant chicken voice... Imagine a T-Rex sitting on a hill and roaring his low pitched earth shattering Cock-A-Doodledoo into the early morning.
I'd love to see Jurassic Park adapt this.
Definitely, simply because there are no 2GHz laptops available from Apple.
Even if you use PostFactoX to install OS X on unsupported hardware your Mac must have a G3 or later to run OS X. I don't think OS X (even 10.1) will run on a 604.
You might have installed OS X with PostFactoX on a 7500/7600 with a G3 upgrade card, but then it's not a 604 anymore.
Well, that's indeed pretty disappointing (I'm not a programmer, so I was just guessing), though it might not necessarily be Apple's fault, it could have to do with copyright to certain parts of the drivers that doesn't belong to Apple. :-(
I always thought you'd get Shakespeare's works by doing so...
It'll come preinstalled with it and be based on GNU HURD.
Shouldn't a look at the drivers for Airport Extreme in Darwin help there? I know, that drivers in darwin are done quite differently than you'd write them for Linux, but shouldn't it be enough to understand how to basically write drivers for the AirportExtreme card?
The next step will be to get rid of those drivers. They're the ones always screwing up anyway, what better solution than to eliminate the biggest cause of error in driving?
Let's just build cars that drive themselves and everybody start walking to work again. Problem solved.
...and while doing so abolish selling CDs in general. From now on your SONY Music will be available solely on MDs in ATRAC format.
I was just being a bit utopic, but that's what they'd really like to do, isn't it?
Froogle finds some motherboards:
http://tinyurl.com/6r5nv
The Blade Center JS20 from IBM also looks nice:
http://tinyurl.com/62z9p
And there's the Pegasos:
http://www.pegasosppc.com/
Well, not much but IBM has been doing a lot to promote the PPC platform, blame the vendors.
...and SuSe and Turbolinux and Gentoo and ROCK Linux and Fedora and CRUX and... do you want me to continue?
You mean like those OrangePC cards many years ago? I wonder, why you don't get those anymore. I thought they were neat.
No it happens with any Japanese page I visit with Camino. Changing encodings doesn't fix the issue. The problem is that Camino for some reason uses the proper characters, but mixes all kinds of different fonts, so the pages looks unbearably ugly. I've experienced this with any version of Camino and I wonder why this is.
It still makes a complete visual mess when trying to display Japanese. It displays some words using different fonts for each character and quirks like this. Makes the page really ugly. I have no idea why that is, because Firefox renders those pages perfectly (as does Safari).
It's a shame because I'd rather use Camino than Firefox. Firefox doesn't use native widgets and still doesn't really look & feel like a fully OS X "native" application (although they're really doing their best to get closer).