From: Alejandro Colomar <alx@kernel.org>
To: 凄临雨 <superzmy@qq.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Feedback on Linux Manual Website - Translation Feature Compatibility
Date: Wed, 1 May 2024 12:13:49 +0200 [thread overview]
Message-ID: <ZjIV5KYc21zdl4eG@debian> (raw)
In-Reply-To: <tencent_B0B00C911A5C95BC9167B6D4E5BEF4251006@qq.com>
[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]
Hi zmy,
On Wed, May 01, 2024 at 12:18:35PM +0800, 凄临雨 wrote:
> Feedback on Linux Manual Website - Translation Feature Compatibility
>
> Dear Linux Manual Web Team,
>
> I hope you are doing well. I am reaching out to provide some feedback
> regarding the Linux Manual website that I believe could help improve
> its usability for a wider audience.
Can you please provide a link to the website you're referring to?
> I have noticed that the <pre> tags used on the website to display
> code and command examples are not compatible with the translation
> features embedded in web browsers.
The current website is <https://www.kernel.org/doc/man-pages/>, but that
is minimal and doesn't have any <pre> tags.
Or maybe you're referring to
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/README>
?
That's not the website, but rather a web view of the source code of the
repository. It does use <pre> for everything, but because it's
formatting an entire file in the source repository.
Have a lovely day!
Alex
> This has created a barrier for
> non-native English speakers who rely on these translation tools to
> better understand the technical content presented.
>
> The use of <pre> tags to preserve the formatting of code blocks
> unfortunately prevents these users from being able to translate the
> text easily. While the intention to maintain the original formatting
> is appreciated, it would be beneficial to explore alternatives that
> allow the translation functionality to work alongside the display of
> code.
>
> I wanted to bring this to your attention as it impacts the
> accessibility of the content for international users. I believe
> addressing this could significantly enhance the user experience for a
> diverse audience.
>
> Thank you for the excellent resources you provide to the Linux
> community, and for considering this feedback.
>
> Warm regards,
>
> zmy
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2024-05-01 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_B0B00C911A5C95BC9167B6D4E5BEF4251006@qq.com>
2024-05-01 10:13 ` Alejandro Colomar [this message]
2024-05-02 11:58 ` =?gb18030?B?u9i4tKO6IEZlZWRiYWNrIG9uIExpbnV4IE1hbnVhbCBXZWJzaXRlIC0gVHJhbnNsYXRpb24gRmVhdHVyZSBDb21wYXRpYmlsaXR5?= =?gb18030?B?xuDB2dPq?=
2024-05-02 13:36 ` 回复: Feedback on Linux Manual Website - Translation Feature Compatibility Alejandro Colomar
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=ZjIV5KYc21zdl4eG@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=superzmy@qq.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