On 8/14/2014 7:15 AM, bhargava.animes...@gmail.com wrote:
I am using gecko SDK 28.0 in my application. When my application is installed
in path having japanese/korean characters then in my embedded browser nothing
is shown.We found following error in logs
Could not read chrome manifest
In our code , we are having following snippet :
rv = NS_NewNativeLocalFile(nsEmbedCString((char *)filepath), PR_FALSE,
getter_AddRefs(libxul));
if (NS_FAILED(rv))
{
throw BALBrowserException();
}
rv = NS_NewNativeLocalFile(
On 8/14/2014 9:08 AM, bhargava.animes...@gmail.com wrote:
In our code , we are having following snippet :
rv = NS_NewNativeLocalFile(nsEmbedCString((char *)filepath), PR_FALSE,
getter_AddRefs(libxul));
if (NS_FAILED(rv))
{
throw BALBrowserException();
}
-embedding-bounces+g4=novadsp@lists.mozilla.org] On Behalf Of
bhargava.animes...@gmail.com
Sent: 14 August 2014 14:09
To: dev-embedding@lists.mozilla.org
Subject: Re: Issues with chrome.manifest when installed in path having
japanese characters
In our code , we are having following snippet
On 8/14/2014 9:58 AM, g...@novadsp.com wrote:
I am not sure if your problem is identical to one I recently had to solve.
XRE_InitEmbedding2Type on Windows uses ReadDependentCB() and TS_tfopen()
internally (implemented in nsXPCOMGlue.cpp. In the 2 helpers, which both
take char* parameters, the
This is correct and intentional: see the comment at
http://mxr.mozilla.org/mozilla-central/source/xpcom/build/nsXULAppAPI.h#155
We do this because on Windows the native charset doesn't represent
unicode. So we use a wmain entry point and wchar, and convert to UTF8
immediately so that we can
