[Openstack-i18n] django_openstack_auth translation setup?

Andreas Jaeger aj at suse.com
Sun Apr 27 19:47:57 UTC 2014


On 04/27/2014 08:02 PM, Akihiro Motoki wrote:
> I am not sure which is better to move django_openstack_auth to a
> separate project in Transifex or to keep it as a part of Horizon
> project in Transifex. In general it looks reasonable to move
> django_openstack_auth to a separate project. Only thing I concern is
> that strings from django_openstack_auth is also visible as a part of
> OpenStack dashboard and splitting django_openstack_auth makes it
> difficult to identify a string when translator finds a wrong string.
> 
> I would like to know input from others from the point of view of
> (pure) translators.

>From the translators point who want to translate just the dashboard,
having django_openstack_auth in the same translation project might
indeed be preferred.

Thanks for bringing in the other perspective, I was looking at the
scripting side.

> I already know too much detail of translations/horizon/openstack infra
> mechanism and
> I am afraid I cannot make an appropriate decision from translator perspective.

;)

Andreas

> Thanks,
> Akihiro
> 
> 
> On Mon, Apr 28, 2014 at 2:51 AM, Andreas Jaeger <aj at suse.com> wrote:
>> On 03/21/2014 10:19 AM, Andreas Jaeger wrote:
>>> On 03/21/2014 09:18 AM, Ying Chun Guo wrote:
>>>> Hello, Andreas
>>>>
>>>> django_openstack_auth uses the script "upstream_translation_update.sh"
>>>> and accept "django_openstack_auth" as a parameter.
>>>> The script "upstream_translation_update.sh" is a common job definition
>>>> and works for nova, glance, and etc.
>>>> As to current situation, I wonder if it can accept "openstack_auth" as
>>>> the parameter.
>>>>
>>>> Yes, it needs a resource in Transifex. I have created:
>>>> https://www.transifex.com/projects/p/horizon/resource/djangopo/
>>>
>>> We need to special case this setup so that it ends at the right place,
>>> what do you think of this patch:
>>> https://review.openstack.org/82037
>>>
>>> Please check that all filenames - also in the repository and transifex
>>> match, this is tricky.
>>
>>
>> thinking further, it would be much easier, if the transifex setup would
>> not be part of horizon but a separate repository following the naming
>> scheme we use elsewhere - so set this up under
>> https://www.transifex.com/projects/p/django_openstack_auth/resource/openstack_auth.
>> Could you adjust this, please?
>>
>> 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
>>
>> _______________________________________________
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
> 


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



More information about the Openstack-i18n mailing list