ID 501510 - Using an ampersand (&) and a semicolon (;) on a Text node will always try to evaluate the text in between them as a Unicode character

Problem summary
Using an ampersand (&) and a semicolon (;) on a Text node will always try to evaluate the text in between them as a Unicode character

This appears to be due to the syntax required for HTML/hex/decimal entities. For example, © will display ©
https://learn.foundry.com/nuke/content/reference_guide/draw_nodes/text.html 

This issue happens in both Nuke's Node Graph and in Nuke Studio's Timeline.

Customer reported version
N/A

Customer reported platform
N/A

Steps to reproduce


1) Open Nuke.

2) Create a Text node.

3) In the message field, type in a sentence that contains an ampersand (&) then a semicolon (;). For example:

here is some text & here is some more; there appears to be a bug

​

Expected behaviour
If the syntax is not a HTML entity, then the raw string should be displayed in the Viewer.

Actual behaviour
Using an ampersand (&) and a semicolon (;) on a Text node will always try to evaluate the text in between them as a Unicode character.

Workaround
Adding a semicolon directly after the ampersand will give the expected result. For example, change the following text:

here is some text & here is some more; there appears to be a bug

To this:

here is some text &; here is some more; there appears to be a bug

​

Reproduced by support
This bug has been reproduced in:
Nuke 13.1v2 - Windows 10 - macOS 10.13 (High Sierra) - Linux CentOS 7
Nuke 9.0v1 - Windows 10 - macOS 10.13 (High Sierra)

Earliest version tested
Nuke 9.0v1  
- This issue appears to be in all versions of the product