With the version 2.4.7 we changed the format of the language strings a bit. This was because of the allowed but IMHO dirty format of strings as not enclosed string values in the language files. In that format it wasn't possible to set an explicit value i.e. only with a space.
format until now:
name_of_key = Value of string text_of_an_email = """Hello [username] Welcome in the forum. A concentrated form of words in the e-mail-templates wasn't and will not be a problem. Good bye""" string_with_apostrophe = This wasn't a problem until now
format from now on:
name_of_key = 'Value of string' text_of_an_email = """Hello [username] Welcome in the forum A concentrated form of words in the e-mail-templates wasn't and will not be a problem. Good bye""" string_with_apostrophe = 'This isn\'t a problem from now on'
Please mention the different handling of apostrophes within strings. Apostrophes inside a one-line-string must be masked with a backslash (old:
wasn't => new:
wasn\'t). This affects only one-line-strings that are from now on enclosed with single quotes (
'). Multiline strings, that are enclosed in
""" are not affected by the necessity of masking.
Additionally, the change of the format can actually have the side effect of cropped strings in the present language files. Even with a scrutinised search in the files it is possible to have missed a few occurences of apostrophes inside strings. The string gets cropped at the first occurence of an unmasked apostrophe.
key_of_a_string_with_forgotten_masking = 'It isn't impossible to miss occurences.'
If one finds such a bug, please solve it yourself in a first step with searching for the string in the language file, masking the apostrophe (
\') and testing it. Please leave a report afterwards in this thread or as a Github issue if you have a Github account.
Thank you, tschö, Auge