<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="http://git.reviewboard.kde.org/r/106787/">http://git.reviewboard.kde.org/r/106787/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On October 10th, 2012, 8:22 p.m., <b>Jasem Mutlaq</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;">Thanks, that must have been quite an effort!! Few questions:
1. How did you extract the strings exactly?
2. Property NAMES should not be translated as they are used internally by INDI. Property LABELS can be translated though.
3. Many strings are quite technical and would be immensly difficult to translate without proper context.
4. Many INDI drivers (e.g. 3rd party) are not included here, and due to the nature of INDI itself (dynamic introspection of drivers as they come), such strings would never get translated.
5. How would this list be maintained?
6. Any proposals for enabling i18n in libindi itself? </pre>
</blockquote>
<p>On October 10th, 2012, 8:33 p.m., <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;">1. Yuri did, not me, maybe he can answer
2. Right, but the places i i18n the name is only used in case the label is empty
3. Right, but we can't really give a better context due to us not "controlling" the origin of the string
4. We can always add strings as we go
5. Manually or if Yuri did use some script, using that
6. Well, I guess that's up to the libindi developers themselves, no idea how/when/who develops libindi, maybe you can shed some light in there, but from what i remember Yuri mentioned there was not much hope?</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;">1. I used sed -n 's/.*"\(.*\)".*/\1/p' $i | sort | uniq >> results.txt for *.cpp then remove unneeded entries (not shown in the GUI, log messages were also removed).
4. Only the drivers from the default installation were. 3rd party drivers (and 3rd party extensions) are not an aim of KDE translations.
5. I thought libindi is quite stable in it's core messages. If it's not, we can add messages anytime.
6. It is quite unlikely that the translation infrastructure will be in place and working at the time of KDE 4.10 release. Do you have any plan for this as libindi developer? ;)</pre>
<br />
<p>- Yuri</p>
<br />
<p>On October 10th, 2012, 8:04 p.m., Albert Astals Cid wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KStars, Akarsh Simha, Jasem Mutlaq, and Yuri Chornoivan.</div>
<div>By Albert Astals Cid.</div>
<p style="color: grey;"><i>Updated Oct. 10, 2012, 8:04 p.m.</i></p>
<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;">Since libindi does not seem to provide translations, we fake the messages as if they were ours</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;">Tested the x-test language, now i have xx everywhere meaning the messages are correctly translated</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>kstars/indi/guimanager.cpp <span style="color: grey">(05e97fd)</span></li>
<li>kstars/indi/indidevice.cpp <span style="color: grey">(af0f732)</span></li>
<li>kstars/indi/indielement.cpp <span style="color: grey">(d8c167e)</span></li>
<li>kstars/indi/indiproperty.cpp <span style="color: grey">(5f8fc36)</span></li>
<li>kstars/libindi_strings.cpp <span style="color: grey">(PRE-CREATION)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/106787/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>