ID 412014 - Using uppercase file extensions for custom font files prevents the font from appearing on the Text2 node

Problem summary
Using uppercase file extensions for custom font files prevents the font from appearing on the Text2 node.

Uppercase file extensions with the original Text node works as expected.

Customer reported version
Nuke 11.3v4

Customer reported platform
Windows 10

Steps to reproduce

1) Firstly, you will need a custom font file saved somewhere on your system - an example .ttf is attached. To reproduce the issue, the file extension will need to be uppercase (for example .TTF).

2) Launch Nuke and open the Project Settings (Press the S key on the Node Graph).

3) Inside Project Settings, open the 'Node' tab and set the 'project font path' knob to the directory where the custom font file is saved.

4) Create a Text node and open the 'font' dropdown knob. Notice that the custom font does not appear in the list.

5) If you now change the file extension on your system to lowercase and press 'Rescan font paths' (Project Settings > Node), the custom font should appear on the Text node.

Expected behaviour
The custom font should appear in the 'font' dropdown menu on the Text2 node.

Actual behaviour
The custom font does not appear in the 'font' dropdown menu on the Text2 node.

Reproduced by support
This bug has been reproduced in:

Nuke 12.0v2 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)

Nuke 12.0v1 - Windows 10

Nuke 11.3v1 - Windows 10

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke 9.0v1 - Windows 10

Nuke 8.0v1 - Windows 10

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