It is unreasonable to get snippy with someone who is not familiar with your situation and is dealing with you entirely via e-mail.It is, however, reasonable to read the actual E-mails.
It is obvious Joe Clark doesn’t know how to handle sources.Funny, I managed to swing a few small exclusives over the years, and committed almost no errors to print in a decade's work, and received almost no complaints from sources.
No individual is entitled to private information, as Clark apparently thinks he is.As the AOL kidz write these days, WTF? OS X's new approach to language resources was not private information. (The code might be, but the approach isn't.) And the whole discussion concerned approach.
actually, joe clark's weblog has an ISSN number, which makes it a "credentialed" publication in the eyes ofNational Library of Canada, shurely?!the U.S. government.
Joe Clark has a history of stirring up trouble just to make himself look cool and to feed his ego.Big surprise for they hefty Cam here, but since I'm the one living the life, I can advise simply that I do get into scrapes from time to time, but I do not seek them out. Plopped onto a scale opposite some other Webloggers, I have the ego of a Buddhist monk.
This is simply another example of Joe playing the same old game: "Look at me. I am cool Joe Clark. I like to cause trouble. Whoo. Whee."I deny being cool. God, do I ever deny it. You have no idea.
Seriously - Joe is playing his game. The PR people are playing theirs. I have no doubt both sides are sore from giggling over how funny they are.BZZT. Wrong answer. Thank you for playing.
First of all, an ISSN number most emphatically does not make your publication "credentialed" in the eyes of the US government. The Library of Congress's ISSN web pages make it clear that the advantages of having an ISSN are mostly centered around simplified identification purposes, and that anyone can get one for any sort of publication whatsoever so long as that publication comes out indefinitely. They mean absolutely nothing when it comes to journalistic legitimacy. And the First Amendment makes it clear that the United States Government does not have the right to go around "credentialing" media at all.
Second, ISSNs are, well, International. There's nothing particularly American about them.
Anyway, "credentials" only exist in the eye of the beholder. An ISSN number does not make your publication any more or less worthy than a non-ISSN-holding publication. In the end, all that matters is whether anyone's heard of you and respects you. (Compare to Matt Drudge, for example, who everyone's heard of but who plenty of PR types will refuse to deal with on the grounds that he's not a "real publication", when in reality they're just afraid of or annoyed by him. Also compare to, say, John C. Dvorak, who could get these same flaks to lick Cheez Whiz off his ass for no purpose other than his own pleasure, simply because they're afraid if they don't, he'll turn around and make them look bad somewhere down the line in one of his numerous columns in "legitimate" publications.)
posted by aaron at 4:10 PM on May 4, 2001
I find it very interesting that Joe has left out the first email that he sent to Apple.Because I couldn't find the damn thing. I'm pretty sure I hit a public-relations
mailto: link in Lynx, which lets me send a message but doesn't keep them. I know, however, that all I said was "Who do I talk to about Mac OS X localization?"; there were no substantive details.
Given the unreasonable self-important tone of his later emails, it's hard to believe that his (or "your," if you're reading, Joe) initial request was as benign as he claims.I don't find it hard to believe. I'm the one who sent it.
Just because you have a website does not make you a journalist.Hey! Quit plagiarizing me! I wrote that back in June!
Nor does having a degree does not make you a journalist.How you say, in English?
No one has any obligation to tell you anything, and you have no right to whine about it when they reject you.Within given legal constraints, we can write whatever the heck we want. A request for comment is on the record. And so was my side of the conversation. Full disclosure.
Wait... didn't someone write in with the remark “Just because you have a website does not make you a journalist. I'm sorry, it doesnt. Nor does having a degree does not make you a journalist”? I brazenly assumed that someone cared what the definition of a journalist was.Ten years of paid published articles (pushing 400 of them) in a couple of dozen periodicals, plus paid editing, plus being invited to speak at journalism conferences, plus published editorial photography – at what point do I officially become a journalist?Who cares, Joe?
[H]ow do I react when someone comes to me and proclaims that they are the voice of their respective community and want to get my word to their audience(s)... such a dialogue would be resource consuming (time, money...), and I have to have some way of verifying their claim and legitimating their pull on my resources.Very easy online: Just read the Weblog archives.
I can't imagine Ford bothering with a PR agency when it's clear from the content of his site that he has multiple deep contacts inside Apple engineering. Ford's entire output has been of the Mac world, for the Mac world and by the Mac world and as you said yourself, you turn to Macintouch for the real dope. And Joe Clark is...?A legitimate journo, whether anyone's heard of me or not. Also tired after a long day. I love you, too.
den beste: "It's just more of the traditional Apple arrogance."Untrue. Bill Evans of Apple personally intervened and was Cc:ed on various snatchmails.
Whoa, there goes the knee. Apple wasn't even involved. You know all the names of all the people who were involved. Blaming vaguely defined corporate moods should really be a strategy of last resort.
Fortunately, the localization features (which allow for applications to be elegantly decked out in multiple languages, and packaged into what appears to be a single binary) don't have a hill of beans to do with web server interaction. If you want to send web pages in multiple languages, get thee to O'Reilly already. Edelman's people may have flown off the handle, but the article was a pipe dream in any case because Mr. Clark was wrong on the facts.Also untrue. I made no factual errors. There was scarcely enough information to get wrong in the first place! The dream was to talk to the International Herald Tribune Web team (never could get an E-mail address that worked!) and the OS X localizationistas to compare notes on preloading as a localization approach. IHT does preloading on the Web, but only of English-language articles; OS X preloads multiple languages in the operating system, but not on the Web. I wanted to marry the two.
You must be joking. This OS has been in active development for two years, and the package/localization features go back to NeXT, which has been around for more than a decade. You may not have known enough about the subject, but to claim the information didn't exist is ludicrous and unsupportable.I didn't make that claim. There wasn't enough information at my disposal to flub.
What is it you think you mean by "OS X preloads multiple languages"?English, French, Dutch, German, Japanese, and Spanish are installed with OS X. You can select whichever one you wish (actually, you can list them in order of preference) and the interface instantly changes. In the olden days, you had to buy a separate OS in the target language and/or do a custom install.
If you want to localize web pages, look into Apache's HTTP content negotiation and use a browser that supports the extremely common HTTP_ACCEPT_LANGUAGE header. Do not redundantly send along copies of a given page in multiple languages and depend on DHTML and/or OS-level trickery to exclude most of them.I am not unfamiliar with the mechanics. The mechanics of a new preloading approach to localized Web pages would have been the subject of the discussion. We're not necessarily going to refuse to "redundantly send along copies of a given page" just kuz you tell us to. Under certain circumstances it may be appropriate, just as under certain circumstances Flash is appropriate.

so please, oblige me with the briefest explanation of how a "preloading" scheme, if it existed and even if it weren't platform-specific, would be in any way preferable to the HTTP content negotiation that's been widely supported, on every platform, for yearsSomeone seems to equate pursuing an idea with advocating it. As the story clearly stated, for sites that must be completely bilingual on every page (not uncommon, e.g., with the government of Canada), is this newfangled approach actually useful, or more of a pain in the arse?
« Older Happy Birthday,... | "Rosen said she expected the r... Newer »
This thread has been archived and is closed to new comments
posted by tranquileye at 2:02 PM on May 4, 2001