Hi Mirjana,

The steps look fine to me.

In case this is useful here is a tool to find Unicode properties of a glyph or code point. http://unicode.org/cldr/utility/character.jsp

-Dennis

From: <latingp-bounces@icann.org> on behalf of Mirjana Tasić <Mirjana.Tasic@rnids.rs>
Date: Friday, January 27, 2017 at 1:31 PM
To: Latin GP <latingp@icann.org>
Subject: [EXTERNAL] [Latingp] Proposal - How to proceed with attesting Latin letters in MSR2 using available sources, starting from language alphabets side

Here are some thoughts how the attestation can be done. Please, feel free to comment, correct, add some ideas…

Regards Mirjana

________________________________________________________

Proposal - How to proceed with attesting Latin letters in MSR2 using available sources, starting from language alphabets side:

For every language, some information on the alphabet used by that language could be found starting from http://www.omniglot.com/writing/langalph.htm and browsing every individual entry for languages listed in the section which shows the languages using Latin script.

Every letter in the specific alphabet should be investigated and checked against  Latin part of MSR2 with attestation . There are three possible cases:

1. If the letter is previously marked with CLDR in column Ref in the table Latin part of MSR2 with attestation , this letter has to be skipped, it is attested.

2. If any letter (without CLDR in column Ref) is found, the row in the table must be filled with available information.

3. If any new letter, which is not in the table Latin part of MSR2 with attestation, would be found, it has to be added at the end of table with all available information.

4. Minimum set of information on specific letter that has to be filled in the table Latin part of MSR2 with attestation, are:
   1. Unicode code
   2. Glyph (if the source allows copy/paste function)
   3. Example of language using the code point
   4. UNICODE character name
   5. Comment on the sources which provided relevant information