Skip to content

docs(tm): Correct the Memory location and document the toggle - #165

Open
KevinJump wants to merge 1 commit into
masterfrom
docs/tm-17.9.0-memory-location
Open

docs(tm): Correct the Memory location and document the toggle#165
KevinJump wants to merge 1 commit into
masterfrom
docs/tm-17.9.0-memory-location

Conversation

@KevinJump

Copy link
Copy Markdown
Member

Part of the 17.9.0 documentation. Review only — please don't merge yet, the four TM 17.9.0 docs PRs are best read together.

Why

The Translation Memory page tells people to go to Settings → Translation Manager → Memory. That is wrong as of 17.9.0 — Memory moved into the Translations section. Anyone on the current version follows that sentence and doesn't find it.

What changed

  • Corrected the location, with an upgrade note for people who can't find it.
  • Documented the MemoryEnabled config toggle, including that turning it off leaves stored entries alone.
  • Noted that seeing the screen now needs the View translation memory permission.

Wants a screenshot

memoryEntries.png still shows the old Settings location and should be retaken from the Translations section. I can capture it but can't write PNGs into the repo from here, so it needs doing by hand — the screen is Translations → Memory with a connector row showing total and approved entries.

Note on links

Links to ../getStarted/upgrade#… resolve once the upgrade/config PR merges. onBrokenLinks is warn in this repo, so nothing breaks if this merges first.

🤖 Generated with Claude Code

Translation Memory moved from Settings to the Translations section in
17.9.0, so the "go to Settings -> Translation Manager -> Memory" line was
wrong for anyone on the current version. Adds an upgrade note for people
who can't find it, the MemoryEnabled config toggle, and a note that seeing
the screen now needs the View translation memory permission.

The screenshot still shows the old location and wants retaking.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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