Skip to content

fix(node): update strings guide for three translation approaches#273

Closed
moss-bryophyta wants to merge 1 commit into
generaltranslation:mainfrom
moss-bryophyta:fix/node-strings-guide-accuracy
Closed

fix(node): update strings guide for three translation approaches#273
moss-bryophyta wants to merge 1 commit into
generaltranslation:mainfrom
moss-bryophyta:fix/node-strings-guide-accuracy

Conversation

@moss-bryophyta

Copy link
Copy Markdown
Contributor

The Node.js strings guide was written when there were two translation approaches (getGT() and msg()/getMessages()). After tx() was added, the frontmatter description and a callout still said "two" / "both."

Changes:

  • Frontmatter description: "Two approaches" → "Three approaches"
  • Callout: "Both approaches produce identical translations" → clarifies that getGT() and msg()/getMessages() are build-time equivalents, while tx() is for runtime
  • Fixed msg() link: pointed to /docs/node/api/get-messages (the getMessages page) → /docs/node/api/strings/msg (the correct msg page)

- description: "Two approaches" → "Three approaches" (tx() was added)
- callout: "Both approaches" → clarify getGT() and msg()/getMessages() are build-time, tx() is runtime
- fix msg() link: /docs/node/api/get-messages → /docs/node/api/strings/msg (correct page)
@moss-bryophyta
moss-bryophyta requested a review from a team as a code owner April 29, 2026 15:04
@moss-bryophyta
moss-bryophyta enabled auto-merge (squash) April 29, 2026 15:04
@moss-bryophyta

Copy link
Copy Markdown
Contributor Author

Closing stale docs PR — docs review is moving to a linter-based workflow going forward, and this backlog is now out of date (per Taylor). Keeping #372 and #373.

auto-merge was automatically disabled July 17, 2026 18:09

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant