[Qgis-community-team] [Qgis-tr] Setting rules to officially publish docs in a target language
DelazJ
delazj at gmail.com
Fri Feb 18 01:41:04 PST 2022
Hi Etienne,
We do not translate testing (debatable but too much moving imho and not
enough workforce). Only the latest LTR is being translated. So currently,
only docs for 3.16 is available in Transifex. What translators work with is
what users read, (almost) Live.
3.22 should be pushed in upcoming days weeks. One of the reasons I also
want to know which set of languages we should begin this new round with.
Harrissou
Le 18 février 2022 08:00:00 GMT+01:00, Etienne Trimaille <
etienne.trimaille at gmail.com> a écrit :
>
> What about the idea of having two rules ?
>
> - https://docs.qgis.org/testing/en/docs/user_manual/ 5%, so good for
> translators ?
> - https://docs.qgis.org/latest/en/docs/user_manual/ which is a redirect
> to https://docs.qgis.org/3.16/en/docs/user_manual/ 35% to keep a better
> quality for end users (not being disappointed when they switch to their own
> language not fully translated)
>
> I'm not sure if it's possible, just the idea.
>
> Le jeu. 17 févr. 2022 à 19:15, DelazJ <delazj at gmail.com> a écrit :
>
>> Hi all,
>> A late reply
>>
>> Le mar. 25 janv. 2022 à 12:13, Jörn Gutzeit <j.gutzeit at umwelt-it.de> a
>> écrit :
>>
>>> Transifex Webtranslation page for QGIS is on
>>> https://www.transifex.com/qgis/
>>>
>>> Hi,
>>>
>>> I am a member of the German QGIS User Group and translation has been an
>>> issue with us for a long time. We have already set up a special team to
>>> that, unfortunately with low success so far .. (we also have some technical
>>> problems with Transifex and wonder how other translators solve them, but
>>> that is another topic).
>>>
>>
>> Maybe could you open another thread and expand on the Transifex issues?
>>
>>>
>>> But, no excuses: of course the rules should be the same for all
>>> languages! We also think that something that is only translated about 20%
>>> can badly be called a "german-language manual" and that this is
>>> disappointing for users. Therefore, it is of course right no longer to
>>> publish the german-language manual if it does not fit to the requirements.
>>>
>>> OK
>>
>>> But I would like to add a personal opinion: I don't know what exactly it
>>> would mean if a language is no longer published. But if that means that
>>> only Transifex is available for translation, I fear that it will be even
>>> more difficult for translation. For me, it is a great help if I can access
>>> the manual as a complete document to get a quick overview of the whole
>>> chapter or of what still needs to be translated. In Transifex I can only
>>> see the paragraph I am translating. And I think it might also make it more
>>> difficult to convince new people to contribute to the translation.
>>>
>>
>> Jörn, I understand your personal opinion and it was one of the motivation
>> to keep displaying some languages. But experience has proven that while
>> being able to view the manual as you translate is great, very nice and
>> helpful, it doesn't necessarily motivate more translators to contribute
>> (otherwise we wouldn't have this discussion). And *a contrario*, if you
>> look at the hungarian crew, their translation was at 5% [0] when I opened
>> this topic, they are a month later around 10% [1] AND they are not
>> published. Not yet. If they keep that pace...
>>
>>
>>> Is there maybe a more resource-friendly way to make the docs available
>>> online? (of course same for all languages)
>>>
>>
>> The easy and fair one that comes to mind is building the 60 docs but we
>> all agree that it's not resource friendly, and not really useful for many.
>> That said, recipes to build the docs are on the github repo... if language
>> communities are interested...
>>
>> Fact is there's no clear rule currently and for fairness, we need rules.
>> Maybe setting a threshold and making everyone aware of it can help clarify
>> things and provide a (lower) target to reach for some communities. Or
>> maybe, removing the language can stimulate its speakers. I know these are
>> all wishes... And I don't have an answer...
>>
>> [0]
>> https://github.com/qgis/QGIS-Documentation/commit/baf2f2a5fe93c497eb52963d92b56fdcbc921f5b#diff-7788e4e804a06b351338159aff9398a759b7d784303ebfcfcedab13c624b323bR79
>> [1]
>> https://github.com/qgis/QGIS-Documentation/commit/3604b7265301c97d0601f962f067dc9bb15d672b#diff-7788e4e804a06b351338159aff9398a759b7d784303ebfcfcedab13c624b323bR79
>>
>> Regards,
>> Harrissou
>>
>>>
>>>
>>> Greetings,
>>> Jörn
>>>
>>> Am 24.01.2022 um 12:22 schrieb Alexandre Neto:
>>>
>>> Hello Harrissou,
>>>
>>> Thanks for rasing the topic. And sorry for the late reply. For PT_pt, we
>>> are failing to engage people to translations, so it seems reasonable that
>>> the language is dropped from the builds for now.
>>>
>>> Thanks,
>>>
>>> Alexandre Neto
>>>
>>> A segunda, 24/01/2022, 10:34, pathmapper <pathmapper at posteo.de>
>>> escreveu:
>>>
>>>> Hi,
>>>>
>>>> I've contacted the German QGIS User Group about this topic (German
>>>> translation with 21.38% would not be published anymore if the treshold
>>>> would be 35%).
>>>>
>>>> Maybe let's wait for some feedback.
>>>>
>>>> Cheers,
>>>> Björn
>>>>
>>>> On 24.01.2022 10:42, DelazJ wrote:
>>>> > Hi all,
>>>> >
>>>> > Le 15/01/2022 à 12:27, Etienne Trimaille a écrit :
>>>> >
>>>> >> Hi,
>>>> >>
>>>> >> IIRC, I think it must be 30% translated in QGIS Desktop to be
>>>> >> included in the binary.
>>>> >
>>>> > Thanks for the reply, Etienne. Actually for Desktop, it's now 35%
>>>> > (
>>>> https://github.com/qgis/QGIS/blob/973b97af24836568aa0ebffceddb459e9bf47942/scripts/update_ts.sh#L149
>>>> > [5]).
>>>> >
>>>> > Aligning docs to that ratio can indeed be an option that makes sense.
>>>> > In which case, published languages for 3.22 (start) would probably be
>>>> > Dutch, French, Italian, Japanese, Korean, Portuguese (Brazil) and
>>>> > Spanish. Any opinions?
>>>> >
>>>> > Regards,
>>>> >
>>>> > Harrissou
>>>> >
>>>> >> I just found this old thread:
>>>> >> https://lists.osgeo.org/pipermail/qgis-tr/2014-January/000238.html
>>>> >> [4]
>>>> >> I'm not sure where it's written on the website.
>>>> >>
>>>> >> Le lun. 10 janv. 2022 à 16:19, DelazJ <delazj at gmail.com> a écrit :
>>>> >>
>>>> >>> Dear community,
>>>> >>>
>>>> >>> QGIS documentation is being translated into almost sixty languages
>>>> >>> [0] but we currently publish the docs in around 20 languages [1].
>>>> >>> The choice of the published languages does not really rely on
>>>> >>> fully objective and fair system (mix of the ratio of translations,
>>>> >>> members, technical challenges, published in website...).
>>>> >>> Fact is today we have a number of published docs whose ratio of
>>>> >>> translation is quite (really) low, meaning that release after
>>>> >>> release, we are storing multiple copies of almost English docs in
>>>> >>> our servers, and we disappoint languages speakers who may expect
>>>> >>> reading their docs in their language but finally fall on English.
>>>> >>> On the other hand, we have some languages whose ratio is better
>>>> >>> than published languages', and they still are not published.
>>>> >>>
>>>> >>> This message is to discuss whether we should set up clearer rules
>>>> >>> to publish a language? If yes, which ones?
>>>> >>>
>>>> >>> [0]
>>>> >>>
>>>> >>
>>>> >
>>>> https://docs.qgis.org/3.16/en/docs/user_manual/preamble/contributors.html#statistics-of-translation
>>>> >>> [1]
>>>> >>> [1]
>>>> >>>
>>>> >>
>>>> >
>>>> https://github.com/qgis/QGIS-Documentation/blob/release_3.16/Makefile#L7
>>>> >>> [2]
>>>> >>>
>>>> >>> Kind regards,
>>>> >>> Harrissou
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> Qgis-community-team mailing list for organizing community
>>>> >>> resources such as documentation, translation etc..
>>>> >>> Qgis-community-team at lists.osgeo.org
>>>> >>> https://lists.osgeo.org/mailman/listinfo/qgis-community-team [3]
>>>> >
>>>> >
>>>> > Links:
>>>> > ------
>>>> > [1]
>>>> >
>>>> https://docs.qgis.org/3.16/en/docs/user_manual/preamble/contributors.html#statistics-of-translation
>>>> > [2]
>>>> >
>>>> https://github.com/qgis/QGIS-Documentation/blob/release_3.16/Makefile#L7
>>>> > [3] https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>>>> > [4]
>>>> https://lists.osgeo.org/pipermail/qgis-tr/2014-January/000238.html
>>>> > [5]
>>>> >
>>>> https://github.com/qgis/QGIS/blob/973b97af24836568aa0ebffceddb459e9bf47942/scripts/update_ts.sh#L149
>>>> >
>>>> > _______________________________________________
>>>> > Qgis-community-team mailing list for organizing community resources
>>>> > such as documentation, translation etc..
>>>> > Qgis-community-team at lists.osgeo.org
>>>> > https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>>>> _______________________________________________
>>>> Qgis-community-team mailing list for organizing community resources
>>>> such as documentation, translation etc..
>>>> Qgis-community-team at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>>>>
>>>
>>> _______________________________________________
>>> Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..Qgis-community-team at lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/qgis-community-team
>>>
>>>
>>> --
>>> Jörn Gutzeit Umwelt IT
>>> Umweltdatenbearbeitung
>>> Lothringerstraße 68
>>> 52070 Aachen
>>> 0176 - 43 03 93 31www.umwelt-it.de
>>>
>>> _______________________________________________
>>> QGIS-Translators mailing list
>>> Qgis-tr at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/qgis-tr
>>>
>> _______________________________________________
>> Qgis-community-team mailing list for organizing community resources such
>> as documentation, translation etc..
>> Qgis-community-team at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-community-team/attachments/20220218/ae76f83a/attachment-0001.html>
More information about the Qgis-community-team
mailing list