The evidence report (#33) is written entirely in English, in a project whose Spanish half is the reason it exists.
A teacher using the Spanish interface presses a button labelled Guardar reporte, and gets a document titled Reporte de análisis de escritura whose every other word — the score, the caveats, the checkable facts, the citation issues, the "how often this is wrong" section — is in English. FolderToHtml additionally hardcodes lang="en" even though the single-document report takes its lang from the analysed text.
That is not a polish item. The caveats are the part this project insists must be read, and they are the part a Spanish-speaking committee cannot read. A page that says "A score is not proof" to someone who does not read English is, functionally, a page that says only the score.
What it needs
All report prose moves out of src/SignsOfAI.Core/Reporting/EvidenceReport.cs and into the rule packs' messages — the same mechanism PackMessages already uses for the analyzer's wording, so a new language ships a report along with its rules, with no C# and no compiler. That keeps it consistent with the project's rule that extension points are JSON anyone can contribute.
Two things to be careful about:
- Which language. The report should follow the analysed text, not the interface, exactly as the findings already do — a Spanish teacher marking an English essay wants the English tells quoted verbatim. But the caveats and the "how often this is wrong" section are addressed to the reader, not about the text, so they should follow the interface. That split is the same distinction the app already draws and already documented as looking like a bug when it is not.
- Fallback wording.
PackMessages falls back to English on a missing key, which is right for a finding message and wrong for a caveat: a half-translated report that silently drops "this is not proof" into English is worse than one that admits it has no translation. The caveat needs an explicit "not available in this language" path.
Until then
The report is honest but only to English readers, and it should not be presented to Spanish-speaking teachers as finished.
The evidence report (#33) is written entirely in English, in a project whose Spanish half is the reason it exists.
A teacher using the Spanish interface presses a button labelled Guardar reporte, and gets a document titled Reporte de análisis de escritura whose every other word — the score, the caveats, the checkable facts, the citation issues, the "how often this is wrong" section — is in English.
FolderToHtmladditionally hardcodeslang="en"even though the single-document report takes itslangfrom the analysed text.That is not a polish item. The caveats are the part this project insists must be read, and they are the part a Spanish-speaking committee cannot read. A page that says "A score is not proof" to someone who does not read English is, functionally, a page that says only the score.
What it needs
All report prose moves out of
src/SignsOfAI.Core/Reporting/EvidenceReport.csand into the rule packs'messages— the same mechanismPackMessagesalready uses for the analyzer's wording, so a new language ships a report along with its rules, with no C# and no compiler. That keeps it consistent with the project's rule that extension points are JSON anyone can contribute.Two things to be careful about:
PackMessagesfalls back to English on a missing key, which is right for a finding message and wrong for a caveat: a half-translated report that silently drops "this is not proof" into English is worse than one that admits it has no translation. The caveat needs an explicit "not available in this language" path.Until then
The report is honest but only to English readers, and it should not be presented to Spanish-speaking teachers as finished.