From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [RFC 1/1] Start of documentation standards document
Date: Fri, 22 Oct 2021 18:23:02 +0200 [thread overview]
Message-ID: <ad09d687-4114-450d-0a84-ed2744384793@bootlin.com> (raw)
In-Reply-To: <20211011132004.n7cwcmzuc2qaqvzs@fedora>
Hi Quentin,
Many thanks for the review and the fixes!
I took all your suggestions. Let me just comment the open questions.
On 10/11/21 3:20 PM, Quentin Schulz wrote:
>
>> +The "GNOME HIG Colors" palette is used for our graphics
>> +(get it from <https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.gnome.org_Teams_Design_HIG-2Dapp-2Dicons_-2D_blob_master_GNOME-2520HIG.gpl&d=DwIFAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=QF3FZ993w-Eq44rMQY6KNn14ixpGQT25sTiSTI-PGOPWUDrRFhSlyigzrwqiikfb&s=6cYqH1OYrt_hp21c09Bm4naMFbxGx6VNLQ24IwHZ8H8&e= >
>> +if you don't have it in your installation of Inkscape)
>> +
> "if you don't get it from Inkscape" ?
>
> In any case, missing a point at the end of the sentence.
I'll let you check the update I'm sending soon.
> While we're at the moment we pick color palettes, are we sure this one
> is ok for colorblind people?
Oops, that's a serious concern. This prompted me to read
https://www.smashingmagazine.com/2016/06/improving-color-accessibility-for-color-blind-users/
Perhaps we should state that graphical items shouldn't be differentiated
by color only. They should also use a different shape, pattern or
different text. We could also make it mandatory to write text in black
or white with sufficient contrast with the background.
In particular, using "red" or "green" should be the only way to
differentiate between correct and incorrect. Additional shapes (such as
STOP and OK signs) and text should explicit the difference.
What do you think?
> I would even go as far as to say the source of the clipart should be
> given in the commit log so that we can check ourselves?
Makes sense. I added this.
>
> Thanks for starting this Michael, long overdue :)
>
> I shall dig into my mail archives to add the rST rules we came up with
> some months ago :)
I'm definitely interested in these rules.
Many thanks,
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2021-10-22 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 18:58 [RFC 0/1] Documentation standards Michael Opdenacker
2021-10-08 18:58 ` [RFC 1/1] Start of documentation standards document Michael Opdenacker
2021-10-11 13:20 ` [docs] " Quentin Schulz
2021-10-22 16:23 ` Michael Opdenacker [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=ad09d687-4114-450d-0a84-ed2744384793@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@theobroma-systems.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;
as well as URLs for NNTP newsgroup(s).