[Latingp] Minutes from the call on May 30, 2017

Mon Jun 5 15:38:12 UTC 2017

Given the enormous number of languages involved, perhaps it would be better to establish which ones will be included at this time.  That is, go for inclusion, rather than exclusion. 

And then, separately, principles and processes for including the occasional additional codepoint, if a language which we did not get thru in this initial effort requires it.  Bill Jouris
Inside Products
bill.jouris at insidethestack.com
831-659-8360
925-855-9512 (direct)

      From: Mats Dufberg <mats.dufberg at iis.se>
 To: "ahmedbakhat at yahoo.com" <ahmedbakhat at yahoo.com> 
Cc: Latin GP <latingp at icann.org>
 Sent: Monday, June 5, 2017 3:09 AM
 Subject: Re: [Latingp] Minutes from the call on May 30, 2017

#yiv1664357667 #yiv1664357667 -- _filtered #yiv1664357667 {panose-1:2 7 3 9 2 2 5 2 4 4;} _filtered #yiv1664357667 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv1664357667 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv1664357667 {font-family:PMingLiU;panose-1:2 2 5 0 0 0 0 0 0 0;}#yiv1664357667 #yiv1664357667 p.yiv1664357667MsoNormal, #yiv1664357667 li.yiv1664357667MsoNormal, #yiv1664357667 div.yiv1664357667MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1664357667 a:link, #yiv1664357667 span.yiv1664357667MsoHyperlink {color:blue;text-decoration:underline;}#yiv1664357667 a:visited, #yiv1664357667 span.yiv1664357667MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv1664357667 span.yiv1664357667EmailStyle17 {color:windowtext;}#yiv1664357667 span.yiv1664357667msoIns {text-decoration:underline;color:teal;}#yiv1664357667 .yiv1664357667MsoChpDefault {font-size:10.0pt;} _filtered #yiv1664357667 {margin:70.85pt 70.85pt 70.85pt 70.85pt;}#yiv1664357667 div.yiv1664357667WordSection1 {}#yiv1664357667 Ahmed,    If you start with MSR -- or actually MSR2 -- and try to find languages that support the inclusion of its code points you would never be able to confirm that no code points outside of MSR2 that are needed to support the languages that the Latin GP wants to support. I do not say that such code points will be included, but we should be aware of any limitation in the support of the languages that are claimed to be supported.    If there is any code point in MSR2 not used by any language we would have to investigate every language anyway to confirm that the code point can be excluded.    Besides the Latin code points there are non-spacing marks that are used in combination with Latin code points. Those combinations could have different status in language, either being considered to be a character on its own or being a modified character. In the repertoire that the Latin GP suggests that such non-spacing marks are limited to just those combinations that are really used in the languages that the group wants to support. To find those combinations we have to investigate all languages.    Another aspect is that the method of going code point by code point in MS2 requires that we already know where to find what we are looking for. And when you start studying the material for a language, the hardest step can be to find sources and understanding what they say. After that it could be more straight forward to extract the characters. -- I do not claim that the task is simple. In my work for ICANN Pre-Delegation Testing, I have already done that. There are many grey areas, but that is our task to dig into.    There is no other way than going through all the languages.       Yours, Mats    --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/       From: <latingp-bounces at icann.org> on behalf of Ahmed Bakhat via Latingp <latingp at icann.org>
Reply-To: "ahmedbakhat at yahoo.com" <ahmedbakhat at yahoo.com>
Date: Sunday 4 June 2017 at 15:35
To: "textualsolutions at gmail.com" <textualsolutions at gmail.com>, Mirjana Tasić <Mirjana.Tasic at rnids.rs>
Cc: Latin GP <latingp at icann.org>
Subject: Re: [Latingp] Minutes from the call on May 30, 2017    I raised the issue during the to meeting work on Repertoire, as this group has yet not started its meetings, to devise principles for inclusion / exclusion, so ghat we should have solid grounds to include code points. Furthermore, some one has to present on behalf of the group, what we have done and what is the way forward.    Regarding my email containing draft principles, I wanted to communicate that before going for any strategy ( either inclusion of code ponits on the basis of language or on the basis of MSR) we should have principles for it. In my perception it would be easy to go for MSR is much easy as compared to languages, as it would take years to finish 180 languages.  It doesn't mean at all that we will start from zero, Marjina has already done most of the work,  so we can quickly go through it and work on rest of the code points.    Best Regards,    Ahmed Bakht       Sent from Yahoo Mail on Android    
On Sun, 4 Jun 2017 at 3:52 pm, Textual Solutions <textualsolutions at gmail.com> wrote: _______________________________________________
Latingp mailing list
Latingp at icann.org
https://mm.icann.org/mailman/listinfo/latingp 
_______________________________________________
Latingp mailing list
Latingp at icann.org
https://mm.icann.org/mailman/listinfo/latingp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/latingp/attachments/20170605/cdc47f8e/attachment.html>