Andromeda/jank-client-fork
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

update qqq

Browse source
This commit is contained in:
MathMan05 2024-11-12 14:42:39 -06:00
parent a1df59dccc
commit 9dc7637ee9
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
translations/qqq.json
View file

@ -8,7 +8,7 @@
"comment":"Don't know how often I'll update this top part lol" "comment":"Don't know how often I'll update this top part lol"
}, },
"qqq":{ "qqq":{
"How this works":"For the strings I'm using much of the same logic as https://github.com/wikimedia/jquery.i18n with some minor modifications, though I am not using jquery, some strings are are using MarkDown, the ones that are should hopefully be obvious. \nA quick summary of everything here, $number will be replaced by something after the fact, wether it be a name or number. You'll also see {{PLURAL:$1|message|messages}} which can support as many plural forms as you need, the first one $1 will be used to select the next ones, the next ones will be the number in order, so if $1 is one it'll select the first item, if it's 2 it'll select the second item, if $1 does not point to a valid item it'll select the last item. I've also implemented GENDER, though it's unused in the translations, it'd go {{GENDER:$1|male|female|neutral}}.\nThe json format is relatively simple, the base object has a @metadata that'll credit the authors of the translation, then for each language it'll have a string that either contains the translation in json, or points to the translation as a string, for example you'll see \"ru\": \"/translations/ru.json\" in en.json as en.json does not contain the russian translation directly, instead it says that the russian translation is at that location. Untranslated strings should remain blank, Jank Client has code to fallback to other languages if strings don't exist in a translation, so do not leave the english translations in translation files that are not the english one, this is why the russian translation is largely empty.", "How this works":"For the strings I'm using much of the same logic as https://github.com/wikimedia/jquery.i18n with some minor modifications, though I am not using jquery, some strings are are using MarkDown, the ones that are should hopefully be obvious. \nA quick summary of everything here, $number will be replaced by something after the fact, wether it be a name or number. You'll also see {{PLURAL:$1|message|messages}} which can support as many plural forms as you need, the first one $1 will be used to select the next ones, the next ones will be the number in order, so if $1 is one it'll select the first item, if it's 2 it'll select the second item, if $1 does not point to a valid item it'll select the last item. I've also implemented GENDER, though it's unused in the translations, it'd go {{GENDER:$1|male|female|neutral}}.\nThe json format is relatively simple, the base object has a @metadata that'll credit the authors of the translation, then it'll contain the translations. Untranslated strings should remain blank, Jank Client has code to fallback to other languages if strings don't exist in a translation, so do not leave the english translations in translation files that are not the english one, this is why the russian translation is largely empty.",
"context":"Jank Client is a spacebar client, and due to spacebar being an implementation of the discord APIs, much of Jank Clients text is like that of discord.", "context":"Jank Client is a spacebar client, and due to spacebar being an implementation of the discord APIs, much of Jank Clients text is like that of discord.",
"permissions":{ "permissions":{
"description":"This object contains the descriptions of permisions, along with their names." "description":"This object contains the descriptions of permisions, along with their names."