Skip to content
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

Update Transifex guidelines #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions translationguidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,10 +46,17 @@ The purpose of the glossary is to provide consistency for the key terminology in
Currently, we have over 100 high frequency terms in English, and these should be available in all core languages. The translators are encouraged to add more terms in their own language. Generally, it is best to just add the base form of a word (e.g., a verb in infinitive, or a noun as as subject, and not as a direct/indirect object).

## Bisq-Website Transifex Project
There are several symbols that don't need to be translated or changed. They should be market in Transifex as "notranslate". Here are a few examples.
- If you see `{% text %}` it is a Liquid element and should not be translated.
- `_blank` should not be translated.
- `’` is an apostrophe, like in `I'm`, and will appear in the software as an apostrophe.
The strings tagged as "notranslate" in Transifex should remain in English. The following warning that appears bellow the translation box let's you know so:
```The notranslate tag has been assigned to this string. You can add a copy of the source string as translation.```

The strings tagged "languagecode" in Transifex (lang: "en" and language: "English") should be replaced with the [language and localization code](https://en.wikipedia.org/wiki/Language_localisation#Language_tags_and_codes) of the respective language being translated. For language with multiple versions, only the country code shall go between the brackets in the "language" key. The "language" strings should be translated to the local language like in the example below: instead of replacing "English" with "French", it should be replaced with "Français". They are important for the website language selector and should follow the following standard:

| | lang | language |
| :--: | :--: | :-- |
| French | fr | Français |
| Portuguese | pt-BR | Português (BR) |
| | pt-PT | Português (PT) |


## Style Guide
The purpose of the style guide is to set certain translation standards for our projects. It covers the tone of the target language, style and various nuances for specific languages, and discusses how to deal with hard to translate terms such as Bitcoin or blockchain.
Expand Down