The most important thing is not to share this as TXT, since the application will need to guess the encoding or even worse: use the default. Make it an RTF and choose the encoding and everything will be fine.

Just some feedback:
I opened your file with several applications on Mac OSX (10.4).

• TextEdit: When I open it with the default settings (‘Open files using automatic encoding detection’), there are issues, i.e. ø in Sørensen = √∏, for example. Changing the preferences to ‘Open files using UTF-8‘ helps.
• Similar with Safari. ø = ø Switching from ‘Standard’ to ‘Unicode (UTF-8)’ helps
• My favourite text editor, skEdit, gets it right in the first place. Its preferences say ‘Open files with UTF-8’

Hope that is of use for somebody.

TextWrangler also opens the file correctly.
Textwrangler is free.

http://www.barebones.com/products/textwrangler/

On Mac OSX (10.4)

I think UTF-8 enjoys broader support than 16-bit Unicode. But Ralf is probably right in suggesting a format that can represent the encoding explicitly.

Thanks everybody. This was very helpful!

I will fix some errors that have come to light and re-post v1.1 in 3 formats: TXT RTF & PDF.

By the way; TextEdit can be made to use 'Unicode UTF-8' also. But you have to make a change in the preferences.

The other thing which I neglected to say and may be useful to know is that to test for Lingala ( one of the languages ) you must have extended Latin -B support in the font being tested. I would like to add more languages like this over time. Maybe then I can group them by Latin, Latin A & Latin B.

What do you think?

The revised (v1.1) files are up. If people want the RTF they will have to email me until such a time as Typophile adds it as a supported file type in threads.

Cool, thanks for posting.

I was wondering why "Type" is capitalized on the first line and then spotted a couple of other typos - "greared" & "Cyrilic".

Thx, Si

Thanks Simon!

I have update both threads to have the latest version: 1.2