Re: XDG critical grammar issue

"Bollinger, John" <[email protected]> Mon, 24 Jun 2024 13:51:41 +0000
Newsgroups gmane.linux.xdg.devel
Message-ID <CH2PR04MB6950675D16BC11D9008B9786E0D42@CH2PR04MB6950.namprd04.prod.outlook.com>
--_000_CH2PR04MB6950675D16BC11D9008B9786E0D42CH2PR04MB6950namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


It's well and good to desire more customization options for users, but that=
's still not an XDG issue.  Rather:

  *
it is within the power and scope of responsibility of each desktop project =
(GNOME, for example) to provide a way for users to opt for window titles, m=
enu items, etc. to be presented in differently-cased form than is read from=
 .desktop files, if the project should choose to do so.
  *
it is within the power and scope of responsibility of projects and redistri=
butors that provide .desktop files to provide string content within, includ=
ing internationalized content, in an appropriate form (whatever that means,=
 contextually).

XDG is not in control of those details, nor should it be.


Best,

John Bollinger

________________________________
From: xdg <[email protected]> on behalf of David Chmelik <d=
[email protected]>
Sent: Saturday, June 22, 2024 8:06 PM
To: [email protected] <[email protected]>
Subject: Re: XDG critical grammar issue

[You don't often get email from [email protected]. Learn why this is impor=
tant at https://aka.ms/LearnAboutSenderIdentification ]

Caution: External Sender. Do not open unless you know the content is safe.


On Fri, 21 Jun 2024 08:50:04 -0000 (UTC), David Chmelik wrote:
People convinced me it's a style issue, though my opinion hasn't changed
what should(n't) be titles, so I wish users that don't edit XDG code have
more choice.



________________________________

Email Disclaimer: www.stjude.org/emaildisclaimer
Consultation Disclaimer: www.stjude.org/consultationdisclaimer

--_000_CH2PR04MB6950675D16BC11D9008B9786E0D42CH2PR04MB6950namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
It's well and good to desire more customization options for users, but that=
's still not an XDG issue.&nbsp; Rather:</div>
<ul>
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
it is within the power and scope of responsibility of each desktop project =
(GNOME, for example) to provide a way for users to opt for window titles, m=
enu items, etc. to be presented in differently-cased form than is read from=
 .desktop files, if the project
 should choose to do so.</div>
</li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi=
ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
it is within the power and scope of responsibility of projects and redistri=
butors that provide .desktop files to provide string content within, includ=
ing internationalized content, in an appropriate form (whatever that means,=
 contextually).</div>
</li></ul>
<div id=3D"appendonsend"></div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
XDG is not in control of those details, nor should it be.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Best,</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
John Bollinger</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<hr style=3D"display: inline-block; width: 98%;">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><span style=3D"font-family: Calibri, =
sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b>&nbsp;xdg &l=
t;[email protected]&gt; on behalf of David Chmelik &lt;dchm=
[email protected]&gt;<br>
<b>Sent:</b>&nbsp;Saturday, June 22, 2024 8:06 PM<br>
<b>To:</b>&nbsp;[email protected] &lt;[email protected]&gt;=
<br>
<b>Subject:</b>&nbsp;Re: XDG critical grammar issue</span>
<div>&nbsp;</div>
</div>
<div style=3D"font-size: 11pt;">[You don't often get email from dchmelik@gm=
ail.com. Learn why this is important at
<a href=3D"https://aka.ms/LearnAboutSenderIdentification" id=3D"OWA664bdee7=
-96aa-0cef-3b04-c4e4b3bb884b" class=3D"OWAAutoLink" data-auth=3D"NotApplica=
ble">
https://aka.ms/LearnAboutSenderIdentification</a>&nbsp;]<br>
<br>
Caution: External Sender. Do not open unless you know the content is safe.<=
br>
<br>
<br>
On Fri, 21 Jun 2024 08:50:04 -0000 (UTC), David Chmelik wrote:<br>
People convinced me it's a style issue, though my opinion hasn't changed<br=
>
what should(n't) be titles, so I wish users that don't edit XDG code have<b=
r>
more choice.<br>
<br>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"2"><br>
Email Disclaimer: www.stjude.org/emaildisclaimer<br>
Consultation Disclaimer: www.stjude.org/consultationdisclaimer<br>
</font>
</body>
</html>

--_000_CH2PR04MB6950675D16BC11D9008B9786E0D42CH2PR04MB6950namp_--