TheCloud/PronounsPage
1
0
Fork 0
mirror of https://gitlab.com/PronounsPage/PronounsPage.git synced 2025-09-23 12:43:48 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'localisation-doc' into 'main'

Browse Source 
(doc) localisation updates

See merge request PronounsPage/PronounsPage!463
This commit is contained in:
Andrea Vos 2024-05-25 14:42:20 +00:00
commit 684cd2446f
1 changed files with 18 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
locale/en/blog/creating-new-language-version.md
View File

@ -13,7 +13,7 @@ Maybe someone already started working on that language?
It would be useful to coordinate before you put work into it.
We'll invite you to our Discord server and offer support.
If you know how to work with tools like Git, Yarn, JavaScript etc.,
If you know how to work with tools like Git, Pnpm, JavaScript etc.,
you can head to [the source code](https://gitlab.com/PronounsPage/PronounsPage/),
clone the repository and set up the project according to the instruction in `README.md`.
You'll be able to see the changes in real time as you make them.
@ -47,6 +47,21 @@ to respecting their names, in which we use the names “Ashley” and “Samanth
please use instead some names that are popular in your culture.
Basically, feel free to add, remove and edit stuff in order to make the content
as useful, fitting and relevant to your language as possible.
Other notable keys for localisation are `quotation` which describes the quotation marker popularly used in the language
or `calendar.date` and `calendar.dates` which together describe the date format.
Because we are a site about gender-neutral language, please try to use it whenever possible
– even when they are not normative forms.
Some translations have special placeholders:
- Words delimited by `%` like `%day%` describe a placeholder where the value is dynamically inserted,
use these to define the position where the inserted value should go
- Links are defined via `{target=display text}`
Obviously you should translate the display text like normal, but in the case of internal links
(which don’t leave the current side) you should use the same route name like in `config.suml`
- Icons are rendered with `[name]`. There is no translation needed here
- In flag names you can add morphemes, e.g. when a flag stands for an adjective
and it needs to be gendered in your language: `'Arrománti{inflection_c}'` (more on that below)
Also, remember that not everything in this file will necessarily require a translation from you.
For instance, the Polish locale contains translations for the “names” module,
@ -135,13 +150,11 @@ of [inclusive language suggestions](/inclusive), etc.
Once a first draft of the “static” parts (even just a translation) is ready,
please ping me ([@andrea](/@andrea)) on Discord,
or send us an email to [contact@pronouns.page](mailto:contact@pronouns.page),
or send us an email to [localisation@pronouns.page](mailto:localisation@pronouns.page),
or submit a pull request, etc. – and I'll set up a test server
where you'll be able to see your work in practice as well as start adding the “dynamic” parts directly via the website.
The website also offers an interface to propose missing translations of new features and correct errors in the existing ones.
Please **don't use it until your version gets published**, as it adds more unnecessary work and possible edit conflicts.
In the early stages let's just work on the `translations.suml` file directly.
After the test server is up, it also offers an interface to propose missing translations of new features and correct errors in the existing ones.
## And more…