[Neobrahmigp] IP review of Oriya LGR 20181220

[Kuldeep Patnaik]

Thank you Dr Sarmad,
I will revert to you soon.

Best Regards
Kuldeep Patnaik

On Wed, Feb 6, 2019 at 8:45 AM Sarmad Hussain <sarmad.hussain at icann.org>
wrote:

> Dear Kuldeep, all,
>
>
>
> Please find below (and attached) the review of the proposal by IP.  Kindly
> let us know if you have any queries.
>
>
>
> We look forward to the final version, incorporating the feedback.
>
>
>
> Regards,
> Sarmad
>
>
>
>
> ------------------------------
>
> To: Neo-Brahmi Generation Panel
> From: Integration Panel
> Subject: Updated Oriya Proposal dated 20181220
>
> The IP has reviewed the updated proposal and has a few additional comments
> and suggestions as set out below and in the attached document where
> suggested edits are shown in redline. Once these are reviewed, accepted or
> altered by the GP, the proposal is ready to be finalized.
>
> *DOCX*
>
> (1) The .docx proposal would still benefit if the citation of specific
> characters would* as much as possible *include the code point, glyph and
> character name (especially, for example, in 3.6, 3.7, 3.8 and 3.9). This
> would make it much more easily read by non-Oriya reading people.
>
> (2) There is a missing space in the heading "10.3 Oriyaand Telugu".
>
> This, and many other instances of missing spaces and small copy edits have
> been addressed by the suggested edits in the attached document. The GP is
> encouraged to review and accept these or make additional changes.
>
> (3) The discussion of variants vs. confusables could use some small edits
> to align better with the terminology and explanation used across the Root
> Zone LGR. (See attached document)
>
>
>
> (4) Halant should be capitalized to match usage elsewhere. (See attached
> document).
>
>
>
> (5) Page 12, the fourth page of the Public Comments Feedback for  ...
> Oriya, claims (in 3.4 and 3.6) that ISO 15919 is to be used for lossless
> trasliteration of the characters, but in fact the IPA seems to be used
> everywhere for phonetic renderings, thus for example using j rather than y.
>
>
>
> *XML*
>
> The updated XML passes our tool
>
>
>
> *TXT*
>
> The label file has been verified.
>
>
> ------------------------------
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/neobrahmigp/attachments/20190206/7f79f0be/attachment.html>