Closed kathy-phet closed 1 year ago
Oops sorry, I'll repeat https://github.com/phetsims/rosetta/issues/329 over here:
Hello! I spent 15 minutes and wrote a script that should show every translation in which the current value of a translated template string key does not match the english version in master. I think it will at least be a good starting point, but it is worth noting that there may be a disconnect between published sims and master. Please also note that this does not look at any values of the babel translation "history", just the current value.
I think it would be good to think of figuring out if/how all of these should be changed, as opposed to just handling for molecule polarity. Perhaps a more common issue?
It wasn't clear to me if we should do this via rosetta interface, (which will likely help by triggering a rebuilt of the production version), or something else that is faster and more behind the scenes. Over to you @kathy-phet to see the scope of the issue (beyond molecule-polarity) and to recommend who should lead the assault!
Transferring this issue to babel. It's not specific to molecule-polarity, it's a problem in many sims, as demonstrated by the "Results" in https://github.com/phetsims/babel/issues/18.
@kathy-phet can you please prioritize this?
@oliver-phet - If you can take care of Molecule Polarity by next Tuesday that would be great, and since I don't think it will take a lot of time just finish the list off before you leave for the holiday, and close this issue that would be ideal. Since we know Rosetta won't let this happen again, we can just fix these and be done. Thanks!
@kathy-phet @oliver-phet and I spoke again today. We are most worried about https://github.com/phetsims/rosetta/issues/329 and if translators can continue to make this mistake, but when it comes time to fix things, here is a more accurate script that compared the release branch en strings to babel, instead of using master. I also fixed a bug where non ascii chars were not being printed in the results:
QA ran into this for the scenery-phet ht
strings (listed above) over in https://github.com/phetsims/friction/issues/315. @oliver-phet what is the current status on this issue? Can we prioritize that fix? Should this be blocking the publication of friction?
QA ran into this for the scenery-phet
ht
strings (listed above) over in phetsims/friction#315. @oliver-phet what is the current status on this issue? Can we prioritize that fix? Should this be blocking the publication of friction?
I don't have any updates on this. I'm still on hold to do any manual fixes until either
I can do the manual fixes whenever, but it seems that until the pattern validation is fixed this issue can continue to occur. @kathy-phet I think this is your call. Do you want (probably @jbphet @liammulh) to try to fix the validation issue in Rosetta 1.0? Wait until Rosetta 2.0 is published? Or just do manual clean up now (and possibly again)?
@oliver-phet - I discussed with JB before break. I think you should do the manual fixes now. There will not likely be very many additional breaks, since we have not figured out how to even reproduce it.
@oliver-phet, I see https://github.com/phetsims/babel/commit/8fb649d97bc7bae09ea91fff2d3266d97430ea71 came in. Could you please give an update for this issue? Perhaps it was all covered over in https://github.com/phetsims/rosetta/issues/329 (now closed?)
Sorry, I forgot there were 2 issues about this. All the pattern fixes (identified by @jbphet 's script output) were made in https://github.com/phetsims/rosetta/issues/329
If there's something else for me on this issue, let me know!
Awesome! I confirmed my specific bug is fixed on master with https://github.com/phetsims/friction/issues/315, and will be picked up in the next rc/production deploy.
In issue https://github.com/phetsims/rosetta/issues/329, we note that some translations have "translated" the strings that are within a code pattern. These strings need to remain as original strings, for the code to correctly work. They are basically variable names, not actual text that needs to be translated.
We need to find the translations where the code pattern was mistakenly translated, and fix it. We will do this by hand for the Molecule Polarity strings. Over in https://github.com/phetsims/rosetta/issues/329, we are investigating if babel allows this error to happen now or whether it has a fix already in place.
@oliver-phet - Can you please go through the existing translations, and inspect this row
pattern.dipoleDirection | {{from}} → {{to}} -- | --And if it reads anything differently from the English, replace it with the English version. {{from}} → {{to}}
And do so without changing the credits? @zepumph - I think you mentioned you might be able to make a quick script to see which translations needed this hand fix?
Here is a short list CM started: