Add Arabic (ar) backoffice translation

[tarikrital]

Description

This PR adds a complete Arabic (ar.xml) translation for the Umbraco backoffice, covering all core areas (content, settings, users, etc.).

Motivation

• Improve accessibility for Arabic-speaking users.
• Encourage localization contributions for other languages.

Testing

• Verified translations in Umbraco v 13.8.1.

Preview:

[github-actions]

Hi there @wpplumber, thank you for this contribution! 👍

While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:

• It's clear what problem this is solving, there's a connected issue or a description of what the changes do and how to test them
• The automated tests all pass (see "Checks" tab on this PR)
• The level of security for this contribution is the same or improved
• The level of performance for this contribution is the same or improved
• Avoids creating breaking changes; note that behavioral changes might also be perceived as breaking
• If this is a new feature, Umbraco HQ provided guidance on the implementation beforehand
• 💡 The contribution looks original and the contributor is presumably allowed to share it

Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution.

If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

Thanks for providing this @wpplumber - will be good to provide better support for Arabic in the backoffice.

I wonder if you would be up for pairing this with a second PR for Umbraco 16 please - i.e. into main - that provides the equivalent update for the localization file format there? If so, thanks very much in advance.

This is primarily, but not solely, client-side in 14+: https://docs.umbraco.com/umbraco-cms/customizing/foundation/localization

I'm happy to pull this in for 13 too, but I wouldn't want to do it only for that and be in a position where we ship with something for 13 but not the newer versions.

Seems some have had some joy with AI in reducing the effort on this - see e.g. https://richardsoeteman.net/blog/converting-backoffice-language-files-using-chatgpt/

There was also a tool built to do this by a community member: https://github.com/liamlaverty/umb-localization-migrator

[tarikrital]

Welcome @AndyButland,

I'm available to provide it for V16. Thanks for mentioning the useful tools to simplify migration.

Honestly AI is a superpower for devs today but should be used carefully.

I'll let you know when the V16 PR is ready.

[tarikrital]

I think I don't have achance to contribute V16 yet! No need for other PR because Arabic language exist on V16.

[AndyButland]

So there is! Sorry, I guess someone had provided them before. Nonetheless, I'll give this a quick test and we can include it for 13.

[AndyButland]

Do you think this could/should be named ar.xml so for all Arabic, and not just Arabic (Morocco). Reason is if you look at the other languages we ship with, we only provide a country specific one if there's already a general language one. For example we have de.xml for German, and de-ch.xml for Swiss German.

If so, could you rename it to ar.xml?

And if there are certain phrases that you would want to provide a Moroccan specific translation, they can be in the ar-ma.xml file.

Although it doesn't look like this has bene done historically, the country specific file only needs to have records for those translations that are different from the main language file - it doesn't need all of them copied over.

[tarikrital]

Thanks @AndyButland, useful answer from you!

[AndyButland]

Thanks @wpplumber, all looks good to me having tested out locally. Really appreciated.

I just pushed a small update to fix up the language header now we have made this for Arabic in general.