This needs to be decided per language team. I'm personally not fond of
web based tools and anonymus contributions have not had the best
quality in the past. And you cannot talk to the submitters at all.
在 2024/6/18 04:23, Thomas Lange 写道:
....For reference, weblate is a web based tool:
- I'm interested in what may help translators, for e.g. is git a
barrier for people to become an active translator? Would a web based
tool help?
https://hosted.weblate.org/projects/
There are many open source projects and Debian's projects use it now.
Am 18.06.2024 11:21 schrieb Helge Kreutzmann:
This needs to be decided per language team. I'm personally not fond of
web based tools and anonymus contributions have not had the best
quality in the past. And you cannot talk to the submitters at all.
Weblate canb be configured that way that only logged in persons are able to contribute.
It is also very easy to "talk" to the contributors via the comment fields.
Weblate is definitely not perfect. Especially their upstream team IMHO has a lacy definition of usability and "good" documentation.
But to my research it is currently the only acceptable platform in FLOSS environment. And their development is very active.
But to my research it is currently the only acceptable platform in
FLOSS
environment. And their development is very active.
I would contend this. There are many translation communities working
without weblate.
Hi,
I can share my impressions from the web team point of view during the
BoF. Summary:
- I'm interested in what may help translators, for e.g. is git a
barrier for people to become an active translator? Would a web based
tool help?
This needs to be decided per language team. I'm personally not fond of[...]
web based tools and anonymus contributions have not had the best
quality in the past. And you cannot talk to the submitters at all.
I think this is just lack of (wo)man power. Translation is important, but
too few people take the time to prepare (good) translations and there
is so much to translate.
Hi,
I can share my impressions from the web team point of view during the
BoF. Summary:
- there are some very active and well maintained languages in the
webwml repo
- there are more languages that are inactive or stalled. Major changes
in english are not applied to those languages.
- it hard to see which language team is inactive, since we still have
git commits in the webwml repo, but not from translators. These are
almost simple changes from non-translators (like http -> https,
fixing URLs,...)
- I'm interested in what may help translators, for e.g. is git a
barrier for people to become an active translator? Would a web based
tool help?
Am Tue, Jun 18, 2024 at 08:36:20AM +0800 schrieb xiao sheng wen(肖盛文):
在 2024/6/18 04:23, Thomas Lange 写道:
....For reference, weblate is a web based tool:
- I'm interested in what may help translators, for e.g. is git a
barrier for people to become an active translator? Would a web based
tool help?
https://hosted.weblate.org/projects/
There are many open source projects and Debian's projects use it now.
This needs to be decided per language team.
I'm personally not fond of
web based tools and anonymus contributions have not had the best
quality in the past. And you cannot talk to the submitters at all.
I think this is just lack of (wo)man power. Translation is important, but
too few people take the time to prepare (good) translations and there
is so much to translate.
I would love to contribute to the web pages
as well, but my resource are already bound to manpages-l10n and
others.
From my manpages-l10n experience: Having a good infrastructure, trying
to take care of the needs of translators, really helps.
So, in my opionion, what would really help is better education to the english authors. If you only fix trivial (english) issues, e.g. commas, quote signs, links, etc., then translators should not see it. So either
all up to date translations are bumped without change or the fix (e.g.
http → https) is done by the english author. This way, translators which are up to date are releaved of work. And of course, separating trivial
and content updates.
Am Tue, Jun 18, 2024 at 09:21:01AM +0000 schrieb Helge Kreutzmann:
So, in my opionion, what would really help is better education to the english authors. If you only fix trivial (english) issues, e.g. commas, quote signs, links, etc., then translators should not see it. So either all up to date translations are bumped without change or the fix (e.g. http → https) is done by the english author. This way, translators which are up to date are releaved of work. And of course, separating trivial
and content updates.
Makes sense. What are you guys doing to teach those english authors?
Am Mon, Jun 17, 2024 at 10:23:28PM +0200 schrieb Thomas Lange:
If all this does not help we should probably accept find some minimum
level of activity in some translation and in case some language is
falling below this level it might be better to remove this translation (rather than providing "really" (whatever this means is to be discussed) outdated translations)
- it hard to see which language team is inactive, since we still have
git commits in the webwml repo, but not from translators. These are
almost simple changes from non-translators (like http -> https,
fixing URLs,...)
Good point. Seems somehow to stress my idea that we should try to
reach out to real persons.
- I'm interested in what may help translators, for e.g. is git a
barrier for people to become an active translator? Would a web based
tool help?
I'm not competent to answer this. My gut feeling tells me that if some volunteer really wants to contribute the tools do not matter much. I've
seen my "non-Linux-office-only-educated" daughter Minh from Vietnam
doing an intro session into CVS (at that time) and Git by Felipe and the
next day she started with using these. It might be that "easier" tools
are possibly helpful to attract new contributors more easily since not everybody is sufficiently motivated to climb that steep hill in the first place. So the contact to past translators cold include some kind of questionaire like:
1. Do you think that (re-)gaining the skills you need to restart
your translation work is a blocker? yes/no
2. Do you think you could find someone who takes over your work
would be easier if the tools would be easier to use? yes/no
I'm convinced that we as technically addictect persons can not find a
proper answer to this question amongst ourselves.
Maybe we could start by collecting "best practices" within the l10n
teams and then thinks about how to best "teach" those to the english
authors?
Hi,
Some months ago I setup up https://weblate.debian.net
I was planning run some tests with portuguese translations and then open to everyone.
But we can start to test it, specially the admin part.
Am Mon, Jun 17, 2024 at 10:23:28PM +0200 schrieb Thomas Lange:
- I'm interested in what may help translators, for e.g. is git a
barrier for people to become an active translator? Would a web based
tool help?
I'm not competent to answer this. My gut feeling tells me that if some volunteer really wants to contribute the tools do not matter much. I've
seen my "non-Linux-office-only-educated" daughter Minh from Vietnam
doing an intro session into CVS (at that time) and Git by Felipe and the
next day she started with using these. It might be that "easier" tools
are possibly helpful to attract new contributors more easily since not everybody is sufficiently motivated to climb that steep hill in the first place. So the contact to past translators cold include some kind of questionaire like:
So, in my opionion, what would really help is better education to the
english authors. If you only fix trivial (english) issues, e.g. commas,
quote signs, links, etc., then translators should not see it. So either
all up to date translations are bumped without change or the fix (e.g.
http → https) is done by the english author. This way, translators which are up to date are releaved of work. And of course, separating trivial
and content updates.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 344 |
Nodes: | 16 (2 / 14) |
Uptime: | 29:51:48 |
Calls: | 7,518 |
Calls today: | 15 |
Files: | 12,713 |
Messages: | 5,642,178 |
Posted today: | 2 |