Authors, Apologies for the delay in publication. While preparing the document for publication, one our scripts noted the following error in the PDF file:
Errors 1 Text cannot be mapped to Unicode While troubleshooting, we were advised not to mix LTR and RTL scripts within the same <t> element and to include explanatory text that uses the <u> element. We have updated the file to be more similar to RFC 9290 (which also uses “שלום") — "TITLE=שלום” now appears in artwork and is followed by the following explanatory text: where in direction of reading, the sequence of characters is: "ש" (HEBREW LETTER SHIN, U+05E9), "ל" (HEBREW LETTER LAMED, U+05DC), "ו" (HEBREW LETTER VAV, U+05D5), "ם" (HEBREW LETTER FINAL MEM, U+05DD). This update resolves the error noted above. The updated files are available here: https://www.rfc-editor.org/authors/rfc9639.xml https://www.rfc-editor.org/authors/rfc9639.txt https://www.rfc-editor.org/authors/rfc9639.pdf https://www.rfc-editor.org/authors/rfc9639.html These diffs highlight the recent updates only: https://www.rfc-editor.org/authors/rfc9639-lastdiff.html https://www.rfc-editor.org/authors/rfc9639-lastrfcdiff.html Please review and let us know if we may continue with publication. Thank you, RFC Editor/sg > On Nov 25, 2024, at 7:56 AM, Martijn van Beurden <mva...@gmail.com> wrote: > > Hi Madison, > > At the moment I am not aware of any other updates. Many thanks for taking > care of this last-minute change. > > Kind regards, Martijn van Beurden > > Op ma 25 nov 2024 16:38 schreef Madison Church <mchu...@amsl.com>: > Hi Authors, > > IANA has completed their updates for the Free Lossless Audio Codec (FLAC) > registry (see https://www.iana.org/assignments/flac/flac.xhtml). We will > resume the publication process of this document if there are no further > updates. > > Thank you! > RFC Editor/mc > > > On Nov 25, 2024, at 8:35 AM, Madison Church <mchu...@amsl.com> wrote: > > > > Hi Sabrina, > > > > Both updates look good now. Thank you! > > > > RFC Editor/mc > > > >> On Nov 22, 2024, at 7:58 PM, Sabrina Tanamal via RT <iana-mat...@iana.org> > >> wrote: > >> > >> Hi Madison, > >> > >> Apologies for missing the updated Application ID. This has been fixed: > >> > >> https://www.iana.org/assignments/flac > >> > >> Thanks, > >> Sabrina > >> > >> On Fri Nov 22 20:07:32 2024, mchu...@amsl.com wrote: > >>> Hi Sabrina, > >>> > >>> Upon reviewing the change more closely, it looks like the Application > >>> ID column for this entry needs to be updated as well (same row as w64 > >>> [1]): > >>> > >>> OLD: > >>> 0x773634C0 > >>> > >>> NEW: > >>> 0x77363420 > >>> > >>> Apologies for the noise! > >>> > >>> Thank you, > >>> RFC Editor/mc > >>> > >>>> On Nov 22, 2024, at 2:01 PM, Madison Church <mchu...@amsl.com> wrote: > >>>> > >>>> Hi Sabrina, > >>>> > >>>> The change looks good. Thank you for your help! > >>>> > >>>> RFC Editor/mc > >>>> > >>>>> On Nov 22, 2024, at 12:31 PM, Sabrina Tanamal via RT <iana- > >>>>> mat...@iana.org> wrote: > >>>>> > >>>>> Hi Martijn, Madison, all, > >>>>> > >>>>> We've added the footnote for the following registration: > >>>>> > >>>>> 0x773634C0 w64 [1] FLAC Wave64 chunk storage [foreign-metadata][RFC- > >>>>> ietf-cellar-flac-14] IETF > >>>>> > >>>>> Please see > >>>>> https://www.iana.org/assignments/flac > >>>>> > >>>>> If any other changes are required, just let us know. > >>>>> > >>>>> Best regards, > >>>>> > >>>>> Sabrina Tanamal > >>>>> Lead IANA Services Specialist > >>>>> > >>>>> On Wed Nov 20 09:44:16 2024, mva...@gmail.com wrote: > >>>>>> Hi, > >>>>>> > >>>>>> I think adding a footnote is fine, as long as future entries with a > >>>>>> space > >>>>>> can be included in a similar way. > >>>>>> > >>>>>> Kind regards, Martijn van Beurden > >>>>>> > >>>>>> Op wo 20 nov 2024 02:29 schreef Sabrina Tanamal via RT <iana- > >>>>>> mat...@iana.org > >>>>>>> : > >>>>>> > >>>>>>> Hi Michael, all, > >>>>>>> > >>>>>>> Would it be okay if we proceed with adding a footnote as Madison > >>>>>>> suggested > >>>>>>> below? > >>>>>>> > >>>>>>> If you'd like us to try the other options, we may need a little > >>>>>>> more time > >>>>>>> to look into this. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Sabrina > >>>>>>> > >>>>>>> On Fri Nov 15 16:07:02 2024, mcr+i...@sandelman.ca wrote: > >>>>>>>> > >>>>>>>> Madison Church <mchu...@amsl.com> wrote: > >>>>>>>>> Hi Martijn, *IANA, > >>>>>>>> > >>>>>>>>> Thank you for your quick reply! We have made updates to the > >>>>>>>>> document > >>>>>>>>> as requested. > >>>>>>>> > >>>>>>>>> Regarding "w64 " and your note: > >>>>>>>>>> In the second column, a since whitespace character > >>>>>>>>>> was added. This is intentional, as each ID is four bytes (and, > >>>>>>>>>> if > >>>>>>>>>> representable in ASCII, four characters) meaning w64 is too > >>>>>>>>>> short > >>>>>>>>>> without that space. > >>>>>>>> > >>>>>>>>> Due to the significance of this single space character, and the > >>>>>>>>> fact > >>>>>>>>> that it was shown as "w64 " in [FLAC-implementation] and that > >>>>>>>>> the > >>>>>>>>> change in the XML file does not yield a change in the > >>>>>>>>> publication > >>>>>>>>> formats, perhaps a note should be added for this value? > >>>>>>>> > >>>>>>>> Can we use some UTF-8 that results in an ␣ ? > >>>>>>>> I also found: > >>>>>>>> https://www.fileformat.info/info/unicode/char/2423/index.htm > >>>>>>>> > >>>>>>>> Or does that result in more confusion? > >>>>>>>> Or even "w64<space>" > >>>>>>>> > >>>>>>>> -- > >>>>>>>> Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT > >>>>>>>> consulting ) > >>>>>>>> Sandelman Software Works Inc, Ottawa and Worldwide > >>>>>>> > >>>>>>> > >>>>> > >>>> > >> > > > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
