Template Manager: Keep editor and file tree layout LTR when administrator is RTL

I am writing this here to get input from RTL users

When Joomla administrator is configured to use an RTL language, the two-column layout in the Template Manager's code editor is also reversed.

This results in the file tree appearing on the right-hand side and the code editor on the left-hand side.

Although this is consistent with the general RTL layout of the administrator interface, it is not necessarily appropriate for a code editing environment.

Current behaviour

When using an RTL administrator language:

• The file tree is displayed on the right-hand side.
• The code editor is displayed on the left-hand side.

Proposed behaviour

Keep the two-column layout of the template editor LTR, regardless of the administrator language direction:

• The file tree should always appear on the left-hand side.
• The code editor should always appear on the right-hand side.
• The surrounding Joomla administrator interface should continue to respect the selected language direction.

Why?

Code editors and IDEs conventionally place the file explorer on the left and the editing area on the right. Developers are familiar with this arrangement, and it provides a consistent experience regardless of the language they use for the administrator interface.

Additionally, filenames, directory paths and source code are predominantly written using LTR characters. Reversing the columns for RTL languages offers little benefit and makes the editing environment less familiar.

This is a specialised interface where maintaining a consistent layout is arguably more important than mirroring the entire interface.

Suggested solution

Set the direction of the container holding the file tree and code editor to LTR.

This should affect only the two-column editor layout, leaving the rest of the administrator interface, including toolbars, tabs and other controls, to follow the selected language direction.

Additional Work

There are some additional RTL oddities that need to be fixed in the template manager but this is a starting point