Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

I think the idea of encoding "regional identifiers" instead of actual flags was to avoid a political minefield, and that flags change over time. (Afghanistan has haad something like 20 different flags) I also imagine PR China wouldn't be too happy if someone wanted to encode a Tibetan flag. You're

Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

OK I see the point of the PRI. But using joiners in the middle of the same flag is worse than just using start/end (which also have a clean way to e mapped to glyphs without using complex rendering like ligatures : start+RIS...+RIS+end can fully be converted to individual glyphs producing a flag sh

Re: polytonic Greek: diacritics above long vowels ᾱ, ῑ, ῡ

> Classical Greek might qualify [for a CLDR entry] It certainly qualifies, but we require that a submitter commit to collecting a minimal amount of data before we add it. See http://cldr.unicode.org/index/cldr-spec/minimaldata Mark * * *— Il meglio

Re: polytonic Greek: diacritics above long vowels ᾱ, ῑ, ῡ

On 8/5/2013 11:26 AM, Whistler, Ken wrote: Inclusion of the precomposed characters now seen in the U+1FXX block was part of the price of the merger. What was included was precisely the repertoire requested by Greece, and no attempt was made to further rationalize forms including macrons for An

RE: Just an observation

Steffen Daode Nurpmeso observed: > Hello, in UAX #44 i read > > Simple_Titlecase_Mapping ... > Note: If this field is null, then the Simple_Titlecase_Mapping > is the same as the Simple_Uppercase_Mapping for this character. > > So a parser has to be aware of this, automatically falling

RE: _Unicode_code_page_and_?.net

> > On 7/30/2013 3:27 PM, Asmus Freytag wrote: > > > architectures that depended on swapping character sets (code > > > pages) in mid stream > > > > I thought systems were usually married to a particular code page. I'm > > wondering where (historically) you'd actually change to a different > > co

Re: polytonic Greek: diacritics above long vowels ᾱ, ῑ, ῡ

On Mon, 5 Aug 2013 03:09:37 +0200 Philippe Verdy wrote: > 2013/8/4 Richard Wordingham > > They are missing from the set of precomposed characters. (It's been > > argued that, in an ideal world, *all* precomposed characters would > > be missing.) > Of course you could argue that, but then the

Re: polytonic Greek: diacritics above long vowels ᾱ, ῑ, ῡ

On Sun, 04 Aug 2013 19:21:34 -0700 Stephan Stiller wrote: > > Most of the polytonic precomposed vowels are in the auxiliary > > exemplars for Modern Greek. > I don't know – probably because of the Katharevousa legacy and the > fact that Ancient Greek lives on in literary idioms, for which you > o

RE: polytonic Greek: diacritics above long vowels ᾱ, ῑ, ῡ

Poring back over this voluminous thread to Stephan Stiller's original question: > If one wants to indicate vowel length for the length-ambiguous vowels α, > ι, υ in Ancient Greek, one writes ᾱ, ῑ, ῡ. Is there a reason for why > there are no diacritic-precomposed characters? I guess it's because >

Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

On 05/08/2013, Philippe Verdy wrote: > The way I perceive the regional indicators (in Uncode 6.0), they are > absolutely not used and will be never used at all as long as there are no > complements such as the minimum brackets I suggest to fix them. The 26 > letter-like characters are basically b

Re: FW: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

Anyway the only sequences that are mapped to regional indicators are for private extensions of SJIS in Japan, respetively from KDDI and SoftBank 1F1E8 1F1F3;;F3D2;FBB3 # [CN] People's Republic of China 1F1E9 1F1EA;;F3CF;FBAE # [DE] Germany 1F1EA 1F1F8;;F348;FBB1 # [ES] Spain 1F1EB 1F1F7;;F3CE;FBA

Re: FW: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

Dear Pradeep, The information you got from WhatsApp is wrong. The Unicode Consortium does not "design and create Emoji", and support in WhatsApp for the Indian flag is entirely up to WhatsApp. Please read the last two questions at http://www.unicode.org/faq/emoji_dingbats.html#12 and work with Wha

Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

I don't know. I've not followed much the ongoing work on Japanese emoji. But I know that it contains a few flags in Japanese systems (I'm not sure they were or will be encoded in the UCS or if regional indicator characters will be substitutes for the proposed Emojis if they are not encoded). The w

Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

The way they are encoded, they assume that they will contextually represent the start or the end of the code. This completely breaks the character model and these characters will probably never be used as such. It would have been easier to support them if there was TWO additional bracketing charac

Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

🇮🇳 http://en.wikipedia.org/wiki/Regional_Indicator_Symbol On 05/08/2013, Michael Everson wrote: > Pradeep, > > The Unicode Consortium and ISO/IEC JTC1/SC2 defined a set of "Regional > Indicator symbols" (basically a special coded form of the letters A-Z) and > when two of those come together li

Re: [WhatsApp Support] Your Request: Windows Phone Client 2.10.523(ticket #7044796)

Pradeep, The Unicode Consortium and ISO/IEC JTC1/SC2 defined a set of "Regional Indicator symbols" (basically a special coded form of the letters A-Z) and when two of those come together like CN or GB, the Chinese or UK flag can be displayed, if the font vendor supports a single flag glyph for