06-14-2011 05:24 PM
When testing the application using the web browser on the playbook the string appears correcrtly calling document.write to output the string to the screen. However after compiling into a webworks app using bbwp and deploying using blackberry-deploy the string appears incorrectly with a mix of unexpected characters. Any suggestions? Can anyone else replicate this problem? It is important to note that that string is passed to customAskAsync as a title for the dialog.
06-16-2011 11:25 AM
I believe the issue could be that the customAskAsyn() launches an AIR dialog which only supports english. If you were to create a modal <div> with choice options (keeping it in the browser) you likely won't have the issue.
06-17-2011 04:51 AM
03-20-2012 02:10 PM
Has this issue been fixed yet? Is there anyway to specify character encoding when compiling? This is still a problem for applications which present multi-language strings to customAskAsync or standardAskAsync in tablet webworks 2.2. When will this be fixed?