My C# project saves files and creates folders with the extended ASCII character "²" (superscript 2). Is this safe to work with internationally? Is this something that could cause any issues with the .NET libraries or Windows functions?
+2
A:
Starting windows NT (?) filenames are always unicode. so there shouldn't be a problem.
Things do get hairy when you start using alternative space characters, transliterated characters or characters which should have a bidirectional context but that is not the case with the superscript 2
shoosh
2010-03-17 20:32:17
Specifically, UTF-16.
Ignacio Vazquez-Abrams
2010-03-17 20:37:11
Nefariousity
2010-03-18 15:46:20
indeed they do.
shoosh
2010-03-18 20:33:38