From: Jonathan Corbet <corbet@lwn.net>
To: Matic Urbanija <maticurbanija@protonmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Translation of kernel documentation
Date: Mon, 10 Jun 2024 14:09:30 -0600 [thread overview]
Message-ID: <87le3cv9tx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <Enls7GJQSRW6Z77NFFcLl19W5U8xKlzEGyKAIOr36JDcFQMaEYewfYgYUz5WcNW3X7Xfi7btGAXNT8Ue_WMGIjaxgdDZiKTk_CcGj-fIMH0=@protonmail.com>
Matic Urbanija <maticurbanija@protonmail.com> writes:
> first of all, I'm terribly sorry if this isn't the right place to ask
> about translation. I sent an email to helpdesk but so far no answer
> from them.
As has already been said, this is the right place.
Out of curiosity, which "helpdesk" did you send email to?
> My name is Matic Urbanija, I am a teacher at Vegova - Upper Secondary
> School of Electrical and Computer Engineering and Technical Gymnasium
> Ljubljana, Slovenia (https://www.vegova.si/about-us-vegova/).
>
> I would like to translate kernel documentation into Slovenian
> language. Maybe some of my students would also like to participate.
>
> Are there some special requirements or procedures which have to be
> fulfilled before starting translation project? What is the proper or
> recommend way to start to translate the kernel documentation?
Best is to look at how the other languages are handled. I would
recommend starting with the stuff in Documentation/process/ as being of
the most general interest.
If you can recruit somebody else to help with review of translation
patches, that would be most helpful. On my own, I'm not qualified to
know what's a good translation and what isn't.
I do have to ask one question: is it your intent to maintain this
translation once it has gone upstream? Documentation evolves over time;
having a bunch of out-of-date translations in the tree is not
particularly useful. I'll be a lot happier about accepting a new
translation if I have some assurance that it will not end up in that
state.
Thanks,
jon
next prev parent reply other threads:[~2024-06-10 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 17:45 Translation of kernel documentation Matic Urbanija
2024-06-07 19:11 ` Matthew Wilcox
2024-06-10 18:44 ` Carlos Bilbao
2024-06-10 18:49 ` Carlos Bilbao
2024-06-10 20:11 ` Jonathan Corbet
2024-06-10 20:09 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 16:38 Matic Urbanija
2024-06-17 14:25 ` Jonathan Corbet
2024-06-17 15:30 ` Matic Urbanija
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87le3cv9tx.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=maticurbanija@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).