In the Aminet you will find my Unicode implementation. I am currently writing a text editor which is fully unicode capable (using the glyphs for the full unicode set, which are already available in my Unicode implementation).
The text editor I'm writing won't "plug in" to Voyager, however in its current state of completion it is already capable of reading and writing UTF8, and so you could use it to read anything (e.g. HTML) in UTF8, and show it in plaintext. It can also read and display files in other heritage character sets such as Big5, Shift-JIS, the ISO8859s, ISCII, etc. It also converts HTML-style &...; character encodings if required. The program is working Ok now, but needs some further debugging before I put it on the Aminet. I have been slow working on it, as I have been suffering from depression on and off. After I finish my text editor (which I call "UText"), I will do a Unicode-capable amigaguide (which will be able to read & show heritage amigaguides and also amigaguides written in UTF8, which will be a much easier project than UText. After that, I will embark on a HTML/CSS2 viewer, though most likely plaintext only. However, you could use it as a plug-in to Voyager, to show the plain text in non-Latin1 properly. UText updates window-fulls of text in less than a second if you pre-load the unicode glyphs required (to pre-load a full Unicode set of 65536 glyphs takes about 2 megabytes of memory), but if it has to grab all the glyphs from diskfiles on the fly it takes three seconds to update a window-full (on an accelerated Amiga 1200). In practice, alphabetic languages require only a small range of Unicode glyphs to be pre-loaded. If anyone wants to correspond through email with me about UText, I would be glad to hear from you.
