[prev in list] [next in list] [prev in thread] [next in thread]
List: kwin
Subject: Re: Review Request 118338: [kwin] Streamline Comment fields of KCMs
From: Sebastian_Kügler <sebas () kde ! org>
Date: 2014-05-27 13:55:13
Message-ID: 20140527135513.21363.96160 () probe ! kde ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> On May 27, 2014, 5:23 a.m., Martin Gräßlin wrote:
> > kcmkwin/kwincompositing/kwincompositing.desktop, line 15
> > <https://git.reviewboard.kde.org/r/118338/diff/1/?file=275206#file275206line15>
> >
> > Why "Graphics"? Which graphics is it compositing? Those in Krita?
>
> Thomas Lübking wrote:
> the problematic term is actually "compositor" - prepending anything won't help but \
> only confuse the savvy. "advanced/enhanced window/desktop rendering (the \
> compositor)"?
> stay away from "acceleration" - it's accelerated, but doesn't accelerate (slow \
> window paints slow)... except moving windows around ;-)
Well, I asked myself the question the other way round: Which compositor? Mozart? What \
is it compositing? Layered cakes?
"Which graphics?" is clear from the context, the whole systemsettings section is \
about how hardware is used, that makes it clear that is has to do with graphics \
hardware, even if "compositing" doesn't bear a meaning for this user.
> On May 27, 2014, 5:23 a.m., Martin Gräßlin wrote:
> > kcmkwin/kwinrules/kwinrules.desktop, line 77
> > <https://git.reviewboard.kde.org/r/118338/diff/1/?file=275214#file275214line77>
> >
> > I would go with "Window Specific Rules"
I used that initially, but it would have to be "Window-Specific Rules", which does \
look a bit uncommon to me (dash and capitalization), so I avoided it.
I'll send an updated version with the other changes later.
- Sebastian
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118338/#review58535
-----------------------------------------------------------
On May 27, 2014, 12:26 a.m., Sebastian Kügler wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/118338/
> -----------------------------------------------------------
>
> (Updated May 27, 2014, 12:26 a.m.)
>
>
> Review request for kwin, Localization and Translation (l10n) and KDE Usability.
>
>
> Repository: kwin
>
>
> Description
> -------
>
> [kwin] Streamline Comment fields of KCMs
>
> This patch applies a common language and type-setting to the
> systemsettings modules in kwin.
>
> Considerations:
> - The comment field might repeat the name, or give more detail about the
> specific settings on this page, this makes sense with how
> systemsettings and kcmshell present it
> - Mentioning the words settings, configure, options, etc. is avoided --
> it is clear from the context that these are settings and options.
> - Title-case throughout in line with human interface guidelines, see
> http://techbase.kde.org/Projects/Usability/HIG/Capitalization
> - The comment ends up being the title, so the
> - tech slang is avoided as much as possible, but left in where really
> necessary
> - I've left the Name field "mostly untouched", as that one is key for
> the user to find the right module in systemsettings' icon view and in
> the sidebars
>
> The most prominent change is "Compositor" to "Graphics Compositor" (in
> the Title field). This is more like a "suggestion", if you don't like
> it, I'll take it out again. Reasoning: "Compositor" is a very technical
> term, people who know graphics might recognize it. Others might not
> understand that "composite" is about graphics -- hence the
> specialization.
>
>
> Diffs
> -----
>
> kcmkwin/kwincompositing/kcmkwineffects.desktop \
> 390199bbd04d2fb485cc5f0af2de8481b7c43c5a \
> kcmkwin/kwincompositing/kwincompositing.desktop \
> 087b589c942cd204f7cbecd9e1bfb8bd9dfbd714 \
> kcmkwin/kwindecoration/kwindecoration.desktop \
> 51a20348d220b1e6a0072e5638889c0b52033fb2 kcmkwin/kwindesktop/desktop.desktop \
> 9e9506cc160f15e0acbad71e1925fe27b1e2ca0b kcmkwin/kwinoptions/kwinactions.desktop \
> 0ebd40ce4013fa8bc2e4e1df1f872eee9e50dc3c kcmkwin/kwinoptions/kwinadvanced.desktop \
> 6cbb95a5f29ad862fdd3ccc84de204411b0a5985 kcmkwin/kwinoptions/kwinfocus.desktop \
> d50fb8287e90c4ca5415be92956bca43d849e74c kcmkwin/kwinoptions/kwinmoving.desktop \
> cd6dcbca39af3280601be7c4026957de0712283b kcmkwin/kwinoptions/kwinoptions.desktop \
> 6075a5c0df088d3bfc74fba317ec17a3577a6103 kcmkwin/kwinrules/kwinrules.desktop \
> cded4371548872cf4c21a636b29ee20c5b81de67 \
> kcmkwin/kwinscreenedges/kwinscreenedges.desktop \
> 404f28afb0c9bfe2fbbf4ff0e15410f0a7aead1e kcmkwin/kwintabbox/kwintabbox.desktop \
> 5955e106b047de22a4439ae6589f9e10a3e2df36
> Diff: https://git.reviewboard.kde.org/r/118338/diff/
>
>
> Testing
> -------
>
>
> Thanks,
>
> Sebastian Kügler
>
>
[Attachment #5 (text/html)]
<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 \
solid;"> <tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://git.reviewboard.kde.org/r/118338/">https://git.reviewboard.kde.org/r/118338/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <p style="margin-top: 0;">On May 27th, 2014, 5:23 a.m. UTC, <b>Martin \
Gräßlin</b> wrote:</p> <blockquote style="margin-left: 1em; border-left: 2px solid \
#d0d0d0; padding-left: 10px;">
<table width="100%" border="0" bgcolor="white" style="border: 1px solid #C0C0C0; \
border-collapse: collapse; margin: 2px padding: 2px;"> <thead>
<tr>
<th colspan="4" bgcolor="#F0F0F0" style="border-bottom: 1px solid #C0C0C0; \
font-size: 9pt; padding: 4px 8px; text-align: left;"> <a \
href="https://git.reviewboard.kde.org/r/118338/diff/1/?file=275206#file275206line15" \
style="color: black; font-weight: bold; text-decoration: \
underline;">kcmkwin/kwincompositing/kwincompositing.desktop</a> <span \
style="font-weight: normal;">
(Diff revision 1)
</span>
</th>
</tr>
</thead>
<tbody>
<tr>
<th bgcolor="#e9eaa8" style="border-right: 1px solid #C0C0C0;" \
align="right"><font size="2">15</font></th> <td bgcolor="#fdfebc" width="50%"><pre \
style="font-size: 8pt; line-height: 140%; margin: 0; ">Name=Compositor</pre></td> \
<th bgcolor="#e9eaa8" style="border-left: 1px solid #C0C0C0; border-right: 1px solid \
#C0C0C0;" align="right"><font size="2">15</font></th> <td bgcolor="#fdfebc" \
width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; ">Name=<span \
class="hl">Graphics </span>Compositor</pre></td> </tr>
</tbody>
</table>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Why \
"Graphics"? Which graphics is it compositing? Those in Krita?</pre> \
</blockquote>
<p>On May 27th, 2014, 7:11 a.m. UTC, <b>Thomas Lübking</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">the problematic term is \
actually "compositor" - prepending anything won't help but only confuse \
the savvy. "advanced/enhanced window/desktop rendering (the compositor)"?
stay away from "acceleration" - it's accelerated, but doesn't \
accelerate (slow window paints slow)... except moving windows around ;-)</pre> \
</blockquote>
</blockquote>
<pre style="margin-left: 1em; white-space: pre-wrap; white-space: -moz-pre-wrap; \
white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Well, I \
asked myself the question the other way round: Which compositor? Mozart? What is it \
compositing? Layered cakes?
"Which graphics?" is clear from the context, the whole systemsettings \
section is about how hardware is used, that makes it clear that is has to do with \
graphics hardware, even if "compositing" doesn't bear a meaning for \
this user.</pre> <br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <p style="margin-top: 0;">On May 27th, 2014, 5:23 a.m. UTC, <b>Martin \
Gräßlin</b> wrote:</p> <blockquote style="margin-left: 1em; border-left: 2px solid \
#d0d0d0; padding-left: 10px;">
<table width="100%" border="0" bgcolor="white" style="border: 1px solid #C0C0C0; \
border-collapse: collapse; margin: 2px padding: 2px;"> <thead>
<tr>
<th colspan="4" bgcolor="#F0F0F0" style="border-bottom: 1px solid #C0C0C0; \
font-size: 9pt; padding: 4px 8px; text-align: left;"> <a \
href="https://git.reviewboard.kde.org/r/118338/diff/1/?file=275214#file275214line77" \
style="color: black; font-weight: bold; text-decoration: \
underline;">kcmkwin/kwinrules/kwinrules.desktop</a> <span style="font-weight: \
normal;">
(Diff revision 1)
</span>
</th>
</tr>
</thead>
<tbody>
<tr>
<th bgcolor="#e9eaa8" style="border-right: 1px solid #C0C0C0;" \
align="right"><font size="2">77</font></th> <td bgcolor="#fdfebc" width="50%"><pre \
style="font-size: 8pt; line-height: 140%; margin: 0; ">Comment=Configure settings \
specifically for a window</pre></td> <th bgcolor="#e9eaa8" style="border-left: 1px \
solid #C0C0C0; border-right: 1px solid #C0C0C0;" align="right"><font \
size="2">77</font></th> <td bgcolor="#fdfebc" width="50%"><pre style="font-size: \
8pt; line-height: 140%; margin: 0; ">Comment=Rules for Specific Windows</pre></td> \
</tr>
</tbody>
</table>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I would go with \
"Window Specific Rules"</pre> </blockquote>
</blockquote>
<pre style="margin-left: 1em; white-space: pre-wrap; white-space: -moz-pre-wrap; \
white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I used that \
initially, but it would have to be "Window-Specific Rules", which does look \
a bit uncommon to me (dash and capitalization), so I avoided it.
I'll send an updated version with the other changes later.</pre>
<br />
<p>- Sebastian</p>
<br />
<p>On May 27th, 2014, 12:26 a.m. UTC, Sebastian Kügler wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" \
style="background-image: \
url('https://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); \
background-position: left top; background-repeat: repeat-x; border: 1px black \
solid;"> <tr>
<td>
<div>Review request for kwin, Localization and Translation (l10n) and KDE \
Usability.</div> <div>By Sebastian Kügler.</div>
<p style="color: grey;"><i>Updated May 27, 2014, 12:26 a.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
kwin
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" \
style="border: 1px solid #b8b5a0"> <tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;">[kwin] Streamline Comment fields of KCMs
This patch applies a common language and type-setting to the
systemsettings modules in kwin.
Considerations:
- The comment field might repeat the name, or give more detail about the
specific settings on this page, this makes sense with how
systemsettings and kcmshell present it
- Mentioning the words settings, configure, options, etc. is avoided --
it is clear from the context that these are settings and options.
- Title-case throughout in line with human interface guidelines, see
http://techbase.kde.org/Projects/Usability/HIG/Capitalization
- The comment ends up being the title, so the
- tech slang is avoided as much as possible, but left in where really
necessary
- I've left the Name field "mostly untouched", as that one is key for
the user to find the right module in systemsettings' icon view and in
the sidebars
The most prominent change is "Compositor" to "Graphics \
Compositor" (in the Title field). This is more like a "suggestion", if \
you don't like it, I'll take it out again. Reasoning: "Compositor" \
is a very technical term, people who know graphics might recognize it. Others might \
not understand that "composite" is about graphics -- hence the
specialization.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>kcmkwin/kwincompositing/kcmkwineffects.desktop <span style="color: \
grey">(390199bbd04d2fb485cc5f0af2de8481b7c43c5a)</span></li>
<li>kcmkwin/kwincompositing/kwincompositing.desktop <span style="color: \
grey">(087b589c942cd204f7cbecd9e1bfb8bd9dfbd714)</span></li>
<li>kcmkwin/kwindecoration/kwindecoration.desktop <span style="color: \
grey">(51a20348d220b1e6a0072e5638889c0b52033fb2)</span></li>
<li>kcmkwin/kwindesktop/desktop.desktop <span style="color: \
grey">(9e9506cc160f15e0acbad71e1925fe27b1e2ca0b)</span></li>
<li>kcmkwin/kwinoptions/kwinactions.desktop <span style="color: \
grey">(0ebd40ce4013fa8bc2e4e1df1f872eee9e50dc3c)</span></li>
<li>kcmkwin/kwinoptions/kwinadvanced.desktop <span style="color: \
grey">(6cbb95a5f29ad862fdd3ccc84de204411b0a5985)</span></li>
<li>kcmkwin/kwinoptions/kwinfocus.desktop <span style="color: \
grey">(d50fb8287e90c4ca5415be92956bca43d849e74c)</span></li>
<li>kcmkwin/kwinoptions/kwinmoving.desktop <span style="color: \
grey">(cd6dcbca39af3280601be7c4026957de0712283b)</span></li>
<li>kcmkwin/kwinoptions/kwinoptions.desktop <span style="color: \
grey">(6075a5c0df088d3bfc74fba317ec17a3577a6103)</span></li>
<li>kcmkwin/kwinrules/kwinrules.desktop <span style="color: \
grey">(cded4371548872cf4c21a636b29ee20c5b81de67)</span></li>
<li>kcmkwin/kwinscreenedges/kwinscreenedges.desktop <span style="color: \
grey">(404f28afb0c9bfe2fbbf4ff0e15410f0a7aead1e)</span></li>
<li>kcmkwin/kwintabbox/kwintabbox.desktop <span style="color: \
grey">(5955e106b047de22a4439ae6589f9e10a3e2df36)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/118338/diff/" style="margin-left: \
3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic