On 04/12/2017 06:42 PM, D. Michael McIntyre wrote: > I used to post the status report from scripts/make-ts along with these > announcements. I used to run that immediately prior to declaring a > string freeze.
OK, I'll add that to the process. One thing I noticed... make-ts generates three files that are not in version control: data/AutoloadStrings.cpp data/InstrumentStrings.cpp data/QMenuStrings.cpp These are generated temporarily to make sure strings from various non-code places end up in the .ts files. Since we don't ignore these in version control, they are a nuisance and have to be deleted manually or excluded when committing. Some solutions come to mind: 1. Go ahead and commit them. The advantage to this is that they are always available for translators to refer to, even if they don't run make-ts. It also makes it clear that these are to be in version control. 2. Add them to the svn:ignore property for the data directory. This way they won't be accidentally committed. Translators can generate them any time they want, and they won't show up when committing. This is probably the most gentle change. 3. Have the make-ts script delete them once it is done. My problem with this is that the files will no longer exist if someone runs make-ts and starts doing translation work. I assume that the translation tool will then have nowhere to point them to for an explanation as to why these strings are in the .ts file. Worst-case, we can just document the issue and move on. Any preference for any of these solutions from the perspective of a translator? Ted. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
