You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ Here's a few tips as you go along:
19
19
* Instead of translating from scratch, consider contacting [@nysenthil] to get an IBM Watson machine translation as a starting point and revising from there.
20
20
* All translations (manual or machine-generated) must be reviewed and approved by a native speaker.
21
21
* Translated articles should be stored next to the English articles in a subfolder named as the [two-character language code](https://www.loc.gov/standards/iso639-2/php/code_list.php) of the translation (e.g. the `de` subfolder for German).
22
+
If the translation is specific to a locale, then the two-digit locale code should be a part of the subfolder name (e.g. a `pt-br` for Brazilian Portuguese).
22
23
* The filename of the article should be changed to include two-character language code prefix.
23
24
* The special `index.md` files for each section should also be translated, as they are used in the Learning Path section of the [new website](https://innersourcecommons.net/learn/learning-path/)
24
25
* After `index.md` file and the first article (01-*.asciidoc) for a section are translated and merged, all landing page links in translated articles can be pointed to the translated landing page. (e.g. [landing page for Contributor in German](https://innersourcecommons.org/de/learn/learning-path/contributor))
0 commit comments