You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're working on the C++ source code you mostly don't need to worry about these files as they are automatically updated with new strings that need translating by the build process.
Translators should be able to work on these files with Qt Linguist
History
Before it moved to GitHub, Brewtarget source code and project management used to be done on Launchpad. The Launchpad Translations tools were used for collaborating on translations. However, this meant jumping through some hoops because Launchpad Translations uses GNU gettext Portable Object (.po) files, but the code needs Qt Translation Source (.ts) files (because we use Qt's native translation management facilities rather than the GNU translation tools & libraries. So you needed to do transcoding back and forth.
After moving to GitHub, it made less sense to retain the .po files and more sense to work directly on the .ts files with the Qt Linguist tool.