-
Notifications
You must be signed in to change notification settings - Fork 229
Copyedit comments
Contents of this page:
This comment can be used as a template to post in the Issue comment thread before copyediting begins.
EN
Hello @author,
This lesson is now with our copyeditor @copyeditor who aims to complete the work by ~[DATE].
@author please note that you won't have direct access to make further edits to your files during this Phase.
Any further revisions can be discussed with your editor @editor after copyedits are complete.
Thank you for your understanding.
ES
Hola @autor,
Esta lección está ahora con nuestro/a corrector/a de estilo @copyeditor, cuyo objetivo es completar el trabajo antes del ~[FECHA].
@autor, tenga en cuenta que no tendrá acceso directo para realizar más ediciones en sus archivos durante esta fase.
Cualquier revisión adicional se puede discutir con su editor/a @editor una vez completadas las correcciones.
Gracias por su comprensión.
FR
Bonjour @auteur,
Cette leçon est maintenant entre les mains de notre [correcteur/correctrice], qui envisage de terminer ses corrections avant le [DATE].
@auteur, veuillez noter que vous n’aurez pas accès au fichier pour y faire des changements pendant cette Phase.
Vous pourrez discuter de changements additionnels avec votre [rédacteur/rédactrice] après le retour [du correcteur/de la correctrice].
Merci pour votre compréhension.
PT
Olá @autor,
Neste momento, esta lição encontra-se com o revisor do texto / copyeditor @copyeditor, que completará o trabalho até ~[DATA].
@autor, não poderá realizar mais alterações aos seus ficheiros durante esta Fase.
As revisões adicionais poderão ser debatidas com o seu editor @editor, após o fim da revisão do texto.
Agradecemos a compreensão.
This comment can be used as a template to post in the Issue comment thread when the copyedits are ready to be reviewed by the author and editor:
EN
Hello @author and @editor, I've prepared a [PR with the copyedits for your review](https://github.com/programminghistorian/ph-submissions/pull/XXX).
There, you'll be able to [review the 'rich-diff'](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) to see my edits in detail. You'll also find brief instructions for how to reply to any questions or comments which came up during the copyedit.
When you're both happy, we can merge in the PR.
FR
Bonjour @rédactuer·ice et @auteur·e,
J'ai préparé une [« Pull Request »](https://github.com/programminghistorian/ph-submissions/pull/XXX) (demande de tirage) avec les corrections.
Vous pourrez y [consulter le « rich-diff »](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) pour voir mes modifications en détail. Vous trouverez également de brèves instructions sur la manière de répondre aux questions ou aux commentaires qui ont été formulés pendant la correction du texte.
Lorsque vous serez satisfait·es, nous pourrons fusionner la branche de correction.
This comment can be use as a template to post in the Pull Request comment thread when the copyedits are ready to be reviewed by the author and editor:
Hello @author and @editor. I've now prepared the copyedits for this lesson. I'd be grateful if you could review the adjustments and confirm that you are happy for me to merge these. You can see the details of my edits under the [files changed](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) tab!
I'd like to bring your attention to the comments I have attached to specific lines. You can respond to any of my suggestions via the comments below, or click _Resolve conversation_ if you're happy with them like this:
![image](https://github.com/programminghistorian/jekyll/assets/143802849/6a73acb9-215d-4fe1-8ab7-247921a3e6a4)
If you want to make edits, please work [here](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) by clicking the three dots at the upper right of the file, then _Edit file_:
#Take screenshot of relevant lesson
FR
J'ai maintenant préparé les corrections pour cette leçon. Je vous serais reconnaissant·e de bien vouloir examiner mes ajustements et de confirmer que vous êtes d'accord. Vous pouvez voir les détails de mes modifications sous l'onglet Files changed en haut de cette page.
J'aimerais attirer votre attention sur les commentaires que j'ai joints à certaines lignes. Vous pouvez répondre à toutes mes suggestions via les commentaires ci-dessous, ou cliquer sur Resolve conversation si vous êtes satisfait·es :
Si vous souhaitez apporter des modifications, veuillez le faire ici en cliquant sur les trois petits points en haut à droite du fichier, puis sur Edit file :
#Prendre capture d'écran de la leçon
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees