Edits for N1589 Introduction, paragraph 1, sentence 2, change "This guidance" to "This document". [It is not clear what is meant.] 1. In para 2, change "ISO/IEC 24772-1" to "ISO/IEC 24772-1:2024". [Which revision is referenced matters.] SM - not this early. 2. At the end add "ISO/IEC/IEEE 60559:2020, Information technology – Microprocessor Systems – Floating-Point arithmetic" [This is very important for floating-point arithmetic. It is totally inappropriate to move this to the bibliography. It is referenced normatively in 6.4.] SM - ok 3. In para 1, change "ISO/IEC 24772-1, ISO/IEC 1539-1" to "ISO/IEC 24772-1:2024,1, ISO/IEC 1539-1:2023". [Which revision is referenced matters.] SM ok 3.10. Change "the current Fortran standard" to "ISO/IEC 1539-1:2023". [The next revision might have different obsolescent features.] SM - no. This is a definition. The next version will have different features. 4.1. Change "previous editions of ISO iEC 1539-1" to "previous versions of the Fortran standard". [Fortran began as an ANSI standard in 1966, became ISO 1539 in 1977, and became ISO/IEC 1539-1 later. We caught all this by talking about previous versions of the Fortran standard.] SM - the ISO editor explicitly prohibited this. 4.1. Change "ISO IEC 1539-1 Programming language Fortran" to "ISO/IEC 1539-1:2023". [Use the correct wording.] sm - done 4.3, 4.4, 4.10.1, 4.10.5, 5, 6.37.1, 6.58.1, 6.65.2. Change "ISO IEC" to "ISO/IEC". [Typos.] sm - Fixed 4.4. In para 2, change "Annex A.2 of ISO IEC 1539-1" to "ISO/IEC 1539-1:2023, Annex A.2". [The editor's suggestion should be accepted (already done in 4.3).] SM Fixed 4.6. In para 2, change "0.0/0.0" to "divide zero by zero". [The IEEE standard says "divide zero by zero" because it applies however zero is represented. We need to do this too.] SM fixed 4.6. In para 2, change "not a number (a NaN))" to "a NaN (not a number)". [The technical term is NaN and is defined in the IEEE standard.] SM - defined above in same paragraph, so just use "NaN" 4.6. In para 2, change the IEEE terms in italics (NaN, overflow, ...) to Roman in quotes. [ISO style now used elsewhere in the document.] SM - OK 4.6. In para 2, change `The flags are therefore called {\it sticky}.' to `The flags are therefore sometimes called "sticky".' ["sticky" is not an IEEE term.] SM OK 4.6. In para 2, change "divide_by_zero" to "divideByZero". [This is the term used by the IEEE standard.] SM Ok 4.7. "companion processor" should not be in italics. [It is not used in italics in the Fortran standard.] SM Ok 4.10. Change the Fortan terms in italics (images, coarray, ...) to Roman in quotes. [ISO style now used elsewhere in the document.] 4.10.6, para 2. Change "{\tt MPI}. {\tt MPI}" to "MPI. MPI". ["MPI" should not be in code font. It is not an identifier in the language, unlike MPI_Irecv, MPI_Isend, etc.] sm Ok 6.2.2 and many other places. Add comma after "ISO/IEC 24772-1:2024" in references to subclauses. [This is the ISO style.] SM Ok 6.3.1. In para 2, change "ISO/IEC 1539" to "ISO/IEC 1539:2023,". [The ISO style for a clause of a standard.] SM Ok 6.4.1, paragraph 1, line 2. Change "60559:" to "60559". [Delete the colon. Typo.] SM OK 6.4.2, penultimate bullet. Change to "Where the intrinsic modules {\tt IEEE_EXCEPTIONS}, {\tt IEEE_ARITHMETIC}, and {\tt IEEE_FEATURES} are in use, apply the procedures of {\tt IEEE_EXCEPTIONS} and {\tt IEEE_ARITHMETIC} with names starting {\tt IEEE_SUPPORT} to determine which features of ISO/IEC 60559 are supported;" [We need to be much more explicit about what we are recommending.] SM Reject. This is a late technical change that could require FDIS ballot. Also, if the list is incomplete it is problematic. It also would require wording changes in 6.4.1 6.6.1. In para 6, change "ISO/IEC 10646 character" to "ISO 10646 character". [This is a Fortran term. If we feel it needs to defined in this document, add to 3 3.7a ISO 10646 character character whose representation method corresponds to UCS-4 in ISO/IEC 10646:2020] SM Made simple change 6.32.1. In paragraph 4, line 1, change "parameter passing " to "argument-passing" and in paragraph 5, line 1, change "parameter" to "argument-passing" for consistency with the use of "argument-passing" in paragraphs 3 and 6. [It is confusing to use different terms when the same meaning is intended and this is the term used in Fortran.] SM Done 6.37.1. Change "ISO IEC 1539-1 does not provide language-specific mechanisms to convert between unrelated types." to "ISO/IEC 1539-1;2023 does not provide other means to convert between unrelated types." [The date is needed in case a revision provides other means. The present wording is wrong because transfer, etc are language-specific mechanisms to convert between unrelated types.] SM - Ok, but left "mechanisms" vs "means" 6.44.1. In para 3, change "code block" to "block" thrice. {"block" is a Fortran term. Do we need to add it to 3?] SM We are using upcasts, downcasts and crosscuts in general terms. "Code block" is also used here in a general sense. I think this needs discussion. 6.54.1, line 1, change the second "Fortran" to "ISO/IEC 1539-1:2023". SM Accept in principle, but changed "Fortran" to "it" 6.54.1, Delete "on the given variable". [The intended effect might be to assign a value to another variable.] SM Ok 6.58.1. Add comma after "ISO/IEC 1539:2023". [The ISO style for a clause of a standard.] SM Ok 6.58.1. Change the final occurrence of "ISO/IEC 1539-1" to "ISO/IEC 1539-1:2023". [There is a reference to a clause of the standard in the sentence. Also, a different mechanism is expected in the next version of the standard.] SM Done 6.61.2. Indent the numbered list. [It belongs only to the third list item.] SM Ok 6.62.2. In third bullet change "at relevant intervals" to "at appropriate times". [Awkward reuse of "relevant" and it is not the interval that matters. Could go back to the original "from time to time".] SM - We disagree significantly here. The interval could be time-based but could also be based on other factors, such as the state of a shared variable. "from time to time" is too lax. Changed to "at appropriate intervals" which makes the change editorial. 7.3.1, para 2. Do not indendent the paragraph. After "allocatable" add "for defined behaviour:" then start a list. Delete ",and for correct operation," then start the second list item. [There are two separate cases to consider, pointer and allocatable. They should be treated similarly]. SM Ok. 7.3.1, para 3. Do not indendent the paragraph and change "paragraph" to "paragraphs". [Match the edits to para 2.] SM Done. Bibliography, move the single item to 2 and remove Bibliography. [This is very important for floating-point arithmetic. It should be referenced normatively in 6.4.] SM - OK, but expect ISO editor to reject.