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
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
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
Assumptions and questions
Our doc resources are primarily
en-USthis may end up being easier referencing a standalone translation mcp outside of this workSince we have to compile the server having the locales compiled alongside or within our
distis feasibleA 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