There is also a radical but simple solution :
1. Saying that the review of translated document by another speaker of
same language is highly recommended, but not mandatory.
2. Inserting on the top of each translated html document a "flashy" link
(a WARNING) that displays a message indicating that "The translation
process is subject to errors, and in case of doubt, please refer to
original english document".
Le 14/10/2020 à 18:08, Lucien Gentis a écrit :
Le 14/10/2020 à 17:09, Nick Kew a écrit :
On Wed, 14 Oct 2020 15:39:03 +0200
Pavel Vecherin <vecher...@gmail.com> wrote:
@doc
One thought: why not keep in the repository translations that require
review by filename,
for example "name-based.xml.ru.need_review".
+1 to some such approach. Needs thought on implementation.
Why not, in the style of Translation status
(http://home.apache.org/~takashi/translation-status/index.html#2.4)
with a link on top of the doc that points to that list and suggesting
to contribute
And some script (or page) that could collect such files (by lang).
This could direct a new contributor in the right way.
It seems to me that this can be useful (of course, if there is no such
thing yet, I may have missed something).
@Nick
... we should (if anything) particularly welcome Russian
colleagues ;) !
If the opportunity presents itself, I will say hello to Igor from
Nick. :))
:)
Some years back I had occasion to engage with the nginx community.
It was a positive experience.
<quote cite="https://bahumbug.wordpress.com/2013/02/22/tengine/";>
How much of a barrier is language? I’ve written about that before, and
now it’s my turn to find myself the wrong side of a language barrier.
Actually that applies to nginx too: the Russian-born web server has a
core community whose language I don’t speak. Developing the
nginx-ironbee module gave me an opportunity to test a barrier from
the outside, and I’m happy to report I got some helpful responses and
productive technical discussion on nginx’s English-language developer
list. A welcoming community and no language barrier to what I was
doing.
</quote>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
