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

[Jonathan Corbet]

Carlos Bilbao <carlos.bilbao@xxxxxxx> 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