patternfly / patternfly/patternfly-mcp

Review locale integration

Open
#151 0 comments 0 reactions 1 assignee View on GitHub

@cdcabrera is already working on this.

Since Apr 1, 2026.

PF Team
Dominant language
TypeScript
Stars
5
Forks
11
Avg merge
3d 5h
Merged PRs (30d)
17

Description

As a developer and maintainer it would a general improvement to expose and allow locales for the various strings that are used for logging and markdown display.

Acceptance criteria

  • Review viability and effort ONLY, this is not an implementation issue

    • review viability of server locale settings being processed from host
      • this should account for any locale the llm/model my be running in
    • review a cli and programmatic locale override for scenarios we can't foresee
    • review available packages

Assumptions and questions

  • Our doc resources are primarily en-US this may end up being easier referencing a standalone translation mcp outside of this work

  • Since we have to compile the server having the locales compiled alongside or within our dist is feasible

  • A standalone directory, or underneath src, containing some level of JSON, sans TypeScript might work, but it would be a developer-nice to having Typing annotations pop up for the string identifiers instead of having to reference the files.

  • Server logs would be easier if we migrated towards "codes" vs burning cycles on "admin locale"


Jira Issue: PF-3886

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.