fix: ui: escape journal title once

[ptamarit]

❤️ Thank you for your contribution!

Description

Fixes #2919
See description in the linked issue.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings.
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Frontend

• I've followed the CSS/JS and React guidelines.
• I've followed the web accessibility guidelines.
• I've followed the user interface guidelines.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[tmorrell]

Looks like a sensible change. The only thought I have is a lot of the other fields seem to deal with escaping in the ui serializer. Not sure if it makes sense to fix this upstream instead.

[ptamarit]

Looks like a sensible change. The only thought I have is a lot of the other fields seem to deal with escaping in the ui serializer. Not sure if it makes sense to fix this upstream instead.

@tmorrell are you referring to SanitizedUnicode? Not sure to understand, because this is already used for the journal title field.
In this case, the problem is that React is escaping text, and react-i18n is also escaping the text, causing double escaping and displaying of HTML entities.

[tmorrell]

@ptamarit Yeah, I was wondering why it wasn't needed for other fields like description and title, but it's because those aren't run through i18n. Thanks for the explanation