Update tools.json

[Stephan-P]

Updates of (automated?) Dutch translations

Summary by CodeRabbit

• Documentation
  • Updated Dutch language translations for privacy-related messages across page labels, digital signing, timestamping, and PDF overlay tools.

[coderabbitai]

📝 Walkthrough

Walkthrough

Dutch localization text updated in four tool sections to refine privacy messaging and adjust pronoun formality. Privacy statements now emphasize data remaining on the user's device or browser. PDF overlay section changes formal pronouns to informal variants.

Changes

Dutch Localization Updates

Layer / File(s)	Summary
Privacy Messaging public/locales/nl/tools.json	Privacy statements refined across Add page labels, Digital signing, and Timestamping tools to emphasize user data "stays on" device/browser rather than alternative phrasing (lines 119, 733, 760).
Pronoun & Description Updates public/locales/nl/tools.json	PDF overlay section updates formal Dutch pronouns (u/uw) to informal variants (jouw) and refines tool descriptions in upload, download, and FAQ sections (lines 922–932).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hoppity hop through Dutch locale so fine,
Privacy whispers, each word in line,
From formal to "jouw" with a friendly twist,
Data stays local—no device it will miss!
Translation's a joy, a linguistic delight,
This rabbit approves—the phrasing is right! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks required sections from the template including Type of change, Testing details, and Contributor checklist, though it briefly mentions the update is for Dutch translations.	Complete the pull request description by filling in all required sections: specify the type of change, describe how the translations were tested, and verify the contributor checklist items.
Title check	❓ Inconclusive	The title 'Update tools.json' is overly generic and vague, using only the filename without indicating the actual purpose or nature of the changes.	Use a more descriptive title that explains what was updated, e.g., 'Update Dutch translations in tools.json' or 'Improve Dutch privacy UI text for PDF tools'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@public/locales/nl/tools.json`:
- Line 733: The Dutch subtitle for the digital signature tool uses the wrong
preposition ("op jouw browser"); update the "subtitle" value in
public/locales/nl/tools.json (the "subtitle" key shown in the diff) to use the
natural phrasing "in jouw browser" so the sentence reads: "Jouw privésleutel
blijft in jouw browser." Ensure spacing and punctuation remain consistent with
the surrounding JSON entry.
- Line 932: The translation for the "faqPrivacyAnswer" string overstates
guarantees by saying "volledige privacy garandeert"; update the value for the
"faqPrivacyAnswer" key to a softer, implementation-focused claim that emphasizes
processing happens in the browser and files do not leave the device while
avoiding absolute promises (e.g., mention that this "helpt je privacy te
beschermen" or "beperkt blootstelling" rather than "garandeert volledige
privacy"). Locate the "faqPrivacyAnswer" entry and replace the final clause with
the narrower phrasing.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 030249d4-f761-4f7a-a887-9e4f6aabd6be

📥 Commits

Reviewing files that changed from the base of the PR and between bbffdad and 0c53a4a.

📒 Files selected for processing (1)

• public/locales/nl/tools.json