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
There is a similar, but distinct, issue with variable resolution order like #63, which manifests when using e.g. both $who and $someone in the same tidbit. Pronoun vars like $heshe will always use the last value resolved, so in this example:
$who will grow to be very $adjective. $Heshe will $verb $adverb, and often.
However, their childhood friend $someone will intervene just in time, and
$heshe will marry the one who saved $himher.
$someone is resolved after $who, so all instances of $heshe, $himher, etc. will use $someone's gender, even the ones that occur in text before $someone. (In this case, even the ones after $someone also refer to $who, though.)
In a perfect world, Bucket would understand to which subject each $himher etc. refers and use the correct gender, but that's well beyond what processing currently happens to tidbits.
I don't think there's a simple way to solve this, which is probably why I put off opening an issue about it for so long, but users have been asking about it a fair bit recently so I wanted to have an easy link to reply with that explains the bug. 😅
The text was updated successfully, but these errors were encountered:
There is a similar, but distinct, issue with variable resolution order like #63, which manifests when using e.g. both
$who
and$someone
in the same tidbit. Pronoun vars like$heshe
will always use the last value resolved, so in this example:$someone
is resolved after$who
, so all instances of$heshe
,$himher
, etc. will use$someone
's gender, even the ones that occur in text before$someone
. (In this case, even the ones after$someone
also refer to$who
, though.)In a perfect world, Bucket would understand to which subject each
$himher
etc. refers and use the correct gender, but that's well beyond what processing currently happens to tidbits.I don't think there's a simple way to solve this, which is probably why I put off opening an issue about it for so long, but users have been asking about it a fair bit recently so I wanted to have an easy link to reply with that explains the bug. 😅
The text was updated successfully, but these errors were encountered: