-
Notifications
You must be signed in to change notification settings - Fork 228
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
Issue 3039 #3040
Issue 3039 #3040
Conversation
Former (non-renewing) IPPs > Additional Supporters Make typography consistent, lines 58-76
Former (non-renewing) IPPs > Additional Supporters Make typography consistent, lines 61-79
Former (non-renewing) IPPs > Additional Supporters Make typography consistent, lines 59-77
Former (non-renewing) IPPs > Additional Supporters Make typography consistent, lines 60-80
Update contact, line 110.
Update contact, line 113.
Update contact, line 111.
Update contact, line 114
Update contact at lines 35, 58 and 80.
Update contact at lines 36, 60 and 87.
Update contact at lines 38, 63 and 84.
Update contact at lines 38, 53 and 71.
Add alert-info box to make consistent across /en/ipp, /es/pia, /fr/pi, /pt/ppi
Add html <li> and <div> tags, lines 63-70
Replace Markdown link syntax with html at line 61.
- Create Alumni Partners sub-section - Move (non-renewing) IPPs to Alumni Partners - Sub-divide Additional Supporters into active and past
- Create Alumni Partners sub-section - Move (non-renewing) IPPs to Alumni Partners - Sub-divide Additional Supporters into active and past
Minor edits, lines 69 and 73
- Create Alumni Partners sub-section - Move (non-renewing) IPPs to Alumni Partners - Sub-divide Additional Supporters into active and past
- Create Alumni Partners sub-section - Move (non-renewing) IPPs to Alumni Partners - Sub-divide Additional Supporters into active and past
Update month when we reset partnership rates.
Update month when we reset partnership rates.
Update month when we reset partnership rates.
Update month when we reset partnership rates.
Hello @charlottejmc, When you have time, may I ask for your help to check my French on the following page?: What I've done is:
Thank you 🙂 |
Hi @anisa-hawes, I have had a look and here are my thoughts:
I hope this helps! |
Adjustments to translation at lines 55, 56, 69 and 72.
hi, if I may, for the term "alumni partners", simply "anciens partenaires" ou "partenariats révolus" (as Charlotte proposes) can work here. (as élèves refers to students, and I believe is embarked from the auto translation of the initial alumni term) |
Adjust translation, line 55
Hello @DanielAlvesLABDH, I hope you're well. This PR represents some adjustments to the headings and sub-headings on our Supporters pages. Our aim is to create meaningful sub-headings within our lists of IPP, so we make clear who our active supporters are while also acknowledging institutions that have supported us in the past. May I ask for your help to adjust my attempted Portuguese translations?
You can review the detail of my edits here. With thanks! Anisa |
Hi @anisa-hawes, will look at this tomorrow morning. Best |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have made some suggestions of change
Adjust translations lines 57 and 69
Hello @spapastamkou and @rivaquiroga This PR is ready, with each of the translations checked by native speakers. The only further change I've made is to update the information about which month we reset partnership rates. As discussed with @drjwbaker and @spapastamkou, going forwards will be reviewing our rates mid-year for reset in October (rather than January) to align with ProgHist Ltd's financial year. Thank you. |
I'm moving former (non-renewing) IPPs to the Additional Supporters section of our /en/supporters, /es/colaboradores, /fr/nos-soutiens, /pt/apoiadores pages.
Closes #3039
Checklist
Closes #ISSUENUMBER
to your summary above[ ] if the text needs to be translated, please follow the translation request guidelines, then assign the relevant language team(s) as "Reviewers" and tag both the team as well as the managing editor in your PR.