Baby Buddy uses POEditor for translation contributions. Interested contributors can join translation of Baby Buddy for access to a simple, web-based frontend for adding/editing translation files to the project.
Baby Buddy has support for translation/localization. A manual translation process will look something like this:
Set up a development environment (see Development environment).
gulp makemessages -l xxwhere
xxis a specific locale code in the ISO 639-1 format (e.g., "il" for Italian or "es" for Spanish). This creates a new translation file at
locale/xx/LC_MESSAGES/django.po, or updates one if it exists.
Open the created/updated
django.pofile and update the header template with license and contact info.
Start translating! Each translatable string will have a
msgidvalue with the string in English and a corresponding (empty)
msgstrvalue where a translated string can be filled in.
Once all strings have been translated, run
gulp compilemessages -l xxto compile an optimized translation file (
To expose the new translation as a user setting, add the locale code to the
LANGUAGESarray in the base settings file (
Check if Plotly offers a translation (in
node_modules/plotly.js/dist/) for the language. If it does:
Check if Moment offers a translation (in
node_modules/moment/locale/) for the language. If it does:
Run the development server, log in, and update the user language to test the newly translated strings.
Once the translation is complete, commit the new files and changes to a fork and create a pull request for review.
For more information on the Django translation process, see Django's documentation section: Translation.