[0.17.66] Locale entries starting with a space are ignored.

[eradicator]

What?

A locale entry whichs value starts with an ASCII space is treated as an unknown key:

Code: Select all

stockpile-logistic-infix= (__1__)

Entries that start with a *visual* space or a new line or a full-width space (UTF8) work fine:

Code: Select all

stockpile-logistic-infix=[color=default] (__1__)[/color]
stockpile-logistic-infix=\n(__1__)
stockpile-logistic-infix=　(__1__)

[steinio]

Spaces are not allowed anymore before and after the =.

[eradicator]

Spaces are not allowed anymore before and after the =.

Non-Ascii spaces work just fine in the value (and i'm not talking about the key). If they're actually not supposed to work it would be nice to throw an error. But honestly i'd prefer if i didn't have to use hacks like color=white rich-text tags or non-ascii spaces for such a simple thing.

[Pi-C]

Spaces are not allowed anymore before and after the =.

Are you sure? Here's what the Localisation Tutorial on the wiki says:

Any whitespace after or before "=" is included in the key or string, so "title =Category" related title will give an unknown key error if you are looking for the "title" key, since it is the "title " key.

[Rseding91]

Thanks for the report however no they aren't:

Capture.PNG (24.15 KiB) Viewed 1063 times

[eradicator]

Thanks for the report however no they aren't:

Capture.PNG

Odd. Can't reproduce it anymore. Thanks for checking it out, and sorry for the fuss.