fix: restore clobbered translations (cs, de, fr, it) #409
Conversation
These four translations were clobbered in commit 86c0db2 when the contributor apparently opened these iso-8859-1 and -2 files in a utf-8 editor to make three small changes, the editor changed all the non-ascii characters to REPLACEMENT CHARACTER everywhere, and the files were saved and committed that way. This change just reverts 86c0db2, leaving the three small spelling changes to be reapplied.
Re-apply the original spelling changes after recovering the cs, de, fr, and it translations from the commit that clobbered them. Closes #408.
Yup ... the .class files all still have their old unclobbered contents (and the old uncorrected spelling So somebody ought to run According to |
The spelling error wasn't a huge deal... ;) But I will run it. Dave Cramer On 25 October 2015 at 20:13, Chapman Flack notifications@github.com wrote:
|
The spelling itself could not be a big deal, but with the spelling fixed in the driver code but the Which might also not be such a big deal, but might surprise somebody.... |
fix: restore clobbered translations (cs, de, fr, it)
This should close #408.
I notice there is an open #348 to make
update-translations.sh
be automatically run (contrary to the maintainer instructions on the translations page). I wonder if the project has escaped embarrassment in international quarters exactly because that didn't happen in 2013 when these files got clobbered....