Headstart: /u unicode characters not handled properly

[autumnfjeld]

I discovered this issue when trying to fix headstart annotations for Spanish (wp-content/lib/headstart/annotations/es.json) and I needed to include the phrase "dirección de correo electrónico" in a block attribute. The Spanish ó came out as unicode charactere 00f3n.

Then I tried using the phrases "direcci\u00f3nn de correo electr\u00f3nnico" and then tried a number of variations of the unicode escape \u00f3n and \\u00f3n. Nothing worked, I was never able to produce the result I needed, meaning I could not get the correct Spanish letter to appear in the block.

Steps to reproduce

You can choose any language, but I'll go with Spanish for this example.

1. Edit wp-content/lib/headstart/annotations/es.json -- edit a block that has block attributes, such as "submitButtonText" or "subscribePlaceholder" and input "dirección".

2. From your terminal run headstart (PCYsg-7cr-p2): wp headstart run --url=YOURSITE.wordpress.com --user=YOURUSER --theme=pub/maywood --locale=es

3. Then view the home page (or relevant page) of your site via the visual Editor and see that the Spanish is not displayed properly in that block

What I expected

To use direcci\u00f3nn in the block attribute and see dirección in the visual block.

What happened instead

direcci00f3nn is displayed instead of the proper spanish word

[ramonjd]

@deBhal has been investigating this.

I propose that, if we haven't reached a conclusion on a fix (if indeed one exists), we create an issue in the relevant repo, and/or p2 about it and cc as many relevant folks as possible.

That might yield the next steps, or prompt another team to look at it.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[synora]

@ramonjd I noticed this issue has gone stale. Can we close it out or does it need to remain open?

[ramonjd]

Thanks @synora
I don't think it's a pressing issue, so I think it's fine to close and reopen as necessary later.
I'll cc @autumnfjeld just in case.

[autumnfjeld]

I think this was fixed, if memory serves me correctly @lsl or @deBhal fixed it. I searched for some breadcrumbs to prove that, but no luck.