Page MenuHomePhabricator

The future of Language Converter (or, why do [[Red]] and [[Orange]] spell colo(u)r differently?)
Closed, ResolvedPublic


Let's talk about Language Converter, Content Translation Tools, and wikis split by language variants.

Should zhwiki split for mainland China and Taiwan?

Should we be using LanguageConverter on enwiki to handle British/Australian/Indian/American spelling differences?

Should we be using Content Translation Tools for Catalan and Spanish?

Perhaps Swiss German and "High" German should be different wikis? Or use LanguageConverter? Or use Content Translation tools?

How do we best edit content which has slight localized differences?

Let's discuss!


Event Timeline

cscott raised the priority of this task from to Needs Triage.
cscott updated the task description. (Show Details)
cscott subscribed.

Should zhwiki split for mainland China and Taiwan?
Perhaps Swiss German and "High" German should be different wikis?

Those are decisions made with a very clear process via the LangCom, it's useless to discuss them out of process.

I don't agree that it is useless to discuss them from a technical perspective, since such decisions by the community have technical implications.

And to be clear -- these were questions to prompt discussion, not attempts to make proposals that would be binding or enforced or anything like that. I don't have that kind of power!

So, when we ask, "Should swiss german be a different wiki" what we are really asking is for us to consider the technical (and social, and political) considerations that went into the current state of affairs. Part of this reasoning involved the difficulty of maintaining forks, the ease of use issues with respect to language converter, etc. We can then have a discussion about whether or not maintaining forks ought to be easier, whether we should work harder to improve the user experience of language converter, etc. If we decide to do this work and make accomplishments, perhaps the community would make different decisions. Or perhaps they won't! They may be too invested in the current state of affairs. If so, perhaps it's not worth doing the work in the first place. Or perhaps it should be done because it will help other, less established communities, etc. I think it is worth discussing these issues, to decide what technical things are worth our attention.

At any rate, the point is to start a discussion and think hard about the underlying issues. The result of the discussion is certainly not going to result in a proposal to LangCom at this stage! But it may result in people thinking differently about what our software could/should be able to do.

Spage set Security to None.

Thanks for presenting your session, I updated the task description with links (it seems no one took notes in the Etherpad). Can you add a comment with

  • approximate number of participants
  • any Phabricator tasks resulting from your session
  • any other achievements
Qgil claimed this task.