"&hellip" visible in the "Publish" button

[zacharyhickson]

Issue Overview

"…" text is being printed in the Publish button.

Steps to Reproduce (for bugs)

1. Brand new installation of WordPress on a local MAMP Pro setup.
2. WordPress Version: 4.9.4 (English Australia localisation)
3. Gutenberg Version: 2.5.0
4. No other active plugins

OS: macOS High Sierra 10.13.3
Browser: Google Chrome - Version 65.0.3325.181 (Official Build) (64-bit)
Tested in both Normal and Incognito modes.

Expected Behavior

The "…" should not be outputted as text, but converted to HTML.

Screenshots / Video

[ZebulanStanphill]

Possibly related since they both involve HTML entity parsing: #5717

[felipeelia]

Actually this seems to be a problem with the current translation of the string, as seen in GlotPress.
GlotDict displays this warning:
Warning: The translation contains a final ... that should be translated as …
But in this case I think it should be translated just as is.

[danielbachhuber]

@felipeelia Sorry, I'm not sure I follow. Do you have a suggested resolution for this issue?

[felipeelia]

I think @zacharyhickson can already confirm if it's all right now, @danielbachhuber.
I've sent the correct string to GlotPress and @ntwb has already accepted it (thanks btw).

The problem seems to be in GlotPress or GlotDict, suggesting to translate strings containg ... with …, when it's not always the case.

[zacharyhickson]

Thanks @felipeelia. FYI I've also updated to Gutenberg 2.6.

Seems like the bug is still there though.

What can you do, I guess us Aussies still have a weird language ;)

Do I need to use a different (development) version of Gutenberg to test this?

[ntwb]

I suspect this is due to the generation of strings for Gutenberg in using json_encode() in /lib/parser.php, see WP#32875:Comment#6 for further details on this.

[felipeelia]

Did you update the translations as well, @zacharyhickson?

I'll give a look into that @ntwb. Thanks for dropping by.

[jorgefilipecosta]

The merge of #6114 should have resolved the issue in the publish button. We should have used 'Publish…' ( … is a special char) instead of 'Publish...' (... three points) like we do in the other places.
As the main issue is solved I will close this issue. Thank you for the debugging I think It was useful and we may have some other problems where characters may be wrongly "translated".
Of course, if the issue persists in your tests feel free to reopen.