<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Oct 4, 2018, at 02:45, Paw Boel Nielsen via tz <<a href="mailto:tz@iana.org" class="">tz@iana.org</a>> wrote:<div class=""><br class=""><div><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I propose we change all tz identifiers to randomly generated characters to ensure no UI designer considers showing them to end users.</span></div></blockquote></div><br class=""></div><div class="">All that would do is kick the problem up a level. At some point, there has to be some sort of *map* that defines which tz entry relates to what specific geographical region. ‘Randomized’ identifiers merely mean that that map would have to be maintained separately, but would still have all of the socio-political baggage about proper spelling, transliteration, etc, etc.</div><div class=""><br class=""></div><div class="">I think the current identifier arrangement is about the cleanest approach possible for what is an inherently messy task. TZ adopters do need to understand that those identifiers are essentially arbitrary keys into a database.</div><div class=""><br class=""></div><div class="">Cheers!</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">|----------------------------------------------------------------------|</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">| Frederick F. Gleason, Jr. | Chief Developer |</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">| | Paravel Systems |</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">|----------------------------------------------------------------------|</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">| Like the ski resort of girls looking for husbands and husbands |</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">| looking for girls, the situation is not as symmetrical as it might |</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">| seem. |</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">| -- Alan McKay |</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">|----------------------------------------------------------------------|</span></div></div></body></html>