Skip to content

Commit

Permalink
Merge pull request #3128 from programminghistorian/Issue-3127
Browse files Browse the repository at this point in the history
Issue 3127
  • Loading branch information
anisa-hawes authored Dec 15, 2023
2 parents b75c0fb + e4b8537 commit 0cc8611
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions _posts/2023-11-15-en-call-for-lessons.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Our lessons support readers who want to learn new skills, but the act of writing

_Programming Historian_'s English edition is inviting proposals to fill gaps in our lesson directory. Please explore [our journal](/en/lessons/) to discover what’s already available, and consider what you might be able to add.

If the method or approach you’re interested in writing a lesson about is already represented by the [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) editions of _Programming Historian_, we welcome proposals to translate those existing, original lessons into English. In this call, **proposals for translations will be prioritised for publication**.
If the method or approach you’re interested in writing a lesson about is already represented by the [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) editions of _Programming Historian_, we welcome proposals to translate those existing, original lessons into English. Please review our [Translation Concordance](/translation-concordance) map to identify options for your translation. In this call, **proposals for translations will be prioritised for publication**.

We’re also keen to extend our offer to learners, and invite proposals which focus on methodological approaches, digital techniques and tools including, but not limited to:
- Text encoding, Natural Language Processing, especially for multilingual corpora
Expand All @@ -47,7 +47,7 @@ We’re also keen to extend our offer to learners, and invite proposals which fo
Remember, you can either:

- Propose an original English-language lesson
- Propose a translation into English of an existing, original [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) lesson published in one of the other _Programming Historian_ editions.
- Propose a translation into English of an existing, original [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) lesson published in one of the other _Programming Historian_ editions. Please review our [Translation Concordance](/translation-concordance) map to identify options for your translation.

**If you have an idea, please send us a proposal by January 12th, 2024.**

Expand Down
2 changes: 1 addition & 1 deletion assets/forms/Lesson.Query.Form.txt
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ We encourage prospective authors to think carefully about how their proposal cou

You can [explore our journal](https://programminghistorian.org/en/lessons/) to discover what’s already available and consider what you might be able to add.

If the method or approach you’re interested in writing a lesson about is already represented by the [Spanish](https://programminghistorian.org/es/lecciones/), [French](https://programminghistorian.org/fr/lecons/), or [Portuguese](https://programminghistorian.org/pt/licoes/) editions of _Programming Historian_, we welcome proposals to translate those existing, original lessons into English.
If the method or approach you’re interested in writing a lesson about is already represented by the [Spanish](https://programminghistorian.org/es/lecciones/), [French](https://programminghistorian.org/fr/lecons/), or [Portuguese](https://programminghistorian.org/pt/licoes/) editions of _Programming Historian_, we welcome proposals to translate those existing, original lessons into English. Please review our [Translation Concordance](/translation-concordance) map to identify options for your translation.

---

Expand Down

0 comments on commit 0cc8611

Please sign in to comment.