Learn about the fediverse and find your new community.
This projects uses node 18.13.0.
npm install
npm start devYou can see a list of open and in-progress translations here.
The current translation workflow is described below. If you don't have a GitHub account, or prefer not to use it, feel free to follow steps 1 through 3 and send the translated files via email.
Otherwise, you can fork this repo, make the necessary changes, and open a pull request.
- Navigate to the
translationsfolder. - Add a new language section inside the
info.jsonfile. If you need help with this step, please reach out!
{
"label": "Native name of the language",
"label_en": "English name of the language",
"label_lat": "latinized native name of the language, used for sorting",
"lang_dir": "the direction of the languaue, LTR (left-to-right) or RTL (right-to-left)",
"code": "the ISO 639-1 language code, see https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes",
"available": true, // Should the language be visible in the language picker? true or false
"translators": [ // List of people who contributed to the translation
{
"name": "Person A",
"url": "https://example.social/@person_a"
},
{
"name": "Person B",
"url": "https://example.social/@person_b"
}
]
},- Update the JSON files inside the
datafolder for each page and selected site sections. - Run
npm run translateto generate translation files insidelocales.
Keep in mind that the goal is to communicate the same ideas to an audience in a different culture. For example, in this sentence:
You're probably using Gmail. Or perhaps Outlook. Or Yahoo Mail.
Consider listing services that are popular in your particular country.
Pravdepodobne používaš Gmail. Alebo Zoznam.sk. Možno Centrum.sk.