Started translating to German#575
Merged
alam00000 merged 14 commits intoalam00000:mainfrom Mar 15, 2026
Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughGerman localization changed from formal to informal voice across UI copy, prompts, help text, GDPR/FAQ, and footer—systematic shift from "Sie/Ihr" to "du/dein" with corresponding verb and label adjustments. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 27691667 | Triggered | Generic Password | 3db9566 | public/locales/sv/tools.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (3)
public/locales/de/common.json (3)
354-355: Inconsistent: these unchanged lines still use formal "Sie".The
howItWorkssection still uses formal pronouns while the rest of the file has been converted to informal. Consider updating for consistency.Suggested updates
- "step2": "Klicken Sie auf die Verarbeitungsschaltfläche", - "step3": "Speichern Sie Ihre verarbeitete Datei sofort" + "step2": "Klick auf die Verarbeitungsschaltfläche", + "step3": "Speichere deine verarbeitete Datei sofort"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` around lines 354 - 355, Update the inconsistent formal pronouns in the howItWorks translation keys "step2" and "step3" to match the informal tone used elsewhere in the file: replace formal "Sie" phrasing with informal "du" variants and adjust verbs accordingly so the entries for "step2" and "step3" are consistent with the rest of the locale file's informal style.
122-122: Inconsistent: unchanged formal pronoun "Sie" remains.This line still uses formal "Verwenden Sie" while surrounding text has been converted to informal. Consider updating for consistency:
Suggested update
- "fullWidthDescription": "Verwenden Sie die volle Bildschirmbreite für alle Werkzeuge anstelle eines zentrierten Containers", + "fullWidthDescription": "Verwende die volle Bildschirmbreite für alle Werkzeuge anstelle eines zentrierten Containers",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 122, The translation key "fullWidthDescription" currently uses the formal imperative "Verwenden Sie"; update its value to the informal imperative to match surrounding strings (e.g., change to "Verwende die volle Bildschirmbreite für alle Werkzeuge anstelle eines zentrierten Containers") so the tone is consistent across the locale file; locate the "fullWidthDescription" entry and replace the string accordingly.
362-362: Inconsistent: formal "Sie" remains in simpleMode section.Suggested update
- "subtitle": "Wählen Sie ein Werkzeug aus, um zu beginnen" + "subtitle": "Wähle ein Werkzeug aus, um zu beginnen"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 362, The German translation for the "subtitle" key is using the formal pronoun "Sie" while the simpleMode section should use the informal tone; update the value of the "subtitle" key from "Wählen Sie ein Werkzeug aus, um zu beginnen" to an informal phrasing such as "Wähle ein Werkzeug aus, um zu beginnen" so it matches the rest of simpleMode's tone.
🤖 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/de/common.json`:
- Line 135: Fix the typo in the localization key "resetMessage": replace the
incorrect word "möchteest" with "möchtest" inside the "resetMessage" value so
the German string reads correctly.
- Line 198: Fix the typo in the German translation: update the value for the
"question" key in public/locales/de/common.json from "Verwendt ihr Cookies oder
Analysen, um mich zu verfolgen?" to "Verwendet ihr Cookies oder Analysen, um
mich zu verfolgen?" so the verb is correctly spelled ("Verwendet") while keeping
the rest of the string unchanged.
- Line 117: Change the value for the "shortcutsWarning" translation key from the
infinitive "Vermeiden" to the informal singular imperative "Vermeide" so the
message uses the correct grammatical form and matches the rest of the file's
tone; update the string associated with the "shortcutsWarning" key accordingly.
- Line 175: The translation for the "answer" key mixes formal and informal
pronouns ("Ihre" vs "deine"); update the value of the "answer" key to use "deine
Dateien" consistently (replace "Wir laden Ihre Dateien nie auf einen Server
hoch" with an informal equivalent) so the entire string uses informal "du/deine"
pronouns to match the rest of the message.
- Line 195: The JSON value for the "answer" key contains two grammatical issues:
change the formal pronoun "Ihre Dateien" to the informal "deine Dateien" to
match the surrounding informal tone, and fix subject-verb agreement by replacing
"verlässt" with the plural verb "verlassen" so it reads "...dass deine Dateien
nie dein Gerät verlassen."; update the string value accordingly, preserving the
rest of the sentence and punctuation.
- Line 295: The German translation string under the "description" key in
public/locales/de/common.json contains a typo: "tögliche" should be corrected to
"tägliche"; update the value of the "description" property to replace "tögliche"
with "tägliche" (preserve the rest of the sentence and punctuation).
- Line 183: The German translation for the "answer" key uses the formal pronoun
"Ihren" which is inconsistent with the informal "deinem/deine/du" used
elsewhere; update the string value for the "answer" JSON key to replace "Ihren"
with "deinen" so the sentence reads "... haben wir keinen Zugang zu deinen
Daten." to keep pronoun usage consistent.
---
Nitpick comments:
In `@public/locales/de/common.json`:
- Around line 354-355: Update the inconsistent formal pronouns in the howItWorks
translation keys "step2" and "step3" to match the informal tone used elsewhere
in the file: replace formal "Sie" phrasing with informal "du" variants and
adjust verbs accordingly so the entries for "step2" and "step3" are consistent
with the rest of the locale file's informal style.
- Line 122: The translation key "fullWidthDescription" currently uses the formal
imperative "Verwenden Sie"; update its value to the informal imperative to match
surrounding strings (e.g., change to "Verwende die volle Bildschirmbreite für
alle Werkzeuge anstelle eines zentrierten Containers") so the tone is consistent
across the locale file; locate the "fullWidthDescription" entry and replace the
string accordingly.
- Line 362: The German translation for the "subtitle" key is using the formal
pronoun "Sie" while the simpleMode section should use the informal tone; update
the value of the "subtitle" key from "Wählen Sie ein Werkzeug aus, um zu
beginnen" to an informal phrasing such as "Wähle ein Werkzeug aus, um zu
beginnen" so it matches the rest of simpleMode's tone.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fbe03dd6-56b1-4491-bb73-80375d3e291a
📒 Files selected for processing (1)
public/locales/de/common.json
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
public/locales/de/common.json (1)
272-272: Keep product name capitalization consistent (BentoPDF).Lines 272 and 295 use „Bentopdf“, while the rest of the file uses „BentoPDF“.
Proposed fix
- "description": "In einer Zeit, in der Daten eine Ware sind, gehen wir einen anderen Weg. Die gesamte Verarbeitung für Bentopdf-Werkzeuge erfolgt lokal in deinem Browser. Das bedeutet, deine Dateien berühren niemals unsere Server, wir sehen deine Dokumente nie und verfolgen nicht, was du tust. Deine Dokumente bleiben voll und ganz privat, ohne Hintertürchen. Privatsphäre ist nicht nur eine Funktion; es ist unser Fundament." + "description": "In einer Zeit, in der Daten eine Ware sind, gehen wir einen anderen Weg. Die gesamte Verarbeitung für BentoPDF-Werkzeuge erfolgt lokal in deinem Browser. Das bedeutet, deine Dateien berühren niemals unsere Server, wir sehen deine Dokumente nie und verfolgen nicht, was du tust. Deine Dokumente bleiben voll und ganz privat, ohne Hintertürchen. Privatsphäre ist nicht nur eine Funktion; es ist unser Fundament." - "description": "Schließ dich Tausenden von Benutzer*innen an, die Bentopdf für ihre tägliche Arbeit vertrauen. Erlebe den Unterschied, den Privatsphäre und Leistung machen können.", + "description": "Schließ dich Tausenden von Benutzer*innen an, die BentoPDF für ihre tägliche Arbeit vertrauen. Erlebe den Unterschied, den Privatsphäre und Leistung machen können.",Also applies to: 295-295
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 272, Update the product name capitalization to be consistent by replacing the incorrect "Bentopdf" occurrences with "BentoPDF" in the affected localization entries (e.g., the "description" value that currently contains "Bentopdf" at the referenced diff and the other entry around line 295); search for any other "Bentopdf" tokens in public/locales/de/common.json and change them to "BentoPDF" so all German strings match the rest of the file.
🤖 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/de/common.json`:
- Line 58: Replace the informal imperative "Klick" with the correct form
"Klicke" in the German locale entries; update the value for the "subtitle" key
(currently "Klick auf ein Tool, um den Datei-Uploader zu öffnen") and the two
other entries that use "Klick" (the other keys at the same file around the
occurrences mentioned) so they read "Klicke ...". Ensure only the wording is
adjusted and keep punctuation and surrounding text unchanged.
- Line 286: In the German translation entry under the "description" key in
public/locales/de/common.json, fix the imperative verb typo by replacing "Beginn
sofort mit der Nutzung ..." with the correct imperative "Beginne sofort mit der
Nutzung ..."; update only the string value for the "description" key to preserve
punctuation and surrounding text.
- Line 301: The German subtitle string with key "subtitle" has a case/gender
mismatch ("eine Funktionswunsch"); update the value to use the correct
accusative masculine article "einen" so the text reads "...Ob du eine Frage,
Feedback oder einen Funktionswunsch hast, schreib uns gerne!" ensuring only the
article is changed and punctuation/spacing remain intact.
- Line 186: The FAQ German string under the "question" key currently reads
"Speichern oder verfolgt ihr meine Dateien?" which has a subject-verb mismatch;
change the finite verb to "Speichert" so the sentence becomes correct. Locate
the JSON entry with the "question" key (value containing "Speichern oder
verfolgt ihr meine Dateien?") and update the string to use "Speichert" instead
of "Speichern". Ensure quotation marks and JSON formatting remain valid after
the edit.
---
Nitpick comments:
In `@public/locales/de/common.json`:
- Line 272: Update the product name capitalization to be consistent by replacing
the incorrect "Bentopdf" occurrences with "BentoPDF" in the affected
localization entries (e.g., the "description" value that currently contains
"Bentopdf" at the referenced diff and the other entry around line 295); search
for any other "Bentopdf" tokens in public/locales/de/common.json and change them
to "BentoPDF" so all German strings match the rest of the file.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9a968ab9-33cc-4f59-bc12-33cc96659e3f
📒 Files selected for processing (1)
public/locales/de/common.json
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (1)
public/locales/de/common.json (1)
58-58:⚠️ Potential issue | 🟡 MinorUse the correct informal imperative form (
Klicke).Line 58, Line 64, and Line 231 still use „Klick“. In this informal UI tone, „Klicke“ is the grammatically correct imperative.
Proposed fix
- "subtitle": "Klick auf ein Tool, um den Datei-Uploader zu öffnen", + "subtitle": "Klicke auf ein Tool, um den Datei-Uploader zu öffnen", ... - "clickToSelect": "Klick hier, um eine Datei auszuwählen", + "clickToSelect": "Klicke hier, um eine Datei auszuwählen", ... - "Klick und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern.", + "Klicke und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern.",Also applies to: 64-64, 231-231
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 58, Replace the informal imperative "Klick" with the grammatically correct "Klicke" in the German locale strings: update the value for the "subtitle" key (currently "Klick auf ein Tool, um den Datei-Uploader zu öffnen") and the other identical occurrences in public/locales/de/common.json (the strings at the other two locations flagged in the review, line 64 and line 231) so all three UI strings use "Klicke" consistently.
🧹 Nitpick comments (2)
public/locales/de/common.json (2)
99-99: Use status wording for loader text instead of imperative.Line 99
"Verarbeite..."reads like a command. A neutral status phrase is clearer in a loading indicator.Proposed fix
- "processing": "Verarbeite..." + "processing": "Wird verarbeitet..."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 99, The "processing" localization entry currently uses the imperative "Verarbeite..." which reads like a command; update the value for the "processing" key to a neutral status phrase such as "Wird verarbeitet..." (or "Verarbeitung..." if preferred) so the loader displays a passive status instead of an imperative. Locate the "processing" key in common.json and replace its value accordingly.
44-44: Polish phrasing for more natural German.Line 44 is understandable, but
"Nutz es so viel du willst"is less idiomatic than"Nutze es so viel, wie du willst".Proposed fix
- "description": "Nutz es so viel du willst, ohne versteckte Grenzen." + "description": "Nutze es so viel, wie du willst, ohne versteckte Grenzen."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 44, The German translation for the "description" key is slightly unidiomatic; update the value of the "description" JSON entry (the "description" string) to use more natural phrasing by replacing "Nutz es so viel du willst" with "Nutze es so viel, wie du willst" so the sentence reads: Nutze es so viel, wie du willst, ohne versteckte Grenzen.
🤖 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/de/common.json`:
- Line 272: The product name is inconsistently cased as "Bentopdf" in the JSON
value for the "description" key; update every occurrence in that value (and the
other affected string at the same spot) to the correct casing "BentoPDF" so the
brand appears consistently across translations and matches other strings that
already use "BentoPDF".
- Around line 121-124: Update the German strings to use the informal "du" tone:
change the value for "fullWidthDescription" from "Verwenden Sie die volle
Bildschirmbreite für alle Werkzeuge anstelle eines zentrierten Containers" to an
informal form like "Verwende die volle Bildschirmbreite für alle Werkzeuge
anstelle eines zentrierten Containers", and change "clickToSet" from "Klicken
zum Festlegen" to an informal imperative such as "Klicke zum Festlegen" (or
similar informal phrasing consistent with surrounding strings).
---
Duplicate comments:
In `@public/locales/de/common.json`:
- Line 58: Replace the informal imperative "Klick" with the grammatically
correct "Klicke" in the German locale strings: update the value for the
"subtitle" key (currently "Klick auf ein Tool, um den Datei-Uploader zu öffnen")
and the other identical occurrences in public/locales/de/common.json (the
strings at the other two locations flagged in the review, line 64 and line 231)
so all three UI strings use "Klicke" consistently.
---
Nitpick comments:
In `@public/locales/de/common.json`:
- Line 99: The "processing" localization entry currently uses the imperative
"Verarbeite..." which reads like a command; update the value for the
"processing" key to a neutral status phrase such as "Wird verarbeitet..." (or
"Verarbeitung..." if preferred) so the loader displays a passive status instead
of an imperative. Locate the "processing" key in common.json and replace its
value accordingly.
- Line 44: The German translation for the "description" key is slightly
unidiomatic; update the value of the "description" JSON entry (the "description"
string) to use more natural phrasing by replacing "Nutz es so viel du willst"
with "Nutze es so viel, wie du willst" so the sentence reads: Nutze es so viel,
wie du willst, ohne versteckte Grenzen.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 48507ba6-c2e8-485f-a49b-af5e9a35f229
📒 Files selected for processing (1)
public/locales/de/common.json
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (1)
public/locales/de/common.json (1)
58-58:⚠️ Potential issue | 🟡 MinorUse the standard imperative form
Klickeinstead ofKlick.Line 58, Line 64, and Line 231 still use the colloquial short form. For consistent UI copy, switch to
Klicke.Proposed fix
- "subtitle": "Klick auf ein Tool, um den Datei-Uploader zu öffnen", + "subtitle": "Klicke auf ein Tool, um den Datei-Uploader zu öffnen", - "clickToSelect": "Klick hier, um eine Datei auszuwählen", + "clickToSelect": "Klicke hier, um eine Datei auszuwählen", - "Klick und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern.", + "Klicke und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern.",Also applies to: 64-64, 231-231
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 58, Replace the colloquial short form "Klick" with the standard imperative "Klicke" in the German locale JSON values — e.g., change the value of the "subtitle" key (and any other entries in the same file that contain "Klick", including the other occurrences noted) so the UI copy consistently uses "Klicke". Ensure you only update the string values and preserve surrounding punctuation and spacing.
🤖 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/de/common.json`:
- Line 44: Update the German translation value for the "description" key to use
the more idiomatic comma in the quantity phrase: replace the current string
"Nutz es so viel du willst, ohne versteckte Grenzen." with "Nutz es so viel, wie
du willst, ohne versteckte Grenzen." so the key "description" in common.json
reads the corrected phrase.
- Line 209: Update the "description" JSON value: add a comma before the
subordinate clause "um ein kostenloses..." so the string reads "BentoPDF ist
eine Herzensangelegenheit, entwickelt, um ein kostenloses, privates und
leistungsstarkes PDF-Toolkit für alle bereitzustellen..." — modify the value for
the "description" key accordingly to include the missing comma.
---
Duplicate comments:
In `@public/locales/de/common.json`:
- Line 58: Replace the colloquial short form "Klick" with the standard
imperative "Klicke" in the German locale JSON values — e.g., change the value of
the "subtitle" key (and any other entries in the same file that contain "Klick",
including the other occurrences noted) so the UI copy consistently uses
"Klicke". Ensure you only update the string values and preserve surrounding
punctuation and spacing.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 572e5da4-d17f-40e6-be32-354f010f844c
📒 Files selected for processing (1)
public/locales/de/common.json
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
public/locales/de/common.json (1)
351-363:⚠️ Potential issue | 🟡 MinorInconsistent formal tone in
howItWorksandsimpleModesections.These sections still use formal "Sie/Ihre" while the rest of the file has been updated to informal "du/deine". This creates a jarring inconsistency for users navigating the application.
Lines 354-355 and 362 should be updated to match the informal tone of the rest of the translations.
Proposed fix
"howItWorks": { "title": "So funktioniert's", "step1": "Klicken oder Datei hierher ziehen", - "step2": "Klicken Sie auf die Verarbeitungsschaltfläche", - "step3": "Speichern Sie Ihre verarbeitete Datei sofort" + "step2": "Klicke auf die Verarbeitungsschaltfläche", + "step3": "Speichere deine verarbeitete Datei sofort" }, "relatedTools": { "title": "Verwandte PDF-Tools" }, "simpleMode": { "title": "PDF-Werkzeuge", - "subtitle": "Wählen Sie ein Werkzeug aus, um zu beginnen" + "subtitle": "Wähle ein Werkzeug aus, um zu beginnen" }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` around lines 351 - 363, Update the German translations to use the informal "du/deine" tone: change howItWorks.step2 ("Klicken Sie auf die Verarbeitungsschaltfläche") to an informal form (e.g., "Klicke auf die Verarbeitungsschaltfläche"), howItWorks.step3 ("Speichern Sie Ihre verarbeitete Datei sofort") to informal ("Speichere deine verarbeitete Datei sofort"), and simpleMode.subtitle ("Wählen Sie ein Werkzeug aus, um zu beginnen") to informal ("Wähle ein Werkzeug aus, um zu beginnen"); modify the values for the keys howItWorks.step2, howItWorks.step3, and simpleMode.subtitle accordingly so they match the rest of the file's tone.
♻️ Duplicate comments (3)
public/locales/de/common.json (3)
64-64:⚠️ Potential issue | 🟡 MinorSame "Klick" → "Klicke" issue.
Proposed fix
- "clickToSelect": "Klick hier, um eine Datei auszuwählen", + "clickToSelect": "Klicke hier, um eine Datei auszuwählen",,
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 64, Update the German translation for the key "clickToSelect" in common.json to use the correct imperative form: change the value from "Klick hier, um eine Datei auszuwählen" to "Klicke hier, um eine Datei auszuwählen" so the string under the "clickToSelect" key uses proper German grammar.
58-58:⚠️ Potential issue | 🟡 MinorImperative form "Klick" should be "Klicke".
This was flagged in a previous review but appears unaddressed. Standard German UI copy uses "Klicke" as the correct informal imperative form.
Proposed fix
- "subtitle": "Klick auf ein Tool, um den Datei-Uploader zu öffnen", + "subtitle": "Klicke auf ein Tool, um den Datei-Uploader zu öffnen",,
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 58, Update the German translation for the "subtitle" key in public/locales/de/common.json to use the correct informal imperative form "Klicke" instead of "Klick"; locate the JSON entry with the "subtitle" key and replace the string "Klick auf ein Tool, um den Datei-Uploader zu öffnen" with "Klicke auf ein Tool, um den Datei-Uploader zu öffnen" and save the file so the UI shows the corrected wording.
231-231:⚠️ Potential issue | 🟡 MinorThird instance of "Klick" → "Klicke".
Proposed fix
- "Klick und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern.", + "Klicke und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern.",,
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@public/locales/de/common.json` at line 231, Replace the third occurrence of the German imperative "Klick und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern." with the corrected form "Klicke und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern." in public/locales/de/common.json by updating that string value; search for the exact string literal "Klick und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern." and change it to "Klicke ..." so all instances use the consistent imperative "Klicke".
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@public/locales/de/common.json`:
- Around line 351-363: Update the German translations to use the informal
"du/deine" tone: change howItWorks.step2 ("Klicken Sie auf die
Verarbeitungsschaltfläche") to an informal form (e.g., "Klicke auf die
Verarbeitungsschaltfläche"), howItWorks.step3 ("Speichern Sie Ihre verarbeitete
Datei sofort") to informal ("Speichere deine verarbeitete Datei sofort"), and
simpleMode.subtitle ("Wählen Sie ein Werkzeug aus, um zu beginnen") to informal
("Wähle ein Werkzeug aus, um zu beginnen"); modify the values for the keys
howItWorks.step2, howItWorks.step3, and simpleMode.subtitle accordingly so they
match the rest of the file's tone.
---
Duplicate comments:
In `@public/locales/de/common.json`:
- Line 64: Update the German translation for the key "clickToSelect" in
common.json to use the correct imperative form: change the value from "Klick
hier, um eine Datei auszuwählen" to "Klicke hier, um eine Datei auszuwählen" so
the string under the "clickToSelect" key uses proper German grammar.
- Line 58: Update the German translation for the "subtitle" key in
public/locales/de/common.json to use the correct informal imperative form
"Klicke" instead of "Klick"; locate the JSON entry with the "subtitle" key and
replace the string "Klick auf ein Tool, um den Datei-Uploader zu öffnen" with
"Klicke auf ein Tool, um den Datei-Uploader zu öffnen" and save the file so the
UI shows the corrected wording.
- Line 231: Replace the third occurrence of the German imperative "Klick und
ziehe das Symbol, um die Reihenfolge der Dateien zu ändern." with the corrected
form "Klicke und ziehe das Symbol, um die Reihenfolge der Dateien zu ändern." in
public/locales/de/common.json by updating that string value; search for the
exact string literal "Klick und ziehe das Symbol, um die Reihenfolge der Dateien
zu ändern." and change it to "Klicke ..." so all instances use the consistent
imperative "Klicke".
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 2cbb8dc0-c3e0-4f8b-986d-25a9e301eadd
📒 Files selected for processing (1)
public/locales/de/common.json
Owner
|
Thank you Luna |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I started translating and forgot to open a PR for that.
Expected Results:
Checklist:
Summary by CodeRabbit