Rubidium wrote:

Looking at the strings it gives me the following "feeling"; I've not tested it nor looked at the code:
Looks like it always looks at the gender of the string in front of it and because there isn't a string in front of it, the gender is the first one (i.e. male). Though that does not give a reason why the posadzon* one fails, though getting the gender once might reset it too.

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1790

Meush wrote:

I always had impression that industry related strings are awkward, beginning from industry name (like "{TOWN} {INDUSTRY}") in industry window and subsidies. But that's different topic.
Rubidium, would you like me to rearrange curly brackets to trace the problem? How to rearrange them?

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1791

Rubidium wrote:

It's caused by the cases; the cases push the gender information further into the string and places a "string with cases" marker at the beginning of the string, where the gender determination algorithm expects the gender information to be.

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1796

Meush wrote:

That's great you found it, may we expect a fix soon? :)

Just for clearness, my strings have gender information also in cases:
STR_00FA_COAL_MINE.d
{BLACK}{TINYFONT}{G=f}Kopalni węgla

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1797

Rubidium wrote:

Ok, I think I've solved it. It was a combination of my first hunch and the cases issue. Genders are always retrieve of the next string unless you override that by defining the string (index) to override. As you can see in the next line, I've added the two 0s, so they take the gender of {STRING} instead of town.
For the sake of this test I've given forest (Las) a sexchange, so it is female in this example.

STR_482E_NEW_BEING_PLANTED_NEAR :{BLACK}{BIGFONT}Now{G y a e} {STRING} został{G 0 "" a o} posadzon{G 0 y a e} blisko {TOWN}!
now gives me "Nowa Las została posadzona blisko {TOWN}!". Is that correct (Las is female in this case).

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1798

Meush wrote:

Yes, that's right :)
I will edit these strings soon.

Is change in code required, or editing strings alone will do the job?

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1799

Rubidium wrote:

Code changes are also required, but they'll most likely get to trunk before your changed strings do.

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104#comment1800

Rubidium closed the ticket.

Reason for closing: Fixed

In r10792. At least the code changes, the langfile changes (adding two 0s) are still to be done via WT2.

This comment was imported from FlySpray: https://bugs.openttd.org/task/1104