Windows curl and PowerShell UTF-8: what models miss

Git's curl on Windows turns Cyrillic into question marks while the server still says 200. Alone, Sonnet sent text safely in 9 of 13 tasks and Haiku in 8.

Text that leaves Windows through curl or Windows PowerShell can lose every character outside ASCII before the request is even built, and the server still answers with success. On our test PC, the curl that ships inside Git for Windows converted its command-line arguments to the ANSI code page: Cyrillic arrived as question marks, while dashes, curly quotes and accented letters arrived as lone bytes that a UTF-8 page renders as �. Windows PowerShell did much the same to a string body whenever -ContentType carried no charset. Do language models avoid this? They know the theory, but they often forget it while writing the actual command. Given 13 everyday requests that never mention encoding…

Read the full report on AISkills402: https://aiskills402.com/blog/windows-curl-powershell-utf8-what-models-miss?utm_source=devto&utm_medium=social