Apple should have full multilingual text capability but when they ignore their own text engine -- which had been a major selling point of OS X since back in the beginning -- and use another way of powering their own WP/Page layout program, you have to ask yourself whether their text engine actually has a future.
Also they keep changing OS X. Lots ofr things had to be rewritten or tweaked to work properly with OS X. At one end of the spectrum, you have Chocoflop, a nice little Cocoa graphics program, which the developer had made up to Beta 0.9 in Leopard, but who just gave up with all the changes to Snow Leopard. Dumped the thing, saying he would have to virtually rewrite it to run on X.6.x.
On the other hand, you have Canvas X -- no development for 6-7 years (maybe more) apparently full of bugs, which suddenly starts running virtually bug free~! Clearly, all those bugs we thought were poor work by the Canvas team were actually OS X not operating according to the published specs ... which the Canvas team had followed.
I worry for Nisus who have worked like dogs to get NW up on an OS which clearly was like sludge early on and was like jelly, it seems, until X.6.x. What is Apple going to do now? Is it going to develop two competing text engines or will it dump one -- the one Nisus uses -- and focus instead on the Pages approach? Will that be where we will see multilingual text capability? Is Pages a first shot across the bows of Adobe and Quark? Will Apple try to take over the DTP world as it has the video editing world, and will it bring out a junior version that will kill off smaller WPs in the process?
What does Apple regard as its core?
Cheers, Geoff
Geoffrey Heard
Publisher, Editor, Business Writer
The Worsley Press
FREE Bonus book offer. Get "How to make great ads for (sm)all business" FREE when you buy "Type & Layout: Are you communicating or just making pretty shapes?" or "How to Start and Produce a Magazine or Newsletter". Amazon or
www.worsleypress.com