Open Stack

On 05/08/2014 05:59 PM, Julie Pichon wrote:
> On 08/05/14 16:46, Douglas Fish wrote:
>> I've come across this review for automated translations coming into Horizon
>> https://review.openstack.org/#/c/91523/  It concerns me that it has over a
>> half million LOC in it, and many of these languages have near 0
>> translation.  (I checked here:
>> https://www.transifex.com/projects/p/horizon/).  0 translation languages
>> have just as many lines as full translations; they are just shorter.
>>
>> I can't give you a specific well-defined issue about why this concerns me,
>> but I'm worried about things like how big it might make our distributions,
>> or adding time to how long it takes to clone a new Horizon instance, or use
>> devstack.
>>
>> I've chatted a bit about this in #openstack-horizon. ajaeger has pointed
>> out to me that this isn't the biggest patch we've had for translations.
>> This one, for example, is 5 million lines:
>> https://review.openstack.org/#/c/67521/  This doesn't entirely satisfy me
>> because git clone https://review.openstack.org/openstack/openstack-manuals
>> is taking several minutes for me this morning (full disclosure:  I am
>> having some network flakiness today).  I'd hate for Horizon to take
>> anywhere near that long to clone.
>>
>> Also in #openstack-horizon jpich has shared that we intend to prune some of
>> these langauges out of Horizon as we approach the release.  Maybe it would
>> be best to begin that pruning now, to avoid late dev cycle churn?
>
> One of the suggestions that came up on IRC was to maybe only pull
> translations for languages that are at least 50% complete, or some other
> arbitrary number (not only for Horizon but for all projects).

> We've been careful about which languages we add the po files for in
> Horizon, so it does seem strange to suddenly add back everything,
> especially if we will remove them again at release time.

None of the other projects removes the files. With horizon, you can just 
change "settings.py" to only enable
those languages that are translated properly.

> I wonder if there might be a way to only update languages for which we
> already have the po files in the repo, rather than pull all po files? Or
> if that is desirable at all.

Yes, that is possible as well but then we would need to regularly check 
which languages should go in and which not. This is IMO to much manual work.

> I guess I'd also like to understand what would be the preferred way to
> proceed, from the translation team's perspective :) Is there any use in
> pulling in languages that only have a few unreviewed translated words?
> Then we can try to figure out the technical concerns around the string
> churn and repo size.

Andreas
-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126