Page MenuHomePhabricator

change shy-latn to shy (translatewiki)
Open, Needs TriagePublic

Related Objects

Event Timeline

Makes sense to me.

@Raymond, @abi_, @Nikerabbit - what's the right way to make shy in the Latin alphabet primary?

Here's the current situation:

What should be?

  • What should be in Names.php? Leave it as is or change it to shy?
  • Somehow there is nothing with shy in language-data. I'm open to other suggestions, but I'm inclined to making Latn the default:
shy-latn: [shy]
shy-tfng: [Tfng, [AF], ⵜⴰⵛⴰⵡⵉⵜ]
shy: [Latn, [AF], Tacawit]

I don't want to rename language codes in translatewiki.net - it's too much effort and there is no tooling for that. Just move MessageShy-latn.php to MessagesShy.php and add $fallback = 'shy' and entry to Names.php. I think that is sufficient with the language-data changes you propose.

OK, just to be sure:

  • Will the JSON files remain at shy-latn? Or will they start going to shy,json? It's already exported to core and a bunch of extensions.
  • Should language-data be as I proposed? Will that be convenient for selecting the target language in translatewiki?
  • If a Wikipedia domain is created at shy.wikipedia.org, will it work correctly with compact language links?

When the fallback is set shy and shy-latn will be essentially be the same. As a follow-up shy-latn can be hidden from users, but that is more difficult to do.

And we should add shy to the list of blocked language on translatewiki.net to avoid translations appearing both under shy and shy-latn.

We now have tooling for renaming languages in translatewiki.net.

It will be great =) thank you for the information!
Can you do that?

I'm rather busy at the moment, but if Amir or someone else leads the process, I can run the scripts.

Hi, how can I lead the process? If I can of course.
What I have to do? can you explain it to me, please?

With leading I basically mean having a plan (written down) what are all the changes that need to be done and in which order so that nothing breaks as well as figuring out who needs to be consulted/informed.

I believe we should do the reverse:
If a spoken language is written in (and translated into) more than 1 script, we should always specify script.

I would say those are some kind of unmigrated / historical to-dos.