Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add locale translations #11

Open
marlo-longley opened this issue Sep 26, 2022 · 7 comments
Open

Add locale translations #11

marlo-longley opened this issue Sep 26, 2022 · 7 comments
Labels
analysis needed arclight-core Changes we would make in AL-Core and inherit into NTA

Comments

@marlo-longley
Copy link
Collaborator

Add locale translations into UI
To understand how big a task this is, we need to know how the current templates in AL work, and if there are inline strings we'd need to swap out with locale YAML.

@marlo-longley marlo-longley added analysis needed arclight-core Changes we would make in AL-Core and inherit into NTA labels Sep 26, 2022
@marlo-longley
Copy link
Collaborator Author

@jcoyne
Copy link
Contributor

jcoyne commented Oct 6, 2022

@marlo-longley which locales are we targeting? Do we have all of the metadata available in all locales?

@marlo-longley
Copy link
Collaborator Author

marlo-longley commented Oct 6, 2022

@jcoyne No, we definitely only have English metadata. As I learn more about the product I think this ticket is actually 2 things:

  1. Go through the Arclight templates and make sure they use locale rather than hardcoded text. So that ticket should live in Arclight repo. It is debatable how high a priority this is for this workcyclce. But it's good cleanup work in general (I guess I was trying to tell myself something with this arclight-core label!)

  2. Customize text in NTA-Arclight as needed with translations. The need for this is TBD from @laurensorensen. We have transcripts of A/V in multiple languages, but how those will be accessed/displayed, and if there will need to be translations/multiple locales within the app to support them, is TBD.

@ggeisler
Copy link
Contributor

ggeisler commented Oct 6, 2022

@marlo-longley Might we be missing a step between steps 1 and 2 in your comment above? Step 1 sets Arclight up to effectively provide Arclight UI strings in non-English locales, but we also need to create and populate the non-English locale files so those string translations actually exist in the non-English locales (which will require a non-development step of finding translators for each of the target locales).

I suggest that is a step between your 2 steps because I don't think we should worry too much about your second ssetep of providing NTA-specific translations unless we're sure we will be offering non-English options in core Arclight (i.e., I'm not sure it would be a good user experience to offer German translations of NTA-specific things if the basic core Arclight UI remains in English).

(The two Arclight tickets you reference above do discuss issues around adding new locales to Arclight but they're both closed. I'm thinking we should have an open ticket related to this, if we decide translations are part of our goals for the current workcycle -- FWIW, Hannah indicated this is a high-priority feature, although probably not as high as the more fundamental UI updates, etc.)

@marlo-longley
Copy link
Collaborator Author

marlo-longley commented Oct 6, 2022

Thanks @ggeisler ! That all makes sense to me. Probably overhauling the non-English locale files in Core is way too much for us. We definitely need get clear on what the high priority feature is. My understanding is that the only translated content we will be publishing this workcycle are transcripts of the AV files (in English, the original language, and Hebrew), and that would happen via downloading a file, not viewed in the app. I'm not sure what other translated content there would be within the NTA app. So I'm not clear on what is the high priority.

I know I created this ticket as a form of note-taking during a group meeting. Sorry I don't have a clearer memory of it!

@ggeisler
Copy link
Contributor

ggeisler commented Oct 6, 2022

@marlo-longley I might have time to work on the core Arclight locale stuff during the workcycle so we're prepared to support non-English locale files. And @laurensorensen and I can work on determining whether we could get appropriate translations or not. So we could works towards supporting non-English locales in Arclight, but not commit to doing it if we can't find translators, and not commit any developer time to it.

The NTA-specific translations I think could be relevant, aside from the AV transcripts, are any static text specific to NTA that we display in the NTA application. So things like homepage text, about page text, etc. (e.g., if a user can switch the locale of the NTA app to German and see German language UI elements, it would be nice if they also saw German text on the homepage instead of English). But that is independent and secondary to supporting other languages in core Arclight, I believe.

@laurensorensen
Copy link
Collaborator

Blocked due to lack of time in this workcycle for facilitating the 100s of fields involved in locale translation. Leaving for a future workcycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analysis needed arclight-core Changes we would make in AL-Core and inherit into NTA
Projects
None yet
Development

No branches or pull requests

4 participants