Since 2023, Wikimedia Phabricator is really Phorge.

• the setlocal isn't supposed to make a difference (it only applies the command string itself - ie if a file is named 🧆.txt.
• Setting E is more likely to cause this problem then to solve it...

I think these two are related here:

• https://secure.phabricator.com/T13060 (call setlocal in the master php process, so everything is always en_us)
• T15281 and https://secure.phabricator.com/T12071 (Env-vars are missing because of E)

(I'm able to reproduce. Had to apt-get install language-pack-hu for that...)

When I said inconsistencies, I was talking specifically issues where certain UI elements have the original English version of the text, while others have the "translated" Pirate English version of the text.

I don't think that Pirate English should be consistent. Anyway I think that "Subscribers" should be translated in Pirate English and that is a bug. But what is the "Task history"?

There is a thread to translatewiki.net about adding Phorge: https://translatewiki.net/wiki/Thread:Support/Adding_Phorge_for_translation%3F.
Wikimedia must first migrate to Phorge to add it into translatewiki.net.

A highly unfortunate side-effect of T15077: Rebrand: Tracking task is that it will invalidate a ton of translations. My guess is that upstream did not want to maintain these translations as part of the release product, possibly due to not requiring translations be part of the Phabricator release process. If we pull them into the Phorge codebase then we would likely need to update all translations for any text changes made during development, prior to release. I think it would make sense to host the translations in a repository here but I would worry about them quickly falling out of date. Handling of translations is likely a larger-sized project that we would need help managing.

Well, there are inconsistencies. For example, subscribers are called "spies" in the task overview, but "subscribers" in the task history, and "spies" again in task actions.

It is not very clear to understand where the problem is and how to try to help improve it. I am not familiar with Pirate English. Other than adding "Arrr." I mean.