Personal comment from Michel Suignard (IP member)

[Michel Suignard <michel@xxxxxxxxxxxx>]

First, I want to congratulate the Khmer Generation Panel for their excellent 
work on this Khmer LGR proposal. I have looked at the repertoire and the WLE 
rules and did not find any issues at this point. The following comments are 
only editorial and aim at improving the quality of the PDF documentation 
associated with the XML file.

Michel Suignard
(Integration Panel member)

General
-----------
The Romanized transliteration of Khmer words should be shown consistently for 
all occurrence of Khmer words written in their original script, but not when 
letters are shown in isolation. Because the LGR document is likely to become a 
reference document, it would facilitate reading by people not familiar with the 
Khmer script.

The naming of the Khmer code points is somewhat inconsistent. Most of the time, 
it is done using the form 'Khmer INDEPENDENT VOWEL QUU (U+17A9)' which is a bit 
unorthodox from a Unicode practice point of view, but sometimes part of the 
name is in lower case such as in 'Khmer KAKABAT sign (U+1CE)' in page 7, with 
sometimes the actual glyph displayed, but most of the times not. While the form 
'U+xxxx 'glyph' CHARACTER NAME' is the preferred form ('glyph' being the actual 
glyph), the LGR proposal can use an alternative form as long as it is used 
consistently.

Specific items:
-------------------
Page 5, 3rd paragraph:
'The remaining proposal represents the results of this process.'
->
'The following sections of this proposal represent the result of this process.'

Page 7, section 5.3 1st paragraph:
Remove spurious apostrophe after 'Khmer LGR' in first line.
'by a one of these' -> 'by one of these'

Page 7, section 5.4
'This diacritic sign is not used in repertoire because this sign is used to 
change the pronunciation louder only'
->
'This diacritic sign is not used in the LGR repertoire because the sign is only 
used to make the pronunciation louder'

Insert a space before 'to give stressed intonation'

'As this sign only represents spoken form of the word and it is not normally 
used in written form, it is excluded from repertoire.'
->
'Because this sign only represents spoken forms of the word and it is not 
normally used to represent written forms, it is excluded from the LGR 
repertoire.'

Page 8, section 5.4.5
'so a "series-three" class' -> 'so a class "series-three"'
(note that the term class is not strictly needed here, the term 'series' in 
itself implies a classification.)

Page 11 and 13, section 5.6
One name corresponding to U+17B1 is missing spaces in its description:
QOOTYPEONE -> QOO TYPE ONE

The name description for 17C6 and 17C7 do not represent Unicode Code Point Name 
as claimed in the Table header. Instead of the form 'and Vowel Am', using a 
parenthetical annotation, such as '(Vowel Am)', would separate the official 
name from what is an alternate name not part of the Unicode name.

Page 14, section 6.1
'Khmer GP considers two code points are variants if they are visually same to 
each other in either full consonant form or the subscript form.'
->
'The Khmer Generation Panel considers that two code points are variants if they 
are visually identical to each other in either full consonant form or subscript 
form.'

Page 14, section 6.2
Add 'The' in front of 'Khmer Generation Panel'.

'However, when they occur in combined form in a label their shape changes.'
->
'However, their shape changes when they occur in combined form in a label.'

Page 14, section 7.1
'applied' -> 'applies'

'as this occurs only as the base consonant and not as a subscript consonant'
->
'because it only occurs as a base consonant, not as a subscript consonant'
--------------