4.0 does not yet have dedicated resources for languages, so the 3.x language list is still shown, with the hack in place to allow some capabilities to work for that list of three languages.

Personally, I wouldn't spend much time on this issue. It'll address itself as 4.0 moves toward a stable release and dedicated architecture for the language resources is set up.

I'm concerning Volunteers to inform which Language is installable at the Moment. If its not possible to inform at Installation of content Languages i will let this Issue open.

We can do something about it, sure. But my main point is this is one of those things where the time it would take to do something about it is better spent elsewhere. It is not that German, French, or Persian are the only languages available for 4.0; rather, those three languages have special handling in the 3.x update server files so they show up somewhere (I forget where exactly we needed to add this special handling). Technically, there are no languages available for 4.0 right now and instead of showing empty or broken screens that prevent being able to test any of the language install functionality we just continue showing the 3.x data until the 4.0 system is set up.

Right now, the actual "bug" is 3.x language data is shown to a 4.0 install. The fix to that is to set up the 4.0 language system on our joomla.org hosting and update 4.0 to read from that. Until that happens, we either completely turn off the ability to install languages through a Joomla installation, or we continue showing the 3.x data. I don't think we need to be adding extra code to account specifically for the current development status when everyone's time is better spent on other tasks to get 4.0 in a release ready state.

Simple Solution is to let the Info here stay; no Time waste for it.

Days ago a Volunteer asked cause he installed it-IT ... and nothing happens. Next Time Tester can find Info here.

I forget where exactly we needed to add this special handling

Found it the other day ;)

https://github.com/joomla/update.joomla.org/blob/master/translation-cli/translation_cron.php#L279-L284

Right now, the actual "bug" is 3.x language data is shown to a 4.0 install. The fix to that is to set up the 4.0 language system on our joomla.org hosting and update 4.0 to read from that.

Can someone add the release blocker tag to this please

Just for the record whilst this is indeed a blocker - I don't intend this to be solved for a bit yet - I'd rather we fix this when we're a bit further into beta. gives people easier capabilities to test things for now

We’ll swap this over once we launch the ability for new J4 packs to be added on the downloads site

Until resolved this is still a release blocker.

Language pack component https://github.com/joomla-extensions/pkg_languagepack has been installed on the downloads site. Currently we're working on the sync mechanism so the update XMLs go to the update.joomla.org site (i.e. a new version of this CRON Job to the GForge SOAP API https://github.com/joomla/update.joomla.org/blob/master/translation-cli/translation_cron.php)

joomla-extensions/pkg_languagepack#43 Now the XML view exists - just a matter of copying it onto the update site. Closing this as I've build a PR that can be merged as soon as that copy job is up and running #34302