nisus.com

... maybe you should be searching for every (formatting-insensitive) occurrence of an en dash preceded by two or more lowercase letters and followed by a digit. That could work in some contexts, although knowing the subject matter I think I would have to search for at least three or more letters, a...

Thanks for your reply, Adryan. The method you suggest would be a solution if only the documents concerned didn't contain so many valid en dashes, even in normal (baseline) text. Unfortunately, they do, for example where ranges of pages are cited, for example 'see pages 24–41', or in expressions such...

Thanks for replying in depth. I will look at this tomorrow, as it's late night here now. Yes, the macro expressions in my initial post are incorrect (typed in haste rather than pasted). However, by the time I posted I was pretty certain that the replacement using a macro wasn't working whereas the F...

The macro code I posted above had a typo (missing hyphen in the replacement). It should be: Find and Replace @Text<–([\d])>, @Text<-\1>, 'Eau' And is set to use 'No Super/Sub'. The macro should replace an en dash with a hyphen, but only in normal text, not superscript. It doesn't: it operates on all...

I have a Powerfind Pro expression which works exactly as it should. It does not work when converted to a macro. The expression also uses an attribute, namely baseline set to 'No Super/Sub'. The expression is simple: -([\d]) That is an en dash before the parenthesis, not a hyphen. The replacement is ...

We're currently looking for a replacement for MS Word for 16 users, all working on scientific/medical text on OS X. We are very impressed with your beta software, but if it is released without styles we simply cannot consider it, which would be a great pity. Can anyone provide an estimate of when pa...