-
Notifications
You must be signed in to change notification settings - Fork 228
Requesting Translation Guidelines
Textual changes to our core website pages generally involve translation into at least 2 other languages. To make translating as easy as possible for colleagues, please follow these guidelines:
- Make sure you have everything perfect and ready before you ask for a translation. Have colleagues check over your original wording before submitting a pull request. That way translators only have to help once.
- Translation may involve many files, or many sentences / paragraphs across a file. Be explicit about exactly what you need translated, and ask for it in ticket comments. Don't make translators dig through the files to try to figure out what you need amended. Use the following format, providing enough context so that they do not need to do any wider reading:
Dear Team: can you please help translate the following phrases into Spanish and French?:
about.md
The review process is an integral component of a collaborative and productive effort for scholars to teach and learn from each other.
TO:
The review process is an integral component of a collaborative, productive, and sustainable effort for scholars to teach and learn from each other.
Please discuss explicitly with the translator if you would like to incorporate the translations, or if you want them to do it. Both parties should be clear and provide enough context to the other to enable efficient publication. This simple approach makes it less time consuming for translators to help us with pull requests.
To alert translators to your request, @ both the relevant Managing Editor and Team (e.g. @spapastamkou & @programminghistorian/french-team) in the relevant Issue or Pull Request.
- 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