Pantroid-778 Missing translations in PocketPaint [Also Resolves UX-197] #1343
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.
Title: PAINTROID-778: Fix Missing Translations in PocketPaint [Also Resolves UX-197]
Description:
This PR addresses the missing German translations in the PocketPaint application as outlined in Jira ticket PAINTROID-778 and partially overlaps with UX-197.
Changes Made:
• Updated translations for the following elements in both the tutorial and toolbox:
• Smudge → Verschmieren
• Clipboard → Zwischenablage
• Cliparea → Ausschneiden
• Updated the Color Picker translation:
• Recently Used → zuletzt verwendet
• Verified changes for consistency in the UI and ensured that all elements reflect the correct translations.
Additional Context:
• Before and after screenshots have been included to highlight the changes.
• These fixes not only resolve translation gaps but also improve user experience by maintaining linguistic consistency.
Your checklist for this pull request
Please review the contributing guidelines and wiki pages of this repository.
Include the name of the Jira ticket in the PR’s title
Include a summary of the changes plus the relevant context
Choose the proper base branch (develop)
Confirm that the changes follow the project’s coding guidelines
Verify that the changes generate no compiler or linter warnings
Perform a self-review of the changes
Verify to commit no other files than the intentionally changed ones
Include reasonable and readable tests verifying the added or changed behavior
Confirm that new and existing unit tests pass locally
Check that the commits’ message style matches the project’s guideline
Stick to the project’s gitflow workflow
Verify that your changes do not have any conflicts with the base branch
After the PR, verify that all CI checks have passed
Post a message in the #paintroid Slack channel and ask for a code reviewer
Before: