The names of fields in our Django models get displayed in a number of areas. Most importantly, we use them in forms like the layer metadata and map metadata editing forms. But in general, they get exposed through the Django administrative user interface.
This means we got to internationalize the printed names of those properties. Thankfully, Django provides a 'verbose_name' on the model fields, and a function for lazily getting the translated string to fill them. See the docs here: http://docs.djangoproject.com/en/dev/topics/i18n/internationalization/#lazy-translation I've made a ticket for this here: http://projects.opengeo.org/CAPRA/ticket/668 for what I hope is a good first pass at the problem, though I think by its nature it's going to have to be something we try to remember whenever we implement a new model. (I definitely don't think this should block the beta) I'm working on the fixes for this in this branch: http://github.com/sbenthall/geonode/tree/lazy-issue-668 One issue I'm bumping into is that I'm not sure whether the strings specified by the World Bank's/ISO19139 metadata schema need to be translated. http://projects.opengeo.org/CAPRA/wiki/MetadataSpecification I'm going to email the World Bank specifically about this now, but wanted to bring it up as an example of a more general possible issue around translating strings in Python model code that's not just in the fields. -- Sebastian Benthall OpenGeo - http://opengeo.org
