Most of the Pages screenshots from the article show hyphenation, although how well "Lorem Ipsum" is hyphenated isn't a particularly good indicator of anything, as few hyphenators out there are set up to handle Latin.
Yes, it has live word count. It's a little hidden in the inspector, but it's there, complete with page count, line count, paragraph count, character count...
I think it has something to do with what sounds better. Many of the i-stuff are one syllable words (or word fragments). iDVD doesn't scan terribly well, and is probably the most verbose-sounding i-name.
Some i-stuff has a corresponding pro app (iDVD vs. DVD Studio Pro, or iMovie vs. Final Cut). Others don't (like iCal, iTunes, or iPod).
The victim was not the driver, but a passenger. The car was not in motion. Try googling for McDonalds, Coffee, Lawsuit (and Passenger) for pages like this that debunk many of the myths about this case.
In Luxi Sans, the w, c, and d all have some unevenness; the e's crossbar is too high.
Trebuchet has dropouts in its e's, and its w is uneven.
Times isn't antialiased at all.
Verdana is too thin for its size (and the V is about to fall apart).
The g in Impact is blocky and has some strange lumps.
Georgia almost looks aliased.
Here's a screenshot comparison between your original and the same fonts rendered by MacOS X. (I have most, but not all of the fonts). IMHO, the righthand (MacOS) side looks superior - more like actual typeset text. So what's up? Does freetype suck that badly? Are you using the non-hinted version of freetype? Is this a screen gamma difference? I used Linux/X11/freetype2 daily for a couple of years, and I never got the fonts to look the way I wanted them to. It's almost like the contrast setting is wrong, not to mention the subpixel precision of the glyph control points is out of whack (what's with the V in Verdana, anyway?).
Of course, the flipside is to say that the freetype-rendered text looks crisper, less blurry - especially Impact. I appreciate that distinction - but for me, the consistency of shape and the evenness of the glyph weighting is more important than the apparent focus.
Slashdot Mirror
iWork Pages has a menu item: Save as Template, so you can author your own.
There's no direct relationship between the two similarly named applications.
Most of the Pages screenshots from the article show hyphenation, although how well "Lorem Ipsum" is hyphenated isn't a particularly good indicator of anything, as few hyphenators out there are set up to handle Latin.
Yes, it has live word count. It's a little hidden in the inspector, but it's there, complete with page count, line count, paragraph count, character count...
Yes, based on talking with team members - this isn't based on old NeXT software, nor on ClarisWorks/AppleWorks. It's a new from-scratch application.
... based on demos/conversations at the Apple booth.
Greek is a typesetting term as well. In this case, it's referring to the traditional Lorem Ipsum placeholder.
Actually, the name may be the same, but it's brand new.
I think it has something to do with what sounds better. Many of the i-stuff are one syllable words (or word fragments). iDVD doesn't scan terribly well, and is probably the most verbose-sounding i-name.
Some i-stuff has a corresponding pro app (iDVD vs. DVD Studio Pro, or iMovie vs. Final Cut). Others don't (like iCal, iTunes, or iPod).
I bet he leaves out Tom Bombadil too.
The victim was not the driver, but a passenger. The car was not in motion. Try googling for McDonalds, Coffee, Lawsuit (and Passenger) for pages like this that debunk many of the myths about this case.
I, for one, welcome our new linguistic overlords.
According to the Wayback Machine, itunes.com wasn't used by Apple until mid 2003.
A.L.I.C.E.
Sounds like you want something like MPG321.
Might help to put "Computer Associates" somewhere in the text.
It looks like GIF is what's actually being sent, although with a .fd extension instead of .gif.
That's actually a pop-up blocker circumvention device which, when clicked, causes a pop-under to appear. I got it with Safari too.
It means that Bill expects to get "very rich" from Longhorn and MSN.
Mac OS X Tiger to support resolution independent UI, larger icons
You even commented on some of the problems.
In Luxi Sans, the w, c, and d all have some unevenness; the e's crossbar is too high.
Trebuchet has dropouts in its e's, and its w is uneven.
Times isn't antialiased at all. Verdana is too thin for its size (and the V is about to fall apart).
The g in Impact is blocky and has some strange lumps.
Georgia almost looks aliased.
Here's a screenshot comparison between your original and the same fonts rendered by MacOS X. (I have most, but not all of the fonts). IMHO, the righthand (MacOS) side looks superior - more like actual typeset text. So what's up? Does freetype suck that badly? Are you using the non-hinted version of freetype? Is this a screen gamma difference? I used Linux/X11/freetype2 daily for a couple of years, and I never got the fonts to look the way I wanted them to. It's almost like the contrast setting is wrong, not to mention the subpixel precision of the glyph control points is out of whack (what's with the V in Verdana, anyway?).
Of course, the flipside is to say that the freetype-rendered text looks crisper, less blurry - especially Impact. I appreciate that distinction - but for me, the consistency of shape and the evenness of the glyph weighting is more important than the apparent focus.
The Matrix clocks in at 7.8GB.
At 1 Mb/s, that's close to a day.
Or by "DVD", maybe they mean a low quality copy of the movie you might rent on DVD, with none of the extras, bells or whistles.
Real's web page is customized based on what browser/OS (i.e., the user agent) you're using.
So, with a Safari user agent, I see an ad for RealPlayer 10 for X.
MSIE 6 gets me a huge banner about 49¢ songs.
Mozilla on Linux: RealPlayer for Linux.
Lynx: a blank page.
Duh.
What about the graph on page 3? "Difficulty of owning Window vs Difficulty to make this graph"?
That's self-referential, i.e., recursive. As any professional knows, you can eliminate tail recursion by use of an iterative loop.
There seems to be an awful lot of misparsing of this sentence. Try this version:
Previously, iPod would not play any digitally protected songs that carry restrictions which were not purchased from Apple's own iTunes music store.