sbelsky

@solvingj no, only test cases. As for me, it was enought to understood how to use this library. All interfaces are very simple, so i don't know what to add.

well, firstly, this is not the issue of specific library if you don't know about `bind` idiom.... this library bases on `boost::asio` so obviously you should know something about. secondly,...

please could you provide an example of directory naming in your case?

hmmm i hadn't such problems with my russian clients (although they very like to name directories in native language). I think this issue requires additional investigation.

sorry, i haven't yet fully migrate to current implementation of dir_monitor. and my local `work_thread()` use: `impl->pushback_event(dir_monitor_event(ck->dirname, to_utf8(fni->FileName, fni->FileNameLength / sizeof(WCHAR)), type));` to process result of monitoring. so @Vizor you...

no, `dir_monitor_event` definition has been changed since https://github.com/berkus/dir_monitor/commit/e23eea204f992df94f2f62ba2329338574df50a7. **By the way**, looks like we can remove `helper::to_utf8` at all.

@Vizor after some investigation i have another portion of questions. mainly: how did you reproduce current issue? how did you pass you Czech string into `add_directory` function? like in [my...

heh next time please describe you reprodution steps right away. it will help a lot :) @berkus i think you can close this issue.

previous name is a valid utf8 name... i didn't test especially **Vizor**'s case, but i believe it must be also handled by my PR https://github.com/berkus/dir_monitor/pull/39 changes.

although.. current PR actually solves case mentioned by **Vizor** (appearance of subdirectories of monitored directory with non-ascii names) and my PR 39 solves case with passing non-ascii utf8-encoded string to...