-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Foreign letters gets converted to ? #83
Comments
I did a little more testing on this. When I pipe in your sample graph, I get this output:
This confirms what you are seeing. My next test was to save our graph as a file and give that as a parameter to
I don't get the
|
I started trying to reproduce these results with PowerShell 6.1. From the console, this output also looks wrong:
But if I actually generate a graph it will show the correct characters. It looks like this is solved in PowerShell 6.1. So this is a bug with Windows Powershell and the way it pipes to executables. Still trying to chase down why saving to a file first is not working like I would expect. So I am playing with file encodings. |
I was able to get it to work from a file if I saved it this way:
But that encoding option is not available on Windows PowerShell 5.1 I hate to close the issue this way but I don't have an easy way to fix this on my end. It's resolved by updating PowerShell to the current version (PS 6.1). |
My outputs is actually the output of dot.exe after passing it that simple digraph from your example. That is where the height and position info comes from. It's the default standard out when no image is specified. I figured it was best to bypass Export-PSGraph while troubleshooting this one. I was unable to find a viable workaround in PowerShell 5.1 in my testing. |
When running Export-PSGraph on foreign letters they get converted to ?. Here is a test on the french ç and the danish ø:
Everything is fine in the Powershell code.
It is the creation of the image with dot.exe that introduces the error.
Line 187 in Export-PSGraph.ps1:
This issue should probably be stated to the team creating graphViz.
The text was updated successfully, but these errors were encountered: