-
Notifications
You must be signed in to change notification settings - Fork 356
[SR] Prepare strings for translation - Add context to interactive graph strings #2407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…nslation - Add context to interactive graph strings
Size Change: +1.36 kB (+0.29%) Total Size: 466 kB
ℹ️ View Unchanged
|
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (6bb64d0) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR2407 If you are working in Khan Academy's webapp, you can run: ./dev/tools/bump_perseus_version.js -t PR2407 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, this is a lot of strings! I found a few things that don't look quite right, but most of this LGTM.
srQuadraticGraph: { | ||
context: | ||
"Aria label for the container containing a Quadratic function in the interactive graph widget.", | ||
message: "A parabola on a 4-quadrant coordinate plane.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
message: "A parabola on a 4-quadrant coordinate plane.", | |
message: "A parabola.", |
Why mention the number of quadrants shown in the graph? I don't think this is actually correct; e.g. the graph might only show quadrant 1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we added "4-quadrant" this time because so many of the related strings refer to the quadrant number that something is in. Even if the vertex doesn't show up on the graph, it'll read the quadrant that it's in.
It's a fair point though. Since this would require copy updates from a designer, I'm going to punt it to the phase 2 string updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The contexts you've added to the strings are GREAT! Absolutely love it, thank you!
@@ -505,7 +504,6 @@ export type PerseusStrings = { | |||
point2X: string; | |||
point2Y: string; | |||
}) => string; | |||
// The above strings are used for interactive graph SR descriptions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually liked having this context, as the organization made it easier for our future selves to quickly find the chunk of strings! I'm not fussed either way, however as I know we have some great context on the strings themselves. :)
Co-authored-by: Ben Christel <[email protected]>
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @khanacademy/[email protected] ### Patch Changes - [#2407](#2407) [`016357a5b`](016357a) Thanks [@nishasy](https://github.com/nishasy)! - [SR] Prepare strings for translation - Add context to interactive graph strings ## @khanacademy/[email protected] ### Patch Changes - Updated dependencies \[[`016357a5b`](016357a)]: - @khanacademy/[email protected]
Summary:
We held off on translations until now, beacuse the Interactive Graph strings were
still in flux. Now that they're finalized, we can send them in for translations.
I added context to all the strings that need to be translated so that
the context is for each individual string.
Since these are going to count as new strings, they'll trigger the
action on the PR that will create a translation ticket for us that's
pre-populated with all new strings.
NOTE: This PR is probably easier to review with the "Hide whitespace" option.
Issue: https://khanacademy.atlassian.net/browse/LEMS-2660
Test plan: