Unable to follow instructions in readme

Same problem for me. I am not able to see the Enable 'Administration language'" option

I tried using this module and had similar challenges. I found that going to the "Detection and selection" page and enabling "Customize Content language detection to differ from Interface text language detection settings" in the "Content language detection" section at the bottom, and then making sure URL is enabled there. That got the correct translation to load in the edit interface.

With the above change, I was able to enable "Account administration pages" in the "Interface text language detection" section at the top of the "Detection and selection" page, at which point I was able to set my own account to always use English for the "Administration pages language", using core. The only downside of this approach is that each user must make this change for their own account, which may not always be ideal.

Same for me: I am not able to see the Enable 'Administration language'" option too.

But I find the solution for my need: in the user administration, you can set the administation there: you don't need this module for that! I'm new in Drupal 8/9 and I didn't know it's possible.

When the user language is set to "no preference" the module takes no action, even if the user language is or is not in the detection scheme.

Manual needs to be updated to explain that this adds a controller in the USER.
OR adapt the module script to consider this.

I've had a play around with this module and initially didn't realise that core provides it's own administration page language negotiator, albeit without configuration of paths etc.

I've had a play around with the core one and this module's one and I can't really see why you'd need to use this module unless you had a specific requirement to enable it on specific paths that were not admin paths.

With the config out the box of this module, it doesn't cover all paths, e.g. the path for when you add a translation:

/<trans lang>/node/<nid>/translations/add/<default_lang>/<trans lang>, which can be rectified by adding the path to the module's config screen OR presumably enabling the 'apply on admin routes' toggle.

But at that point I'm pretty sure that is what the core negotiator is doing anyway, applying to any admin route (which is most likely what you want).

Both core and this one require the preferred administration language to be set on a per user basis. With an empty choice there either will appear to 'do nothing'.

So for my use case - sites with NB default language or DE default language and an admin language of EN desired ONLY on admin pages (not any customisable ones), I don't need this module, the core negotiator will suffice. The only use case I can see for this module over the core one is that you can can specify specific paths for it to apply. Whether that functionality is useful or not to you, you'd have to decide.

If you only want a specific language (e.g. EN) to apply to any admin routes then I feel you are probably better off just using the core negotiator and ensuring the admin language setting is set on any user profile that needs it to be.

@ALL the others here, you don't have to be a developer to provide improvements to the README.txt!

Could someone please provide a better README.md and I'm happy to review that.

Would be great, if someone could update the README.md and follow the steps. If issues occur, please report them.