i18n fr-CA Lint — Quebec Bill 96
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Finds the France-French and left-over English lines in your fr-CA locale file before an OQLF complaint does.
Install
i18n-fr-ca-bill96-lint file
Node 18+. The same 9 rules as the VS Code extension, from a terminal or CI.
Free
- Lints the fr-CA locale file you have open with all 9 rules — fr-FR term, English left untranslated, euro currency, slashed date, English number separator, unaccented capital, empty or TODO value, fr-FR locale tag, anglicism — and prints every hit with its line number and the Quebec wording to use instead. No licence key.
--ruleslists every rule
With a licence ($29 once)
- Sweeps every locale file in the workspace in one command, writes the findings to a Markdown report and to a CSV or JSON export you keep, and returns a CI exit code so a bad French build fails the pipeline. $29 once, one licence key per person or CI seat.
i18n-fr-ca-bill96-lint --dir ./templates --report html --out report.html
A Canadian language-service provider bills fr-CA revision at $0.10 to $0.15 a word; a 12,000-word UI string set is $1,200 to $1,800.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "i18n-fr-ca-bill96-lint": { "command": "i18n-fr-ca-bill96-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: i18n fr-CA Lint — Quebec Bill 96
run: pip install rulestamp-i18n-fr-ca-bill96-lint && i18n-fr-ca-bill96-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-i18n-fr-ca-bill96-lint
i18n-fr-ca-bill96-lint --help
Metadata
Release files for rulestamp-i18n-fr-ca-bill96-lint 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_i18n_fr_ca_bill96_lint-1.0.4.tar.gz | 16.8 kB | Without provenance | Details for rulestamp_i18n_fr_ca_bill96_lint-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_i18n_fr_ca_bill96_lint-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_i18n_fr_ca_bill96_lint-1.0.4-py3-none-any.whl |
Total release size: 35.9 kB
Release files / rulestamp_i18n_fr_ca_bill96_lint-1.0.4.tar.gz
| Download URL | rulestamp_i18n_fr_ca_bill96_lint-1.0.4.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b5ec182401405c4618f35ce03cca07140e208f219ae98163f1437cff2a7e998
|
|
BLAKE2b-256 checksum How to use checksums |
4e6715565d15883c282b23ec387fc5850d5a3d6525c18d2a0c358a0566bbe9af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_i18n_fr_ca_bill96_lint-1.0.4-py3-none-any.whl
| Download URL | rulestamp_i18n_fr_ca_bill96_lint-1.0.4-py3-none-any.whl |
|---|---|
| Size | 19.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddd0fcf471ccaab3349d09bd69bcf63ea1ca4ff9004e86a5d4872603d4ad72d0
|
|
BLAKE2b-256 checksum How to use checksums |
8c8c845ae1af49767942b923f2d3dca84c08f1a8689bd819382dc609d2bbd4d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-i18n-fr-ca-bill96-lint 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.