Descriptions for the localization #40
Comments
|
This is just as unhelpful as the descriptions are presumably to you. Can you tell me which need improvement. They are meant to be short so the translators don't have to struggle to understand their meanings. |
|
They are not explain AS they are noe, they are statements.
Den fre. 9. jun. 2017, 19.46 skrev cyberpower678 <[email protected]>:
… This is just as unhelpful as the descriptions are presumably to you. Can
you tell me which need improvement. They are meant to be short so the
translators don't have to struggle to understand their meanings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEbzTFHyJNO1PpBt5LTVOcKK0mDsXPjvks5sCYUMgaJpZM4N1FBt>
.
|
|
Spellcheck interfered.
They are not explainations ad they are now, they are statements.
Den fre. 9. jun. 2017, 21.01 skrev John Erling Blad <[email protected]>:
… They are not explain AS they are noe, they are statements.
Den fre. 9. jun. 2017, 19.46 skrev cyberpower678 ***@***.***
>:
> This is just as unhelpful as the descriptions are presumably to you. Can
> you tell me which need improvement. They are meant to be short so the
> translators don't have to struggle to understand their meanings.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#40 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AEbzTFHyJNO1PpBt5LTVOcKK0mDsXPjvks5sCYUMgaJpZM4N1FBt>
> .
>
|
|
They are from my point of view, and I received no complaints about them until now. They describe what they are, if it's on a button, or if it's describing something else. |
|
I have reported an issue, and you argue the issue don't exist. I'm done
with this.
Den fre. 9. jun. 2017, 21.26 skrev cyberpower678 <[email protected]>:
… They are from my point of view, and I received no complaints about them
until now. They describe what they are, if it's on a button, or if it's
describing something else.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEbzTLFi3ldT7v8or5Q_tU5OU9HJzNWMks5sCZxKgaJpZM4N1FBt>
.
|
|
I'm not arguing anything. I'm not sure what's unclear about the existing descriptors. Am I supposed to write a paragraph for each object? |
|
Try looking at other repos for examples, such as MediaWiki. I agree descriptions like "Label" or "Checkbox" are not by themselves particularly helpful. You should provide context to explain what the message is meant to convey, and not just how it is used. However this probably less important for messages that use To be fair to Cyberpower, I'm not sure any documentation on "best practices" exists, or if it does it is not easy to find. I tried searching on translatewiki.net and found nothing. So for now, as I said, I would model your i18n after other popular repos. |
|
To further clarify, it is my impression that translators are generally able to look at the English message and go off of that. If they are for any reason unsure they look at the qqq, so that's why it's important to provide sufficient context. E.g. submit (which I think should be using |
|
I finally found some documentation on Localization! Thought I'd share it with you... https://www.mediawiki.org/wiki/Localisation Specifically here, see https://www.mediawiki.org/wiki/Localisation#Message_documentation Hope this helps |
Please provide proper descriptions for the localizations, qqq.json is full of way to superficial descriptions, preferably also make a glossary so the strings are standardized.
The text was updated successfully, but these errors were encountered: