cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Grebnov (Akvelon)" <v-seg...@microsoft.com>
Subject RE: Bugs handling name field in cordova-platforms -- was: Re: New project <PATH> vs. <NAME>
Date Fri, 25 Jul 2014 12:04:20 GMT
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. 
2. Add additional property to config.xml to override predefined 'CordovaApp' name. 
	* equal to display name by default? Or CordovaApp
3 Use some algorithm to convert non-ASCII chars from <name></name> contents to
ASCII (Punycode? Replace with underscores?)

Thx!
Sergey
-----Original Message-----
From: Josh Soref [mailto:jsoref@blackberry.com] 
Sent: Thursday, July 24, 2014 10:12 PM
To: dev@cordova.apache.org
Subject: Re: Bugs handling name field in cordova-platforms -- was: Re: New project <PATH>
vs. <NAME>

https://issues.apache.org/jira/browse/CB-5971

Joe Bowser wrote:
>Did this actually break for something.default (and I mean the literal 
>string something.default)?

Yes. It really did, which is why that was the example I provided.

> I thought the bug was ridiculously vague and would be impossible to 
>close as it was written.

It was explicitly precise on a simple test case. I just hoped someone who had some involvement
w/ Java would do the full research instead of expecting an injured bystander to do the research.

Mime
View raw message