in reply to Re^6: how are ARGV and filename strings represented?
in thread how are ARGV and filename strings represented?
It's worse than that. Consider the following program:
#!/usr/bin/perl use warnings; use strict; use feature qw{ say }; use Unicode::Normalize qw{ NFKD NFKC }; say $^O; my $letter = "\N{LATIN SMALL LETTER A WITH ACUTE}"; open my $out, '>', NFKD($letter) or die "Open: $!"; unlink NFKC($letter) or warn "Warn unlink: $!"; unlink NFKD($letter) or die "Unlink: $!";
Running it on Linux and Mac gives the following different outputs:
versuslinux Warn unlink: No such file or directory at ./script.pl line 13.
darwin Unlink: No such file or directory at ./script.pl line 14.
The same happens when you exchange NFKC and NFKD. Yes, on a Mac, normalization happens on top of UTF-8.
|
---|