Hi MusikAnimal,
thank you for consiering me a superhero :-)
Purodha

In T93213#2349164, @Nemo_bis wrote:

I don't quite understand this rationale...

In T135832#2343090, @Mhurd wrote:

@Purodha
Ok to close this ticket?

Resolved.

@ Psychoslave - you are right,

@MusikAnimal Thank you.

The link to ask questions in translatewiki.net sent me here.
It this is the wrong place, the link needs to be amended.

In T48924#2309427, @Glaisher wrote:

Should the edit summary input be in the language of the target language ...

In T134751#2279999, @Aklapper wrote:

How would this technically work to avoid colliding with your browser's right-click menu?

I have clarified the description a bit:
https://translatewiki.net/wiki/Wikimedia:Pageviews-latest-days/qqq

I only partially understand this all, because visual editor is completely outside my world and "even beyond" is even beyond it :-) Visual editor usually makes my browser choke or causes other unpleasant effects, etc. Can one translate without all these useless distractions and time consuming bells and whistles just typing ordinary wiki text?

Yes. What else?

Thanks!

In T133766#2252071, @MusikAnimal wrote:

Ah, looking at this doc I see what you mean. I'm not sure of a solid workaround, then... :(

I guess I can explore a (very) lightweight API implementation for our purposes. It should go pretty fast, just will be a fair amount of work. The advantage here being we can still plug into Intuition and translatewiki, as opposed to a separate set of messages just for JavaScript.

In T133766#2251006, @Ricordisamoa wrote:

In T133766#2250650, @MusikAnimal wrote:

Far from ideal, but it'd work.

The errors need fixing.
How to do that?

In T129352#2172343, @Nemo_bis wrote:

Per Nikerabbit, feel free to reopen when all extensions store their issue tracker URL/component in a composer.json file in their repository.

In T66430#2031492, @Aklapper wrote:

@Purodha: Can you answer the last comment by @Nikerabbit please?

How many revisions do you need to link and how many links do you have space for?

Well, the demo is to show specific translations of messages in an easily browsable ways. Yes, a series of links to the individual translated message pages of the time may do. Din't think of that due to being grossly non-interactive and needing to be very limited by the number of actual links. :-/

We want to accommodate new and non-Wikitext users. That needs to be done in a logical way.

Having an extension, or an extension group, use the installer is imho hardly possible without the extension or group supplying its own additions to the installer, including dependencies and i18n.

All done.

Translate does not know about Phabricator components, but it knows about message groups. Primary message groups and Phabricator components match in the majority of cases, according to Nikerabbit.

In T130196#2149531, @Nemo_bis wrote:

I feel we already had this conversation.

1. ... But all about message groups which is a match in the majority of cases.
2. And it needs to be allowed to learn he necessary. :-)

@Quiddity: Well understood and explained.

@Nikerabbit: If I see it right, Translate is currently not using extension.json either.
As of yet, I could not find where and how the support link is generated. resources/js/ext.translate.editor.js prepares the HTML a element for it but not its href contents.
If we had something like support.issues or support.issues.i18n in extension.json to override the current default, then it would have to contain at least a placeholder for the message ID, possibly more.

Okay, I do not mind much for now, but my suggestion and the request you merged it to are considerably different for users.