mbox series

[v3,0/2] Documentation: Start Spanish translation and include HOWTO

Message ID 20221024145521.69465-1-carlos.bilbao@amd.com
Headers
Series Documentation: Start Spanish translation and include HOWTO |

Message

Carlos Bilbao Oct. 24, 2022, 2:55 p.m. UTC 
  Spanish is the second most spoken language in the world. This patch set
starts the process of translating critical kernel documentation into the
Spanish language.

Link to v2: https://lkml.org/lkml/2022/10/13/866
Changes since v2:
  - Apply improvements proposed by Miguel Ojeda
  - Added Reviewed-By of Miguel Ojeda for first commit
  - Added Reviwed-By of Bagas Sanjaya for second commit

Changes since v1:
  - Added me as MAINTAINER
  - Fixed warnings of kernel test robot
  - Use imperative form in second commit
  - Improved minor translation details

Carlos Bilbao (2):
  Documentation: Start translations to Spanish
  Documentation: Add HOWTO Spanish translation into rst based build system

  Documentation/translations/index.rst          |   1 +
  .../translations/sp_SP/disclaimer-sp.rst      |   6 +
  Documentation/translations/sp_SP/howto.rst    | 617 ++++++++++++++++++
  Documentation/translations/sp_SP/index.rst    |  80 +++
  MAINTAINERS                                   |   5 +
  5 files changed, 709 insertions(+)
  create mode 100644 Documentation/translations/sp_SP/disclaimer-sp.rst
  create mode 100644 Documentation/translations/sp_SP/howto.rst
  create mode 100644 Documentation/translations/sp_SP/index.rst

Comments

Jonathan Corbet Nov. 1, 2022, 9:30 p.m. UTC | #1 
Carlos Bilbao <carlos.bilbao@amd.com> writes:

> Spanish is the second most spoken language in the world. This patch set
> starts the process of translating critical kernel documentation into the
> Spanish language.
>
> Link to v2: https://lkml.org/lkml/2022/10/13/866
> Changes since v2:
>   - Apply improvements proposed by Miguel Ojeda
>   - Added Reviewed-By of Miguel Ojeda for first commit
>   - Added Reviwed-By of Bagas Sanjaya for second commit
>
> Changes since v1:
>   - Added me as MAINTAINER
>   - Fixed warnings of kernel test robot
>   - Use imperative form in second commit
>   - Improved minor translation details
>
> Carlos Bilbao (2):
>   Documentation: Start translations to Spanish
>   Documentation: Add HOWTO Spanish translation into rst based build system
>
>   Documentation/translations/index.rst          |   1 +
>   .../translations/sp_SP/disclaimer-sp.rst      |   6 +
>   Documentation/translations/sp_SP/howto.rst    | 617 ++++++++++++++++++
>   Documentation/translations/sp_SP/index.rst    |  80 +++
>   MAINTAINERS                                   |   5 +
>   5 files changed, 709 insertions(+)
>   create mode 100644 Documentation/translations/sp_SP/disclaimer-sp.rst
>   create mode 100644 Documentation/translations/sp_SP/howto.rst
>   create mode 100644 Documentation/translations/sp_SP/index.rst

I went to apply this series just now, and got the following from "git
am":

WARNING: Message contains suspicious unicode control characters!
         Subject: [PATCH v3 2/2] Documentation: Add HOWTO Spanish translation into rst based build system
            Line: +estable más reciente del kernel, y no están interesados ​​en ayudar a probar
            ---------------------------------------------------------------^
            Char: ZERO WIDTH SPACE (0x200b)
         If you are sure about this, rerun with the right flag to allow.

Any idea what the story is there?  Could I get a resend without that
problem?

Thanks,

jon
Carlos Bilbao Nov. 1, 2022, 10:33 p.m. UTC | #2 
On 11/1/22 16:30, Jonathan Corbet wrote:

> Carlos Bilbao <carlos.bilbao@amd.com> writes:
>
>> Spanish is the second most spoken language in the world. This patch set
>> starts the process of translating critical kernel documentation into the
>> Spanish language.
>>
>> Link to v2: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2022%2F10%2F13%2F866&amp;data=05%7C01%7Ccarlos.bilbao%40amd.com%7Cc3cb093ef27e484b78fa08dabc503ce0%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C638029350093417289%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=dKxHmWM4ljRyAZUw%2BpZ%2BxVM1KxIM5pR098RqnV7w2gs%3D&amp;reserved=0
>> Changes since v2:
>>    - Apply improvements proposed by Miguel Ojeda
>>    - Added Reviewed-By of Miguel Ojeda for first commit
>>    - Added Reviwed-By of Bagas Sanjaya for second commit
>>
>> Changes since v1:
>>    - Added me as MAINTAINER
>>    - Fixed warnings of kernel test robot
>>    - Use imperative form in second commit
>>    - Improved minor translation details
>>
>> Carlos Bilbao (2):
>>    Documentation: Start translations to Spanish
>>    Documentation: Add HOWTO Spanish translation into rst based build system
>>
>>    Documentation/translations/index.rst          |   1 +
>>    .../translations/sp_SP/disclaimer-sp.rst      |   6 +
>>    Documentation/translations/sp_SP/howto.rst    | 617 ++++++++++++++++++
>>    Documentation/translations/sp_SP/index.rst    |  80 +++
>>    MAINTAINERS                                   |   5 +
>>    5 files changed, 709 insertions(+)
>>    create mode 100644 Documentation/translations/sp_SP/disclaimer-sp.rst
>>    create mode 100644 Documentation/translations/sp_SP/howto.rst
>>    create mode 100644 Documentation/translations/sp_SP/index.rst
> I went to apply this series just now, and got the following from "git
> am":
>
> WARNING: Message contains suspicious unicode control characters!
>           Subject: [PATCH v3 2/2] Documentation: Add HOWTO Spanish translation into rst based build system
>              Line: +estable más reciente del kernel, y no están interesados ​​en ayudar a probar
>              ---------------------------------------------------------------^
>              Char: ZERO WIDTH SPACE (0x200b)
>           If you are sure about this, rerun with the right flag to allow.
>
> Any idea what the story is there?  Could I get a resend without that
> problem?
Just tried to apply git am and didn't get any warning. Maybe you are using
an extra flag? I'm running with git version 2.34.1. Could you try replacing
the offending char with a space? Hopefully that solves it.

I apologize for the inconvenience.

Carlos.
>
> Thanks,
>
> jon
Jonathan Corbet Nov. 1, 2022, 10:59 p.m. UTC | #3 
Carlos Bilbao <carlos.bilbao@amd.com> writes:

> On 11/1/22 16:30, Jonathan Corbet wrote:
>
>> 
>>
>> I went to apply this series just now, and got the following from "git
>> am":
>>
>> WARNING: Message contains suspicious unicode control characters!
>>           Subject: [PATCH v3 2/2] Documentation: Add HOWTO Spanish translation into rst based build system
>>              Line: +estable más reciente del kernel, y no están interesados ​​en ayudar a probar
>>              ---------------------------------------------------------------^
>>              Char: ZERO WIDTH SPACE (0x200b)
>>           If you are sure about this, rerun with the right flag to allow.
>>
>> Any idea what the story is there?  Could I get a resend without that
>> problem?
> Just tried to apply git am and didn't get any warning. Maybe you are using
> an extra flag? I'm running with git version 2.34.1. Could you try replacing
> the offending char with a space? Hopefully that solves it.

I'm sorry, it was b4 that complained, not git.  To see it happen, try:

  b4 am 20221024145521.69465-1-carlos.bilbao@amd.com

There were, in fact, two zero-width spaces in there, and two more in
Junio Hamano's name.  I've taken them all out, and learned all about
searching for weird characters in Emacs as a side benefit :)

Series is now applied, thanks.

jon
Bagas Sanjaya Nov. 2, 2022, 9:13 a.m. UTC | #4 
On 11/2/22 05:59, Jonathan Corbet wrote:
> 
> I'm sorry, it was b4 that complained, not git.  To see it happen, try:
> 
>   b4 am 20221024145521.69465-1-carlos.bilbao@amd.com
> 
> There were, in fact, two zero-width spaces in there, and two more in
> Junio Hamano's name.  I've taken them all out, and learned all about
> searching for weird characters in Emacs as a side benefit :)
> 
> Series is now applied, thanks.
> 

Hi jon,

There is still outstanding issue regarding language identifier slug [1],
which isn't addressed yet.

[1]: https://lore.kernel.org/linux-doc/48b4a5a1-2a52-4159-699b-9db73a012892@gmail.com/
[2]: https://lore.kernel.org/linux-doc/Y0ork19pGMhZq8qn@debian.me/

Thanks.
Akira Yokosawa Nov. 2, 2022, 10:05 a.m. UTC | #5 
On Wed, 2 Nov 2022 16:13:57 +0700, Bagas Sanjaya wrote:
> On 11/2/22 05:59, Jonathan Corbet wrote:
>>
>> I'm sorry, it was b4 that complained, not git.  To see it happen, try:
>>
>>   b4 am 20221024145521.69465-1-carlos.bilbao@amd.com
>>
>> There were, in fact, two zero-width spaces in there, and two more in
>> Junio Hamano's name.  I've taken them all out, and learned all about
>> searching for weird characters in Emacs as a side benefit :)
>>
>> Series is now applied, thanks.
>>
> 
> Hi jon,
> 
> There is still outstanding issue regarding language identifier slug [1],
> which isn't addressed yet.
> 
> [1]: https://lore.kernel.org/linux-doc/48b4a5a1-2a52-4159-699b-9db73a012892@gmail.com/
To be clear, I'm OK with sp_SP/ with the explanation given in the changelog
of v3 1/2.

Regards,
Akira

> [2]: https://lore.kernel.org/linux-doc/Y0ork19pGMhZq8qn@debian.me/
> 
> Thanks.
>
Jonathan Corbet Nov. 2, 2022, 2:05 p.m. UTC | #6 
Bagas Sanjaya <bagasdotme@gmail.com> writes:

> On 11/2/22 05:59, Jonathan Corbet wrote:
>> 
>> I'm sorry, it was b4 that complained, not git.  To see it happen, try:
>> 
>>   b4 am 20221024145521.69465-1-carlos.bilbao@amd.com
>> 
>> There were, in fact, two zero-width spaces in there, and two more in
>> Junio Hamano's name.  I've taken them all out, and learned all about
>> searching for weird characters in Emacs as a side benefit :)
>> 
>> Series is now applied, thanks.
>> 
>
> Hi jon,
>
> There is still outstanding issue regarding language identifier slug [1],
> which isn't addressed yet.
>
> [1]: https://lore.kernel.org/linux-doc/48b4a5a1-2a52-4159-699b-9db73a012892@gmail.com/
> [2]: https://lore.kernel.org/linux-doc/Y0ork19pGMhZq8qn@debian.me/

Well, it's clearly somewhat resolved in that I took the patches.

If we want a policy: I think that names not tied to geography are
probably better and that's what we should do in the future.  I don't
think it's worth forcing a change on any of the other translations,
though; they can be renamed if the developers involved choose to do so.

jon