Skip to content

Latest commit

 

History

History
29 lines (22 loc) · 1.38 KB

File metadata and controls

29 lines (22 loc) · 1.38 KB

Internationalization

i18n status: N/A

Reason: this is an operator-facing command line tool with no rendered surface and no end-user audience. Its input is a Power Content Label, a document California regulation prescribes in English, and its output is a finding that quotes English regulatory text back to the reader. Translating a finding while leaving the quoted requirement in English would make the output harder to verify against the source, not easier, and verifying a finding against its source is the whole point of the tool.

There are no user-facing strings in the product sense: every string the tool prints is either a citation, a quotation from a cited document, or a statement about a specific English phrase that was or was not found in the label.

What would change this

A Spanish-language Power Content Label. If the Energy Commission prescribes one, the matching terms in checks.py become locale-dependent and this declaration should be revisited along with them. Until then, adding a locale layer would mean translating the operator's copy of an English legal requirement, which adds a place for the requirement to drift from its source.

What is already locale-safe

Text normalisation in normalize.py runs Unicode NFKC and folds the typographic quote, dash and space variants that PDF extraction introduces, so matching does not depend on which tool produced the document.