[Qgis-psc] Transifex and translation platform alternatives

Tue Aug 23 00:18:03 PDT 2022

Hi,

For the website we probably get away with .po files only, but if we want to
get away from transifex we also need to migrate the application itself
which uses Qt .ts files. IMHO it also makes sense from a translator's point
of view to be able to work on one platform.

Matthias

On Mon, Aug 22, 2022 at 6:00 PM Tim Sutton <tim at kartoza.com> wrote:

> Hi all
>
> And greetings to you Markus! For me I dont have any personal preference as
> to which platform we use, I just tried to provide an alternative with my
> rabbit hole thread. One of the things we were hoping to have is a live
> translate mode. It might make it a little bit messy but possibly we could
> use a low cost plan from transifex just for the QGIS.org pages (basically
> stuff that we would like to be able have more layout control of and some
> WYSIWYG editing in something like wordpress) and then weblate for the rest
> of the content.
>
> @Matthias Kuhn <matthias at opengis.ch> Isn't it that we just need .po file
> support since we generate those from the .ts files ourselves - and those
> are supported by pontoon.
>
> Anyway it would be good to proactively move over before we suddenly get a
> bill or a take down from transifex.
>
> Andreas perhaps we can fund Harrissou or some other willing person to
> take care of this? If not now, maybe in next year's budget?
>
> Regards
>
> Tim
>
> On Mon, Aug 22, 2022 at 12:54 PM Markus Neteler <neteler at osgeo.org> wrote:
>
>> Hi,
>>
>> We are using https://weblate.osgeo.org/ (moved there from transifex) for
>> GRASS GIS and it works great.
>>
>> Markus
>> PS: greetings from Florence :)
>>
>> Delaz J <delazj at gmail.com> schrieb am Mo., 22. Aug. 2022, 12:13:
>>
>>> Hi all,
>>>
>>> Just a quick note that OSGeo has an instance of Weblate. And if I'm not
>>> wrong this is what GRASS and PostGIS are using.
>>>
>>> Harrissou
>>> Le 22/08/2022 à 11:57, Régis Haubourg a écrit :
>>>
>>> Hi Tim,
>>> thanks for raising this rabbit hole issue :)
>>>
>>> We have currently more than 1.5 M strings to translate, and we probably
>>> need 166K strings  for 1.5M words to handle growth in the next years.
>>> I know that Harrissou and Matthias mentioned Weblate as an open source
>>> alternative.
>>>
>>> Looking at the feature grid for Libre projects of Weblate, I'm afraid we
>>> will have issues with the limit of 10 000 strings to translate. If we don't
>>> want to host it ourselves, we might anyway have to go to paying plans.
>>>
>>> Paid plans for transifex will cost a lot too. I see something between
>>> 420 € to  1200 $ / month at least, and this depends a lot if they count
>>> strings or words as a reference.
>>>
>>> I suspect the economic model of cloud weblate would lead us to similar
>>> costs.
>>>
>>> So, I'd prefer the PSC sponsoring someone to try pontoon or weblate
>>> self-hosted alternative.
>>>
>>> Régis
>>>
>>>
>>> Le lun. 22 août 2022 à 10:58, Tim Sutton <tim at kartoza.com> a écrit :
>>>
>>>> Hi all
>>>>
>>>> RABBIT HOLE WARNING
>>>>
>>>> So I have been looking over the options we have for doing live
>>>> translations via transifex or other platforms. I discovered here:
>>>>
>>>> https://docs.transifex.com/projects/open-source-project
>>>>
>>>> that we are not really (i.e. not at all) meeting the criteria of
>>>> Transifex any more. Particularly this one:
>>>>
>>>> "Transifex offers an Open Source Program to Open Source projects that
>>>> have *no funding, revenue, and/or commercialization model*. The intent
>>>> is to support *small* and independent Open Source projects."
>>>>
>>>> I think we should address this and either a) pay to use transifex or b)
>>>> look into using an open source alternative like pontoon (
>>>> https://github.com/mozilla/pontoon/). Pontoon looks great and seems to
>>>> provide quite similar capabilities for the current workflows we have. The
>>>> gotcha seems to be they really try to nudge you to deploying on heroku
>>>> which is yet more managed infrastructure.
>>>>
>>>> Another thing we are wondering is if we can find a system that lets you
>>>> do live translations like transifex does (we don't currently use the
>>>> feature but it would let us separate parts of the web site into something
>>>> more dynamically updatable via a CMS).
>>>>
>>>> So my questions are:
>>>>
>>>> * what do we do about transifex terms and conditions?
>>>> * has anyone looked at alternatives before and come up with a good
>>>> system?
>>>> * is there any interest in us hosting our own pontoon instance?
>>>>
>>>> Regards
>>>>
>>>> Tim
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> ------------------------------------------------------------------------------------------
>>>>
>>>> Tim Sutton
>>>> Visit http://kartoza.com to find out about open source:
>>>>  * Desktop GIS programming services
>>>>  * Geospatial web development
>>>> * GIS Training
>>>> * Consulting Services
>>>> Tim is a member of the QGIS Project Steering Committee
>>>>
>>>> -------------------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Qgis-psc mailing list
>>>> Qgis-psc at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>>
>>> _______________________________________________
>>> Qgis-psc mailing list
>>> Qgis-psc at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>
>>
>
> --
>
> ------------------------------------------------------------------------------------------
> 
>
> Tim Sutton
> Visit http://kartoza.com to find out about open source:
>  * Desktop GIS programming services
>  * Geospatial web development
> * GIS Training
> * Consulting Services
> Tim is a member of the QGIS Project Steering Committee
>
> -------------------------------------------------------------------------------------------
>

-- 
 <https://qfield.org/get/>

QFIELD 2.0 IS HERE! - Hold the power of QGIS in 
your hand - learn more 
<https://www.opengis.ch/2022/04/05/qfield-2-0-is-here/> - get it now 
<https://qfield.org/get>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20220823/704b0413/attachment.htm>