Related Issues

• html: html.UnescapeString("(&#9)") does not decode single character number #66058

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

&bbsp is the escaped form. You should be using the literal non breaking space rune \u00a0.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions

@seankhliao I want it to be EXACTLY   (literally)
The results of the function will be going elsewhere for further processing.

The documentation even states:

Data is unescaped, so that it looks like "a<b" rather than "a& lt;b"

x/net/html only escapes what is necessary, nbsp is not in that list, so you'll never get a literal &npsp; entity out of rendering or the escape functions.

How is that not a bug? How can I properly deal with say <pre>&npsp</pre>? That should be treated literally.

When you call Parse you get Node values that, as the documentation says, contain unescaped data. Your program is rewriting the data to include a string  . That is considered to be unescaped data. When you render it as HTML, that data is escaped. That is what your program shows.

I don't understand what you are trying to do. If you want help using the x/net/html package, please use a forum, not the issue tracker. See https://go.dev/wiki/Questions. Thanks.