Open liammulh opened 1 year ago
Thanks @liammulh, sorry about that. Would it work to do a maintenance release on the published sim somehow? Republishing from master would be very difficult at this point.
Would it break anything to just remove them and their usages from the published 2.3 branch?
A round of maintenance releases has completed and a new one will begin on Tuesday. We have a little window until then to do work in release branches.
Would it break anything to just remove them and their usages from the published 2.3 branch?
It wouldn't break anything from the perspective of the translation utility. However, if you're going to change things on the published 2.3 branch, and you're worried about something breaking, why not prepend the .description
string keys with a11y
? For example, netForce.description
would become a11y.netForce.description
or a11y.netForce
?
The translation utility prevents string keys with a11y
in them from being translated, so these string keys would no longer show up in the translation utility. And then since the string keys would still be present in the sim, presumably nothing would break.
That being said, if you think removing these string keys wouldn't break anything in the sim and would be easier than what I suggested, then go ahead and remove them.
Thanks @liammulh, great. If it's safe to remove them I will go ahead with that.
@jessegreenberg showed me that these strings have a visible
key, which is set to false:
This is the old way of hiding string keys, and I think at some point the translation utility stopped supporting this. However, it would be (I think) easy to add a patch to the translation utility to hide these string keys.
I am going to transfer this to Rosetta.
Actually, I can't, lol. Never mind.
I caused this regression by not implementing the following:
@jessegreenberg, please close this issue and comment in https://github.com/phetsims/rosetta/issues/411 when you republish FAMB off of master.
It looks like FAMB has some old non-Kosher a11y description string keys:
We don't want translators to translate these strings, but we can't really strip these string keys out programmatically because there are other valid string keys with
.description
in them.It looks like on master, these string keys are no longer present, so one way to fix this would be to republish from master.
Assigning @jessegreenberg since he is the responsible dev for FAMB.