From: Min-Hua Chen <minhuadotchen@gmail.com>
To: corbet@lwn.net
Cc: linux-doc-tw-discuss@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
minhuadotchen@gmail.com, rdunlap@infradead.org, src.res@email.cn
Subject: Re: [PATCH v3 0/3] convert TW translation sparse.txt to RST
Date: Wed, 4 Oct 2023 07:40:41 +0800 [thread overview]
Message-ID: <20231003234041.3929-1-minhuadotchen@gmail.com> (raw)
In-Reply-To: <8734yrekon.fsf@meer.lwn.net>
>> docs: sparse: move TW sparse.txt to TW dev-tools
>> docs: sparse: convert sparse.txt to RST
>> docs: sparse: add sparse.rst to toctree
>>
>> .../translations/zh_TW/dev-tools/index.rst | 40 +++++++++++++++++++
>> .../{sparse.txt =3D> dev-tools/sparse.rst} | 2 +-
>> Documentation/translations/zh_TW/index.rst | 2 +-
>> 3 files changed, 42 insertions(+), 2 deletions(-)
>> create mode 100644 Documentation/translations/zh_TW/dev-tools/index.rst
>> rename Documentation/translations/zh_TW/{sparse.txt =3D> dev-tools/spars=
>e.rst} (99%)
>
>So this series introduces a new warning:
>
>WARNING: Unparseable C cross-reference: 'int'
>Invalid C declaration: Expected identifier in nested name, got keyword: int=
> [error at 3]
> int
> ---^
>
>That is ... somewhat unhelpful. I eventually tracked it down to this
>piece in sparse.rst:
>
>> =E6=89=80=E4=BB=A5=E6=9B=B4=E7=B0=A1=E5=96=AE=E7=9A=84=E8=BE=A6=E6=B3=95=
>=E5=8F=AA=E8=A6=81=E9=80=99=E6=A8=A3=E5=81=9A=EF=BC=9A
>>=20
>> typedef int __bitwise pm_request_t;
>>=20
>> #define PM_SUSPEND ((__force pm_request_t) 1)
>> #define PM_RESUME ((__force pm_request_t) 2)
>>=20
>> =E7=8F=BE=E5=9C=A8=E4=BD=A0=E5=B0=B1=E6=9C=89=E4=BA=86=E5=9A=B4=E6=A0=BC=
>=E7=9A=84=E9=A1=9E=E5=9E=8B=E6=AA=A2=E6=9F=A5=E6=89=80=E9=9C=80=E8=A6=81=E7=
>=9A=84=E6=89=80=E6=9C=89=E5=9F=BA=E7=A4=8E=E6=9E=B6=E6=A7=8B=E3=80=82
>
>That needs to be a literal block to be parsed properly. I have taken
>the liberty of changing the first line above to:
>
>> =E6=89=80=E4=BB=A5=E6=9B=B4=E7=B0=A1=E5=96=AE=E7=9A=84=E8=BE=A6=E6=B3=95=
>=E5=8F=AA=E8=A6=81=E9=80=99=E6=A8=A3=E5=81=9A::
>
>...and the warning is gone.
>
>Thus: series applied, but please properly build-test changes like this
>in the future.
>
>Thanks,
>
>jon
Got it, thank you for doing this.
I will do build-test with care in the future.
Min-Hua
prev parent reply other threads:[~2023-10-03 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 5:25 [PATCH v3 0/3] convert TW translation sparse.txt to RST Min-Hua Chen
2023-09-02 5:25 ` [PATCH v3 1/3] docs: sparse: move TW sparse.txt to TW dev-tools Min-Hua Chen
2023-09-02 5:25 ` [PATCH v3 2/3] docs: sparse: convert sparse.txt to RST Min-Hua Chen
2023-09-02 5:25 ` [PATCH v3 3/3] docs: sparse: add sparse.rst to toctree Min-Hua Chen
2023-10-03 16:26 ` [PATCH v3 0/3] convert TW translation sparse.txt to RST Jonathan Corbet
2023-10-03 23:40 ` Min-Hua Chen [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=20231003234041.3929-1-minhuadotchen@gmail.com \
--to=minhuadotchen@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc-tw-discuss@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=src.res@email.cn \
/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