Hello, it seems that Unicode support is the last issue that should be addressed before the library can be added to CVS. Since the issue is somewhat tricky, I'd appreciate some comments before I start coding. The initial description of the approach I plan is at http://zigzag.cs.msu.su:7813/program_options/html/program_options.design.htm... or http://zigzag.cs.msu.su/~ghost/program_options/html/program_options.design.h... So summarize the document, user would be able to pass wchar_t** to the parse_command_line function. If specific option needs unicode, this can be specified like this: ("email", unicode::value<Email>(), "email address") I believe the change will be mostly transparent and won't affect ascii usage. All options are very welcome! TIA, Volodya