Currently a sequence of regional indicator symbols is parsed unambiguously by greedily taking pairs of RIS chars and interpreting them as ISO 3166-1 alpha 2 codes. If REGIONAL INDICATOR DASH and REGIONAL INDICATOR digits are added, along with regional supplementary symbols, then sequences <RIS><RIS><RID><RSS>*<RIS> can be parsed unambiguously as ISO 3166-2, whereas <RIS><RSS>+<RIS> can be parsed as a named sequence signifying a flag of a non-governmental entity (or <RIS><RSS><RIS> - as ISO 3166-1 alpha 3, and longer sequences as non-governmental).
Leo On Thu, Jul 2, 2015 at 11:59 AM, Doug Ewell <[email protected]> wrote: > Leo Broukhis <leob at mailcom dot com> wrote: > >> With extensible self-delimited regional indicator sequences the >> carriers will be able to come to an agreement and to petition Unicode >> to register them as named character sequences symbolizing flags not >> encoded by an ISO entity, like various rainbow flags, making sure that >> the format of such sequences is guaranteed not to clash with any >> existing ISO 3166 format. > > There are already plenty of ways for companies and groups and > individuals to request new emoji. This way would have the disadvantage > of conflating non-regional flags with a coding system for regions, which > doesn't seem like a good idea. > >> Also, ISO 3166-2 can have 2 or 3 letters > > or 1, or digits or a combination > >> after the dash; it makes sense to have the letters after the dash >> self-delimited, if/when REGIONAL INDICATOR DASH is added to >> facilitate encoding of ISO 3166-2 codes. > > I don't understand the significance of this part. > > -- > Doug Ewell | http://ewellic.org | Thornton, CO 🇺🇸 > >
