Kudos on keeping the website alive and fully responsive after 7 years. My group is definitely going to find this useful.
Suggestion:
Our server config is managed by 3 developers and a GitHub repo for the server config.
It would be convenient if you could add specific users as owners to a "group" of plugins. Our group might be called "Survival Network Translations", for example. And that's where we would keep all our translation files and have them managed by 3+ separate users.
Benefits:
1)
If a developer adds a new phrase to an existing translation file (or creates a new file for a new plugin), he doesn't need to ask the owner of the translation file (via the website) to make edits or add a new file. He can simply do it himself.
2)
This would eliminate the issue of having seperate translation files under different user's profiles, if someone decided to upload a new translation file under their personal account. Right now I have 6 plugins under my name but it would be inconvenient for a seperate user to start adding plugins from our server config under his name. It's easier to see all the plugin phrase files listed in 1 place
3)
You could have translators who are responsible for overlooking certain languages. Maybe you'd want 2 chinese translators: every time a phrase gets translated to chinese the other translator can look over the changes and make any edits in case there was a mistake somewhere.
If you end up implementing this - it might also be convenient to be able to assign roles:
"Owner" status users could do anything with the files, including deleting the file, deleting a Phrase, or renaming a phrase.
"Translator" status woudn't have permission to delete files or remove/rename Phrases. But they can edit a language translation if it needs rewording.
Optional side-suggestions
Toggleable setting: Only allow translations from clients with a permission status (Translator, or Owner).
Toggleable setting: After a random user makes a translation, someone with a permission status must OK it for it to be added.
Would look like this within the website (listed under translations):
Phrases awaiting approval:
"es" "test test test"
(Noticed some non-english translations in English when browsing through plugins.)
Edit:
Some after thoughts:
1)
Spoiler
Might also want to write a brief write-up for people new to the website - written with the assumption that there'll be translators with 0 exposure to how sourcemod handles translations.
I ended up discovering that "// 1: description" is used to describe placeholder text - only because I saw it under my plugin phrases
(I was already doing that to make it easier for translators) but I wouldn't have known about the feature otherwise.
I did a write-up I was going to post somewhere else but it's here if you want to use it:
Brief rundown
Take the following example trom a translation file:
Code:
"FF_DELT_INDIVIDUAL"
{
// 1: damage delt
// 2: target's name
"#format" "{1:i},{2:N}"
"en" "Done {lightgreen}{1}{default} damage to {olive}{2}"
}
"#format" "{1:i},{2:N}" tells Sourcemod that the first placeholder {1} is an integer type, and the second placeholder {N} is a placeholder for the client's name.
{1} and {2} act as variables in translation text. So {1} will get replaced with whatever damage was being delt, and {2} will be replaced with the client's name.
{lightgreen}, {default}, & {olive} are color coded tags so text appears in color.
Bracketed out comments ( "// 1: damage delt") just help the website render descriptions for each placeholder.
2)
Spoiler
Some plugins might require a brief "readme" or "about" section for clarification on certain things.
Use this as an example when translating: https://i.imgur.com/GIxpXPO.jpg
1.)
Try to use shorthand abbreviations for panel text.
Common infected = ci, health = HP, accuracy = acc, etc.
panel can cut off if there's too many characters.
2.)
ACC_STATS
Each percent sign % needs an additional percent sign in order for the character to be escaped within a string
So "({1}%% acc (S:{2}%%, C:{3}%%, T:{4}%%)" might actually look like: "(56% acc (S:32%, C:33%, T:27%)"