Stylus: Add a Translators needed button to main UI - Call to action.

[the-j0k3r]

The button would have a maximum of two words long label,

Possible labels

Improve translation
or
Translate Stylus
or
...

And should be displayed in several key places in UI. Perhaps a bigger and colored version like green to make it stand out of the default UI.

e.g.

This would be a good first step in raising awareness to possibly attract new translators to the project especially for those stale languages that no longer have an active translator.

[tophf]

I like the idea.
As for the implementation, I think a link on a separate line is better - makes us look less desperate.

[the-j0k3r]

Yes it should link to something, but as for the format Im not sure if that link only would make Stylus not sound desperate enough, after all I blame you for this suggestion, see Issues with changing default strings

So need to be efficient call to action and not look too understated so doesn't get lost.

[tophf]

If an incomplete translation was a noticeable problem for the users, they would already have complained but in more than one year there were no such complaints so I don't want to add a prominent button. And BTW, it should be shown only in non-English profiles where the amount of translated strings is not 100%, which we can detect programmatically.

[Mottie]

What if for the english profile we include a "Add translation" instead of "Improve translation"?

[tophf]

I think those who use the English UI don't care about translations so I don't want to add a supposedly useless element. Or we could show it only in the manager as an additional link in the last info block named Translations.

[the-j0k3r]

If an incomplete translation was a noticeable problem for the users, they would already have complained

You misunderstand my reasoning/logic for this suggestion, I suggested this because there are defaulst strings that need to be improved and you quoted some problem may exist since some languages dont have an active translator.

I did not suggest this because some translation may be bad or incomplete, or someone complained or not (I dont care about that), but its a bonus shoe that fits all feet.

[tophf]

Compared to this, it's easier for us and less intrusive for users of the affected languages (they didn't complain anyway) to modify those default translations where a change is needed.

[the-j0k3r]

I think those who use the English UI don't care about translations so I don't want to add a supposedly useless element.

The purpose of this is to get translators for all languages especially the stale with no active trabslators i.e legacy strings. Read above reasoning.

So this should be plastered even in English

[the-j0k3r]

Compared to this, it's easier for us and less intrusive for users of the affected languages (they didn't complain anyway) to modify those default translations where a change is needed.

lol, whatever, I think there should be two ways so you can do A-B testing, oh wait we dont collect ANY telemetry, scratch that.

[tophf]

I don't think we should harass the users. A simple additional link in the info block only in the manager is sufficient.

[the-j0k3r]

Why would a legitimate call to action be construed as some harassment IDK,
I didnt suggest that if every time anyone pressed anything you show a Popup with some nag message.

I guess my point is, it should be effective and prominent enough not to be lost against the background or not important enough that its easily dismissed.

[tophf]

Because no one expressed any concern in the current state of translations there's no need for any prominent calls to action.

[the-j0k3r]

Because no one expressed any concern in the current state of translations there's no need for any prominent calls to action.

Again you missed the point why I made this suggestion in first place.

[tophf]

Yeah I don't understand what's this all about. I don't see the problem. And I feel we're going in circles.

[the-j0k3r]

Read this https://github.com/openstyles/stylus/issues/448#issuecomment-407744716

[stonecrusher]

Pro:
I also like a subtle link on a separate line at the bottom of the manager better. Button looks too functional and indeed a bit desparate.
Should also be visible in the english version as that's the default for everyone with a yet untranslated system language. Just name it Translate Stylus for all without further complicating it, independent of translation status. There's always room for improvement, re-reading and having new translators instead of trying to contact someone who translated a lot 2 years ago but has been idle since.

Contra:
On the other hand, people who are couraged enough to contribute (to) a translation will easily find the necessary transifex link

• On the add0n.com homepage
• In the main readme on github
• In the contributing guide via wiki
• By asking on our support channels
• No tangible translation complaints so far

[the-j0k3r]

@stonecrusher

re:

No tangible translation complaints so far

This suggestion was never made considering if there are complaints or not or if its easy or not to find a way to contribute (to) a translation, it just happens to encompass those possibilities. But I see the points being made, I was hoping to see the acknowledgement to my logic which is Issues with changing default strings, but its not important anyway to the possible benefit this change could have.

Just for anyone not following on chat, and to clarify I agree this is going in circles, feel free to implement however you see fit. Its a good idea, end of story 👍

Sorry if any discussion was somewhat passionate, no ill was intended by any of it

[tophf]

Let's start with something more or less modest - one link in the manager - and see what happens in the next month or two.

• English and more than 95% translated languages, which is detected on extension start:
  Get styles | Get help | Translate | Wiki

• everything else gets a longer link in bold font:
  Get styles | Get help | Wiki
  Improve translation

In English we have two "Get" actions, so "Translate" I think should follow them.

[tophf]

Smart behavior outlined above isn't easy to implement in FF as it can't explore the extension package and I'm not yet ready to offload this task to our build script.

Thus, I've only added the short inconspicuous Translate link to the end of the block.

[narcolepticinsomniac]

There's a translate link in the manager. Good enough.