InitializeICUDefaultLocation path string representation.

[Jim Acquavella]

Is this api expecting a utf8 string or ansi?

bool v8::V8::InitializeICUDefaultLocation	(	const char *	exec_path,
		const char *	icu_data_file = nullptr
	)

It would be sort of ironic if the exec path for setting up the ICU location wasn't unicode!  But, it does seem to handle multibyte paths ok, but not unicode. -Jim

[Jim Acquavella]

This is definitely a problem.  Are any other applications that use this API able to run their application if the path has non-ASCII characters?  These paths should use UTF-8 string representations and communicate with the OS accordingly.  Can anyone suggest a work around to this problem? 

--
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to a topic in the Google Groups "v8-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/v8-users/m_VNgpzh4S4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to v8-users+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ben Noordhuis]

On Fri, Sep 7, 2018 at 1:41 AM Jim Acquavella <loude...@gmail.com> wrote:
> Is this api expecting a utf8 string or ansi?
>

> bool v8::V8::InitializeICUDefaultLocation(const char * exec_path,

> const char * icu_data_file = nullptr
> )
>
> It would be sort of ironic if the exec path for setting up the ICU location wasn't unicode! But, it does seem to handle multibyte paths ok, but not unicode. -Jim

It calls LoadLibraryA() on Windows, fopen() on other platforms. I
expect most embedders bundle ICU and V8 together and never deal with
file paths in the first place.

[Jim Acquavella]

Yeah, I can avoid this by placing the icu file next to my executable.  In the future, this should definitely use LoadLibraryW.

Thanks.