#2212 closed enhancement (fixed)
Set up transifex for document translation
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | Website Management, Bots |
Component: | documentation | Version: | master |
Keywords: | Cc: |
Description (last modified by )
We've decided to go with transifex since that seems to be where we'll garner the most translators and there is already a good group of folks (pgRouting, QGIS) familiar with using transifex where there is possibility of cross breeding of translators.
—- OLD NOTE —- PostgreSQL folks said they are setting up Pootle on one of their servers since other groups are interested. They said they can use their infrastructure if we want for our own translation needs.
I'll update this ticket as things progress.
Change History (8)
comment:1 by , 12 years ago
Milestone: | Management 1.0 → Management 2.0 |
---|
comment:2 by , 12 years ago
comment:3 by , 11 years ago
Summary: | Set up Pootle for document translation → Set up transifex for document translation |
---|
Seems other GIS projects pgRouting, QGIS are already using transifex. Best seems to be to host directly on transifex using their free open source hosting offering to take advantage of existing translators. George Silva has offered to help out with this effort.
Related dev mailing list notes: http://lists.osgeo.org/pipermail/postgis-devel/2013-November/023957.html
comment:4 by , 11 years ago
Description: | modified (diff) |
---|
comment:5 by , 11 years ago
Description: | modified (diff) |
---|
comment:6 by , 11 years ago
George has made great progress here. We've got a transifex setup which is linked on http://postgis.net/documentation and already got translators translating away on various languages — including Polish (go Mat ).
Next steps will be integrating all this back into our documentation building and setting up an area on site to show the translations (both PDF and html).
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
closing this part out since this is done and will add the pull as a separate task
continuation of #847