Re: I18n comment: rfc3066 or successor

At 19:42 06/01/21, wrote:
 >Comment from the i18n review of:
 >Comment 8
 >Editorial/substantive: S
 >Location in reviewed document:
 >Sec. 6.3.1
 >"as described in RFC 3066 ([RFC3066])"
 >Recommend 'as described in RFC 3066 ([RFC3066]) or its successor'.
 >Note that its successor is currently only awaiting the IETF editor to
 >assign an RFC number, but has been approved by the IETF to succeed RFC3066.
 >Note also that it will allow for additional subcode values, such as script

Just one small correction: "IETF editor" -> "RFC Editor".

Regards,    Martin. 

Received on Tuesday, 24 January 2006 00:43:18 UTC