[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: Minimum translation percentage for frameworks release
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2014-07-31 11:27:03
Message-ID: CACcA1RpZQN7hc_OVTXEaay-f+g_GJkfSWO=BWP7T3EvdkJY+hg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Jul 31, 2014 at 8:32 AM, Alexander Potashev <aspotashev@gmail.com>
wrote:

> 2014-07-31 3:51 GMT+04:00 Aleix Pol <aleixpol@kde.org>:
> > On Thu, Jul 31, 2014 at 1:36 AM, Alexander Potashev <
> aspotashev@gmail.com>
> > wrote:
> >>
> >> But doing per-framework percentages is no bueno, either: imagine your
> >> app uses KService and you translated only this framework having
> >> skipped its dependencies. Then the app might be translated very poorly
> >> if many strings come from the dependent frameworks.
> >
> > Read again what Albert said, he's not proposing to filter per framework.
>
> Hi Aleix,
>
> Correct - Albert's final idea was to let the downstream decide. I'm
> almost sure that won't work well, specifically most distros will
> probably include all translations we ship, even very incomplete ones
> because
>  1. Packagers won't find out soon they need to do this filtering (i.e.
> they won't notice that we've turned off filtering on our side),
> because they didn't need to with KDE SC 4.x,
>  2. Packagers won't spent their time to write scripts for filtering
> translations in some smart way.
>
> --
> Alexander Potashev
>

Well, then we need to offer proper tooling.

Aleix

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jul 31, 2014 \
at 8:32 AM, Alexander Potashev <span dir="ltr">&lt;<a \
href="mailto:aspotashev@gmail.com" \
target="_blank">aspotashev@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">2014-07-31 3:51 GMT+04:00 Aleix Pol &lt;<a \
href="mailto:aleixpol@kde.org">aleixpol@kde.org</a>&gt;:<br> <div class="">&gt; On \
Thu, Jul 31, 2014 at 1:36 AM, Alexander Potashev &lt;<a \
href="mailto:aspotashev@gmail.com">aspotashev@gmail.com</a>&gt;<br> &gt; wrote:<br>
&gt;&gt;<br>
</div><div class="">&gt;&gt; But doing per-framework percentages is no bueno, either: \
imagine your<br> &gt;&gt; app uses KService and you translated only this framework \
having<br> &gt;&gt; skipped its dependencies. Then the app might be translated very \
poorly<br> &gt;&gt; if many strings come from the dependent frameworks.<br>
&gt;<br>
</div><div class="">&gt; Read again what Albert said, he&#39;s not proposing to \
filter per framework.<br> <br>
</div>Hi Aleix,<br>
<br>
Correct - Albert&#39;s final idea was to let the downstream decide. I&#39;m<br>
almost sure that won&#39;t work well, specifically most distros will<br>
probably include all translations we ship, even very incomplete ones<br>
because<br>
  1. Packagers won&#39;t find out soon they need to do this filtering (i.e.<br>
they won&#39;t notice that we&#39;ve turned off filtering on our side),<br>
because they didn&#39;t need to with KDE SC 4.x,<br>
  2. Packagers won&#39;t spent their time to write scripts for filtering<br>
translations in some smart way.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Alexander Potashev<br></div></div></blockquote><div><br></div><div>Well, then we need \
to offer proper tooling.</div><div><br></div><div>Aleix  </div></div></div></div>



_______________________________________________
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]