[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: Review Request 124328: Man pages for kapidox
From: "Allen Winter" <winter () kde ! org>
Date: 2015-07-14 23:38:20
Message-ID: 20150714233820.27368.51615 () mimi ! kde ! org
[Download RAW message or body]
--===============8994471890688640405==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
> On July 12, 2015, 4:45 p.m., Kevin Krammer wrote:
> > I thought our man pages are written in docbook and then translated by the usual \
> > docbook workflow?
>
> Albert Astals Cid wrote:
> Correct.
>
> Luigi Toscano wrote:
> Yes, because they can be translated. But that means a dependency on kdoctools. On \
> the other side, kapidox is a tier1 (I would say tier0) project, it's python, it's \
> not really Qt based. I don't have a proper solution for this problem right now.
> Scott Kitterman wrote:
> It's really different than the other frameworks. It's not a framework as much as a \
> tool (Python application) for developing the frameworks. I don't think it \
> can/should be done exactly the same as everything else.
> Albert Astals Cid wrote:
> I'm not happy for not keeping our requeriment that our user visible stuff is \
> translatable.
> Scott Kitterman wrote:
> The --help output (which is the only documentation that's currently provided) is \
> already not translatable, so this is no different.
> David Faure wrote:
> This is not user visible. It's not even visible to application developers, IIUC.
> It's an internal tool, much like kde-dev-scripts (in fact this stuff could have \
> been put in kde-dev-scripts...), where none of the scripts have translatable help.
> Allen Winter wrote:
> then I drop my objection. I can read troff well enough :)
>
> Scott Kitterman wrote:
> OK. Does that mean I can go back to Alex Merry's shipit and push the change?
yes.
- Allen
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124328/#review82397
-----------------------------------------------------------
On July 12, 2015, 4 p.m., Scott Kitterman wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/124328/
> -----------------------------------------------------------
>
> (Updated July 12, 2015, 4 p.m.)
>
>
> Review request for KDE Frameworks, Alex Merry, Aurélien Gâteau, and Kevin \
> Krammer.
>
> Repository: kapidox
>
>
> Description
> -------
>
> Add man pages for kapidox scripts
>
>
> Diffs
> -----
>
> docs/depdiagram-generate-all.1 PRE-CREATION
> docs/depdiagram-generate.1 PRE-CREATION
> docs/depdiagram-prepare.1 PRE-CREATION
> docs/kgenapidox.1 PRE-CREATION
> docs/kgenframeworksapidox.1 PRE-CREATION
> setup.py 083543f
>
> Diff: https://git.reviewboard.kde.org/r/124328/diff/
>
>
> Testing
> -------
>
> Built and installed updated version and verified man pages were correctly installed \
> and readable in the KDE man page viewer.
>
> Thanks,
>
> Scott Kitterman
>
>
--===============8994471890688640405==
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit
<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="12" style="border: 1px #c9c399 \
solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;"> \
<tr> <td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://git.reviewboard.kde.org/r/124328/">https://git.reviewboard.kde.org/r/124328/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <p style="margin-top: 0;">On July 12th, 2015, 4:45 p.m. UTC, <b>Kevin \
Krammer</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;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: \
inherit;white-space: inherit;">I thought our man pages are written in docbook and \
then translated by the usual docbook workflow?</p></pre> </blockquote>
<p>On July 12th, 2015, 4:52 p.m. UTC, <b>Albert Astals Cid</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: \
inherit;">Correct.</p></pre> </blockquote>
<p>On July 12th, 2015, 5:47 p.m. UTC, <b>Luigi Toscano</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Yes, \
because they can be translated. But that means a dependency on kdoctools. On the \
other side, kapidox is a tier1 (I would say tier0) project, it's python, it's not \
really Qt based. I don't have a proper solution for this problem right now.</p></pre> \
</blockquote>
<p>On July 12th, 2015, 5:58 p.m. UTC, <b>Scott Kitterman</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">It's \
really different than the other frameworks. It's not a framework as much as a tool \
(Python application) for developing the frameworks. I don't think it can/should be \
done exactly the same as everything else.</p></pre> </blockquote>
<p>On July 12th, 2015, 7:58 p.m. UTC, <b>Albert Astals Cid</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">I'm \
not happy for not keeping our requeriment that our user visible stuff is \
translatable.</p></pre> </blockquote>
<p>On July 12th, 2015, 9:08 p.m. UTC, <b>Scott Kitterman</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 --help output (which \
is the only documentation that's currently provided) is already not translatable, \
so this is no different.</pre> </blockquote>
<p>On July 13th, 2015, 8:36 a.m. UTC, <b>David Faure</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">This \
is not user visible. It's not even visible to application developers, IIUC. It's an \
internal tool, much like kde-dev-scripts (in fact this stuff could have been put in \
kde-dev-scripts...), where none of the scripts have translatable help.</p></pre> \
</blockquote>
<p>On July 13th, 2015, 7 p.m. UTC, <b>Allen Winter</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">then \
I drop my objection. I can read troff well enough :)</p></pre> </blockquote>
<p>On July 14th, 2015, 1:30 p.m. UTC, <b>Scott Kitterman</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;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">OK. \
Does that mean I can go back to Alex Merry's shipit and push the change?</p></pre> \
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: \
inherit;">yes.</p></pre> <br />
<p>- Allen</p>
<br />
<p>On July 12th, 2015, 4 p.m. UTC, Scott Kitterman wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="12" style="border: \
1px #888a85 solid; border-radius: 6px; -moz-border-radius: 6px; \
-webkit-border-radius: 6px;"> <tr>
<td>
<div>Review request for KDE Frameworks, Alex Merry, Aurélien Gâteau, and Kevin \
Krammer.</div> <div>By Scott Kitterman.</div>
<p style="color: grey;"><i>Updated July 12, 2015, 4 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
kapidox
</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;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: \
inherit;white-space: inherit;">Add man pages for kapidox scripts</p></pre> </td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </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;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: \
inherit;white-space: inherit;">Built and installed updated version and verified man \
pages were correctly installed and readable in the KDE man page viewer.</p></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>docs/depdiagram-generate-all.1 <span style="color: \
grey">(PRE-CREATION)</span></li>
<li>docs/depdiagram-generate.1 <span style="color: grey">(PRE-CREATION)</span></li>
<li>docs/depdiagram-prepare.1 <span style="color: grey">(PRE-CREATION)</span></li>
<li>docs/kgenapidox.1 <span style="color: grey">(PRE-CREATION)</span></li>
<li>docs/kgenframeworksapidox.1 <span style="color: grey">(PRE-CREATION)</span></li>
<li>setup.py <span style="color: grey">(083543f)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/124328/diff/" style="margin-left: \
3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>
--===============8994471890688640405==--
[Attachment #3 (text/plain)]
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic