Groups | Search | Server Info | Login | Register
Groups > perl.wxperl.users > #101
| Newsgroups | perl.wxperl.users |
|---|---|
| Date | 2025-01-14 21:46 +0100 |
| Subject | Re: Doubleclick and @ARGV |
| Message-ID | <20250114214653.612e4a3e@phoenix.squirrel.nl> (permalink) |
| References | <20250113224522.5aaf1b0e@phoenix.squirrel.nl> <b360ee30-81d4-4956-b5f8-a5b970a32c06@gmail.com> <20250114171621.57ea3e7b@phoenix.squirrel.nl> <af7ae744-4020-426f-a6fe-0984d3e2d4fc@gmail.com> <20250114180439.1aea60f7@phoenix.squirrel.nl> |
| Organization | Squirrel Consultancy |
| From | jvromans@squirrel.nl (Johan Vromans) |
On Tue, 14 Jan 2025 18:04:39 +0100, Johan Vromans wrote: > Sorry, there is no terminal involved. Well, Windows wouldn't be Windows if it hadn't got some suprises up in its sleeve. You can ask the PowerShell what code page is default. [System.Text.Encoding]::Default On my system, this returned singlebyte iso-8859-1 encoding. This not only applies to the shells, but this is used throughout the whole system. Even in the situation described earlier. To change this, see https://stackoverflow.com/questions/57131654/using-utf-8-encoding-chcp-65001-in-command-prompt-windows-powershell-window What does your system report?
Back to perl.wxperl.users | Previous | Next — Previous in thread | Find similar
Doubleclick and @ARGV jvromans@squirrel.nl (Johan Vromans) - 2025-01-13 22:45 +0100
Re: Doubleclick and @ARGV jvromans@squirrel.nl (Johan Vromans) - 2025-01-14 17:16 +0100
Re: Doubleclick and @ARGV jvromans@squirrel.nl (Johan Vromans) - 2025-01-14 18:04 +0100
Re: Doubleclick and @ARGV jvromans@squirrel.nl (Johan Vromans) - 2025-01-14 21:46 +0100
csiph-web