Planning Barcelona Design Summit session - contributors meetup
Hello, I have started to plan I18n Barcelona Design Summit session. We will have one contributors meetup on October28th (Friday) 2-6pm at Barcelona. Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and write your availability on Barcelona I18n contributors meetup and/or possible discussion topics. And for contributors who could not come to Barcelona, I am planning to have 'virtual meeting time' for one hour during contributors meetup. If someone is unable to come to Barcelona but would like to participate in virtual meeting time, please write your name and time preference on survey: http://doodle.com/poll/zny89dgs53n28y56 . With many thanks, /Ian
Hi, I added a couple of things to the discussion topics in the etherpad. I hope you discuss them and find directions. Perhaps I cannot participate the contributor meetup as usual. I have more important and interesting meetups, Neutron and Ops at the same time slot (Friday afternoon). My added items might be random due to my many hats such a core reviewer of several projects, an operator, i18n liaison, local meetup organizer, i18n contributor and a translator, If you have any questions, find me at Barcelona or reach me online (IRC is preferred). Akihiro 2016-10-07 2:54 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello,
I have started to plan I18n Barcelona Design Summit session. We will have one contributors meetup on October28th (Friday) 2-6pm at Barcelona.
Please see Etherpad: https://etherpad.openstack.org /p/barcelona-i18n-meetup , and write your availability on Barcelona I18n contributors meetup and/or possible discussion topics.
And for contributors who could not come to Barcelona, I am planning to have 'virtual meeting time' for one hour during contributors meetup. If someone is unable to come to Barcelona but would like to participate in virtual meeting time, please write your name and time preference on survey: http://doodle.com/poll/zny89dgs53n28y56 .
With many thanks,
/Ian
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Akihiro, I added two comments based on your opinions. Thanks:) On Sat, Oct 15, 2016 at 1:46 AM Akihiro Motoki <amotoki@gmail.com> wrote:
Hi,
I added a couple of things to the discussion topics in the etherpad. I hope you discuss them and find directions.
Perhaps I cannot participate the contributor meetup as usual. I have more important and interesting meetups, Neutron and Ops at the same time slot (Friday afternoon).
My added items might be random due to my many hats such a core reviewer of several projects, an operator, i18n liaison, local meetup organizer, i18n contributor and a translator, If you have any questions, find me at Barcelona or reach me online (IRC is preferred).
Akihiro
2016-10-07 2:54 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello,
I have started to plan I18n Barcelona Design Summit session. We will have one contributors meetup on October28th (Friday) 2-6pm at Barcelona.
Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and write your availability on Barcelona I18n contributors meetup and/or possible discussion topics.
And for contributors who could not come to Barcelona, I am planning to have 'virtual meeting time' for one hour during contributors meetup. If someone is unable to come to Barcelona but would like to participate in virtual meeting time, please write your name and time preference on survey: http://doodle.com/poll/zny89dgs53n28y56 .
With many thanks,
/Ian
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- --------------------------------------------- 周正喜 Mobile: 13701280947 WeChat: 472174291
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question. According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation >> CLI
logging messages". (there were no categories such as release notes and server user-visible messages)
Thanks, Akihiro 2016-10-15 2:43 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
Hi,
I added a couple of things to the discussion topics in the etherpad. I hope you discuss them and find directions.
Perhaps I cannot participate the contributor meetup as usual. I have more important and interesting meetups, Neutron and Ops at the same time slot (Friday afternoon).
My added items might be random due to my many hats such a core reviewer of several projects, an operator, i18n liaison, local meetup organizer, i18n contributor and a translator, If you have any questions, find me at Barcelona or reach me online (IRC is preferred).
Akihiro
2016-10-07 2:54 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello,
I have started to plan I18n Barcelona Design Summit session. We will have one contributors meetup on October28th (Friday) 2-6pm at Barcelona.
Please see Etherpad: https://etherpad.openstack.org /p/barcelona-i18n-meetup , and write your availability on Barcelona I18n contributors meetup and/or possible discussion topics.
And for contributors who could not come to Barcelona, I am planning to have 'virtual meeting time' for one hour during contributors meetup. If someone is unable to come to Barcelona but would like to participate in virtual meeting time, please write your name and time preference on survey: http://doodle.com/poll/zny89dgs53n28y56 .
With many thanks,
/Ian
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question.
According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation >> CLI >> logging messages". (there were no categories such as release notes and server user-visible messages)
Still, some translators translate log messages first, since they are nice and short ;( We can give translators more guidance on what to translate - or we can go one step further and disable some translations completely. Right now if a project wants translation sync and sends a patch for project-config, it goes in. But does it make sense with current team to translate over 80 projects? Or should we instead tell projects: This is what we focus on, therefore let's only put these documents in Zanata - and nothing else? Especially creating stable branches needs extra work and we should really only do those for projects that the translators can handle, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Another way other than through mailing list to make clear to the translators on the project they should focus on would be using the front page in Zanata. Another option would be changing the project to readonly but it is not ideal to do that over 80+ projects manually. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Mon, Oct 17, 2016 at 4:05 AM, Andreas Jaeger <aj@suse.com> wrote:
On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question.
According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation >> CLI >> logging messages". (there were no categories such as release notes and server user-visible messages)
Still, some translators translate log messages first, since they are nice and short ;(
We can give translators more guidance on what to translate - or we can go one step further and disable some translations completely. Right now if a project wants translation sync and sends a patch for project-config, it goes in. But does it make sense with current team to translate over 80 projects? Or should we instead tell projects: This is what we focus on, therefore let's only put these documents in Zanata - and nothing else?
Especially creating stable branches needs extra work and we should really only do those for projects that the translators can handle,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Another way other than through mailing list to make clear to the translators on the project they should focus on would be using the front page in Zanata.
+1 I'd like to announce "we maintain the Zanata front page to set priority."
Another option would be changing the project to readonly but it is not ideal to do that over 80+ projects manually.
[snip]
Kato's suggestion +1. Thanks. On Mon, Oct 17, 2016 at 8:06 AM Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com> wrote:
Another way other than through mailing list to make clear to the translators on the project they should focus on would be using the front page in Zanata.
+1
I'd like to announce "we maintain the Zanata front page to set priority."
Another option would be changing the project to readonly but it is not
ideal to do that over 80+ projects manually.
[snip]
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- --------------------------------------------- 周正喜 Mobile: 13701280947 WeChat: 472174291
On Sunday 16 October 2016, 20:05:39 Andreas Jaeger <aj@suse.com> wrote:
On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question.
According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation >> CLI >> logging messages". (there were no categories such as release notes and server user-visible messages)
Still, some translators translate log messages first, since they are nice and short ;(
We can give translators more guidance on what to translate - or we can go one step further and disable some translations completely. Right now
No, please don't!
if a project wants translation sync and sends a patch for project-config, it goes in. But does it make sense with current team to translate over 80 projects? Or should we instead tell projects: This is what we focus on, therefore let's only put these documents in Zanata - and nothing else?
To set the focus is fine - as already suggested, there could be pointers on the Zanata start page - but I don't see a reason to disallow lesser important translations. This will even block some language teams where the more relevant projects are already complete. -- Thanks, Robert
On 2016-10-17 09:40, Robert Simai wrote:
On Sunday 16 October 2016, 20:05:39 Andreas Jaeger <aj@suse.com> wrote:
On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question.
According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation >> CLI >> logging messages". (there were no categories such as release notes and server user-visible messages)
Still, some translators translate log messages first, since they are nice and short ;(
We can give translators more guidance on what to translate - or we can go one step further and disable some translations completely. Right now
No, please don't!
if a project wants translation sync and sends a patch for project-config, it goes in. But does it make sense with current team to translate over 80 projects? Or should we instead tell projects: This is what we focus on, therefore let's only put these documents in Zanata - and nothing else?
To set the focus is fine - as already suggested, there could be pointers on the Zanata start page - but I don't see a reason to disallow lesser important translations. This will even block some language teams where the more relevant projects are already complete.
Sure, we shouldn't be in such a situation. I'm asking myself whether there's a middle ground - 82 projects with release notes and log files is a lot. How many do we cover (for the best language, for the best 3,...) today? What shall we do once the next 10 projects want to have translations? Or what can we do to get more translations for those projects that we consider important? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Monday 17 October 2016, 09:52:40 Andreas Jaeger <aj@suse.com> wrote:
On 2016-10-17 09:40, Robert Simai wrote:
On Sunday 16 October 2016, 20:05:39 Andreas Jaeger <aj@suse.com> wrote:
On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question.
According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation
CLI >> logging messages". (there were no categories such as release notes and server user-visible messages)
Still, some translators translate log messages first, since they are nice and short ;(
We can give translators more guidance on what to translate - or we can go one step further and disable some translations completely. Right now
No, please don't!
if a project wants translation sync and sends a patch for project-config, it goes in. But does it make sense with current team to translate over 80 projects? Or should we instead tell projects: This is what we focus on, therefore let's only put these documents in Zanata - and nothing else?
To set the focus is fine - as already suggested, there could be pointers on the Zanata start page - but I don't see a reason to disallow lesser important translations. This will even block some language teams where the more relevant projects are already complete.
Sure, we shouldn't be in such a situation.
I'm asking myself whether there's a middle ground - 82 projects with release notes and log files is a lot. How many do we cover (for the best language, for the best 3,...) today?
What shall we do once the next 10 projects want to have translations?
Or what can we do to get more translations for those projects that we consider important?
It seems atm. it's up to the language teams to evaluate their status, to engage or find additional resources. Probably it's a bigger task to create, but can we have some report/visualization of where we are from different POVs? Start by language, by project, by category (UI, app, log), by importance ..., with options to drill down or combine these. I think there will be more interest if the missing bits and pieces can be highlighted and preferably have links to the translation files in Zanata, to make it as easy as possible to engage and fill the gaps. -- Thanks, Robert
Hello, Robert Simai wrote on 10/17/2016 5:11 PM:
On Monday 17 October 2016, 09:52:40 Andreas Jaeger <aj@suse.com> wrote:
On 2016-10-17 09:40, Robert Simai wrote:
On Sunday 16 October 2016, 20:05:39 Andreas Jaeger <aj@suse.com> wrote:
On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
I think some of my added items might be aggressive, but my main point is that the i18n team needs to express more focused areas to reduce confusion around the feature freeze. GUI message translation continuously gathers interest of translations so far. Documentation translation is the next one. How about CLI? How about server project user-visible messages? How about log messages? This is my question.
According a rough survey I made in OpenStack Days Tokyo last year (one year and a few months ago), translation interest from the attendees was "Horizon > Documentation CLI >> logging messages". (there were no categories such as release notes and server user-visible messages) Still, some translators translate log messages first, since they are nice and short ;(
We can give translators more guidance on what to translate - or we can go one step further and disable some translations completely. Right now No, please don't!
if a project wants translation sync and sends a patch for project-config, it goes in. But does it make sense with current team to translate over 80 projects? Or should we instead tell projects: This is what we focus on, therefore let's only put these documents in Zanata - and nothing else? To set the focus is fine - as already suggested, there could be pointers on the Zanata start page - but I don't see a reason to disallow lesser important translations. This will even block some language teams where the more relevant projects are already complete. Sure, we shouldn't be in such a situation.
I'm asking myself whether there's a middle ground - 82 projects with release notes and log files is a lot. How many do we cover (for the best language, for the best 3,...) today?
What shall we do once the next 10 projects want to have translations?
Or what can we do to get more translations for those projects that we consider important? It seems atm. it's up to the language teams to evaluate their status, to engage or find additional resources. Probably it's a bigger task to create, but can we have some report/visualization of where we are from different POVs? Start by language, by project, by category (UI, app, log), by importance ..., with options to drill down or combine these. But the price of durable and reliable ATM would be high? :)
I agree that I18n as a team needs to encourage translations into various OpenStack projects, rather than limit translation contribution. I think Andreas's mentioning is related to whether we should aware of all of OpenStack projects with releases or not, rather than disabling translations for projects in Zanata. In my opinion, all master branches on every OpenStack project as much as possible would be better to more engage in, as Robert mentioned. However, release-awareness for translation would have different perspective. For example, I have seen that OpenStack infrastructure and release team members were very busy when release date is upcoming: such as soft freeze, hard freeze, and so on. I do not want them to be hurt with numerous log messages, and some of them are also kind translators. Also, since we are one team, discussion on which projects in one language team is interested or not interested, how another language team encourages translation in its local user group, what would be nice translation tips, and so on will make good synergy. So I think discussing translation plan and priority is one of very important to-do things instead of just opening all the projects. Moreover, some translators would have special interests on a specific project. I do not want to block them, but since the priority would be less than what we set overall plan and priority, I would like to see high priority projects first and investigate on i18n things including infrastructure and release cycle for lower priority projects. And another idea: a survey to all language coordinators and/or translators for their interested translation target projects and/or priority would be good. I will bring this as one topic in upcoming IRC meeting (Oct 20 07:00 UTC).
I think there will be more interest if the missing bits and pieces can be highlighted and preferably have links to the translation files in Zanata, to make it as easy as possible to engage and fill the gaps. Yep. Such enhancement is really needed! Hope that Zanata version will be upgrade soon.
By the way, I briefly modified the Zanata front page: https://translate.openstack.org/ (Also it would be great that front page visibility will be enhanced, as I wrote in https://etherpad.openstack.org/p/I18n-Zanata-enhancement ) If you have better idea on front page design and content, please tell me :) With many thanks, /Ian
On Monday 17 October 2016, 20:41:18 Ian Y. Choi <ianyrchoi@gmail.com> wrote: [...]
By the way, I briefly modified the Zanata front page: https://translate.openstack.org/ (Also it would be great that front page visibility will be enhanced, as I wrote in https://etherpad.openstack.org/p/I18n-Zanata-enhancement ) If you have better idea on front page design and content, please tell me :)
I see all the user facing projects are aggregated under the link "Dashboard translation (Required)" https://translate.openstack.org/version-group/view/newton-dashboard-translat... for all languages. Is that the change you made? This is _very_ helpful as it now allows to quickly see the status. Thanks a lot! -- Cheers, Robert
Robert Simai wrote on 10/17/2016 9:28 PM:
On Monday 17 October 2016, 20:41:18 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
[...]
By the way, I briefly modified the Zanata front page: https://translate.openstack.org/ (Also it would be great that front page visibility will be enhanced, as I wrote in https://etherpad.openstack.org/p/I18n-Zanata-enhancement ) If you have better idea on front page design and content, please tell me :) I see all the user facing projects are aggregated under the link
"Dashboard translation (Required)" https://translate.openstack.org/version-group/view/newton-dashboard-translat...
for all languages. Is that the change you made? Actually at that time I did not create such group. Kato-san created this on last July I think.
I have updated a few more on the front page, since now translating mainly on master branch rather than stable-newton version will be nice. For user facing projects of Ocata translation, please see: https://translate.openstack.org/version-group/view/ocata-dashboard-translati... (I have just created such group.)
This is _very_ helpful as it now allows to quickly see the status. Thanks a lot!
Hope that the new group "Ocata dashboard translation" will be also useful to all. :) With many thanks, /Ian
On Monday 17 October 2016, 21:52:13 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Robert Simai wrote on 10/17/2016 9:28 PM:
[...]
I see all the user facing projects are aggregated under the link
"Dashboard translation (Required)" https://translate.openstack.org/version-group/view/newton-dashboard-tran slation
for all languages. Is that the change you made?
Actually at that time I did not create such group. Kato-san created this on last July I think.
Then my sincere thanks go to Kato-san. For some reason I must have overlooked it :-)
I have updated a few more on the front page, since now translating mainly on master branch rather than stable-newton version will be nice. For user facing projects of Ocata translation, please see: https://translate.openstack.org/version-group/view/ocata-dashboard-transla tion/ (I have just created such group.)
This is _very_ helpful as it now allows to quickly see the status. Thanks a lot!
Hope that the new group "Ocata dashboard translation" will be also useful to all. :)
Yes, very nice! Thanks for your support! As a side note, since it's Master it includes the release-notes which makes the percentages for the projects appear very low at first glance. It might be a technical challenge or not feasible at all but probably they better appear within another dashboard... Furthermore I suspect that not all Newton translations have yet been merged back into Master. I don't know who takes care of this. -- Thanks, Robert
Robert Simai wrote on 10/17/2016 10:13 PM:
On Monday 17 October 2016, 21:52:13 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Robert Simai wrote on 10/17/2016 9:28 PM: [...]
I see all the user facing projects are aggregated under the link
"Dashboard translation (Required)" https://translate.openstack.org/version-group/view/newton-dashboard-tran slation
for all languages. Is that the change you made? Actually at that time I did not create such group. Kato-san created this on last July I think. Then my sincere thanks go to Kato-san. For some reason I must have overlooked it :-)
I have updated a few more on the front page, since now translating mainly on master branch rather than stable-newton version will be nice. For user facing projects of Ocata translation, please see: https://translate.openstack.org/version-group/view/ocata-dashboard-transla tion/ (I have just created such group.)
This is _very_ helpful as it now allows to quickly see the status. Thanks a lot! Hope that the new group "Ocata dashboard translation" will be also useful to all. :) Yes, very nice! Thanks for your support!
As a side note, since it's Master it includes the release-notes which makes the percentages for the projects appear very low at first glance. It might be a technical challenge or not feasible at all but probably they better appear within another dashboard... As far as I know, current Zanata does not support such things technically. T.T
Furthermore I suspect that not all Newton translations have yet been merged back into Master. I don't know who takes care of this.
Me did take care of this already around on last weekdays (I did not remember exactly.. Maybe on last Wednesday to Friday). If you find some untranslated strings which seems to be translated on stable-newton but does not be shown on master branch, please tell me with target project name and strings. Then I will consider re-merge for specific projects again. With many thanks, /Ian
On Monday 17 October 2016, 22:53:37 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Robert Simai wrote on 10/17/2016 10:13 PM:
On Monday 17 October 2016, 21:52:13 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
[...]
Furthermore I suspect that not all Newton translations have yet been merged back into Master. I don't know who takes care of this.
Me did take care of this already around on last weekdays (I did not remember exactly.. Maybe on last Wednesday to Friday). If you find some untranslated strings which seems to be translated on stable-newton but does not be shown on master branch, please tell me with target project name and strings. Then I will consider re-merge for specific projects again.
I think I see this at least in magnum-ui master Documents (de) magnum_ui/locale/djangojs manila-ui master Documents (de) manila_ui/locale/django where the translation proposals have 100% matches for the missing strings but are too many to click through. It seems these have not been merged, all others look good to me. Please have a look. -- Thanks, Robert
Hello Alex, As Robert says, I have also found that German strings in stable-newton was not merged to master, but I executed them around Oct 14. Today, I re-executed TM merge for manila-ui and magnum-ui several times. For the first time, I saw a message like: 'manila-ui: merged from master to master'. After then, although I execute it several times, no error messages are not shown. Also, German strings are not still merged. Could you investigate it? I am attaching a screenshot. I think I executed TM merge with choosing right menus. : https://www.dropbox.com/s/qsrfvygfcfc7t7h/zanata-tm-merge-to-master-from-sta... With many thanks, /Ian Robert Simai wrote on 10/18/2016 5:10 PM:
On Monday 17 October 2016, 22:53:37 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Robert Simai wrote on 10/17/2016 10:13 PM:
On Monday 17 October 2016, 21:52:13 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
[...]
Furthermore I suspect that not all Newton translations have yet been merged back into Master. I don't know who takes care of this. Me did take care of this already around on last weekdays (I did not remember exactly.. Maybe on last Wednesday to Friday). If you find some untranslated strings which seems to be translated on stable-newton but does not be shown on master branch, please tell me with target project name and strings. Then I will consider re-merge for specific projects again. I think I see this at least in
magnum-ui master Documents (de) magnum_ui/locale/djangojs manila-ui master Documents (de) manila_ui/locale/django
where the translation proposals have 100% matches for the missing strings but are too many to click through. It seems these have not been merged, all others look good to me. Please have a look.
Hi Ian, It was a bug in the "merge translation". The workaround is that you need to select other version before selecting the actual version. I already merged from stable to master. The bug is already fixed 3.9.0 onwards: https://zanata.atlassian.net/browse/ZNTA-1070 --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Wed, Oct 19, 2016 at 4:09 PM, Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Hello Alex,
As Robert says, I have also found that German strings in stable-newton was not merged to master, but I executed them around Oct 14.
Today, I re-executed TM merge for manila-ui and magnum-ui several times. For the first time, I saw a message like: 'manila-ui: merged from master to master'. After then, although I execute it several times, no error messages are not shown. Also, German strings are not still merged.
Could you investigate it? I am attaching a screenshot. I think I executed TM merge with choosing right menus. : https://www.dropbox.com/s/qsrfvygfcfc7t7h/zanata-tm-merge- to-master-from-stable-newton-manila-ui.png?dl=0
With many thanks,
/Ian
Robert Simai wrote on 10/18/2016 5:10 PM:
On Monday 17 October 2016, 22:53:37 Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Robert Simai wrote on 10/17/2016 10:13 PM:
On Monday 17 October 2016, 21:52:13 Ian Y. Choi <ianyrchoi@gmail.com>
wrote:
[...]
Furthermore I suspect that not all Newton translations have yet been
merged back into Master. I don't know who takes care of this.
Me did take care of this already around on last weekdays (I did not remember exactly.. Maybe on last Wednesday to Friday). If you find some untranslated strings which seems to be translated on stable-newton but does not be shown on master branch, please tell me with target project name and strings. Then I will consider re-merge for specific projects again.
I think I see this at least in
magnum-ui master Documents (de) magnum_ui/locale/djangojs manila-ui master Documents (de) manila_ui/locale/django
where the translation proposals have 100% matches for the missing strings but are too many to click through. It seems these have not been merged, all others look good to me. Please have a look.
Hi Alex, Ian, I can confirm, manila-ui looks good now but magnum-ui appears still to be not merged. Thanks for your support in this matter. -- Regards, Robert On Wednesday 19 October 2016, 16:44:13 Alex Eng <aeng@redhat.com> wrote:
Hi Ian,
It was a bug in the "merge translation". The workaround is that you need to select other version before selecting the actual version. I already merged from stable to master. The bug is already fixed 3.9.0 onwards:
https://zanata.atlassian.net/browse/ZNTA-1070
---------------------------------------------
Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
On Wed, Oct 19, 2016 at 4:09 PM, Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Hello Alex,
As Robert says, I have also found that German strings in stable-newton was not merged to master, but I executed them around Oct 14.
Today, I re-executed TM merge for manila-ui and magnum-ui several times. For the first time, I saw a message like: 'manila-ui: merged from master to master'. After then, although I execute it several times, no error messages are not shown. Also, German strings are not still merged.
Could you investigate it? I am attaching a screenshot. I think I executed TM merge with choosing right menus.
: https://www.dropbox.com/s/qsrfvygfcfc7t7h/zanata-tm-merge-> > to-master-from-stable-newton-manila-ui.png?dl=0
With many thanks,
/Ian
Robert Simai wrote on 10/18/2016 5:10 PM:
On Monday 17 October 2016, 22:53:37 Ian Y. Choi <ianyrchoi@gmail.com>
wrote:
Robert Simai wrote on 10/17/2016 10:13 PM:
On Monday 17 October 2016, 21:52:13 Ian Y. Choi <ianyrchoi@gmail.com>
wrote: [...]
Furthermore I suspect that not all Newton translations have yet been
merged back into Master. I don't know who takes care of this.
Me did take care of this already around on last weekdays (I did not remember exactly.. Maybe on last Wednesday to Friday). If you find some untranslated strings which seems to be translated on stable-newton but does not be shown on master branch, please tell me with target project name and strings. Then I will consider re-merge for specific projects again.
I think I see this at least in
magnum-ui master Documents (de) magnum_ui/locale/djangojs manila-ui master Documents (de) manila_ui/locale/django
where the translation proposals have 100% matches for the missing strings but are too many to click through. It seems these have not been merged, all others look good to me. Please have a look.
Robert, Ian, I've merged for magnum-ui from stabel-newton to master.
participants (7)
-
Akihiro Motoki
-
Alex Eng
-
Andreas Jaeger
-
Ian Y. Choi
-
Kato, Tomoyuki
-
Robert Simai
-
Will Zhou