FindFirstFileW LPCWSTR

Hi Experts,

I am now moving to the utf8everywhere.org way of doing things.  So I'm keeping utf8 as my internal encoding and as output of all my files.  When I need to talk to windows, I am going to convert my utf-8 strings into whatever Windows expects.

So what encoding does Windows expect with calls to FindFirstFileW?  I am compiling with unicode enabled, so I need to widen my utf-8 so that it matches the encoding that FindFirstFileW uses.

Thanks,
Mike
LVL 1
threadyAsked:
Who is Participating?
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
You should have seen the examples at utf8everywhere.org - it is explains exactly what to use for proper "widening" for Win API calls. The "*W" API calls are all "wide", (say UTF16).
0
 
threadyAuthor Commented:
Thank you, I had forgotten.  And yes- all UTF-16...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.