nisus.com

http://www.nisus.com/forum/viewtopic.php?t=2315

martin answered, that this bug has something to do with the system typesetter and therefore cannot be fixed until apple does it,...
so my question: WHY does microsoft word (mac edition) don't show this behaviour?

mainly the bug that keeps me from completly switching to nisus!!

Because Word uses its own text engine, and its own dictionary, and its own spellcheck system. NWP uses the Cocoa text-engine built into Mac OS X as its foundation, which allows it to inherent any upgrades with each OS upgrade. However, it also means that it inherents any bugs as well.

Martin can probably give you a more technically sound answer, but this is the gist of it...

Scott

Hey Mr. Whitlock,

time to change your sig file

thx scott for filling me in,... was missing this piece of information
so there probably won't gonna be an update in near future
apple's keeping me waiting

Nice catch on Mr Whitlock's signature line, Gem.

enC this factor has been a problem for Nisus -- and a lot of other Mac developers -- all along. It would be interesting to see whether the points on pages misbehave as they do in Nisus, or whether the Apple programmers have done a fix of their own to overcome this OS text engine limitation.

Cheers, Geoff

Geoffrey Heard, Business Writer & Publisher

"Type & Layout: Are you communicating or just making pretty shapes" -- Revealed! The secrets of how you can use type and layout to turbocharge your messages in print. See the book at http://www.worsleypress.com

Thanks, Gem...

no problem

I just got to figure out how to get

NW-P 1.0, OSX 10.4.10 intel - 2 gig ram

in with my regular sig, which is the require 80 characters

because it helps a lot in interpreting questions if you know a person's system..


-----------------------------------------------
NW-P 1.0, OSX 10.4.10 intel - 2 gig ram

greenmorpher wrote: enC this factor has been a problem for Nisus -- and a lot of other Mac developers -- all along. It would be interesting to see whether the points on pages misbehave as they do in Nisus, or whether the Apple programmers have done a fix of their own to overcome this OS text engine limitation.

i just crossvalidated it in pages:
> it does NOT happen, so apple probably won't gonna fix this.

any chance nisus can make a tmp.fix on their own?

enC wrote:i just crossvalidated it in pages:
> it does NOT happen, so apple probably won't gonna fix this.

Pages actually uses the same engine as Safari, which is different than the text engine that NWP and TextEdit make use of. So they'll have a different set of behaviors (and bugs).

any chance nisus can make a tmp.fix on their own?

In this case, it's very unlikely. While sometimes we can work around a bug in Apple's text engine it all depends on what the bug is and how accessible that part of the engine is.