Files
TimeTracker/docs/TRANSLATION_SYSTEM.md
Dries Peeters 3f4b273b18 feat: Add command palette, enhance calendar, and improve i18n
This commit implements three major feature enhancements to improve user
productivity and experience:

COMMAND PALETTE IMPROVEMENTS:
- Add '?' key as intuitive shortcut to open command palette
- Maintain backward compatibility with Ctrl+K/Cmd+K
- Enhance visual design with modern styling and smooth animations
- Add 3D effect to keyboard badges and improved dark mode support
- Update first-time user hints and tooltips
- Improve input field detection to prevent conflicts

CALENDAR REDESIGN:
- Implement comprehensive drag-and-drop for moving/resizing events
- Add multiple calendar views (Day/Week/Month/Agenda)
- Create advanced filtering by project, task, and tags
- Build full-featured event creation modal with validation
- Add calendar export functionality (iCal and CSV formats)
- Implement color-coded project visualization (10 distinct colors)
- Create dedicated calendar.css with professional styling
- Add recurring events management UI
- Optimize API with indexed queries and proper filtering

TRANSLATION SYSTEM ENHANCEMENTS:
- Update all 6 language files (EN/DE/NL/FR/IT/FI) with 150+ strings
- Improve language switcher UI with globe icon and visual indicators
- Fix hardcoded strings in dashboard and base templates
- Add check mark for currently selected language
- Enhance accessibility with proper ARIA labels
- Style language switcher with hover effects and smooth transitions

DOCUMENTATION:
- Add COMMAND_PALETTE_IMPROVEMENTS.md and COMMAND_PALETTE_USAGE.md
- Create CALENDAR_IMPROVEMENTS_SUMMARY.md and CALENDAR_FEATURES_README.md
- Add TRANSLATION_IMPROVEMENTS_SUMMARY.md and TRANSLATION_SYSTEM.md
- Update HIGH_IMPACT_FEATURES.md with implementation details

All features are production-ready, fully tested, responsive, and maintain
backward compatibility.
2025-10-07 19:00:07 +02:00

274 lines
6.8 KiB
Markdown

# Translation System Documentation
## Overview
TimeTracker includes a comprehensive internationalization (i18n) system powered by Flask-Babel. The application supports 6 languages out of the box:
- **English** (en) - Default
- **Dutch** (nl - Nederlands)
- **German** (de - Deutsch)
- **French** (fr - Français)
- **Italian** (it - Italiano)
- **Finnish** (fi - Suomi)
## User Experience
### Language Switcher
The language switcher is located in the top navigation bar, positioned between the command palette button and the user profile menu. It features:
- 🌐 Globe icon for easy recognition
- Current language label (on larger screens)
- Dropdown menu with all available languages
- Visual indicator (checkmark) for the currently selected language
- Smooth hover transitions and animations
### Language Selection
Users can change the interface language in two ways:
1. **Via Navigation Bar**: Click the globe icon and select a language from the dropdown
2. **Direct URL**: Visit `/i18n/set-language?lang=<code>` (e.g., `?lang=de` for German)
Language preference is persisted:
- **For authenticated users**: Saved to user profile in database
- **For guests**: Stored in session
## Technical Details
### Translation Files
Translation files are located in `translations/` directory:
```
translations/
├── en/LC_MESSAGES/messages.po # English
├── nl/LC_MESSAGES/messages.po # Dutch
├── de/LC_MESSAGES/messages.po # German
├── fr/LC_MESSAGES/messages.po # French
├── it/LC_MESSAGES/messages.po # Italian
└── fi/LC_MESSAGES/messages.po # Finnish
```
### Configuration
Language configuration is defined in `app/config.py`:
```python
LANGUAGES = {
'en': 'English',
'nl': 'Nederlands',
'de': 'Deutsch',
'fr': 'Français',
'it': 'Italiano',
'fi': 'Suomi',
}
BABEL_DEFAULT_LOCALE = 'en'
```
### Locale Selection Priority
The system determines the user's language in the following order:
1. **User preference from database** (for authenticated users)
2. **Session override** (via set-language route)
3. **Browser Accept-Language header** (best match)
4. **Default locale** (en)
See `app/__init__.py` for the locale selector implementation.
### In Templates
Use the `_()` function to mark strings for translation:
```html
<h1>{{ _('Welcome to TimeTracker') }}</h1>
<button>{{ _('Start Timer') }}</button>
```
For strings with variables, use named parameters:
```html
<p>{{ _('%(app)s is a web-based time tracking application', app='TimeTracker') }}</p>
```
### In Python Code
Import and use the translation function:
```python
from flask_babel import _
message = _('Timer started successfully')
flash(_('Project created'), 'success')
```
## Translation Compilation
Translation files (`.po`) are automatically compiled to binary files (`.mo`) when the application starts. The compilation is handled by `app/utils/i18n.py` which:
1. Checks if `.mo` files exist and are up-to-date
2. Compiles `.po` to `.mo` using Babel's message tools
3. Runs automatically during application initialization
## Adding a New Language
To add a new language:
1. **Add to configuration** in `app/config.py`:
```python
LANGUAGES = {
# ... existing languages ...
'es': 'Español', # Add Spanish
}
```
2. **Create translation directory**:
```bash
mkdir -p translations/es/LC_MESSAGES
```
3. **Initialize translation file**:
```bash
pybabel init -i messages.pot -d translations -l es
```
4. **Translate the strings** in `translations/es/LC_MESSAGES/messages.po`
5. **Restart the application** - translations will compile automatically
## Updating Translations
When you add new translatable strings to the application:
1. **Extract messages**:
```bash
pybabel extract -F babel.cfg -o messages.pot .
```
2. **Update all translation files**:
```bash
pybabel update -i messages.pot -d translations
```
3. **Translate new strings** in each `.po` file
4. **Restart application** - changes will be compiled automatically
## Translation File Format
Translation files use the PO (Portable Object) format:
```po
# Comment
msgid "Original English text"
msgstr "Translated text"
# With context
msgid "Dashboard"
msgstr "Tableau de bord" # French
# Plurals
msgid "1 hour"
msgid_plural "%d hours"
msgstr[0] "1 heure"
msgstr[1] "%d heures"
```
## Best Practices
1. **Keep strings short and contextual**
- Good: `_('Save')`
- Avoid: `_('Click this button to save your changes to the database')`
2. **Use sentence case**
- Good: `_('Start timer')`
- Avoid: `_('START TIMER')`
3. **Avoid concatenation**
- Good: `_('Welcome back, %(name)s', name=user.name)`
- Avoid: `_('Welcome back,') + ' ' + user.name`
4. **Provide context in comments**
```python
# Translators: This is the button to start the time tracking timer
_('Start Timer')
```
5. **Test in multiple languages** to ensure UI layout works correctly
## Troubleshooting
### Language not changing
1. Check browser console for JavaScript errors
2. Verify the language code exists in `LANGUAGES` config
3. Clear browser cache and cookies
4. Check that `.mo` files exist in `translations/<lang>/LC_MESSAGES/`
### Translations not showing
1. Ensure strings are wrapped in `_()` function
2. Check that `.mo` files are compiled (restart application)
3. Verify translation exists in the `.po` file
4. Check for syntax errors in `.po` file
### Compilation errors
If translations fail to compile:
1. Check `.po` file syntax (must be valid)
2. Ensure `msgid` and `msgstr` are properly quoted
3. Look for encoding issues (files must be UTF-8)
## Styling
Language switcher styling is defined in `app/static/base.css`:
- Smooth hover transitions
- Consistent with application design system
- Responsive design (icon-only on small screens)
- Follows light/dark theme
## Accessibility
The language switcher includes:
- Proper ARIA labels and attributes
- Keyboard navigation support
- Clear visual indication of current language
- Tooltip with current language name
- Semantic HTML structure
## Performance
- Translations are compiled at startup (one-time operation)
- Compiled `.mo` files are cached in memory
- No runtime performance impact
- Minimal bundle size increase per language (~50-100KB)
## Future Enhancements
Potential improvements:
1. Add more languages (Spanish, Portuguese, Japanese, etc.)
2. Right-to-left (RTL) language support (Arabic, Hebrew)
3. User-contributed translations via Crowdin or similar
4. Automatic language detection improvement
5. Translation coverage reporting
## Support
For questions or issues with translations:
1. Check this documentation
2. Review `app/__init__.py` locale selector
3. Inspect browser network requests to `/i18n/set-language`
4. Check application logs for translation compilation errors
---
**Last Updated**: 2025-10-07
**Flask-Babel Version**: 4.0.0
**Babel Version**: 2.14.0