nisus.com

FWIW I'll throw in my 2c - IHMO the Draft view is good as it currently stands, and a number of the requests here are perhaps better supported by the Page View, tho further speed increases would help (to make using the Page View more satisfying as a working mode.) The Draft View rightly shows manuall...

At this point, I don't see how Mellel's new format is going to benefit users in any way. I think that comment is unfortunate, as it's simply not the case that there are no benefits to Mellel's proposed XML file format; the big one of course, is XSLT , and the ability to translate their files into m...

Lots of good suggestions here. I particularly support boosting the Document Manager, I'd like this to be a UI for Templates, offer search (SearchKit), viewing meta-data (Spotlight), and sharing Docs and Templates (Bonjour.) Personally, I'd like a full screen mode (I sometimes use a Wacom for marking...

FWIW I think full OpenType/OS X advanced typography support (beyond the automatic ligatures) would be a welcome addition to NWX, and would obviously answer some of the issues with international support. This would also help to fix some UI issues around the use of the System-provided Fonts panel, vs ...

The Nisus guys have been doing these things for a long time, so they know the many traditional WP features that NWX currently lacks, and have said they're working on them, so I'm a little more interested in the 'surprising extras' we might expect. In terms of being able to use NWX in my work I'd nee...

but it does seem that LB is designed to work across different types of documents and applications, not across different docs within the same app. Which is really unfortunate, but would probably require too much high-level support for the interface issues to be reasonably resolved...? Then again 'al...

From the user perspective though, it is a bit of a quandary, if you want to get rid of Word, It seems to me that Pages renders Word docs more reliably than NWX, whereas it's custom file format is a negative; as the Nisoid's say, RTF is a pretty universal format, it's the antithesis of format-lockin ...

Something I'd like to see, post 2.5 I guess, is the ability to open embedded graphics in external applications. Starting in the simplest way possible, I would see NWX allowing me to open an embedded file in whatever system default application I've previously defined (e.g. Open JPEG in Preview), as a...

It could be interesting to have 'link auto detection' as a style property, so that you can set this as the default behaviour, but still allow exceptions, such as retrospectively adding this property; I'm thinking of situations where you want to produce a PDF version of a paper, for instance, that in...

I have to agree that auto-recognition of links can be really annoying, but in some circumstances, it can actually be what you're after. You're probably going to do this anyway, but FWIW, my vote would be to have this as a preference option, so that weirdos (!) that do like the Word behaviour, will h...

Hurray!

That's great news. Like others have opined, perhaps this is best offered as a UI option?

Looking forward (patiently!) to future updates.

I'd be all for this myself -- there are times when you really want to just concentrate on a particular task -- IMHO a growing trend in addressing some of the drawbacks in GUIs, in terms of too much competition for your attention. Lectura is another example, and worth a look for those looking for thi...

Not being a programmer (or giving thought to your workload!), I can throw words like 'easy' and 'simple' around, with gay abandon! ;) ...so, wouldn't it be fairly easy to offer simple Automator support by at least allowing NWX scripts to be run from an Automator workflow? I'm thinking of an Automato...

Noodling around in Tiger, I notice that NWX is much more responsive, scrolling is actually quite decent (PB G4 1Ghz, 1Gb RAM), and the 2.5 alpha runs very nicely, in both draft, and page views. Launch and file open/layout are noticeably quicker, though opening larger files could still do to be faste...

Hmmm, sounds like a licensing issue with the distributors doing the translation...? Would there be anything stopping a community effort to translate the interface?

After all, isn't (fairly) easy localisation one of the supposed features of OS X/Cocoa?

Just a thought....