Translation Repository
All translations are managed in a separate repository:Namida Translations
GitHub Repository: https://github.com/namidaco/namida-translationsVisit this repository to contribute translations or add a new language.
Why Translate?
Translating Namida helps:Expand Accessibility
Make Namida usable for non-English speakers worldwide
Grow Community
Welcome users from different countries and cultures
Improve Experience
Users can navigate the app in their native language
Personal Contribution
Make a meaningful contribution to open source
How to Contribute Translations
Visit the translation repository
Check existing languages
- Browse the repository to see which languages are already available
- Check if your language needs improvements or is missing
Fork the repository
Click the “Fork” button on GitHub to create your own copy of the translation repository.
Add or edit translations
- For a new language: Create a new file following the existing structure
- For improvements: Edit the existing language file
- Follow the format and naming conventions used in the repository
Translation Guidelines
When translating Namida, follow these best practices:General Principles
Maintain context
Maintain context
Understand the context where each string is used. A word might have different translations depending on whether it’s a button, menu item, or description.
Keep it concise
Keep it concise
Try to match the length of the original English text when possible. Very long translations may not fit in the UI.
Use consistent terminology
Use consistent terminology
Use the same translation for technical terms throughout the app. For example, if you translate “playlist” as “liste de lecture” in French, use that consistently.
Preserve placeholders
Preserve placeholders
Keep any placeholders (like
%s, {0}, etc.) exactly as they appear. These are replaced with dynamic content at runtime.Example:Respect formatting
Respect formatting
Maintain any special formatting like line breaks, capitalization patterns, or punctuation that serves a purpose.
Technical Terms
Some technical terms might be better left in English or transliterated, depending on common usage in your language:
- Playlist
- Queue
- Equalizer
- Buffer
- Cache
Tone and Style
- Friendly but professional: Namida has a casual, user-friendly tone
- Clear and direct: Avoid overly formal or complex language
- Consistent voice: Maintain the same tone throughout all translations
What to Translate
The translation repository includes strings for:User Interface Elements
- Menu items and navigation
- Button labels
- Settings options
- Tab names
- Dialog titles and messages
Features and Functions
- Music library terms (albums, artists, genres, etc.)
- Playback controls
- YouTube integration features
- Download and cache options
- Playlist and queue management
Messages and Notifications
- Status messages
- Error messages
- Success confirmations
- Tooltips and hints
Settings and Preferences
- Setting categories
- Setting descriptions
- Option labels
- Help text
Focus on the most commonly used strings first, then work on more specialized features.
Testing Your Translations
After contributing translations:Test in the app
- Download the updated version
- Change language to your translation
- Check for:
- Correctness of translations
- Text that doesn’t fit in the UI
- Missing translations (falling back to English)
- Context mismatches
Translation Tools and Resources
Useful Tools
GitHub Desktop
Makes it easier to fork, edit, and submit translations without command-line knowledge.
VS Code
A good text editor with syntax highlighting for easier editing.
Google Translate
Can help with initial translations, but always review and adjust for context.
DeepL
Often provides more natural translations than Google Translate.
Reference Materials
- Look at how other music apps are translated in your language
- Check official Flutter/Material Design translations for standard UI terms
- Consult with native speakers when unsure
- Use the app yourself to understand the context
Common Translation Challenges
Pluralization
Pluralization
Different languages have different plural rules. Make sure you understand how your language handles:
- Zero items (“no tracks”)
- One item (“1 track”)
- Few items (in some languages)
- Many items (“5 tracks”)
Gender and formality
Gender and formality
Some languages have gendered nouns or formal/informal forms. Choose the appropriate level of formality for a music app (usually informal/neutral).
Right-to-left languages
Right-to-left languages
If you’re translating to Arabic, Hebrew, or other RTL languages:
- The translation framework should handle text direction
- Test thoroughly to ensure UI elements appear correctly
- Report any RTL-specific layout issues
Text expansion/contraction
Text expansion/contraction
Some languages are significantly longer or shorter than English:
- German often expands significantly
- Chinese/Japanese often contract
- Try to keep translations compact to avoid UI overflow
- Report if the UI cannot accommodate your language’s text length
Updating Existing Translations
As Namida evolves, translations need updates:When Updates Are Needed
- New features added to the app
- Changed terminology in English version
- Corrections to existing translations
- Improvements in clarity or naturalness
How to Update
Check for changes
Compare your language file with recent English updates in the translation repository.
Language-Specific Considerations
Currently Available Languages
Check the translation repository for the current list of supported languages.Adding a New Language
To add a language not yet supported:Create a new file
Create a new translation file following the naming convention in the repository (e.g.,
strings_fr.json for French).Translate all strings
Translate every string in the file. Mark any strings you’re unsure about for review.
Even partial translations are helpful! If you can’t translate everything, submit what you have and others may help complete it.
Recognition and Credits
Translation contributors are valued members of the Namida community:- Your GitHub username will appear in the repository’s contributors
- Translators may be credited in release notes
- You’re helping thousands of users enjoy Namida in their language
Quality Assurance
Before Submitting
Review your translations for:- Accuracy: Does it convey the correct meaning?
- Naturalness: Does it sound natural in your language?
- Consistency: Are terms used consistently?
- Completeness: Are all strings translated?
- Placeholders preserved: Are
%s,{0}, etc. intact? - Length: Will it fit in the UI?
- Spelling and grammar: No typos or errors?
Peer Review
If possible, have another native speaker review your translations before submitting.Getting Help
Need help with translations?Telegram Chat
Ask translation questions in the community chat
Discord Server
Coordinate with other translators on Discord
GitHub Issues
Report translation issues or ask questions
GitHub Discussions
Discuss translation approaches and conventions
Translation Best Practices Summary
Do
- Understand context before translating
- Keep translations concise
- Use consistent terminology
- Preserve placeholders and formatting
- Test your translations
- Ask for help when unsure
Don't
- Rely solely on machine translation
- Change placeholder syntax
- Use overly formal language
- Submit without reviewing
- Translate technical terms unnecessarily
- Ignore UI length constraints
Next Steps
Ready to start translating?Visit the repository
Read the repository README
Check for any additional guidelines or instructions in the translation repository.
Thank you for helping make Namida accessible to users around the world! Every translation makes a difference.
Questions?
If you have questions about translating Namida:Contributing Guide
Check the general contributing guide for more information about participating in the Namida project.