Hi,

are you talking about the default during the import/build phase,
or the default encoding served up when the collection is accessed
via the webserver?

For importing, greenstone should be able to automatically detect the
encoding of input documents, but if you have documents where
greenstone gueeses wrong, you can set the "default_encoding" option on
the import plugin that is processing those types of files.

And for serving collections via the web server, there is nothing wrong
with serving the content as utf-8, since all the data is stored internally
in unicode.

John