übersetzung

Translate Android strings.xml into 26 locales with per-language validation.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Pepsi1978/proggs --skill bersetzung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: übersetzung
Source: https://github.com/Pepsi1978/proggs/tree/main/claude-code-setup/skills/%C3%BCbersetzung
Command: npx skills add https://github.com/Pepsi1978/proggs --skill bersetzung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the localization of Android strings.xml across 26 target languages, reducing manual effort and minimizing translation errors by enforcing language-specific rules and preserving essential placeholders.

Core Features & Use Cases

  • End-to-end localization workflow: translate values-*/strings.xml for all 26 locales with per-language verification.
  • Language-specific prompts: apply language rules for PT-PT vs PT-BR, Indian numerals, RTL handling, and tailored glossaries.
  • Quality assurance: ensure placeholder preservation, correct plural forms, and post-translation checks before committing.

Quick Start

Run the 26-language translation workflow to generate all values-*/strings.xml files and commit each language after verification.

Frequently Asked Questions about übersetzung

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate Android strings.xml into multiple languages automatically?

This Skill translates Android strings.xml entries from German into 26 target languages by generating full locale-specific values directories, applying strict translation validation, and committing each language after verification.

Does Android string localization handle RTL languages and regional variants like PT-BR?

Android string localization handles RTL formatting, PT-BR and PT-PT regional variants, native digits, and full-width punctuation by applying tailored per-language prompts and specific validation checks during the translation process.

How do I preserve placeholders when localizing Android strings.xml files?

To preserve placeholders during Android strings.xml localization, the workflow enforces strict validation rules and post-translation quality checks to ensure all existing placeholders remain intact across all 26 generated locale files.

What is the best way to create full 26-language coverage for an Android app?

The best way to create 26-language coverage for an Android app is running an end-to-end localization workflow that generates all required values-*/strings.xml files, applies language-specific rules, and commits each language individually after verification.

Can I verify Android string translations before committing them to my project?

You can verify Android string translations before committing because the workflow applies strict post-translation checks for correct plural forms and placeholder preservation, ensuring quality assurance before each language version is committed.