version checking

Sorry I realise the version checker STILL ain't right and that after running it you'll probably have to find the registration in readme.txt. I will fix this asap.

version of 30 Aug

1 Several fixes for Unicode-formatted text files
2 File Viewer utility (plus documentation in the Help)
3 Work has started on WSConcGram

Immediate plans

I plan for WS5 to have better and speedier handling of XML files. At present WS5's ability to handle attributes in mark-up is quite limited. I hope to implement a solution which will save a WS5-compatible version of each text which it can re-read as needed much faster than re-parsing the original.
Secondly (and with his agreement) I want to build an implementation of Chris Greaves' ConcGram into WordSmith 5.

Version of 16 Aug

Fix to detection of the user's default language.
Fix to WordSmith's noticing when you double-click on a .CNC, .KWS, .LST file (etc.) (only if registered with Windows in the Registry).
WS5 no longer pesters you to start a new file off (if you want that, choose File | New).
Fix to processing of an index in Chinese/Japanese etc whereby an index ended up with only one entry.

Shakespeare corpus availability

At www.lexically.net/wordsmith you should now see access to the Shakespeare corpus I've been working with. Feel free to download and let me know if it is useful to you.
Cheers -- Mike

More fixes 9 Aug

1. index filename choosing made easier
2. "symbol to count as alphabetical" feature installed (for ampersands etc.)
3. WS5 KW files not opening problem is fixed

Fixes and Improvements

WordSmith 5 of 3rd August 2007

UTF8 detection
Unicode menus (because localization into Chinese is starting)
Easier renewal of licence for time-limited users (Register menu option is visible)
Follow-up improvements
Save As Excel default folder fix

UTF8 and Unicode text file formats

I have recently realised that some users processing Russian, Bulgarian etc. may not be getting suitable results because they do not know that WordSmith won't be happy with UTF8. (This is a text file format which doesn't necessarily use 1 byte per character.) I have been working to get WS5 to detect files in this format and automatically compensate, preferably re-saving the text file in 16-bit Unicode.
Cheers -- Mike