From: Brian M. <br...@gr...> - 2009-10-28 03:32:35
|
Translators: I just made a change to all the DateDisplay classes that will affect the translation of months. Previously, the DateDisplay classes used the localized months detected by GrampsLocale. This prohibits us from using a DateDisplay class for translating to languages other than the language Gramps is currently running in. I have added two new string arrays to each DateDisplay class. Those strings need to be translated in the code (we don't use gettext for those). At your leisure, please open your respective _Date_xx.py file and edit the following lines: # TODO: Translate these month strings: long_months = ( u"January", u"February", u"March", u"April", u"May", u"June", u"July", u"August", u"September", u"October", u"November", u"December" ) short_months = ( u"Jan", u"Feb", u"Mar", u"Apr", u"May", u"Jun", u"Jul", u"Aug", u"Sep", u"Oct", u"Nov", u"Dec" ) Please remove the #TODO comment when you are done. Whomever translates Spanish: I translated _Date_es.py for testing purposes. Please double check my work and remove the "# TODO" comment if you are satisfied. Thanks everyone! This change will lead us to be able to have user selectable report translations. ~Brian |