Skip to content
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

Unicode Conversion Issues During Build Process on Non-English Operating Systems #1996

Open
dckaratas opened this issue Nov 17, 2024 · 3 comments

Comments

@dckaratas
Copy link

After the 'dotnet publish' step, in files like Server.VirtualHairInfo.v0 json, places containing the letter 'I' are converted to their Unicode equivalents when the operating system is not in English (in my case, Turkish). This causes an error during the build step. I tried changing the culture value in Main.cs and setting the language in publish.cmd, but these did not resolve the issue. The build was successful when the Windows language was set to English.

@kamronbatman
Copy link
Contributor

Can you post an example of the text? This is handled by the schema generator, which we need to force to English I guess.

@Bohicatv
Copy link
Contributor

The problem stems from how windows maps characters on windows 11 using different languages. Turkish has to be localized in runtime on his computer. Unless we can switch it based on detected system language. I don't know how to do this in .net 8+ without forcing all new compiles into Turkish "tr-TR".

@dckaratas
Copy link
Author

Here an example in Server.VirtualHairInfo.v0.json file after build when windows language set to English

{ "name": "ItemId", "type": "int", "rule": "PrimitiveTypeMigrationRule", "ruleArguments": [ "" ] }

when set to Turkish

{ "name": "\u0130temId", "type": "int", "rule": "PrimitiveTypeMigrationRule", "ruleArguments": [ "" ] }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants