[ui_next] Schedules, values for 'FrequencyDetailSubform__RunEveryLabel' and 'Detail__DetailName: Repeat Frequency', needs to be marked for translations

[sshedmake]

ISSUE TYPE

• Bug Report

SUMMARY

With Japanese (dummy translation) google-chrome, values for 'FrequencyDetailSubform__RunEveryLabel' and 'Detail__DetailName: Repeat Frequency', at 'Templates > JT > Schedules > {Edit and Schedule} Details' screen, appears in English (instead of Japanese)

ENVIRONMENT

• AWX version: 10.0.0
• AWX install method: docker on linux
• Ansible version: 2.10.0.dev0
• Operating System: Fedora 31
• Web Browser: google-chrome

STEPS TO REPRODUCE

1. Do a successful login to the ui_next interface in the preferred language (say Japanese)
2. Navigate to breadcrumb 'Templates > Demo Job Template > Schedules > Run Demo JT 5 Times > {Edit and Schedule} Details'
3. Observe respective values for 'FrequencyDetailSubform__RunEveryLabel' and 'Detail__DetailName: Repeat Frequency'

EXPECTED RESULTS

Content should appear in Japanese

ACTUAL RESULTS

1. 'weeks' | 'months'

2. 'Every week on Monday, Wednesday, Friday for 5 times' | 'Every month on Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday until October 27, 2020'

ADDITIONAL INFORMATION

1. Screenshot higlighting respective values for 'FrequencyDetailSubform__RunEveryLabel' and 'Detail__DetailName: Repeat Frequency', appearing in English, with Japanese google-chrome:

Run every 1 months:

Run every 1 weeks:

[nixocio]

The string for Repeat Frequency is dynamically generated and comes from RRule . After talking with @mabashian about it, we came up with a few possible solutions.

1 - Always show as an English.
2 - Custom translation issue - See: jkbrzt/rrule#13
3 - Hide the field Repeat Frequency if the browser language is not English.
4 - Remove the field - Repeat Frequency, since the info is already present with UI Occurrences.

@trahman73 @wenottingham @sshedmake thoughts?

[mabashian]

Some more information about this field: #6173

[mabashian]

Enhancement here would be to have this string translated (maybe we roll our own implementation of it?) but we plan on leaving that field for now.

[sshedmake]

Added @Spredzy here