update i18n for GeoNode QGIS server

[gubuntu]

Everything in INGC needs to be in Portuguese...

• add GeoNode-QGIS server strings to transifex Geonode project
• then hand over to Jose to finish translating GeoNode into PT

[lucernae]

I'm still unsure on how to do this part. We can either generate the locale and publish it under GeoSAFE. Or we can ask GeoNode community to let us push some source string, even though it's not in their repo yet.

[gubuntu]

I think the latter is better. Better still, how about doing #481 then the strings will be there to transate (I will translate them...)

[gubuntu]

whatever is not translated in GeoNode (like some menu items) should be hidden (although it is preferable to translate them

[lucernae]

Can I have the screenshot of that menu item?

[gubuntu]

login and see the layers menu in PT locale - 'upload documents' and 'upload layers' are still in English

There are various other elements in GeoNode pages (like on the Layers page itself) where there is still English.

which PT locale are we using for GeoNode - pt-pt or pt-br?

Surely the best way to translate these strings is in the upstream project and not in the theme override? although the latter might be quicker for now?

[lucernae]

Can somebody scan through all currently untranslated text and provide screenshoots and url to access it. It was quite difficult to track if it comes from javascript files. It would help if I know the screenshot and url.

Surely the best way to translate these strings is in the upstream project and not in the theme override? although the latter might be quicker for now?

We can search if the string already exists in GeoNode transifex repo. If it's not, we had to push it to theme override or GeoSAFE.

which PT locale are we using for GeoNode - pt-pt or pt-br?

Just pt @gubuntu . If you want to be more specific, we can change the locale name to what you want.

[lucernae]

GeoNode resources overrides available in geosafe (in geosafe.geonode and geosafe.geonode-javascript).

[lucernae]

Note that not all strings urgently needs to be translated, for example strings in admin page probably not so urgent.

[lucernae]

Extra note for javascript translations.

It was very difficult for me to extract strings from most javascript files.

For example the strings in filters list here:

Came from angular template, which is a static resource. At the moment, I don't know how to extract this strings easily so it can be preprocessed by Django. There might be significant effort needed to do this (refactoring or moving the js template).

[gubuntu]

OK I'll explain this to WB, let's not do that if the infrastructure isn't there for tagging and translating

[gubuntu]

this has been done in the ingc-geonode-theme and the geosafe transifex project. the final step now becomes to move the geonode resources from those upstream when we push the rest of our geonode work upstream