4. Internationalization support I do see some vague traces in code that indicate that author new this needs to be supported. But since documentation have exactly zero information and I couldn't figure out how to do it myself, I assume that library doesn't support this. IMO it's required for industrial strength solution.
How many times have you needed internationalization support logging?
Me, personally - never. But may be the fact that I work in domestic department of American company could be accounted for that. But for the boost level library this is a showstopper. Internationalization is not an afterthought.
"Internationalization" is being used as a buzzword here: can you define what you expect to be possible, and then John can say if it is possible or not. All I can think to expect is that if I have a unicode string (or a string in any encoding) that it would get written to the log without corruption. Similarly a log path/filename containing non-ascii characters should work. (I agree that if either of those is not possible that is a show-stopper.) Darren