From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, bilbao@vt.edu
Subject: Re: [PATCH] docs/sp_SP: Add process coding-style translation
Date: Wed, 23 Nov 2022 10:27:19 -0600 [thread overview]
Message-ID: <6fa7ad4d-1c92-121f-25c6-005fd5f1b6b9@amd.com> (raw)
In-Reply-To: <87edtt8wyl.fsf@meer.lwn.net>
On 11/23/22 10:19 AM, Jonathan Corbet wrote:
> Carlos Bilbao <carlos.bilbao@amd.com> writes:
>
>> On 11/21/22 3:13 PM, Jonathan Corbet wrote:
>>> Carlos Bilbao <carlos.bilbao@amd.com> writes:
>>>
>>>> Translate Documentation/process/coding-style.rst into Spanish.
>>>>
>>>> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
>>>> ---
>>>> .../translations/sp_SP/coding-style.rst | 1315 +++++++++++++++++
>>>> Documentation/translations/sp_SP/index.rst | 1 +
>>>> 2 files changed, 1316 insertions(+)
>>>> create mode 100644 Documentation/translations/sp_SP/coding-style.rst
>>>
>>> So I'm kind of slow, I'll admit...but I have finally noticed that you're
>>> not preserving the directory structure used for Documentation/ as a
>>> whole. Is there a reason for that? We've been (slowly) working to
>>> organize our docs in a reader-friendly way, it seems unfortunate to lose
>>> that for the translations...?
>>
>> Yes, you're correct. The order I was following was: "If I didn't speak
>> English, what document would _I_ like to see translated next?". The coding
>> style directives seemed to me like the most important thing next in line.
>> Following this logic, I was planning on translating
>> process/email-clients.rst next.
>>
>> What would be better? Perhaps the documents of process/ in order of
>> appearance? I don't know what would be preferable in terms of organization.
>> Perhaps we have some data on most consulted docs for the Documentation
>> website?
>
> I think I didn't express myself clearly...I don't really care about the
> order in which you do the translations, whatever you think is best is
> fine there. What I was asking about is the *directory structure* of the
> results. Thus, for example, I think that this translation should end up
> in .../sp_SP/process/coding-style.rst.
>
> See what I'm getting at? The directory structure of the translations
> should really match that of the documents they are coming from. Or, at
> least, so it seems to me.
Ah, that makes sense. I will send amended patches.
>
> Thanks,
>
> jon
Thanks,
Carlos
prev parent reply other threads:[~2022-11-23 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:47 Carlos Bilbao
2022-11-21 21:13 ` Jonathan Corbet
2022-11-23 15:01 ` Carlos Bilbao
2022-11-23 16:19 ` Jonathan Corbet
2022-11-23 16:27 ` Carlos Bilbao [this message]
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=6fa7ad4d-1c92-121f-25c6-005fd5f1b6b9@amd.com \
--to=carlos.bilbao@amd.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®