<div dir="auto">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.)<div dir="auto"><br></div><div dir="auto">The problem with full unicode is that do to things like accent chars and wide form, you can easily have 2 names that look identical to a human but are not the same. It was one of the attack vectors for Unicode URLs.</div><div dir="auto"><br></div><div dir="auto"><a href="http://unicode.org/reports/tr36/">http://unicode.org/reports/tr36/</a><br><br><div data-smartmail="gmail_signature" dir="auto">John<br>=:-></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Dec 2, 2016 9:03 PM, "Marco Ceppi" <<a href="mailto:marco.ceppi@canonical.com">marco.ceppi@canonical.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Fri, Dec 2, 2016 at 11:18 AM Nate Finch <<a href="mailto:nate.finch@canonical.com" target="_blank">nate.finch@canonical.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_-5966167013461161040gmail_msg">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.</div></blockquote><div><br></div><div>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:</div><div><br></div><div>juju deploy mysql 數據庫</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Marco</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote m_-5966167013461161040gmail_msg"><div dir="ltr" class="m_-5966167013461161040gmail_msg">On Fri, Dec 2, 2016 at 10:46 AM Marco Ceppi <<a href="mailto:marco.ceppi@canonical.com" class="m_-5966167013461161040gmail_msg" target="_blank">marco.ceppi@canonical.com</a>> wrote:<br class="m_-5966167013461161040gmail_msg"></div><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_-5966167013461161040gmail_msg"><div class="gmail_quote m_-5966167013461161040gmail_msg"><div dir="ltr" class="m_-5966167013461161040gmail_msg">On Fri, Dec 2, 2016 at 10:31 AM Nate Finch <<a href="mailto:nate.finch@canonical.com" class="m_-5966167013461161040gmail_msg" target="_blank">nate.finch@canonical.com</a>> wrote:<br class="m_-5966167013461161040gmail_msg"></div><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_-5966167013461161040gmail_msg">One thing we <i class="m_-5966167013461161040gmail_msg">could</i> 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 💩💩💩💩.</div></blockquote><div class="m_-5966167013461161040gmail_msg"><br class="m_-5966167013461161040gmail_msg"></div></div></div><div dir="ltr" class="m_-5966167013461161040gmail_msg"><div class="gmail_quote m_-5966167013461161040gmail_msg"><div class="m_-5966167013461161040gmail_msg">I bothered Rick about this a while ago (half jokingly) since I own http://💩<a href="http://xn--l3h.ws" class="m_-5966167013461161040gmail_msg" target="_blank">☁.ws</a> (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.</div><div class="m_-5966167013461161040gmail_msg"><br class="m_-5966167013461161040gmail_msg"></div><div class="m_-5966167013461161040gmail_msg">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.</div><div class="m_-5966167013461161040gmail_msg"><br class="m_-5966167013461161040gmail_msg"></div><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div></div><div dir="ltr" class="m_-5966167013461161040gmail_msg"><div class="gmail_quote m_-5966167013461161040gmail_msg"><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_-5966167013461161040gmail_msg"><div class="gmail_quote m_-5966167013461161040gmail_msg"><div dir="ltr" class="m_-5966167013461161040gmail_msg">On Fri, Dec 2, 2016 at 9:29 AM Mark Shuttleworth <<a href="mailto:mark@ubuntu.com" class="m_-5966167013461161040gmail_msg" target="_blank">mark@ubuntu.com</a>> wrote:<br class="m_-5966167013461161040gmail_msg"></div><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000" class="m_-5966167013461161040gmail_msg"> <div class="m_-5966167013461161040m_-7205182819346803673m_-7422526980744485800m_5244638693005292974m_-565663488324985707moz-cite-prefix m_-5966167013461161040gmail_msg">On 02/12/16 09:23, Adam Collard wrote:<br class="m_-5966167013461161040gmail_msg"> </div> <blockquote type="cite" class="m_-5966167013461161040gmail_msg"> <div dir="ltr" class="m_-5966167013461161040gmail_msg"> <div class="gmail_quote m_-5966167013461161040gmail_msg">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.<br class="m_-5966167013461161040gmail_msg"> </div> </div> </blockquote> <br class="m_-5966167013461161040gmail_msg"></div><div bgcolor="#FFFFFF" text="#000000" class="m_-5966167013461161040gmail_msg"> This just transfers the definition of 'OK' to a different codebase.<br class="m_-5966167013461161040gmail_msg"> <br class="m_-5966167013461161040gmail_msg"> 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.</div><div bgcolor="#FFFFFF" text="#000000" class="m_-5966167013461161040gmail_msg"><br class="m_-5966167013461161040gmail_msg"> <br class="m_-5966167013461161040gmail_msg"> Mark<br class="m_-5966167013461161040gmail_msg"> </div></blockquote></div></div></blockquote></div></div><div dir="ltr" class="m_-5966167013461161040gmail_msg"><div class="gmail_quote m_-5966167013461161040gmail_msg"><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> --</blockquote></div></div><div dir="ltr" class="m_-5966167013461161040gmail_msg"><div class="gmail_quote m_-5966167013461161040gmail_msg"><blockquote class="gmail_quote m_-5966167013461161040gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="m_-5966167013461161040gmail_msg"> Juju-dev mailing list<br class="m_-5966167013461161040gmail_msg"> <a href="mailto:Juju-dev@lists.ubuntu.com" class="m_-5966167013461161040gmail_msg" target="_blank">Juju-dev@lists.ubuntu.com</a><br class="m_-5966167013461161040gmail_msg"> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" rel="noreferrer" class="m_-5966167013461161040gmail_msg" target="_blank">https://lists.ubuntu.com/<wbr>mailman/listinfo/juju-dev</a><br class="m_-5966167013461161040gmail_msg"> </blockquote></div></div></blockquote></div> </blockquote></div></div> <br>--<br> Juju-dev mailing list<br> <a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" rel="noreferrer" target="_blank">https://lists.ubuntu.com/<wbr>mailman/listinfo/juju-dev</a><br> <br></blockquote></div></div>