Sergey wrote:
> Looks like the only way to proceed here is to use display name ('name'
> element in config.xml) for visual elements only,
> and different safe string for class/activity, .apk, etc.
> For the safe name we can select from one of the following options:
> 1. Use predefined name (CordovaApp for example) - this is how Windows 8
> platform operates right now.
This is what BlackBerry 10 does too.
> 2. Add additional property to config.xml to override predefined 'CordovaApp'
> name.
> * equal to display name by default?
> Or CordovaApp
I'm not really interested in implementing this, so before I consider it,
someone would have to provide a Use Case explaining why they should be able to
specify the name.
We had one person asking us to change from #1 to what Android was doing, but I
waved it off.
My claim is that a fixed output file is easier to use -- it doesn't require
third party scripts to parse the Cordova build system.
> 3 Use some algorithm to convert non-ASCII chars from <name></name> contents
> to ASCII (Punycode? Replace with underscores?)
I'm not really interested in all the potential bugs in this path. See why I
didn't want to do #2.
