Comments take the format @ page <no.> line <no.> section <no.> objection|comment|editorial [reference] Problem: Explain why here. Be sure to add sufficient explanation for someone not familiar with the problem to be able to make a decision. Action: Be specific. For example: Change "leftmost character" to "first character in the string" (You can normally trust the editor to take care of formatting issues in such changes, including use of the correct font et cetera, unless there is something out of the ordinary) PLease DO NOT USE TABS, nor indent your text unnecessarily. In the special case where you wish to raise a single issue which has similar ramifications at many places in the document, but which can be discussed together, it is helpful if you state the first instance at the page number and list later instances in the bug report , for example: @ page 344 line 62 section printf objection Also scanf Problem: Terms used in printf, scanf, and similar interface specs are not consistent. In various places the terms "conversion letter", "conversion specifier", and "conversion character" are used interchangeably. I believe the correct term is "conversion character", as defined on page 344, line 59. Action: Here and also at page 344 line 52 section printf objection page 344 line 53 section printf objection page 346 line 92 section printf objection page 381 line 40-41 section scanf objection page 382 line 43 section scanf objection Change "specifier" or "conversion specifier(s)" or "conversion letter" to "conversion character(s)" Please include line numbers and a section reference (either numeric or interface name). Bug Categorization There may be cases where the originator feels unable to provide text, for example where a clarification is requested. In such cases there are two possibilities: - write down one of the possible alternatives. This at least serves to illustrate your concern. - contact someone else, in advance, who may be able to suggest some wording. Wording can be improved at the resolution meeting, but there will not be time to create new wording, and no possibility of subsequent off-line text generation. To emphasize: CHANGE REQUESTS WITHOUT EXPLICIT EDITING INSTRUCTIONS WILL BE REJECTED. 1. Objections You should only classify an issue as an "objection" if you would vote against approval of the submission if that issue is not resolved. Any objection which is not supported by rationale, or which does not provide a responsive proposal for resolution, will be deemed invalid, and reclassified as a "comment". 2. Comments If you wish to raise an issue where you believe that a better solution is available, but the issue would not, on its own, cause you to vote against approval of the submission if the issue were not resolved, you should classify it as a "comment". 3. Editorials Issues marked as editorial will not be discussed, they are included in this mechanism as a simple way to bring such matters to the sponsors attention. (If you see someone else classifying an issue as editorial, and you believe it DOES need discussion or clarification, you should resubmit the point yourself, with a different classification.) Note that it could be helpful for you to include a company identifier and sequence number (eg Acme-001) in the optional "reference" field, for later cross referencing. single numbered list. -------------------------- end of file -----------------------------------