clone/logseq
1
0
Fork 0
mirror of https://github.com/logseq/logseq.git synced 2026-02-01 22:47:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Translate two translations that weren't usable by all langs

Browse Source 
See #9716. Position matters for some langs like Turkish
This commit is contained in:
Gabriel Horner
2023-06-23 09:51:33 -04:00
parent 08f70c979e
commit 43df7dfd9a
3 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/contributing-to-translations.md
View File

@@ -84,6 +84,7 @@ Almost all translations are small. The only exceptions to this are the keys `:tu
* Some translations may include punctuation like `:` or `!`. When translating them, please use the punctuation that makes the most sense for your language as you don't have to follow the English ones.
* Some translations may include arguments/interpolations e.g. `{1}`. If you see them in a translation, be sure to include them. These arguments are substituted in the string and are usually used something the app needs to calculate e.g. a number. See [these docs](https://github.com/tonsky/tongue#interpolation) for more examples.
* Rarely, a translation may need to translate formatted text by returning [hiccup-style HTML](https://github.com/weavejester/hiccup#syntax). In this case, a Clojure function is the recommended approach. For example, a function translation would look like `(fn [] [:div "FOO"])`. See `:on-boarding/main-title` for an example.
## Fix Mistakes
There is a lint command to catch common translation mistakes - `bb