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

Descriptions for the localization #40

Open
jeblad opened this Issue Jun 9, 2017 · 9 comments

Comments

Projects
None yet
3 participants
@jeblad

jeblad commented Jun 9, 2017

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.

@cyberpower678

This comment has been minimized.

Show comment
Hide comment
@cyberpower678

cyberpower678 Jun 9, 2017

Owner

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.

Owner

cyberpower678 commented Jun 9, 2017

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.

@jeblad

This comment has been minimized.

Show comment
Hide comment
@jeblad

jeblad Jun 9, 2017

jeblad commented Jun 9, 2017

@jeblad

This comment has been minimized.

Show comment
Hide comment
@jeblad

jeblad Jun 9, 2017

jeblad commented Jun 9, 2017

@cyberpower678

This comment has been minimized.

Show comment
Hide comment
@cyberpower678

cyberpower678 Jun 9, 2017

Owner

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.

Owner

cyberpower678 commented Jun 9, 2017

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.

@jeblad

This comment has been minimized.

Show comment
Hide comment
@jeblad

jeblad Jun 9, 2017

jeblad commented Jun 9, 2017

@cyberpower678

This comment has been minimized.

Show comment
Hide comment
@cyberpower678

cyberpower678 Jun 9, 2017

Owner

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?

Owner

cyberpower678 commented Jun 9, 2017

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?

@MusikAnimal

This comment has been minimized.

Show comment
Hide comment
@MusikAnimal

MusikAnimal Jun 12, 2017

Collaborator

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 {{Identical}}.

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.

Collaborator

MusikAnimal commented Jun 12, 2017

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 {{Identical}}.

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.

@MusikAnimal

This comment has been minimized.

Show comment
Hide comment
@MusikAnimal

MusikAnimal Jun 12, 2017

Collaborator

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 \n{{Identical|Submit}}) is straightforward. They probably don't need to look at qqq. fpdisplayopen however says "Display open reports" which can be interpreted any number of ways for someone who is unfamiliar with the application, and finding out that it is the text for a checkbox doesn't help them.

Collaborator

MusikAnimal commented Jun 12, 2017

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 \n{{Identical|Submit}}) is straightforward. They probably don't need to look at qqq. fpdisplayopen however says "Display open reports" which can be interpreted any number of ways for someone who is unfamiliar with the application, and finding out that it is the text for a checkbox doesn't help them.

@MusikAnimal

This comment has been minimized.

Show comment
Hide comment
@MusikAnimal

MusikAnimal Jul 13, 2017

Collaborator

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

Collaborator

MusikAnimal commented Jul 13, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment