OASIS Virtual I/O Device (VIRTIO) TC

Hi Rusty and all, I've just taken a good look at the virtio files for publication, and they will need a few additional modifications to the front pages.  Although the TC Process does not allow changes to the document content after approval, the front pages (down through the table of contents) may be modified without any need for the TC to re-approve anything. I'm attaching a ZIP file containing examples of the front pages for both the Committee Specification Draft 01 (csd01) and the Public Review Draft 01 (csprd01) EXACTLY as they should appear, and I'll list the needed changes below. We should be ready to publish the files and begin the Public Review quickly after we receive the updated files. They should be sent to me and Chet. Changes needed to the csd01 files: - Subtitle needs to include the csd number "01", so it will be Committee Specification Draft 01 - Citation format needs to include the csd number "01", and also the word "OASIS" before - so it will be OASIS Committee Specification Draft 01. - It also needs a period after the "01", and also at the end, after the URI. Please see the attached example, and follow it exactly. Changes needed to the csprd01 files: - Subtitle needs to be:  (on two lines) Committee Specification Draft 01 / Public Review Draft 01 - Date needs to be 03 December 2013 - in three places - subtitle, citation format, and footers (it now says 04 December) - Citation format needs to show "OASIS Committee Specification Draft 01 / Public Review Draft 01".  It also needs a period after the (second) "01", and also at the end, after the URI. Again, please see the attached examples. Finally, there is an issue which I don't think we can address for csd01/csprd01 (without re-approval by the TC), but which I very much hope can be addressed in future publications: - The 18 footnotes each appear as individual HTML files, leading to a terrible clutter in the publication directory. We'd like to see if they can either be included in the main HTML file (typically at the end of the file) or if this can't be arranged, then in a "footnotes" subdirectory. Although Chet is on vacation now, I'll also check with him to see if we (TC Administration) can apply the "subdirectory" fix to these files during publication.  It may qualify as an allowable style modification. Best regards, Paul -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst Attachment: virtio-v1.0-new-front-pages.zip Description: Zip archive

Hi rusty and all, I should also emphasize that the updated files should NOT contain any changes from the material approved by the TC on December 3, other than the necessary changes to the front pages. Best regards, Paul On Fri, Dec 20, 2013 at 2:49 PM, Paul Knight < paul.knight@oasis-open.org > wrote: Hi Rusty and all, I've just taken a good look at the virtio files for publication, and they will need a few additional modifications to the front pages.  Although the TC Process does not allow changes to the document content after approval, the front pages (down through the table of contents) may be modified without any need for the TC to re-approve anything. I'm attaching a ZIP file containing examples of the front pages for both the Committee Specification Draft 01 (csd01) and the Public Review Draft 01 (csprd01) EXACTLY as they should appear, and I'll list the needed changes below. We should be ready to publish the files and begin the Public Review quickly after we receive the updated files. They should be sent to me and Chet. Changes needed to the csd01 files: - Subtitle needs to include the csd number "01", so it will be Committee Specification Draft 01 - Citation format needs to include the csd number "01", and also the word "OASIS" before - so it will be OASIS Committee Specification Draft 01. - It also needs a period after the "01", and also at the end, after the URI. Please see the attached example, and follow it exactly. Changes needed to the csprd01 files: - Subtitle needs to be:  (on two lines) Committee Specification Draft 01 / Public Review Draft 01 - Date needs to be 03 December 2013 - in three places - subtitle, citation format, and footers (it now says 04 December) - Citation format needs to show "OASIS Committee Specification Draft 01 / Public Review Draft 01".  It also needs a period after the (second) "01", and also at the end, after the URI. Again, please see the attached examples. Finally, there is an issue which I don't think we can address for csd01/csprd01 (without re-approval by the TC), but which I very much hope can be addressed in future publications: - The 18 footnotes each appear as individual HTML files, leading to a terrible clutter in the publication directory. We'd like to see if they can either be included in the main HTML file (typically at the end of the file) or if this can't be arranged, then in a "footnotes" subdirectory. Although Chet is on vacation now, I'll also check with him to see if we (TC Administration) can apply the "subdirectory" fix to these files during publication.  It may qualify as an allowable style modification. Best regards, Paul -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

On Fri, Dec 20, 2013 at 02:58:52PM -0500, Paul Knight wrote: > Finally, there is an issue which I don't think we can address for csd01/ > csprd01 (without re-approval by the TC), but which I very much hope can be > addressed in future publications: > - The 18 footnotes each appear as individual HTML files, leading to a > terrible clutter in the publication directory. We'd like to see if they can > either be included in the main HTML file (typically at the end of the file) > or if this can't be arranged, then in a "footnotes" subdirectory. > > Although Chet is on vacation now, I'll also check with him to see if we (TC > Administration) can apply the "subdirectory" fix to these files during > publication.  It may qualify as an allowable style modification. htlatex has an option to place footnotes at the end of the file with the main text. I attach an example result. If this is desired, pls let me know and I'll commit this change. ---> html: make footnotes inline Makes text search easier and reduces clutter in the public directory. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> --- diff --git a/makehtml.sh b/makehtml.sh index cad297c..93e26b5 100755 --- a/makehtml.sh +++ b/makehtml.sh @@ -7,7 +7,7 @@ cp virtio-html.tex $SPECDOC.tex #uncomment if you have a broken t4ht #PATH=./t4ht-workaround:${PATH} htlatex $SPECDOC.tex "virtiohtml,info,charset=utf-8" " -cunihtf -utf8" -htlatex $SPECDOC.tex "virtio-html,info,charset=utf-8" " -cunihtf -utf8" +htlatex $SPECDOC.tex "virtio-html,info,charset=utf-8,fn-in" " -cunihtf -utf8" rm $SPECDOC.tex -- MST Attachment: virtio-v1.0-wd02.zip Description: Zip archive

"Michael S. Tsirkin" <mst@redhat.com> writes: > On Fri, Dec 20, 2013 at 02:58:52PM -0500, Paul Knight wrote: >> Finally, there is an issue which I don't think we can address for csd01/ >> csprd01 (without re-approval by the TC), but which I very much hope can be >> addressed in future publications: >> - The 18 footnotes each appear as individual HTML files, leading to a >> terrible clutter in the publication directory. We'd like to see if they can >> either be included in the main HTML file (typically at the end of the file) >> or if this can't be arranged, then in a "footnotes" subdirectory. >> >> Although Chet is on vacation now, I'll also check with him to see if we (TC >> Administration) can apply the "subdirectory" fix to these files during >> publication.  It may qualify as an allowable style modification. > > htlatex has an option to place footnotes at the end of > the file with the main text. > > I attach an example result. > > If this is desired, pls let me know and I'll commit this change. Yes, let's do that. I prefer inline footnotes anyway. Thanks, Rusty.

Paul Knight <paul.knight@oasis-open.org> writes: > Hi Rusty and all, > > I've just taken a good look at the virtio files for publication, and they > will need a few additional modifications to the front pages. > > Although the TC Process does not allow changes to the document content > after approval, the front pages (down through the table of contents) may be > modified without any need for the TC to re-approve anything. > > I'm attaching a ZIP file containing examples of the front pages for both > the Committee Specification Draft 01 (csd01) and the Public Review Draft 01 > (csprd01) EXACTLY as they should appear, and I'll list the needed changes > below. > > We should be ready to publish the files and begin the Public Review quickly > after we receive the updated files. They should be sent to me and Chet. > > Changes needed to the csd01 files: > - Subtitle needs to include the csd number "01", so it will be Committee > Specification Draft 01 Done. > - Citation format needs to include the csd number "01", and also the word > "OASIS" before - so it will be OASIS Committee Specification Draft 01. Done. > - It also needs a period after the "01", and also at the end, after the URI. Done. > Please see the attached example, and follow it exactly. In addition, I added a horizontal rule above the Notices section in the html, as your example had. > Changes needed to the csprd01 files: > - Subtitle needs to be: (on two lines) > Committee Specification Draft 01 / > Public Review Draft 01 Done. > - Date needs to be 03 December 2013 - in three places - subtitle, citation > format, and footers (it now says 04 December) Damn, that's entirely my fault; I updated the respitory and regenerated. Fixed. > - Citation format needs to show "OASIS Committee Specification Draft 01 / > Public Review Draft 01". It also needs a period after the (second) "01", > and also at the end, after the URI. > Again, please see the attached examples. Yep, fixed too. These fixes have all been committed to the repository, so hopefully the next time we generate a draft it will be flawless. Attached below. > Finally, there is an issue which I don't think we can address for > csd01/csprd01 (without re-approval by the TC), but which I very much hope > can be addressed in future publications: > - The 18 footnotes each appear as individual HTML files, leading to a > terrible clutter in the publication directory. We'd like to see if they can > either be included in the main HTML file (typically at the end of the file) > or if this can't be arranged, then in a "footnotes" subdirectory. Hmm, I'll have to dig deeper to see if I can do that. > Although Chet is on vacation now, I'll also check with him to see if we (TC > Administration) can apply the "subdirectory" fix to these files during > publication. It may qualify as an allowable style modification. Thanks, Rusty. > Best regards, > Paul > -- > Paul Knight <paul.knight@oasis-open.org> - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > Attachment: virtio-v1.0-csd01.zip Description: Zip archive Attachment: virtio-v1.0-csprd01.zip Description: Zip archive

Thanks, Rusty -- this looks good. We'll move the individual footnote files in the HTML format into a subdirectory for publication. Best regards, Paul On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell < rusty@au1.ibm.com > wrote: Paul Knight < paul.knight@oasis-open.org > writes: > Hi Rusty and all, > > I've just taken a good look at the virtio files for publication, and they > will need a few additional modifications to the front pages. > > Although the TC Process does not allow changes to the document content > after approval, the front pages (down through the table of contents) may be > modified without any need for the TC to re-approve anything. > > I'm attaching a ZIP file containing examples of the front pages for both > the Committee Specification Draft 01 (csd01) and the Public Review Draft 01 > (csprd01) EXACTLY as they should appear, and I'll list the needed changes > below. > > We should be ready to publish the files and begin the Public Review quickly > after we receive the updated files. They should be sent to me and Chet. > > Changes needed to the csd01 files: > - Subtitle needs to include the csd number "01", so it will be Committee > Specification Draft 01 Done. > - Citation format needs to include the csd number "01", and also the word > "OASIS" before - so it will be OASIS Committee Specification Draft 01. Done. > - It also needs a period after the "01", and also at the end, after the URI. Done. > Please see the attached example, and follow it exactly. In addition, I added a horizontal rule above the Notices section in the html, as your example had. > Changes needed to the csprd01 files: > - Subtitle needs to be:  (on two lines) > Committee Specification Draft 01 / > Public Review Draft 01 Done. > - Date needs to be 03 December 2013 - in three places - subtitle, citation > format, and footers (it now says 04 December) Damn, that's entirely my fault; I updated the respitory and regenerated.  Fixed. > - Citation format needs to show "OASIS Committee Specification Draft 01 / > Public Review Draft 01".  It also needs a period after the (second) "01", > and also at the end, after the URI. > Again, please see the attached examples. Yep, fixed too. These fixes have all been committed to the repository, so hopefully the next time we generate a draft it will be flawless. Attached below. > Finally, there is an issue which I don't think we can address for > csd01/csprd01 (without re-approval by the TC), but which I very much hope > can be addressed in future publications: > - The 18 footnotes each appear as individual HTML files, leading to a > terrible clutter in the publication directory. We'd like to see if they can > either be included in the main HTML file (typically at the end of the file) > or if this can't be arranged, then in a "footnotes" subdirectory. Hmm, I'll have to dig deeper to see if I can do that. > Although Chet is on vacation now, I'll also check with him to see if we (TC > Administration) can apply the "subdirectory" fix to these files during > publication.  It may qualify as an allowable style modification. Thanks, Rusty. > Best regards, > Paul > -- > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

Hi Rusty and all, An interesting item, which I don't think will affect publication, shows up in the HTML versions of the documents: It is probably related to kerning with the LaTex system: There are combined letters "?" (as opposed to the individual letters "fi")in the word "Speci?cation" on the front page and elsewhere, and various occurrences of double-f "?", which are actually represented by non-ascii characters.  (This may or may not show up in this email for your amusement.) Luckily, these do not occur in the URIs, as far as I have been able to see... that would be a problem. For future publications, is there some control over "kerning" to prevent this?  I think we can live with it, but it's an interesting element which could cause problems in some situations. Best regards, Paul On Mon, Dec 23, 2013 at 12:16 PM, Paul Knight < paul.knight@oasis-open.org > wrote: Thanks, Rusty -- this looks good. We'll move the individual footnote files in the HTML format into a subdirectory for publication. Best regards, Paul On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell < rusty@au1.ibm.com > wrote: Paul Knight < paul.knight@oasis-open.org > writes: > Hi Rusty and all, > > I've just taken a good look at the virtio files for publication, and they > will need a few additional modifications to the front pages. > > Although the TC Process does not allow changes to the document content > after approval, the front pages (down through the table of contents) may be > modified without any need for the TC to re-approve anything. > > I'm attaching a ZIP file containing examples of the front pages for both > the Committee Specification Draft 01 (csd01) and the Public Review Draft 01 > (csprd01) EXACTLY as they should appear, and I'll list the needed changes > below. > > We should be ready to publish the files and begin the Public Review quickly > after we receive the updated files. They should be sent to me and Chet. > > Changes needed to the csd01 files: > - Subtitle needs to include the csd number "01", so it will be Committee > Specification Draft 01 Done. > - Citation format needs to include the csd number "01", and also the word > "OASIS" before - so it will be OASIS Committee Specification Draft 01. Done. > - It also needs a period after the "01", and also at the end, after the URI. Done. > Please see the attached example, and follow it exactly. In addition, I added a horizontal rule above the Notices section in the html, as your example had. > Changes needed to the csprd01 files: > - Subtitle needs to be:  (on two lines) > Committee Specification Draft 01 / > Public Review Draft 01 Done. > - Date needs to be 03 December 2013 - in three places - subtitle, citation > format, and footers (it now says 04 December) Damn, that's entirely my fault; I updated the respitory and regenerated.  Fixed. > - Citation format needs to show "OASIS Committee Specification Draft 01 / > Public Review Draft 01".  It also needs a period after the (second) "01", > and also at the end, after the URI. > Again, please see the attached examples. Yep, fixed too. These fixes have all been committed to the repository, so hopefully the next time we generate a draft it will be flawless. Attached below. > Finally, there is an issue which I don't think we can address for > csd01/csprd01 (without re-approval by the TC), but which I very much hope > can be addressed in future publications: > - The 18 footnotes each appear as individual HTML files, leading to a > terrible clutter in the publication directory. We'd like to see if they can > either be included in the main HTML file (typically at the end of the file) > or if this can't be arranged, then in a "footnotes" subdirectory. Hmm, I'll have to dig deeper to see if I can do that. > Although Chet is on vacation now, I'll also check with him to see if we (TC > Administration) can apply the "subdirectory" fix to these files during > publication.  It may qualify as an allowable style modification. Thanks, Rusty. > Best regards, > Paul > -- > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

A bit of follow-up on the "fi" and "ff" issue: - first, I see that the TC (?) apparently ran into the issue and introduced a workaround in the file /tex/makehtml.sh #For some unclear reason we get 'fi' replaced by NULL character #on Fedora. file recognizes result as a binary data. - second, for what it's worth, a bit of information which indicates that there may be a way to shut it off in TeX: " TeX  is an example of a computer typesetting system that makes use of ligatures automatically. The  Computer Modern Roman  typeface provided with TeX includes the five common ligatures  ff ,  fi ,  fl ,  ffi , and  ffl . When TeX finds these combinations in a text it substitutes the appropriate ligature, **unless overridden by the typesetter.** " [1] [1]  http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting This isn't an area where I can likely be of much help other than to wish you luck... Best regards, Paul On Mon, Dec 23, 2013 at 4:38 PM, Paul Knight < paul.knight@oasis-open.org > wrote: Hi Rusty and all, An interesting item, which I don't think will affect publication, shows up in the HTML versions of the documents: It is probably related to kerning with the LaTex system: There are combined letters "?" (as opposed to the individual letters "fi")in the word "Speci?cation" on the front page and elsewhere, and various occurrences of double-f "?", which are actually represented by non-ascii characters.  (This may or may not show up in this email for your amusement.) Luckily, these do not occur in the URIs, as far as I have been able to see... that would be a problem. For future publications, is there some control over "kerning" to prevent this?  I think we can live with it, but it's an interesting element which could cause problems in some situations. Best regards, Paul On Mon, Dec 23, 2013 at 12:16 PM, Paul Knight < paul.knight@oasis-open.org > wrote: Thanks, Rusty -- this looks good. We'll move the individual footnote files in the HTML format into a subdirectory for publication. Best regards, Paul On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell < rusty@au1.ibm.com > wrote: Paul Knight < paul.knight@oasis-open.org > writes: > Hi Rusty and all, > > I've just taken a good look at the virtio files for publication, and they > will need a few additional modifications to the front pages. > > Although the TC Process does not allow changes to the document content > after approval, the front pages (down through the table of contents) may be > modified without any need for the TC to re-approve anything. > > I'm attaching a ZIP file containing examples of the front pages for both > the Committee Specification Draft 01 (csd01) and the Public Review Draft 01 > (csprd01) EXACTLY as they should appear, and I'll list the needed changes > below. > > We should be ready to publish the files and begin the Public Review quickly > after we receive the updated files. They should be sent to me and Chet. > > Changes needed to the csd01 files: > - Subtitle needs to include the csd number "01", so it will be Committee > Specification Draft 01 Done. > - Citation format needs to include the csd number "01", and also the word > "OASIS" before - so it will be OASIS Committee Specification Draft 01. Done. > - It also needs a period after the "01", and also at the end, after the URI. Done. > Please see the attached example, and follow it exactly. In addition, I added a horizontal rule above the Notices section in the html, as your example had. > Changes needed to the csprd01 files: > - Subtitle needs to be:  (on two lines) > Committee Specification Draft 01 / > Public Review Draft 01 Done. > - Date needs to be 03 December 2013 - in three places - subtitle, citation > format, and footers (it now says 04 December) Damn, that's entirely my fault; I updated the respitory and regenerated.  Fixed. > - Citation format needs to show "OASIS Committee Specification Draft 01 / > Public Review Draft 01".  It also needs a period after the (second) "01", > and also at the end, after the URI. > Again, please see the attached examples. Yep, fixed too. These fixes have all been committed to the repository, so hopefully the next time we generate a draft it will be flawless. Attached below. > Finally, there is an issue which I don't think we can address for > csd01/csprd01 (without re-approval by the TC), but which I very much hope > can be addressed in future publications: > - The 18 footnotes each appear as individual HTML files, leading to a > terrible clutter in the publication directory. We'd like to see if they can > either be included in the main HTML file (typically at the end of the file) > or if this can't be arranged, then in a "footnotes" subdirectory. Hmm, I'll have to dig deeper to see if I can do that. > Although Chet is on vacation now, I'll also check with him to see if we (TC > Administration) can apply the "subdirectory" fix to these files during > publication.  It may qualify as an allowable style modification. Thanks, Rusty. > Best regards, > Paul > -- > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

Paul, what's the status of the draft? It's been a month since the committee approved it, and you previously said the ligatures fix can wait until draft 2. Thanks, Rusty. Paul Knight <paul.knight@oasis-open.org> writes: > A bit of follow-up on the "fi" and "ff" issue: > > - first, I see that the TC (?) apparently ran into the issue and introduced > a workaround in the file /tex/makehtml.sh > > #For some unclear reason we get 'fi' replaced by NULL character > #on Fedora. file recognizes result as a binary data. > > > - second, for what it's worth, a bit of information which indicates that > there may be a way to shut it off in TeX: > > "TeX < http://en.wikipedia.org/wiki/TeX > is an example of a computer > typesetting system that makes use of ligatures automatically. The Computer > Modern Roman < http://en.wikipedia.org/wiki/Computer_Modern > typeface > provided with TeX includes the five common ligatures *ff*, *fi*, *fl*, *ffi*, > and *ffl*. When TeX finds these combinations in a text it substitutes the > appropriate ligature, **unless overridden by the typesetter.**" [1] > > [1] http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting > > This isn't an area where I can likely be of much help other than to wish > you luck... > > Best regards, > Paul > > > On Mon, Dec 23, 2013 at 4:38 PM, Paul Knight <paul.knight@oasis-open.org>wrote: > >> Hi Rusty and all, >> >> An interesting item, which I don't think will affect publication, shows up >> in the HTML versions of the documents: >> >> It is probably related to kerning with the LaTex system: >> >> There are combined letters "?" (as opposed to the individual letters >> "fi")in the word "Speci?cation" on the front page and elsewhere, and >> various occurrences of double-f "?", which are actually represented by >> non-ascii characters. (This may or may not show up in this email for your >> amusement.) >> >> Luckily, these do not occur in the URIs, as far as I have been able to >> see... that would be a problem. >> >> For future publications, is there some control over "kerning" to prevent >> this? I think we can live with it, but it's an interesting element which >> could cause problems in some situations. >> >> Best regards, >> Paul >> >> >> On Mon, Dec 23, 2013 at 12:16 PM, Paul Knight <paul.knight@oasis-open.org>wrote: >> >>> Thanks, Rusty -- this looks good. >>> >>> We'll move the individual footnote files in the HTML format into a >>> subdirectory for publication. >>> >>> Best regards, >>> Paul >>> >>> >>> On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell <rusty@au1.ibm.com>wrote: >>> >>>> Paul Knight <paul.knight@oasis-open.org> writes: >>>> > Hi Rusty and all, >>>> > >>>> > I've just taken a good look at the virtio files for publication, and >>>> they >>>> > will need a few additional modifications to the front pages. >>>> > >>>> > Although the TC Process does not allow changes to the document content >>>> > after approval, the front pages (down through the table of contents) >>>> may be >>>> > modified without any need for the TC to re-approve anything. >>>> > >>>> > I'm attaching a ZIP file containing examples of the front pages for >>>> both >>>> > the Committee Specification Draft 01 (csd01) and the Public Review >>>> Draft 01 >>>> > (csprd01) EXACTLY as they should appear, and I'll list the needed >>>> changes >>>> > below. >>>> > >>>> > We should be ready to publish the files and begin the Public Review >>>> quickly >>>> > after we receive the updated files. They should be sent to me and Chet. >>>> > >>>> > Changes needed to the csd01 files: >>>> > - Subtitle needs to include the csd number "01", so it will be >>>> Committee >>>> > Specification Draft 01 >>>> >>>> Done. >>>> >>>> > - Citation format needs to include the csd number "01", and also the >>>> word >>>> > "OASIS" before - so it will be OASIS Committee Specification Draft 01. >>>> >>>> Done. >>>> >>>> > - It also needs a period after the "01", and also at the end, after >>>> the URI. >>>> >>>> Done. >>>> >>>> > Please see the attached example, and follow it exactly. >>>> >>>> In addition, I added a horizontal rule above the Notices section in the >>>> html, as your example had. >>>> >>>> > Changes needed to the csprd01 files: >>>> > - Subtitle needs to be: (on two lines) >>>> > Committee Specification Draft 01 / >>>> > Public Review Draft 01 >>>> >>>> Done. >>>> >>>> > - Date needs to be 03 December 2013 - in three places - subtitle, >>>> citation >>>> > format, and footers (it now says 04 December) >>>> >>>> Damn, that's entirely my fault; I updated the respitory and >>>> regenerated. Fixed. >>>> >>>> > - Citation format needs to show "OASIS Committee Specification Draft >>>> 01 / >>>> > Public Review Draft 01". It also needs a period after the (second) >>>> "01", >>>> > and also at the end, after the URI. >>>> > Again, please see the attached examples. >>>> >>>> Yep, fixed too. >>>> >>>> These fixes have all been committed to the repository, so hopefully the >>>> next time we generate a draft it will be flawless. >>>> >>>> Attached below. >>>> >>>> > Finally, there is an issue which I don't think we can address for >>>> > csd01/csprd01 (without re-approval by the TC), but which I very much >>>> hope >>>> > can be addressed in future publications: >>>> > - The 18 footnotes each appear as individual HTML files, leading to a >>>> > terrible clutter in the publication directory. We'd like to see if >>>> they can >>>> > either be included in the main HTML file (typically at the end of the >>>> file) >>>> > or if this can't be arranged, then in a "footnotes" subdirectory. >>>> >>>> Hmm, I'll have to dig deeper to see if I can do that. >>>> >>>> > Although Chet is on vacation now, I'll also check with him to see if >>>> we (TC >>>> > Administration) can apply the "subdirectory" fix to these files during >>>> > publication. It may qualify as an allowable style modification. >>>> >>>> Thanks, >>>> Rusty. >>>> >>>> > Best regards, >>>> > Paul >>>> > -- >>>> > Paul Knight <paul.knight@oasis-open.org> - Tel: +1 781-861-1013 >>>> > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>>> > information society >>>> > Document Process Analyst< >>>> http://www.oasis-open.org/people/staff/paul-knight > >>>> >>>> >>> >>> >>> -- >>> Paul Knight <paul.knight@oasis-open.org> - Tel: +1 781-861-1013 >>> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>> information society >>> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >>> >>> >> >> >> -- >> Paul Knight <paul.knight@oasis-open.org> - Tel: +1 781-861-1013 >> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >> information society >> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >> >> > > > -- > Paul Knight <paul.knight@oasis-open.org> - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight >

Hi Rusty,  Paul is prepping Virtio now. We had an unusually large number of tickets to work through in December plus, of course, the Christmas/New Year's holiday. But Virtio is up now and should be done this week.  You can see the queue of tickets at  https://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&pid=10010&status=1   Best,  /chet  On Tue, Jan 7, 2014 at 1:07 AM, Rusty Russell < rusty@au1.ibm.com > wrote: Paul, what's the status of the draft? It's been a month since the committee approved it, and you previously said the ligatures fix can wait until draft 2. Thanks, Rusty. Paul Knight < paul.knight@oasis-open.org > writes: > A bit of follow-up on the "fi" and "ff" issue: > > - first, I see that the TC (?) apparently ran into the issue and introduced > a workaround in the file /tex/makehtml.sh > > #For some unclear reason we get 'fi' replaced by NULL character > #on Fedora. file recognizes result as a binary data. > > > - second, for what it's worth, a bit of information which indicates that > there may be a way to shut it off in TeX: > > "TeX < http://en.wikipedia.org/wiki/TeX > is an example of a computer > typesetting system that makes use of ligatures automatically. The Computer > Modern Roman < http://en.wikipedia.org/wiki/Computer_Modern > typeface > provided with TeX includes the five common ligatures *ff*, *fi*, *fl*, *ffi*, > and *ffl*. When TeX finds these combinations in a text it substitutes the > appropriate ligature, **unless overridden by the typesetter.**" [1] > > [1] http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting > > This isn't an area where I can likely be of much help other than to wish > you luck... > > Best regards, > Paul > > > On Mon, Dec 23, 2013 at 4:38 PM, Paul Knight < paul.knight@oasis-open.org >wrote: > >> Hi Rusty and all, >> >> An interesting item, which I don't think will affect publication, shows up >> in the HTML versions of the documents: >> >> It is probably related to kerning with the LaTex system: >> >> There are combined letters "?" (as opposed to the individual letters >> "fi")in the word "Speci?cation" on the front page and elsewhere, and >> various occurrences of double-f "?", which are actually represented by >> non-ascii characters.  (This may or may not show up in this email for your >> amusement.) >> >> Luckily, these do not occur in the URIs, as far as I have been able to >> see... that would be a problem. >> >> For future publications, is there some control over "kerning" to prevent >> this?  I think we can live with it, but it's an interesting element which >> could cause problems in some situations. >> >> Best regards, >> Paul >> >> >> On Mon, Dec 23, 2013 at 12:16 PM, Paul Knight < paul.knight@oasis-open.org >wrote: >> >>> Thanks, Rusty -- this looks good. >>> >>> We'll move the individual footnote files in the HTML format into a >>> subdirectory for publication. >>> >>> Best regards, >>> Paul >>> >>> >>> On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell < rusty@au1.ibm.com >wrote: >>> >>>> Paul Knight < paul.knight@oasis-open.org > writes: >>>> > Hi Rusty and all, >>>> > >>>> > I've just taken a good look at the virtio files for publication, and >>>> they >>>> > will need a few additional modifications to the front pages. >>>> > >>>> > Although the TC Process does not allow changes to the document content >>>> > after approval, the front pages (down through the table of contents) >>>> may be >>>> > modified without any need for the TC to re-approve anything. >>>> > >>>> > I'm attaching a ZIP file containing examples of the front pages for >>>> both >>>> > the Committee Specification Draft 01 (csd01) and the Public Review >>>> Draft 01 >>>> > (csprd01) EXACTLY as they should appear, and I'll list the needed >>>> changes >>>> > below. >>>> > >>>> > We should be ready to publish the files and begin the Public Review >>>> quickly >>>> > after we receive the updated files. They should be sent to me and Chet. >>>> > >>>> > Changes needed to the csd01 files: >>>> > - Subtitle needs to include the csd number "01", so it will be >>>> Committee >>>> > Specification Draft 01 >>>> >>>> Done. >>>> >>>> > - Citation format needs to include the csd number "01", and also the >>>> word >>>> > "OASIS" before - so it will be OASIS Committee Specification Draft 01. >>>> >>>> Done. >>>> >>>> > - It also needs a period after the "01", and also at the end, after >>>> the URI. >>>> >>>> Done. >>>> >>>> > Please see the attached example, and follow it exactly. >>>> >>>> In addition, I added a horizontal rule above the Notices section in the >>>> html, as your example had. >>>> >>>> > Changes needed to the csprd01 files: >>>> > - Subtitle needs to be:  (on two lines) >>>> > Committee Specification Draft 01 / >>>> > Public Review Draft 01 >>>> >>>> Done. >>>> >>>> > - Date needs to be 03 December 2013 - in three places - subtitle, >>>> citation >>>> > format, and footers (it now says 04 December) >>>> >>>> Damn, that's entirely my fault; I updated the respitory and >>>> regenerated.  Fixed. >>>> >>>> > - Citation format needs to show "OASIS Committee Specification Draft >>>> 01 / >>>> > Public Review Draft 01".  It also needs a period after the (second) >>>> "01", >>>> > and also at the end, after the URI. >>>> > Again, please see the attached examples. >>>> >>>> Yep, fixed too. >>>> >>>> These fixes have all been committed to the repository, so hopefully the >>>> next time we generate a draft it will be flawless. >>>> >>>> Attached below. >>>> >>>> > Finally, there is an issue which I don't think we can address for >>>> > csd01/csprd01 (without re-approval by the TC), but which I very much >>>> hope >>>> > can be addressed in future publications: >>>> > - The 18 footnotes each appear as individual HTML files, leading to a >>>> > terrible clutter in the publication directory. We'd like to see if >>>> they can >>>> > either be included in the main HTML file (typically at the end of the >>>> file) >>>> > or if this can't be arranged, then in a "footnotes" subdirectory. >>>> >>>> Hmm, I'll have to dig deeper to see if I can do that. >>>> >>>> > Although Chet is on vacation now, I'll also check with him to see if >>>> we (TC >>>> > Administration) can apply the "subdirectory" fix to these files during >>>> > publication.  It may qualify as an allowable style modification. >>>> >>>> Thanks, >>>> Rusty. >>>> >>>> > Best regards, >>>> > Paul >>>> > -- >>>> > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >>>> > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>>> > information society >>>> > Document Process Analyst< >>>> http://www.oasis-open.org/people/staff/paul-knight > >>>> >>>> >>> >>> >>> -- >>> Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >>> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>> information society >>> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >>> >>> >> >> >> -- >> Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >> information society >> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >> >> > > > -- > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Hi Rusty, Welcome back from vacation everyone! Virtio was published just BEFORE Christmas, on December 24. Subject :  30-day Public Review for Virtual I/O Device (VIRTIO) Version 1.0 From :  Paul Knight < paul.knight@oasis-open.org > To : members@lists.oasis-open.org , virtio@lists.oasis-open.org , tc-announce@lists.oasis-open.org , virtualization@lists.linux-foundation.org , freebsd-virtualization@freebsd.org , qemu-devel@nongnu.org , xen-devel@lists.xenproject.org Date : Tue, 24 Dec 2013 14:14:55 -0500 The Public Review was announced as extending to the end of January. You may want to forward the announcement around again if you think that potential reviewers might have missed the message, since it was just before the holidays. It was announced to the TC mailing list at: https://lists.oasis-open.org/archives/virtio/201312/msg00126.html , with an additional followup message  (please read it, since it describes how the TC needs to handle each comment!) later that day: https://lists.oasis-open.org/archives/virtio/201312/msg00127.html , as well as another message from Chet on December 26  ( https://lists.oasis-open.org/archives/virtio/201312/msg00129.html ) to let the TC know that he had added an announcement to the OASIS web site at https://www.oasis-open.org/news/announcements/30-day-public-review-for-virtual-i-o-device-virtio-v1-0 and posted a notice in the OASIS LinkedIn group. Please let me and Chet know if you have any questions about the Public Review process, such as typical methods of acknowledging and tracking all PR comments. Best regards, Paul On Tue, Jan 7, 2014 at 1:07 AM, Rusty Russell < rusty@au1.ibm.com > wrote: Paul, what's the status of the draft? It's been a month since the committee approved it, and you previously said the ligatures fix can wait until draft 2. Thanks, Rusty. Paul Knight < paul.knight@oasis-open.org > writes: > A bit of follow-up on the "fi" and "ff" issue: > > - first, I see that the TC (?) apparently ran into the issue and introduced > a workaround in the file /tex/makehtml.sh > > #For some unclear reason we get 'fi' replaced by NULL character > #on Fedora. file recognizes result as a binary data. > > > - second, for what it's worth, a bit of information which indicates that > there may be a way to shut it off in TeX: > > "TeX < http://en.wikipedia.org/wiki/TeX > is an example of a computer > typesetting system that makes use of ligatures automatically. The Computer > Modern Roman < http://en.wikipedia.org/wiki/Computer_Modern > typeface > provided with TeX includes the five common ligatures *ff*, *fi*, *fl*, *ffi*, > and *ffl*. When TeX finds these combinations in a text it substitutes the > appropriate ligature, **unless overridden by the typesetter.**" [1] > > [1] http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting > > This isn't an area where I can likely be of much help other than to wish > you luck... > > Best regards, > Paul > > > On Mon, Dec 23, 2013 at 4:38 PM, Paul Knight < paul.knight@oasis-open.org >wrote: > >> Hi Rusty and all, >> >> An interesting item, which I don't think will affect publication, shows up >> in the HTML versions of the documents: >> >> It is probably related to kerning with the LaTex system: >> >> There are combined letters "?" (as opposed to the individual letters >> "fi")in the word "Speci?cation" on the front page and elsewhere, and >> various occurrences of double-f "?", which are actually represented by >> non-ascii characters.  (This may or may not show up in this email for your >> amusement.) >> >> Luckily, these do not occur in the URIs, as far as I have been able to >> see... that would be a problem. >> >> For future publications, is there some control over "kerning" to prevent >> this?  I think we can live with it, but it's an interesting element which >> could cause problems in some situations. >> >> Best regards, >> Paul >> >> >> On Mon, Dec 23, 2013 at 12:16 PM, Paul Knight < paul.knight@oasis-open.org >wrote: >> >>> Thanks, Rusty -- this looks good. >>> >>> We'll move the individual footnote files in the HTML format into a >>> subdirectory for publication. >>> >>> Best regards, >>> Paul >>> >>> >>> On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell < rusty@au1.ibm.com >wrote: >>> >>>> Paul Knight < paul.knight@oasis-open.org > writes: >>>> > Hi Rusty and all, >>>> > >>>> > I've just taken a good look at the virtio files for publication, and >>>> they >>>> > will need a few additional modifications to the front pages. >>>> > >>>> > Although the TC Process does not allow changes to the document content >>>> > after approval, the front pages (down through the table of contents) >>>> may be >>>> > modified without any need for the TC to re-approve anything. >>>> > >>>> > I'm attaching a ZIP file containing examples of the front pages for >>>> both >>>> > the Committee Specification Draft 01 (csd01) and the Public Review >>>> Draft 01 >>>> > (csprd01) EXACTLY as they should appear, and I'll list the needed >>>> changes >>>> > below. >>>> > >>>> > We should be ready to publish the files and begin the Public Review >>>> quickly >>>> > after we receive the updated files. They should be sent to me and Chet. >>>> > >>>> > Changes needed to the csd01 files: >>>> > - Subtitle needs to include the csd number "01", so it will be >>>> Committee >>>> > Specification Draft 01 >>>> >>>> Done. >>>> >>>> > - Citation format needs to include the csd number "01", and also the >>>> word >>>> > "OASIS" before - so it will be OASIS Committee Specification Draft 01. >>>> >>>> Done. >>>> >>>> > - It also needs a period after the "01", and also at the end, after >>>> the URI. >>>> >>>> Done. >>>> >>>> > Please see the attached example, and follow it exactly. >>>> >>>> In addition, I added a horizontal rule above the Notices section in the >>>> html, as your example had. >>>> >>>> > Changes needed to the csprd01 files: >>>> > - Subtitle needs to be:  (on two lines) >>>> > Committee Specification Draft 01 / >>>> > Public Review Draft 01 >>>> >>>> Done. >>>> >>>> > - Date needs to be 03 December 2013 - in three places - subtitle, >>>> citation >>>> > format, and footers (it now says 04 December) >>>> >>>> Damn, that's entirely my fault; I updated the respitory and >>>> regenerated.  Fixed. >>>> >>>> > - Citation format needs to show "OASIS Committee Specification Draft >>>> 01 / >>>> > Public Review Draft 01".  It also needs a period after the (second) >>>> "01", >>>> > and also at the end, after the URI. >>>> > Again, please see the attached examples. >>>> >>>> Yep, fixed too. >>>> >>>> These fixes have all been committed to the repository, so hopefully the >>>> next time we generate a draft it will be flawless. >>>> >>>> Attached below. >>>> >>>> > Finally, there is an issue which I don't think we can address for >>>> > csd01/csprd01 (without re-approval by the TC), but which I very much >>>> hope >>>> > can be addressed in future publications: >>>> > - The 18 footnotes each appear as individual HTML files, leading to a >>>> > terrible clutter in the publication directory. We'd like to see if >>>> they can >>>> > either be included in the main HTML file (typically at the end of the >>>> file) >>>> > or if this can't be arranged, then in a "footnotes" subdirectory. >>>> >>>> Hmm, I'll have to dig deeper to see if I can do that. >>>> >>>> > Although Chet is on vacation now, I'll also check with him to see if >>>> we (TC >>>> > Administration) can apply the "subdirectory" fix to these files during >>>> > publication.  It may qualify as an allowable style modification. >>>> >>>> Thanks, >>>> Rusty. >>>> >>>> > Best regards, >>>> > Paul >>>> > -- >>>> > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >>>> > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>>> > information society >>>> > Document Process Analyst< >>>> http://www.oasis-open.org/people/staff/paul-knight > >>>> >>>> >>> >>> >>> -- >>> Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >>> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>> information society >>> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >>> >>> >> >> >> -- >> Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >> information society >> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >> >> > > > -- > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

Paul, thanks - I missed that. I'll post the other announcements...  /chet On Tue, Jan 7, 2014 at 10:03 AM, Paul Knight < paul.knight@oasis-open.org > wrote: Hi Rusty, Welcome back from vacation everyone! Virtio was published just BEFORE Christmas, on December 24. Subject :  30-day Public Review for Virtual I/O Device (VIRTIO) Version 1.0 From :  Paul Knight < paul.knight@oasis-open.org > To : members@lists.oasis-open.org , virtio@lists.oasis-open.org , tc-announce@lists.oasis-open.org , virtualization@lists.linux-foundation.org , freebsd-virtualization@freebsd.org , qemu-devel@nongnu.org , xen-devel@lists.xenproject.org Date : Tue, 24 Dec 2013 14:14:55 -0500 The Public Review was announced as extending to the end of January. You may want to forward the announcement around again if you think that potential reviewers might have missed the message, since it was just before the holidays. It was announced to the TC mailing list at: https://lists.oasis-open.org/archives/virtio/201312/msg00126.html , with an additional followup message  (please read it, since it describes how the TC needs to handle each comment!) later that day: https://lists.oasis-open.org/archives/virtio/201312/msg00127.html , as well as another message from Chet on December 26  ( https://lists.oasis-open.org/archives/virtio/201312/msg00129.html ) to let the TC know that he had added an announcement to the OASIS web site at https://www.oasis-open.org/news/announcements/30-day-public-review-for-virtual-i-o-device-virtio-v1-0 and posted a notice in the OASIS LinkedIn group. Please let me and Chet know if you have any questions about the Public Review process, such as typical methods of acknowledging and tracking all PR comments. Best regards, Paul On Tue, Jan 7, 2014 at 1:07 AM, Rusty Russell < rusty@au1.ibm.com > wrote: Paul, what's the status of the draft? It's been a month since the committee approved it, and you previously said the ligatures fix can wait until draft 2. Thanks, Rusty. Paul Knight < paul.knight@oasis-open.org > writes: > A bit of follow-up on the "fi" and "ff" issue: > > - first, I see that the TC (?) apparently ran into the issue and introduced > a workaround in the file /tex/makehtml.sh > > #For some unclear reason we get 'fi' replaced by NULL character > #on Fedora. file recognizes result as a binary data. > > > - second, for what it's worth, a bit of information which indicates that > there may be a way to shut it off in TeX: > > "TeX < http://en.wikipedia.org/wiki/TeX > is an example of a computer > typesetting system that makes use of ligatures automatically. The Computer > Modern Roman < http://en.wikipedia.org/wiki/Computer_Modern > typeface > provided with TeX includes the five common ligatures *ff*, *fi*, *fl*, *ffi*, > and *ffl*. When TeX finds these combinations in a text it substitutes the > appropriate ligature, **unless overridden by the typesetter.**" [1] > > [1] http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting > > This isn't an area where I can likely be of much help other than to wish > you luck... > > Best regards, > Paul > > > On Mon, Dec 23, 2013 at 4:38 PM, Paul Knight < paul.knight@oasis-open.org >wrote: > >> Hi Rusty and all, >> >> An interesting item, which I don't think will affect publication, shows up >> in the HTML versions of the documents: >> >> It is probably related to kerning with the LaTex system: >> >> There are combined letters "?" (as opposed to the individual letters >> "fi")in the word "Speci?cation" on the front page and elsewhere, and >> various occurrences of double-f "?", which are actually represented by >> non-ascii characters.  (This may or may not show up in this email for your >> amusement.) >> >> Luckily, these do not occur in the URIs, as far as I have been able to >> see... that would be a problem. >> >> For future publications, is there some control over "kerning" to prevent >> this?  I think we can live with it, but it's an interesting element which >> could cause problems in some situations. >> >> Best regards, >> Paul >> >> >> On Mon, Dec 23, 2013 at 12:16 PM, Paul Knight < paul.knight@oasis-open.org >wrote: >> >>> Thanks, Rusty -- this looks good. >>> >>> We'll move the individual footnote files in the HTML format into a >>> subdirectory for publication. >>> >>> Best regards, >>> Paul >>> >>> >>> On Fri, Dec 20, 2013 at 10:54 PM, Rusty Russell < rusty@au1.ibm.com >wrote: >>> >>>> Paul Knight < paul.knight@oasis-open.org > writes: >>>> > Hi Rusty and all, >>>> > >>>> > I've just taken a good look at the virtio files for publication, and >>>> they >>>> > will need a few additional modifications to the front pages. >>>> > >>>> > Although the TC Process does not allow changes to the document content >>>> > after approval, the front pages (down through the table of contents) >>>> may be >>>> > modified without any need for the TC to re-approve anything. >>>> > >>>> > I'm attaching a ZIP file containing examples of the front pages for >>>> both >>>> > the Committee Specification Draft 01 (csd01) and the Public Review >>>> Draft 01 >>>> > (csprd01) EXACTLY as they should appear, and I'll list the needed >>>> changes >>>> > below. >>>> > >>>> > We should be ready to publish the files and begin the Public Review >>>> quickly >>>> > after we receive the updated files. They should be sent to me and Chet. >>>> > >>>> > Changes needed to the csd01 files: >>>> > - Subtitle needs to include the csd number "01", so it will be >>>> Committee >>>> > Specification Draft 01 >>>> >>>> Done. >>>> >>>> > - Citation format needs to include the csd number "01", and also the >>>> word >>>> > "OASIS" before - so it will be OASIS Committee Specification Draft 01. >>>> >>>> Done. >>>> >>>> > - It also needs a period after the "01", and also at the end, after >>>> the URI. >>>> >>>> Done. >>>> >>>> > Please see the attached example, and follow it exactly. >>>> >>>> In addition, I added a horizontal rule above the Notices section in the >>>> html, as your example had. >>>> >>>> > Changes needed to the csprd01 files: >>>> > - Subtitle needs to be:  (on two lines) >>>> > Committee Specification Draft 01 / >>>> > Public Review Draft 01 >>>> >>>> Done. >>>> >>>> > - Date needs to be 03 December 2013 - in three places - subtitle, >>>> citation >>>> > format, and footers (it now says 04 December) >>>> >>>> Damn, that's entirely my fault; I updated the respitory and >>>> regenerated.  Fixed. >>>> >>>> > - Citation format needs to show "OASIS Committee Specification Draft >>>> 01 / >>>> > Public Review Draft 01".  It also needs a period after the (second) >>>> "01", >>>> > and also at the end, after the URI. >>>> > Again, please see the attached examples. >>>> >>>> Yep, fixed too. >>>> >>>> These fixes have all been committed to the repository, so hopefully the >>>> next time we generate a draft it will be flawless. >>>> >>>> Attached below. >>>> >>>> > Finally, there is an issue which I don't think we can address for >>>> > csd01/csprd01 (without re-approval by the TC), but which I very much >>>> hope >>>> > can be addressed in future publications: >>>> > - The 18 footnotes each appear as individual HTML files, leading to a >>>> > terrible clutter in the publication directory. We'd like to see if >>>> they can >>>> > either be included in the main HTML file (typically at the end of the >>>> file) >>>> > or if this can't be arranged, then in a "footnotes" subdirectory. >>>> >>>> Hmm, I'll have to dig deeper to see if I can do that. >>>> >>>> > Although Chet is on vacation now, I'll also check with him to see if >>>> we (TC >>>> > Administration) can apply the "subdirectory" fix to these files during >>>> > publication.  It may qualify as an allowable style modification. >>>> >>>> Thanks, >>>> Rusty. >>>> >>>> > Best regards, >>>> > Paul >>>> > -- >>>> > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >>>> > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>>> > information society >>>> > Document Process Analyst< >>>> http://www.oasis-open.org/people/staff/paul-knight > >>>> >>>> >>> >>> >>> -- >>> Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >>> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >>> information society >>> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >>> >>> >> >> >> -- >> Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 >> OASIS < http://www.oasis-open.org/ > - Advancing open standards for the >> information society >> Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > >> >> > > > -- > Paul Knight < paul.knight@oasis-open.org >  - Tel: +1 781-861-1013 > OASIS < http://www.oasis-open.org/ > - Advancing open standards for the > information society > Document Process Analyst< http://www.oasis-open.org/people/staff/paul-knight > -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Paul Knight <paul.knight@oasis-open.org> writes: > Hi Rusty, > > Welcome back from vacation everyone! > > Virtio was published just BEFORE Christmas, on December 24. Oops! Thanks, I missed that somehow in my email catchup. Excellent work. Cheers, Rusty.

On Mon, Dec 23, 2013 at 06:12:11PM -0500, Paul Knight wrote: > A bit of follow-up on the "fi" and "ff" issue: > > - first, I see that the TC (?) apparently ran into the issue and introduced a > workaround in the file /tex/makehtml.sh > > #For some unclear reason we get 'fi' replaced by NULL character > #on Fedora. file recognizes result as a binary data. > > > - second, for what it's worth, a bit of information which indicates that there > may be a way to shut it off in TeX: > > "TeX is an example of a computer typesetting system that makes use of ligatures > automatically. The Computer Modern Roman typeface provided with TeX includes > the five common ligatures ff, fi, fl, ffi, and ffl. When TeX finds these > combinations in a text it substitutes the appropriate ligature, **unless > overridden by the typesetter.**" [1] > > [1]  http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting > > This isn't an area where I can likely be of much help other than to wish you > luck... > > Best regards, > Paul Do we still have this issue? I don't see the problem in the pdf here: https://www.oasis-open.org/news/announcements/30-day-public-review-for-virtual-i-o-device-virtio-v1-0 words like specification and offset all appear fine now.

Hi Michael and all, I believe that the PDF is fine, but the HTML contains the non-ascii representations of ligatures, instead of the characters "fi" and "ff". Although most users would not notice it, I remember having it cause some issues in my processing stream, in particular a step in which I copy the phrase "Committee Specification Draft 01" from the HTML document to an environment variable for generating things like the manifest file, etc. If it can be avoided by setting something in the production environment, that would be helpful.  Best regards, Paul On Thu, Jan 9, 2014 at 12:06 PM, Michael S. Tsirkin < mst@redhat.com > wrote: On Mon, Dec 23, 2013 at 06:12:11PM -0500, Paul Knight wrote: > A bit of follow-up on the "fi" and "ff" issue: > > - first, I see that the TC (?) apparently ran into the issue and introduced a > workaround in the file /tex/makehtml.sh > >     #For some unclear reason we get 'fi' replaced by NULL character >     #on Fedora. file recognizes result as a binary data. > > > - second, for what it's worth, a bit of information which indicates that there > may be a way to shut it off in TeX: > > "TeX is an example of a computer typesetting system that makes use of ligatures > automatically. The Computer Modern Roman typeface provided with TeX includes > the five common ligatures ff, fi, fl, ffi, and ffl. When TeX finds these > combinations in a text it substitutes the appropriate ligature, **unless > overridden by the typesetter.**" [1] > > [1]  http://en.wikipedia.org/wiki/Typographic_ligature#Computer_typesetting > > This isn't an area where I can likely be of much help other than to wish you > luck... > > Best regards, > Paul Do we still have this issue? I don't see the problem in the pdf here: https://www.oasis-open.org/news/announcements/30-day-public-review-for-virtual-i-o-device-virtio-v1-0 words like specification and offset all appear fine now. -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

On Thu, Jan 09, 2014 at 12:27:29PM -0500, Paul Knight wrote: > Hi Michael and all, > > I believe that the PDF is fine, but the HTML contains the non-ascii > representations of ligatures, instead of the characters "fi" and "ff". Yes, html seems problematic. I didn't find a nice way to disable this for HTML yet. Worst case we'll do a post-processing step and change these back to ascii for draft 2. > Although most users would not notice it, I remember having it cause some issues > in my processing stream, in particular a step in which I copy the phrase > "Committee Specification Draft 01" from the HTML document to an environment > variable for generating things like the manifest file, etc. > > If it can be avoided by setting something in the production environment, that > would be helpful.  > > Best regards, > Paul > > > On Thu, Jan 9, 2014 at 12:06 PM, Michael S. Tsirkin <mst@redhat.com> wrote: > > On Mon, Dec 23, 2013 at 06:12:11PM -0500, Paul Knight wrote: > > A bit of follow-up on the "fi" and "ff" issue: > > > > - first, I see that the TC (?) apparently ran into the issue and > introduced a > > workaround in the file /tex/makehtml.sh > > > >     #For some unclear reason we get 'fi' replaced by NULL character > >     #on Fedora. file recognizes result as a binary data. > > > > > > - second, for what it's worth, a bit of information which indicates that > there > > may be a way to shut it off in TeX: > > > > "TeX is an example of a computer typesetting system that makes use of > ligatures > > automatically. The Computer Modern Roman typeface provided with TeX > includes > > the five common ligatures ff, fi, fl, ffi, and ffl. When TeX finds these > > combinations in a text it substitutes the appropriate ligature, **unless > > overridden by the typesetter.**" [1] > > > > [1]  http://en.wikipedia.org/wiki/Typographic_ligature# > Computer_typesetting > > > > This isn't an area where I can likely be of much help other than to wish > you > > luck... > > > > Best regards, > > Paul > > Do we still have this issue? > I don't see the problem in the pdf here: > https://www.oasis-open.org/news/announcements/ > 30-day-public-review-for-virtual-i-o-device-virtio-v1-0 > words like specification and offset all appear fine now. > > > > > > -- > Paul Knight  - Tel: +1 781-861-1013 > OASIS - Advancing open standards for the information society > Document Process Analyst >

On Thu, 2014-01-09 at 18:02 +0000, Michael S. Tsirkin wrote: > On Thu, Jan 09, 2014 at 12:27:29PM -0500, Paul Knight wrote: > > Hi Michael and all, > > > > I believe that the PDF is fine, but the HTML contains the non-ascii > > representations of ligatures, instead of the characters "fi" and "ff". > > Yes, html seems problematic. > I didn't find a nice way to disable this for HTML yet. Give this one a try: 8<--------------

On Thu, Jan 09, 2014 at 06:37:07PM +0000, Pawel Moll wrote: > On Thu, 2014-01-09 at 18:02 +0000, Michael S. Tsirkin wrote: > > On Thu, Jan 09, 2014 at 12:27:29PM -0500, Paul Knight wrote: > > > Hi Michael and all, > > > > > > I believe that the PDF is fine, but the HTML contains the non-ascii > > > representations of ligatures, instead of the characters "fi" and "ff". > > > > Yes, html seems problematic. > > I didn't find a nice way to disable this for HTML yet. > > Give this one a try: > > 8<-------------- > >From 36edea8583bd2b3a572101f3ea57aca25634dcfb Mon Sep 17 00:00:00 2001 > From: Pawel Moll <pawel.moll@arm.com> > Date: Thu, 9 Jan 2014 18:35:30 +0000 > Subject: [PATCH] html: Convert ligatures into normal ASCII characters > > Signed-off-by: Pawel Moll <pawel.moll@arm.com> > --- > unicode.4hf 5 +++++ > 1 file changed, 5 insertions(+) > create mode 100644 unicode.4hf > > diff --git a/unicode.4hf b/unicode.4hf > new file mode 100644 > index 0000000..b7e69b2 > --- /dev/null > +++ b/unicode.4hf > @@ -0,0 +1,5 @@ > +'&#xFB01;' '' 'fi' '' > +'&#xFB02;' '' 'fl' '' > +'&#xFB00;' '' 'ff' '' > +'&#xFB03;' '' 'ffi' '' > +'&#xFB04;' '' 'ffl' '' > -- > 1.8.3.2 > 8<-------------- > > Seems to work for me, although I don't know exactly why (I have a > feeling, but no proof ;-) > > Pawel Doesn't seem to work for me although the file is actually opened and read (checked with strace). Because of some broken-ness in Fedora htlatex replaces them with instead of proper unicode characters, that's probably why. Any idea how to debug that problem?

On Thu, Jan 09, 2014 at 06:37:07PM +0000, Pawel Moll wrote: > On Thu, 2014-01-09 at 18:02 +0000, Michael S. Tsirkin wrote: > > On Thu, Jan 09, 2014 at 12:27:29PM -0500, Paul Knight wrote: > > > Hi Michael and all, > > > > > > I believe that the PDF is fine, but the HTML contains the non-ascii > > > representations of ligatures, instead of the characters "fi" and "ff". > > > > Yes, html seems problematic. > > I didn't find a nice way to disable this for HTML yet. > > Give this one a try: > > 8<-------------- > >From 36edea8583bd2b3a572101f3ea57aca25634dcfb Mon Sep 17 00:00:00 2001 > From: Pawel Moll <pawel.moll@arm.com> > Date: Thu, 9 Jan 2014 18:35:30 +0000 > Subject: [PATCH] html: Convert ligatures into normal ASCII characters > > Signed-off-by: Pawel Moll <pawel.moll@arm.com> OK my issues turned out to be due to font paths being misconfigured. I figured it out and now your patch works. I checked it in, thanks a lot. Also added some documentation on possible tex4ht issues for people that might encounter them. > --- > unicode.4hf 5 +++++ > 1 file changed, 5 insertions(+) > create mode 100644 unicode.4hf > > diff --git a/unicode.4hf b/unicode.4hf > new file mode 100644 > index 0000000..b7e69b2 > --- /dev/null > +++ b/unicode.4hf > @@ -0,0 +1,5 @@ > +'&#xFB01;' '' 'fi' '' > +'&#xFB02;' '' 'fl' '' > +'&#xFB00;' '' 'ff' '' > +'&#xFB03;' '' 'ffi' '' > +'&#xFB04;' '' 'ffl' '' > -- > 1.8.3.2 > 8<-------------- > > Seems to work for me, although I don't know exactly why (I have a > feeling, but no proof ;-) > > Pawel > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

On Mon, 2013-12-23 at 16:38 -0500, Paul Knight wrote: > Hi Rusty and all, > > An interesting item, which I don't think will affect publication, shows up > in the HTML versions of the documents: > > It is probably related to kerning with the LaTex system: > > There are combined letters "?" (as opposed to the individual letters > "fi")in the word "Speci?cation" on the front page and elsewhere, and > various occurrences of double-f "?", which are actually represented by > non-ascii characters. (This may or may not show up in this email for your > amusement.) Ah, I'm afraid this is probably a Linux thing. We all use Linux and the characters above actually render correctly as ligatures in all our font systems. I suspect windows, not having the TeX/LaTeX heritage doesn't know what to do with them, but none of us proofreading would actually see the problem ... we probably need proofreader who actually uses windows to avoid other issues like this in future. > Luckily, these do not occur in the URIs, as far as I have been able to > see... that would be a problem. No, TeX won't use ligatures in URIs > For future publications, is there some control over "kerning" to prevent > this? I think we can live with it, but it's an interesting element which > could cause problems in some situations. Yes, we can turn it off entirely using the fontspec package. http://www.ctan.org/tex-archive/macros/xetex/latex/fontspec/ I think the command is defaultfontfeatures{Ligatures=NoCommon,NoRequired,NoRare} James

On Tue, Dec 24, 2013 at 08:10:36PM +0000, James Bottomley wrote: > On Mon, 2013-12-23 at 16:38 -0500, Paul Knight wrote: > > Hi Rusty and all, > > > > An interesting item, which I don't think will affect publication, shows up > > in the HTML versions of the documents: > > > > It is probably related to kerning with the LaTex system: > > > > There are combined letters "?" (as opposed to the individual letters > > "fi")in the word "Speci?cation" on the front page and elsewhere, and > > various occurrences of double-f "?", which are actually represented by > > non-ascii characters. (This may or may not show up in this email for your > > amusement.) > > Ah, I'm afraid this is probably a Linux thing. We all use Linux and the > characters above actually render correctly as ligatures in all our font > systems. I suspect windows, not having the TeX/LaTeX heritage doesn't > know what to do with them, but none of us proofreading would actually > see the problem ... we probably need proofreader who actually uses > windows to avoid other issues like this in future. > > > Luckily, these do not occur in the URIs, as far as I have been able to > > see... that would be a problem. > > No, TeX won't use ligatures in URIs > > > For future publications, is there some control over "kerning" to prevent > > this? I think we can live with it, but it's an interesting element which > > could cause problems in some situations. > > Yes, we can turn it off entirely using the fontspec package. > > http://www.ctan.org/tex-archive/macros/xetex/latex/fontspec/ > > I think the command is > > defaultfontfeatures{Ligatures=NoCommon,NoRequired,NoRare} > > James {} would be needed around a list: defaultfontfeatures{Ligatures={NoCommon,NoRequired,NoRare}} We would also need to drop Mapping=tex-text and maybe add NoContextual just in case. NoRare is off by default so should not be needed. But we do have this problem with htlatex and I don't know how to fix it properly yet.

On Thu, Jan 09, 2014 at 07:28:58PM +0200, Michael S. Tsirkin wrote: > On Tue, Dec 24, 2013 at 08:10:36PM +0000, James Bottomley wrote: > > On Mon, 2013-12-23 at 16:38 -0500, Paul Knight wrote: > > > Hi Rusty and all, > > > > > > An interesting item, which I don't think will affect publication, shows up > > > in the HTML versions of the documents: > > > > > > It is probably related to kerning with the LaTex system: > > > > > > There are combined letters "?" (as opposed to the individual letters > > > "fi")in the word "Speci?cation" on the front page and elsewhere, and > > > various occurrences of double-f "?", which are actually represented by > > > non-ascii characters. (This may or may not show up in this email for your > > > amusement.) > > > > Ah, I'm afraid this is probably a Linux thing. We all use Linux and the > > characters above actually render correctly as ligatures in all our font > > systems. I suspect windows, not having the TeX/LaTeX heritage doesn't > > know what to do with them, but none of us proofreading would actually > > see the problem ... we probably need proofreader who actually uses > > windows to avoid other issues like this in future. > > > > > Luckily, these do not occur in the URIs, as far as I have been able to > > > see... that would be a problem. > > > > No, TeX won't use ligatures in URIs > > > > > For future publications, is there some control over "kerning" to prevent > > > this? I think we can live with it, but it's an interesting element which > > > could cause problems in some situations. > > > > Yes, we can turn it off entirely using the fontspec package. > > > > http://www.ctan.org/tex-archive/macros/xetex/latex/fontspec/ > > > > I think the command is > > > > defaultfontfeatures{Ligatures=NoCommon,NoRequired,NoRare} > > > > James > > {} would be needed around a list: > > defaultfontfeatures{Ligatures={NoCommon,NoRequired,NoRare}} > > We would also need to drop Mapping=tex-text and maybe add NoContextual > just in case. NoRare is off by default so should not be needed. > > > But we do have this problem with htlatex and I don't know > how to fix it properly yet. > > this bug report seems to be related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=307647 but I don't understand what's suggested there.