Hint to locale translation rules instead to handbook

[La Geek]

In Glotpress you see this hint:

It would be absolutely helpful for the entire translation process if the local rules, glossaries and slack channel were linked. Something like this:

The hint should be a translatable string. Only if it was not translated, or no local links exist, the reference to the English manual should be displayed.
Or we could use the same list as in the email for new editors.

Translators may find the glotpress, if they click on the plugins or theme page on "translate it into your language". In this case they don't know the existing local rules/glossaries and slack-channels.

[Presskopp]

This would be a very welcome enhancement for the onboarding process! +1

[oschmehr]

We often see contributors translating strings (with best intentions) but they're not aware of local rules, our glossary and the german #polyglots channel.
Such a custumizable hint as described above would be a great help for them (and us). +1

[casiepa]

Please note that polyglots is keeping track of local slacks (​https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/) and Style guides, glossaries (​https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/list-of-glossaries-per-locale/).

Technically speaking, if this is to become a CPT, polyglots could continue to keep it updated.

[tobifjellner]

I see a couple of things that would make this change a little bit more complicated then one might realize from start:

1. The "translate" website itself isn't translated. Technically speaking, it uses en_US all over. So just "making this string translatable" doesn't fix it.
2. The welcome notice is for the whole "translate" website. Someone may have discarded this message for, say, German, but after that head over to French translations. So information about discarded notices might need to be handled with higher granularity.

Related: ​https://github.com/GlotPress/GlotPress-WP/issues/709

[tobifjellner]

Related: ​https://github.com/GlotPress/GlotPress-WP/issues/709

But probably easier and quicker to solve this completely in meta.
Put two strings in "Rosetta":
Translators: Adopt this string for your locale, example "What you should know when translating to en_GB"
"Get started with WordPress translations."

Translators: Link to more information about translation of WordPress. Change to a welcome note/style guide, etc for your locale, if relevant.
"​https://make.wordpress.org/polyglots/handbook/"

Then a hack in the theme for translate.wordpress.org should use these strings in the language currently being translated. Would probably need a Cronjob that will copy the strings to the relevant place in the theme...

[tobifjellner]

The string in https://meta.trac.wordpress.org/attachment/ticket/3522/Image1.png is built using information from the client's http accept headers. (and, of course, the fact that the plugin catalog is a translated environment, which translate.wordpress.org is not.)

[Presskopp]

After talking to @tellyworth on slack here 3 screenshots illustrating the issue a bit more I hope

see
​https://wordpress.slack.com/archives/C02QB8GMM/p1537393331000100

We should show a link to Slack if the team of the language I chose has one.
We should show a link to the Style Guide if the team of the language I chose has one.
Some extra configurable field by language would be ideal to place some extra info.

Those links should be in an alert design/color so they will be catching your eye.

We need new translators to read these ressources first, before they start translating and best if they also join slack. Rejecting faulty translations is frustrating for both sides.

[ocean90]

In 8731:

Translate/Rosetta: Register a navigation menu for storing helpful resources for translation contributors.

See #3522.

[ocean90]

In 8751:

Translate: Update editor interface for translations.

• Increase focus on translation by moving original, context and translation into the same column.
• Add tabs for plural forms.
• Move action buttons more closely to textarea.
• Increase size for textareas.
• Automatically resize textarea heights.
• Provide an area for suggestions, see #4430.
• Add help dialog with support for locale resources, see #3522.
• Stack columns on mobile.

See #4431.

[ocean90]

Quoting ​https://make.wordpress.org/polyglots/2019/05/08/updated-editor-interface/

Help Dialog
The help dialog can be extended with resources specific to the current locale. This is done by a new navigation menu on the Rosetta site which is assigned to the “Resources for translation editors” location. Two levels and descriptions are supported.

The menu markup is cached for an hour.