Fwd: XDG critical grammar issue

Philipp Wolfer <[email protected]> Fri, 21 Jun 2024 14:46:42 +0200
Newsgroups gmane.linux.xdg.devel
Message-ID <CAP9XNzR2q0bWJoY=Q=zhEvsbM-9CtbX+--0ygNFn4ggHF6tnQw@mail.gmail.com>
--000000000000ee0dc1061b65d432
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Am Fr., 21. Juni 2024 um 11:00 Uhr schrieb David Chmelik <[email protected]=
m
>:

> [...]
>
> A bugs.KDE.org person mistakenly told me it's 'title case', but most
> aren't names/titles rather than generic (non-title) categories--as in my
> first paragraph's example--which aren't proper nouns.
>


Some notes just because I researched the user interface capitalization
standards for various platforms recently. Title case (
https://en.wikipedia.org/wiki/Title_case) for many UI elements is very
common and actually recommended in the style guides for various platforms.
That's true for window titles, but also notably for button labels and menu
items.

Here are a few key guidelines:

*Microsoft style guides* recommend title case only for window titles,
sentence case otherwise. See

https://learn.microsoft.com/en-us/windows/win32/uxguide/text-ui#capitalizat=
ion

*Use title-style capitalization for titles, sentence-style capitalization
for all other UI elements. *

It's worth mentioning that the older style preferred title case for more UI
elements, including buttons.


The *Apple human interface guidelines* leaves it to each app whether they
want to use title or sentence case, but it should be done consistently. See=
:

https://developer.apple.com/design/human-interface-guidelines/writing#Best-=
practices
<https://developer.apple.com/design/human-interface-guidelines/writing>

*Decide whether you want to use title case or sentence case for alerts,
page titles, headlines, button labels, and links. Throughout the HIG,
you=E2=80=99ll find guidelines for specific components, but how you format =
your
text is a reflection of your app=E2=80=99s voice. Title case is more formal=
, while
sentence case is more casual. Choose a style that fits your app.*

They do recommend title case for menu items (but it is preferable to use
single word items):

*Use title-style capitalization if you need to use more than one word in
the menu title.*

and for buttons:

*Using title-style capitalization, consider starting the label with a verb
to help convey the button=E2=80=99s action =E2=80=94 for example, a button =
that lets people
add items to their shopping cart might use the label =E2=80=9CAdd to Cart.=
=E2=80=9D*



The *GNOME human interface guidelines* tend more towards using title case
for most elements

*Header capitalization should be used for any headings, including headings
in header bars, tab titles, and view titles. It should also be used for
short control labels that do not normally form proper sentences, such as
button labels, switch labels and menu items.*

https://developer.gnome.org/hig/guidelines/writing-style.html#capitalizatio=
n



The *KDE human interface guidelines* are in this regard similar to GNOME:

https://develop.kde.org/hig/text_and_labels/#capitalization-and-punctuation

*Android Material 3 guidelines* recommend sentence case:

https://m3.material.io/foundations/content-design/style-guide/ux-writing-be=
st-practices

--=20
Philipp


--=20
Philipp Wolfer

--000000000000ee0dc1061b65d432
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Am Fr., 21. Juni 2024 um 11:00=C2=A0Uhr schrieb David Chme=
lik &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">dchmelik@gm=
ail.com</a>&gt;:<div class=3D"gmail_quote"><div dir=3D"ltr"><div dir=3D"ltr=
"><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">[...]<br><br></blockquote><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">
A <a href=3D"http://bugs.KDE.org" rel=3D"noreferrer" target=3D"_blank">bugs=
.KDE.org</a> person mistakenly told me it&#39;s &#39;title case&#39;, but m=
ost <br>
aren&#39;t names/titles rather than generic (non-title) categories--as in m=
y <br>
first paragraph&#39;s example--which aren&#39;t proper nouns.<br>
</blockquote></div><br clear=3D"all"><br></div><div>Some notes just because=
 I researched the user interface capitalization standards for various platf=
orms recently. Title case (<a href=3D"https://en.wikipedia.org/wiki/Title_c=
ase" target=3D"_blank">https://en.wikipedia.org/wiki/Title_case</a>) for ma=
ny UI elements is very common and actually recommended in the style guides =
for various platforms. That&#39;s true for window titles, but also notably =
for button labels and menu items.</div><div><br></div><div></div><div>Here =
are a few key guidelines:<br></div><div></div><div><br></div><div><p><b>Mic=
rosoft style guides</b> recommend title case only for window titles, senten=
ce case otherwise. See</p>

<p><a href=3D"https://learn.microsoft.com/en-us/windows/win32/uxguide/text-=
ui#capitalization" rel=3D"nofollow noopener" target=3D"_blank">https://lear=
n.microsoft.com/en-us/windows/win32/uxguide/text-ui#capitalization</a></p>
<blockquote><p><i>Use title-style capitalization for titles, sentence-style=
 capitalization for all other UI elements.=C2=A0</i></p></blockquote>
<p>It&#39;s worth mentioning that the older style preferred title case for =
more UI elements, including buttons.<br></p><p><br></p><p>The <b>Apple huma=
n interface guidelines</b> leaves it to each app whether they want to use t=
itle or sentence case, but it should be done consistently. See:</p>

<p><a href=3D"https://developer.apple.com/design/human-interface-guidelines=
/writing" rel=3D"nofollow noopener" target=3D"_blank">https://developer.app=
le.com/design/human-interface-guidelines/writing#Best-practices</a></p>
<blockquote><p><i>Decide whether you want to use title case or sentence=20
case for alerts, page titles, headlines, button labels, and links.=20
Throughout the HIG, you=E2=80=99ll find guidelines for specific components,=
 but=20
how you format your text is a reflection of your app=E2=80=99s voice. Title=
 case
 is more formal, while sentence case is more casual. Choose a style that
 fits your app.</i></p></blockquote>
<p>They do recommend title case for menu items (but it is preferable to use=
 single word items):</p>
<blockquote><p><i>Use title-style capitalization if you need to use more th=
an one word in the menu title.</i></p></blockquote>
<p>and for buttons:</p>
<blockquote><p><i>Using title-style capitalization,
 consider starting the label with a verb to help convey the button=E2=80=99=
s=20
action =E2=80=94 for example, a button that lets people add items to their=
=20
shopping cart might use the label =E2=80=9CAdd to Cart.=E2=80=9D</i></p></b=
lockquote><p>=C2=A0</p><p>The <b>GNOME human interface guidelines</b> tend =
more towards using title case for most elements</p>
<blockquote><p><i>Header capitalization should be used for any headings,=20
including headings in header bars, tab titles, and view titles. It=20
should also be used for short control labels that do not normally form=20
proper sentences, such as button labels, switch labels and menu items.</i><=
/p></blockquote>
<p><a href=3D"https://developer.gnome.org/hig/guidelines/writing-style.html=
#capitalization" rel=3D"nofollow noopener" target=3D"_blank">https://develo=
per.gnome.org/hig/guidelines/writing-style.html#capitalization</a></p>

<p>=C2=A0</p>

<p>The <b>KDE human interface guidelines</b> are in this regard similar to =
GNOME:</p><p><a href=3D"https://develop.kde.org/hig/text_and_labels/#capita=
lization-and-punctuation" rel=3D"nofollow noopener" target=3D"_blank">https=
://develop.kde.org/hig/text_and_labels/#capitalization-and-punctuation</a><=
/p></div></div><div><br></div><div><p><b>Android Material 3 guidelines</b> =
recommend sentence case:</p>

<p><a href=3D"https://m3.material.io/foundations/content-design/style-guide=
/ux-writing-best-practices" rel=3D"nofollow noopener" target=3D"_blank">htt=
ps://m3.material.io/foundations/content-design/style-guide/ux-writing-best-=
practices</a></p></div><div><span class=3D"gmail_signature_prefix"><br></sp=
an></div><div><span class=3D"gmail_signature_prefix">-- </span></div><div d=
ir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"=
><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">Philipp<=
br></div></div></div></div></div></div></div></div></div></div></div>
</div><br clear=3D"all"><br><span class=3D"gmail_signature_prefix">-- </spa=
n><br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_si=
gnature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><span>Philipp Wolfer</=
span></div></div></div></div></div></div>

--000000000000ee0dc1061b65d432--