araclean 0.2.0__tar.gz

araclean-0.2.0/.cspell/project-words.txt

@@ -0,0 +1,95 @@
+# Project & tooling vocabulary that is not Arabic-domain terminology.
+# The Arabic glossary lives in cspell.json `words` (ADR-0007); this file holds
+# the non-domain words cspell's bundled dictionaries don't already know.
+# One word per line; blank lines and `#` comments are ignored.
+
+# Unicode code points referenced in prose (cf. FEFF/FDFF in the glossary)
+FEFC
+
+# Unicode Standard technical vocabulary (UAX #15 / UCD), not Arabic-domain terms
+noncharacter
+noncharacters
+nonspacing
+precomposed
+doachashmee
+chashmi
+pepet
+
+# Domain-adjacent proper nouns
+Hijri
+Uyghur
+Jawi
+Pegon
+
+# ruff lint vocabulary (the ambiguous-unicode allow-list, RUF001-003)
+confusables
+
+# pytest / tooling config keys
+addopts
+testpaths
+excinfo
+capsys
+optionflags
+doctests
+
+# pandas / polars vocabulary (the dataframe-accessor docs, issue 0021/0022)
+dataframes
+tolist
+
+# Typer / CLI vocabulary (issue 0020): Typer's styled-echo helper
+secho
+
+# informal English used in the spec prose
+grabbable
+invisibles
+precomputes
+configurably
+elongatable
+disjointness
+toolkits
+
+# linguistics vocabulary (stopword handling, issue 0017) the bundled dicts lack
+clitics
+proclitics
+enclitics
+subordinators
+
+# emoji handling (issue 0013) — the `emoji` library's verb and its inflections
+demojize
+demojizing
+
+# release/versioning tooling (ADR-0008)
+Commitizen
+commitizen
+SemVer
+changelog
+
+# Python / ML / packaging ecosystem referenced in the ADRs
+stdlib
+vectorizer
+maturin
+pypa
+arabicstopwords
+
+# mkdocs / docs-site tooling (issue 0023): mkdocs-material + pymdownx config keys and the
+# pygments lexer name for an interactive-session ("pycon") code block.
+pymdownx
+superfences
+linenums
+crossrefs
+pycon
+
+# Unicode / regex technical vocabulary (roadmap 0.2/0.3 + Phase 1 steps)
+keycap
+keycaps
+guillemets
+guillemet
+lookaheads
+unflanked
+carrierless
+retargets
+
+# Python API identifiers referenced in prose
+maxunicode
+omap
+autojunk

araclean-0.2.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: Bug report
+about: A normalization step or the API produces the wrong output, or raises unexpectedly
+title: "fix: "
+labels: bug
+assignees: ""
+---
+
+## What happened
+
+A clear description of the bug.
+
+## Reproduction
+
+The smallest input + configuration that reproduces it. Please paste **text**, not a screenshot, so
+the exact code points are preserved.
+
+```python
+from araclean import normalize  # or the profile / step you used
+
+text = "..."            # the input string
+result = normalize(text, profile="SEARCH")   # the call you made
+```
+
+## Expected vs. actual output
+
+- **Expected:** `...`
+- **Actual:** `...`
+
+If it raised instead, paste the full traceback.
+
+## Environment
+
+- araclean version: <!-- python -c "import araclean; print(araclean.__version__)" -->
+- Python version:
+- OS:
+- Extras installed (if any): `[cli]` / `[pandas]` / `[polars]` / `[emoji]` / none
+
+## Anything else
+
+Optional: the Unicode code points involved (`U+0640` …), the linguistic intent, or links.

araclean-0.2.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,13 @@
+# Force contributors through the structured templates above; a "blank issue" escape hatch is disabled
+# so every report carries the input/config/version detail a normalization bug needs to be actionable.
+blank_issues_enabled: false
+contact_links:
+  - name: Question or discussion
+    url: https://github.com/MhdMartini/araclean/discussions
+    about: Usage questions, ideas, and anything that isn't a concrete bug or feature request.
+  - name: Security vulnerability
+    url: https://github.com/MhdMartini/araclean/security/advisories/new
+    about: Report a security issue privately — please do not open a public issue.
+  - name: Code of Conduct
+    url: https://github.com/MhdMartini/araclean/blob/main/CODE_OF_CONDUCT.md
+    about: How we expect everyone to behave, and how to report abuse.

araclean-0.2.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,36 @@
+---
+name: Feature request
+about: Propose a new step, profile, or behavior
+title: "feat: "
+labels: enhancement
+assignees: ""
+---
+
+## What's missing
+
+The normalization/cleaning behavior you need and the use case behind it.
+
+## Proposed behavior
+
+Concrete input → output examples. For a new transformation, show a few representative strings and the
+output you'd expect.
+
+| input | expected output |
+| ----- | --------------- |
+| `...` | `...`           |
+
+## Safety class
+
+Is this lossless (`ENCODING_REPAIR`) or lossy (`LINGUISTIC_FOLDING`)? Which profiles should include
+it? (A lossless profile — `LIGHT`, `CLASSICAL` — may only contain `ENCODING_REPAIR` steps.)
+
+## Terminology (if it introduces a new concept)
+
+araclean uses **Arabic-primary names** glossed to the English equivalent
+([ADR-0007](../../docs/adr/0007-arabic-primary-terminology.md)). If your proposal names a new
+operation, suggest the established Arabic term and its English gloss so it can be added to
+[`GLOSSARY.md`](../../GLOSSARY.md).
+
+## Alternatives considered
+
+Existing steps/profiles you tried, and why they don't cover this.

araclean-0.2.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+<!--
+Thanks for contributing to araclean! Keep the PR focused on one change.
+The title must be a Conventional Commit (e.g. `feat(steps): add ReduceElongation`) — it feeds the
+version bump and changelog (ADR-0008).
+-->
+
+## What & why
+
+What this changes and the motivation. Link any issue it closes (`Closes #NN`).
+
+## How it behaves
+
+Input → output (or the error) that demonstrates the change, ideally mirrored by a new test.
+
+## Definition-of-done checklist
+
+See [CONTRIBUTING.md](../CONTRIBUTING.md#the-test-bar-definition-of-done) for the full bar.
+
+- [ ] Behavior test written **first** (TDD) and asserts **observable behavior through the public
+      interface** — not internal tables, private attributes, or step order.
+- [ ] New/changed `Step`s declare their `safety` class; any lossless profile (`LIGHT`, `CLASSICAL`)
+      still contains only `ENCODING_REPAIR` steps.
+- [ ] Steps precompute their `str.translate` table / compiled `re` at construction (no per-call setup
+      or validation).
+- [ ] Gate is green locally: `uv run pre-commit run --all-files` (ruff, mypy --strict, pyright,
+      pytest, cspell).
+- [ ] New Arabic term ⇒ added a [`GLOSSARY.md`](../GLOSSARY.md) row + docs abbreviation; public names
+      are Arabic-primary with an English gloss in the docstring (ADR-0007).
+- [ ] Commits are Conventional Commits; `[project].version` is **not** hand-edited.
+- [ ] Docs/ADRs updated if behavior, terminology, or a decision changed.

araclean-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,171 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+    tags: ["v*"] # a release tag (issue 0024) runs the gate, then publishes + deploys docs
+  pull_request:
+  workflow_dispatch: # manual end-to-end DRY RUN of the build/publish pipeline (0024 AC4)
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  gate:
+    # The full quality gate (ruff, mypy, pyright, pytest, cspell) via pre-commit.
+    # OS/Python-independent, so it runs once.
+    name: quality gate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - run: uv sync
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+      - name: pre-commit
+        run: uv run pre-commit run --all-files --show-diff-on-failure
+
+  commits:
+    # Conventional-Commit lint over the PR's commits (ADR-0008). The local
+    # commit-msg hook can be bypassed, so cz check runs server-side too; it reads
+    # the same rules cz bump uses to derive the version, so the changelog/bump
+    # can't be poisoned by a malformed message.
+    name: commit messages
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - run: uv sync
+      - name: commitizen check
+        run: uv run cz check --rev-range ${{ github.event.pull_request.base.sha }}..${{ github.event.pull_request.head.sha }}
+
+  docs:
+    # Build the docs site under --strict (issue 0023), so a broken link, a page missing from the
+    # nav, or a stale generated page fails CI. The `docs` dependency group is separate from `dev`,
+    # so only this job installs mkdocs-material; the docs guard tests (drift/cross-check/doctest/
+    # tooltips) run here with mkdocs present (they skip in the lean `gate`/`test` jobs).
+    name: docs site
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - run: uv sync --group docs
+      - name: mkdocs build --strict
+        run: uv run mkdocs build --strict
+      - name: docs guards (drift, cross-check, doctest, tooltips, search)
+        run: uv run pytest tests/test_docs.py
+
+  test:
+    # Behavior + types across the supported Python and OS matrix.
+    name: test (py${{ matrix.python }} · ${{ matrix.os }})
+    strategy:
+      fail-fast: false
+      matrix:
+        # os: [ubuntu-latest, macos-latest, windows-latest]
+        os: [ubuntu-latest]
+        python: ["3.12", "3.13", "3.14"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python }}
+      - run: uv sync
+      - name: pytest
+        run: uv run pytest
+      - name: mypy --strict
+        run: uv run mypy
+      - name: pyright
+        run: uv run pyright
+
+  build:
+    # Build the sdist + wheel and validate the package metadata. Runs on every release tag AND on a
+    # manual workflow_dispatch — the dispatch path is the end-to-end DRY RUN (issue 0024, AC4): it
+    # produces and checks the exact artifacts a real publish would upload, without uploading them, so
+    # the packaging pipeline is proven before the first PyPI release. The built dist is handed to
+    # `publish` as an artifact, so the bytes that are checked are the bytes that ship.
+    name: build distribution
+    if: startsWith(github.ref, 'refs/tags/v') || github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - name: build sdist + wheel
+        # The version is static in pyproject.toml (cz owns it via `version_provider = "uv"`), so the
+        # build needs no git history — hatchling reads `[project].version` directly.
+        run: uv build
+      - name: check distribution metadata
+        run: uvx twine check --strict dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    # Tag-triggered PyPI publish via Trusted Publishing (OIDC) — no stored token (ADR-0008, issue
+    # 0024). The OIDC publisher PyPI was given is bound to THIS workflow file (ci.yml), so the publish
+    # step must live here; moving it to another file would require re-doing the PyPI setup. Gated
+    # behind the full quality gate + the build/metadata check, so a tag only ships when everything is
+    # green. `id-token: write` lets the action mint the short-lived OIDC token it trades to PyPI; no
+    # other permission is granted. The `pypi` environment is a seam for adding a required-reviewer
+    # rule later (the publisher was registered with environment "any", so none is required today).
+    name: publish to PyPI
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: [gate, docs, test, build]
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/araclean
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  docs-deploy:
+    # Versioned docs (issue 0024, story 52): `mike` publishes the tag's docs as a pinned X.Y.Z version
+    # with a moving `latest` alias and makes `latest` the default, so the docs a reader lands on match
+    # the araclean version they installed — a reproducibility requirement (PRD), not a nicety. mike
+    # commits the rendered site to the `gh-pages` branch that GitHub Pages serves; `contents: write`
+    # authorizes that push and is the only permission granted. Runs after the gate + strict docs build
+    # are green, so the site can never be deployed broken.
+    name: deploy versioned docs
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: [gate, docs, test]
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # mike appends to the existing gh-pages history it rewrites
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - run: uv sync --group docs
+      - name: configure git identity for the gh-pages commit
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+      - name: mike deploy
+        run: |
+          version="${GITHUB_REF_NAME#v}"
+          uv run mike deploy --push --update-aliases "$version" latest
+          uv run mike set-default --push latest

araclean-0.2.0/.gitignore

@@ -0,0 +1,27 @@
+.ralph
+issues/
+docs/competitive-landscape.md
+
+# Python
+.venv/
+__pycache__/
+*.py[cod]
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.hypothesis/
+build/
+dist/
+*.egg-info/
+
+# Benchmark outputs: asv's envs/results/html (issue 0019) and pytest-benchmark's saved runs. The
+# benchmark *suites* (benchmarks/, asv.conf.json) are tracked; only their generated timings are not.
+.asv/
+.benchmarks/
+
+# Docs site build output (issue 0023): `mkdocs build` writes to site/. The source pages (docs/) and
+# the generated, committed pages are tracked; only the rendered HTML is not.
+site/
+
+# Node (cspell runs via npx)
+node_modules/

araclean-0.2.0/.pre-commit-config.yaml

@@ -0,0 +1,71 @@
+# Quality gate (issue 0001). Every hook runs the project's pinned tool via
+# `uv run` so there is a single source of tool versions (the uv lockfile);
+# cSpell runs via npx against the project dictionary (cspell.json).
+#
+#   uv run pre-commit install          # wire the hooks
+#   uv run pre-commit run --all-files  # run the whole gate
+minimum_pre_commit_version: "3.7.0"
+default_install_hook_types: [pre-commit, commit-msg]
+# Hooks below run at pre-commit unless they opt into another stage (only the
+# commitizen hook does, at commit-msg) — so cspell/pytest don't lint commit text.
+default_stages: [pre-commit]
+
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff (lint)
+        entry: uv run ruff check --force-exclude
+        language: system
+        types_or: [python, pyi]
+        require_serial: true
+
+      - id: ruff-format
+        name: ruff (format)
+        entry: uv run ruff format --force-exclude
+        language: system
+        types_or: [python, pyi]
+        require_serial: true
+
+      - id: mypy
+        name: mypy --strict
+        entry: uv run mypy
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: pyright
+        name: pyright
+        entry: uv run pyright
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: pytest
+        name: pytest
+        entry: uv run pytest
+        language: system
+        types: [python]
+        pass_filenames: false
+        always_run: true
+
+      - id: cspell
+        name: cspell (canonical terminology)
+        # --no-must-find-files: a commit can stage a file cspell has nothing to check (the generated
+        # uv.lock, which cspell skips); without this, cspell exits non-zero on "no files" when that
+        # file is checked alone, failing the commit even though nothing is misspelled. A real
+        # misspelling in a checked file still fails the hook.
+        entry: npx --yes cspell@9.8.0 --no-progress --no-summary --no-must-find-files
+        language: system
+        types: [text]
+        # npx's package cache is not concurrency-safe: pre-commit splits a long file list (CI's
+        # --all-files) into batches it runs IN PARALLEL, and concurrent `npx --yes` installs into
+        # a cold cache corrupt each other (seen in CI as a bogus SyntaxError from inside
+        # cspell-lib). One serial invocation installs once, then checks everything.
+        require_serial: true
+
+      - id: commitizen
+        name: commitizen (Conventional Commit message)
+        entry: uv run cz check --allow-abort --commit-msg-file
+        language: system
+        stages: [commit-msg]

araclean-0.2.0/CHANGELOG.md

@@ -0,0 +1,52 @@
+## v0.2.0 (2026-06-12)
+
+### BREAKING CHANGE
+
+- remove the exclude_sukun option from RemoveTashkeel and
+remove_tashkeel and drop it from the serialized config. Sukun is the
+absence of a vowel (not a haraka) but always rides with HARAKAT —
+stripping the vowels while leaving a bare sukun was never a use case, so
+the flag added API surface for no real need. Sukun is still removed only
+alongside HARAKAT, never on its own.
+
+### Feat
+
+- implement offset-preserving normalization (Phase 2 Bet 1, ADR-0012)
+- add the polars .araclean Series namespace (0022)
+- add the pandas .araclean Series accessor (0021)
+- add the araclean CLI — a thin Typer adapter over the facade (0020)
+- add RemoveStopwords — a curated, versioned, negation-safe stopword list (0017)
+- add the config trust boundary — NormalizeConfig, JSON Schema, safety audit (0016)
+- add SOCIAL — the noisy-user-text profile that keeps the signal (0014)
+- add CLASSICAL — the vocalization-preserving lossless profile (0015)
+- add HandleEmoji — keep / strip / demojize (0013)
+- add cleaning steps — CleanURLs, CleanMentions, CleanHTML (0012)
+- add Pipeline ergonomics — batch, repr, select (0005)
+- add ML, the conservative-on-letters profile (0011)
+- add SEARCH, the maximal recall profile (0010)
+- add ReduceElongation, the repeated-letter elongation cap (0009)
+- add MapDigits + MapPunctuation, the digit/punctuation folds (0008)
+- add the four opt-in letter folds (0007)
+- add RemoveTashkeel, the first lossy step (0006)
+- preserve line structure in CollapseWhitespace by default
+- complete LIGHT with the four char-map steps (0004)
+- fold Arabic presentation forms into LIGHT (0003)
+- thread NormalizeUnicode through all three layers (0002)
+
+### Fix
+
+- harden apply_aligned (ADR-0012 review) and repair the CI gate
+- make `asv run` build araclean via pip instead of a missing wheel (0019)
+- flatten line breaks in the SEARCH profile per ADR-0010 (0025)
+- give every lossy profile the shared CollapseWhitespace+NFC closing tail
+- **steps**: complete the alef/hamza letter-fold repertoire (0007)
+- cover the full tashkeel repertoire; drop exclude_sukun (0006)
+- guarantee canonical NFC output so normalize is idempotent
+
+### Refactor
+
+- consolidate the duplicated _build_pipeline helper into one
+
+### Perf
+
+- fuse a pipeline's consecutive str.translate steps into one pass (0018)

araclean-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations