You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run GatorGrader inside of a Docker container on Windows 10 Pro or Windows 10 Enterprise, especially in the cmd prompt, there are some circumstances in which the checkmark and the xmark do not display correctly. Instead, there may be a box with various types of glyphs to indicate that the correct unicode symbol is not supported.
We should try to track down what default font and terminal combinations do not work correct and then provide instructions on how to fix this issue, if possible. If it is not possible to fix it in certain circumstances, then we might want to consider using a symbol that is more universally supported or at least provide documentation that the symbols will be wrong if you use Docker and Windows 10 Pro or Enterprise to run GatorGrader.
Can someone else who uses Windows 10 Pro or Windows 10 Enterprise provide a screenshot that demonstrates this problem? Finally, I should confirm that I don't think that this is ever an issue when GatorGrader is run in Docker on either Linux or MacOS.
The text was updated successfully, but these errors were encountered:
gkapfham
changed the title
Checkmarks do not display correctly when using GatorGrader in Windows and PowerShell or cmd
Checkmarks do not display when running GatorGrader in Windows and PowerShell/cmd
Jun 27, 2020
If you run GatorGrader inside of a Docker container on Windows 10 Pro or Windows 10 Enterprise, especially in the
cmd
prompt, there are some circumstances in which the checkmark and the xmark do not display correctly. Instead, there may be a box with various types of glyphs to indicate that the correct unicode symbol is not supported.We should try to track down what default font and terminal combinations do not work correct and then provide instructions on how to fix this issue, if possible. If it is not possible to fix it in certain circumstances, then we might want to consider using a symbol that is more universally supported or at least provide documentation that the symbols will be wrong if you use Docker and Windows 10 Pro or Enterprise to run GatorGrader.
Can someone else who uses Windows 10 Pro or Windows 10 Enterprise provide a screenshot that demonstrates this problem? Finally, I should confirm that I don't think that this is ever an issue when GatorGrader is run in Docker on either Linux or MacOS.
The text was updated successfully, but these errors were encountered: