Update Angular translations for poeditor pre-3.5

[Bill Erickson]

The Evergreen Angular translation strings need to be updated in our poeditor instance so we can translate more of the Angular interfaces.

Some fixes are needed to EG as well to address nested i18n issues in the templates. Patch on the way for that.

[Bill Erickson (berick)]

Small i18n template fix pushed:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1862395-angular-i18n-updates

[Bill Erickson (berick)]

Regarding PO editor, I've never updated the files before. Is it as simple as using the Import action and uploading the .xmb file? (I'm wary of clobbering people's work).

[Jane Sandberg (sandbergja)]

At least in the poeditor UI, there is an "overwrite old translations" checkbox to be careful of. I would assume that we wouldn't lose any work with that unchecked: https://poeditor.com/kb/importing-and-exporting-strings (famous last words).

Feel free to use the Spanish translation as a sandbox. It has exactly one translation (mine, which I could easily re-do).

[Jane Sandberg (sandbergja)]

I got excited about this, and uploaded the xmb file. And it doesn't look like I clobbered anything!

[Jane Sandberg (sandbergja)]

I started some documentation here: https://wiki.evergreen-ils.org/doku.php?id=poeditor

[Jane Sandberg (sandbergja)]

Thanks for the template fix, Bill. It works well for me, and I pushed it to master and rel_3_4.

Since that was only part of the puzzle, I'm not sure what we should do about targeting this launchpad bug.

[Evergreen Bug Maintenance (bugmaster)]

Removing milestone targets because this work is not finished and appears to have no ETA.

[Jane Sandberg (sandbergja)]

Since this bug is for an unsupported version of Evergreen, can we close it?

[Andrea Neiman (aneiman)]

+1, marking won't fix.