problem language

[mehdininja]

Hello
The language of my site is persian and extensions language is persian. (joomla 4.4.0 no problem).

I updated Joomla from 4.4.0 to 4.4.1, but why did the language of some extensions become English !
What is the problem in joomla 4.4.1?

[toivo]

This sounds like the language strings in the language files have linebreaks, which are not allowed after the update to Joomla 4.4.1.

Code: Select all

<br> <br />

Edit the language files and remove the linebreaks.

This behaviour was reported yesterday and removing the linebreaks brings up the translated text:
Update to 4.4.1 and Helix-ultimate Template blip

[nacc]

My understanding of the issue, introduced in J! 4.4.1 and J! 5.0.1, is not that a language constant contains literally <br /> is taken from @brian's explanation on GitHub:

As can be seen there is one invalid string. Instead of it being on one line ending with " it is spread across multiple line

In other words, it looks like it is not valid to have a language constant defined as:

Code: Select all

CONSTANT_NAME="This is the translation
of the constant
spread over
multiple lines."

It would be acceptable to define the constant as:

Code: Select all

CONSTANT_NAME="This is the translation of the same language constant that does not have hard-coded line-breaks in it even though the translation may result in text that wraps over several lines."

I don't see how the following would be invalid:

Code: Select all

CONSTANT_NAME="This is the translation<br />of the constant<br />spread over<br />multiple lines."

[toivo]

@nacc, you are right. The HTML linebreak tags <br> are allowed. The lines I tested with had linebreak tags and extended into a second line. Once combined into one line, the translation worked.

[mehdininja]

hello
The problem is not from <br> <br />. The problem is with the new line.

PLG_Test="test1
test2"

[ceford]

What is the problem in joomla 4.4.1?

In J4.4.1 and 5.0.1, in LanguageHelper.php (3 instances), this line:

Code: Select all

                $strings = parse_ini_file($fileName, false, INI_SCANNER_RAW);

Replaced this line in previous versions:

Code: Select all

                $strings = parse_ini_file($fileName);

I think this was for security reasons. The outcome is that any multi-line string in a language ini file will cause the whole ini file to be skipped.