I'd support having a fully unicode display name. I'm not sure what is best
for the short name. (That also gives us things like "vSphere" and "MySQL"
with proper capitalisation.)
The problem with full unicode is that do to things like accent chars and
wide form, you can easily have 2 names that loo
On Fri, Dec 2, 2016 at 11:18 AM Nate Finch wrote:
> I generally assume that "hard to type" doesn't apply when you're talking
> about someone's native language. Yes, you or I would have trouble
> typing 數據庫 (database), but to someone in China, that's probably a word they
> type all the time. For
I generally assume that "hard to type" doesn't apply when you're talking
about someone's native language. Yes, you or I would have trouble
typing 數據庫 (database), but to someone in China, that's probably a word they
type all the time. Forcing people to use an English translation for the
name of th
On Fri, Dec 2, 2016 at 10:31 AM Nate Finch wrote:
> One thing we *could* do to support non-english names that would not
> entirely open the door to emoji etc is to simply constrain the names to
> unicode letters and numbers. Thus you could name something 數據庫 but
> not .
>
I bothered Rick ab
One thing we *could* do to support non-english names that would not
entirely open the door to emoji etc is to simply constrain the names to
unicode letters and numbers. Thus you could name something 數據庫 but
not .
On Fri, Dec 2, 2016 at 9:29 AM Mark Shuttleworth wrote:
> On 02/12/16 09:23, A
On 02/12/16 09:23, Adam Collard wrote:
> True, but we could do normalisation in the charm store to prevent
> malicious names. I think it's an important aspect of software in the
> modern world that it can support the wide array of languages that we
> humans use.
This just transfers the definition
On Fri, 2 Dec 2016 at 13:43 Mark Shuttleworth wrote:
> On 02/12/16 07:46, Adam Collard wrote:
> > It'd be nice to have full Unicode support in both charm and
> > application names.
>
> Steady on, that would make it easy to have misleading charm names, or
> ones that are very difficult for people
On 02/12/16 07:46, Adam Collard wrote:
> It'd be nice to have full Unicode support in both charm and
> application names.
Steady on, that would make it easy to have misleading charm names, or
ones that are very difficult for people to type. I don't mind lifting
the restriction on up-front digits,
It'd be nice to have full Unicode support in both charm and application
names.
On Fri, 2 Dec 2016 at 12:43 Nate Finch wrote:
> There's no technical reason for the restriction, AFAIK. I believe it's
> just aesthetic.
>
> On Fri, Dec 2, 2016, 5:50 AM James Page wrote:
>
> Hi All
>
> Is there a s
There's no technical reason for the restriction, AFAIK. I believe it's
just aesthetic.
On Fri, Dec 2, 2016, 5:50 AM James Page wrote:
> Hi All
>
> Is there a specific rationale for application names being limited to not
> starting with a digit? I get why they can't end with one but I don't see
10 matches
Mail list logo
