-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proofing PDF #220
Comments
Please leave any comments about it here and I will include mark them up in the PDF. |
I read through it, and I didn't find any issues. I think it looks great. |
There are a few questions at the end that we need to address. |
I have found and left comments on the following so far:
I'll upload the final annotated PDF here before I submit it so that people can review the comments. |
I also never got @aktech to confirm the spelling of his name. |
Comments on questions at the end of the PDF:
Yes, these appear to be correct (from what I can tell, they are identical to the ones in our pdf, except US state names have been abbreviated).
These all look correct.
(TODO)
I do not know here. Perhaps @matthewturk can answer this. The automatically generated citation at http://iopscience.iop.org/article/10.1088/0067-0049/192/1/9/meta (the URL from the DOI) gives a single page number as we have used. |
Another comment: supplement links have been changed from "supplement section 3" to "section S3" throughout. Should we modify and update the supplement to number sections with the "S" prefix? This may not be worth the hassle. Also, interesting note: it appears that cross document links will work (they link to the DOI). |
The supplement still has line numbers so we may want to try to submit an updated version anyway. |
Another note, I don't know if it was intentional, but all the internal cross-section links have been changed to plain text (like in footnote 9, "as noted in section 5.1" was changed to "as noted in Section, 'The core'" with no linking). |
I don't know if I should bother about it, but I also noticed that the document table of contents metadata is missing from the PDF, making it harder to navigate in a PDF viewer that supports that. |
@aktech thank you. Can you please correct the spelling on the PeerJ site. |
Did not hear from @matthewturk, so I will just say that I do not know about the Turk, et. al. reference. As far as I tell, the reference is correct. It is what is given as the citation at the DOI. |
I think that's right, yes.
…On Fri, Dec 9, 2016 at 3:06 PM, Aaron Meurer ***@***.***> wrote:
Did not hear from @matthewturk <https://github.com/MatthewTurk>, so I
will just say that I do not know about the Turk, et. al. reference. As far
as I tell, the reference is correct. It is what is given as the citation at
the DOI <http://iopscience.iop.org/article/10.1088/0067-0049/192/1/9/meta>
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFbu2hOJTFbB0m8XX87EJ2_uk12sXg0ks5rGcK_gaJpZM4LISVG>
.
|
Here is the final proof with annotations. Please review the annotations |
I also plan to leave the following in the "notes for staff" field when I upload it:
|
Done. |
I went over the pdf document and I think the annotations looks good. |
PeerJ has a PDF for proofing. They want it back within one business day, so if you want to look at it, please do so by tomorrow.
Here is the PDF: peerj-cs-103-proof.pdf. Do not circulate this proofing PDF as it will change before publication.
Here are their instructions:
The text was updated successfully, but these errors were encountered: