You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in any Joomla language file (ini format) , write some Chinese language character in the date string after the comment symbol like:
; @date 三 2013
Expected result
com_localise will ignore anything it can not parse in "comments" and go on to open that language file for editing.
Actual result
com_localise refuse to open that language file and return a warning message:
0 DateTime::__construct(): Failed to parse time string (三 2013) at position 0 (�): Unexpected character
System information (as much as possible)
Joomla v3.6.5
com_localise v4.0.29 dev
PHP 7.0
Additional comments
I think, "comment" is comment, it is not CODE. Why com_localise will treat comment contents as normal code? If com_localise can not understand the Chinese language in date string ( which in fact is in comment line), just skip it, and go on to open that file. Because, we use com_localise to check real language keys , not comments.
Thank you.
The text was updated successfully, but these errors were encountered:
Steps to reproduce the issue
in any Joomla language file (ini format) , write some Chinese language character in the date string after the comment symbol like:
; @date 三 2013
Expected result
com_localise will ignore anything it can not parse in "comments" and go on to open that language file for editing.
Actual result
com_localise refuse to open that language file and return a warning message:
System information (as much as possible)
Joomla v3.6.5
com_localise v4.0.29 dev
PHP 7.0
Additional comments
I think, "comment" is comment, it is not CODE. Why com_localise will treat comment contents as normal code? If com_localise can not understand the Chinese language in date string ( which in fact is in comment line), just skip it, and go on to open that file. Because, we use com_localise to check real language keys , not comments.
Thank you.
The text was updated successfully, but these errors were encountered: