Part of that discussion last year was that the library now handles this properly internally. There are mechanisms for handling UTF-16 Windows APIs and so forth. You should be able to use them rather than needing to roll your own.
--Greg On Wed, Jan 27, 2021 at 2:23 PM Tobias Klein <cont...@tklein.info> wrote: > Hi all, > > I just recently faced some issues related to Unicode paths on Windows > <https://github.com/ezra-project/node-sword-interface/issues/9> and > remembered the (brief) discussion on this list last summer. > > I then learned about what's needed to handle Unicode paths properly on > Windows (working with all those w-prefixed methods and having to convert > all strings to UTF16 before calling those methods). > > If anyone of you ever runs in the same issues (I suppose many of you > already did ...), this blogpost has been very helpful to me: > > *Using UTF-8 as the internal representation for strings in C and C++ with > Visual Studio* > http://www.nubaria.com/en/blog/?p=289 > > Blessings, I hope you're all doing fine! > > Best regards, > Tobias > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
