That is what the 2 byte utf-8 character looks like if it is displayed
as Western instead (it is displayed as 2 single byte characters). If
you want to see if greenstone imported it properly, you can look
at the doc.xml files in the archives directory (these files are all
encoded in utf-8). If it's fine in the file, then it might be a browser
issue. If it's not fine in the file, you might have a too-old
version of greenstone. You could also try explicitly telling the
plugin which encoding your files are in, although I'm pretty sure
that this shouldn't make a difference for entity (&....;) conversions.

> that I can eventually search them? Do I need to upgrade to a more
> recent version of Greenstone?

I don't know - you didn't say which version you are using :) It works
fine with gsdl version 2.39.

John McPherson