On Fri, Dec 2, 2016 at 11:18 AM Nate Finch <nate.fi...@canonical.com> 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. Forcing people to use an English translation for the > name of their software is not very welcoming in this day and age. > Realistically, alpha-numerics are the most accessible character base today. Unicode domains, the global index of ip addresses, just recently added unicode support. If you have a charm in the store named 數據庫, only those with keyboards that support those characters will work (without a lot of time fumbling unicode libraries). My point was more this, for accessibility I think the middle ground is: juju deploy mysql 數據庫 You're taking a named product, which is a flat - alpha numerical - charm name that everyone can type and access, and deploying it in Juju as a name pertinent to you. I'm sure this adds more complexities to core, in general, but it's the only place I could imagine unicode working well, even then it's a bit of a stretch weighing the pros and cons for the amount of work needed to support unicode throughout Juju as an application name. Marco > On Fri, Dec 2, 2016 at 10:46 AM Marco Ceppi <marco.ce...@canonical.com> > wrote: > > On Fri, Dec 2, 2016 at 10:31 AM Nate Finch <nate.fi...@canonical.com> > 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 about this a while ago (half jokingly) since I own http:// > 💩☁.ws <http://xn--l3h.ws> (poo cloud!) and was going to make a charm > accompanying that name. Localized unicode characters - emoji or otherwise - > are still a difficult UX compared to alphanumerics. It takes me 10 mins to > find the emojis to type the damn domain in if I'm not on a phone. > > The only path for unicode names I could see happening, and it's a stretch, > is if the application name can be set to a larger range of characters. > Where you may want to name horizon deployed in your environment to > something localized (or emoji) but the charm name should be flat and simple. > > On Fri, Dec 2, 2016 at 9:29 AM Mark Shuttleworth <m...@ubuntu.com> wrote: > > 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 of 'OK' to a different codebase. > > It's much better to have a simple rule that can be well documented, > enforced the same way in store and client and snapd, and typed on any > laptop without having to refer to the internet for assistance. > > > Mark > > -- > > > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
