6.0.1-RC7

Solving more detected bugs running under J5.2

com_localise-6.0.1-RC7.zip

6.0.1-RC6

• Update fr-FR language (ty @fontanil)
• Keep alive session when editing a translation
• Minor bug fixes

com_localise-6.0.1-RC6.zip

6.0.1-RC5

Fixing language files with content issues reverting the string to en-GB.

com_localise-6.0.1-RC5.zip

6.0.1-RC4

Continue adding fixes to minor issues detected to run with J5.

6.0.1-RC3

To install with Joomla 5.
Solving some new detected bugs.
com_localise-6.0.1-RC3.zip

6.0.1-RC2

Solving some bugs under Joomla5.
jmlocalise-6.0.1-RC2.zip
Installable package

6.0.1-RC1

To test with Joomla! 5.

5.0.1-RC3

Continuing with the task and basic explanations on the operation that JM Simonet left at the Previous release of com_localise 5.0.0-RC1

This version of com_localise is Joomla 4.0 ready:

• Uninstall all former versions on a local instance of J4 and install this one.
• Using en-GB as admin language can help to create the setup.

You may have to modify some php.ini parameters to cope with large ini files.
Examples:

• max_input_vars = 10000
• memory_limit = 1024M
• post_max_size = 256M
• upload_max_filesize = 254M

Then make sure to load the Languages view first and then Options to set your parameters.

If you enable en-GB reference language and development (screenshot above, advised), save, open the Translations view, select client and the target language, it will take some time to get the display. This is normal as it fetches through github the last 4.X-dev ini files and then compare them to your language.

NEW AT COM_LOCALISE 5.0.1-RC3
The default edition mode now have a new look, which gives more flexibility to add features. Such as the language RTL or LTR direction:

FILTERS
The 'Improved keys filters' now allow handle from the language to translate keys that are not in en-GB reference such as 'Deleted in en-GB', 'Renamed in en-GB', 'Extra in translation' and 'Personalised plurals' key cases:

PARSER
Added at translated language strings edition a parser for placeholders type {}, %1$s, etc and HTML comming form the en-GB language and, if not 'False positive', to keep equal in the language to translate.

From translations view you can now filter by 'Content State' >> 'Issued'

And then at edition view filter by "Issued string"

PLURALS

If your original installed language pack has been done on crowdin, the default plural forms (when they are simple, as en-GB) are not the en-GB default one... (Grrr)

• If you intend to go on translating on crowdin and just use com_localise to check errors, etc., then keep the crowdin plural forms.
• If you drop crowdin (except for the installation part), you can safely delete the crowdin plurals (ONE, OTHER) and translate as usual the en-GB variant in the normal section.
• Due there is no way to handle plural cases without dump false positives when missing root key, and currently that en-GB root key for plurals is not necessary have to exist, some plural cases can to be undetectables by this code, and, your personalised ones for that cases be displayed as "Extra keys in translation" (Grrr2).

The good news is that all plural cases than follow the basic rules (almost all them) can to be detected by the com_localise code:

OTHER
Settings as Complete, Copyrights, etc. should be similar to com_localise for J3.
Package making is simplified.

Please post any issue in this repo.