Re: bug report: initdb failure on Microsoft Windows if path to initdb contains special chars

=?utf-8?B?U3TDtmNrZXIgQmVybmhhcmQgLSBha3RpdndlYiBHbWJI?= <bernhard(dot)stoecker(at)aktivweb(dot)de> writes:
> I’d like to report an issue concerning initdb on Microsoft Windows if running initdb.exe from a directory that contains special chars like German umlauts. The error message is: FATAL: invalid byte sequence for encoding "UTF8": 0xf6 0x63 0x6b

The directory name contains those, you mean?

Our position on this is that the data directory's path name has to be
valid in the encoding you are selecting for the database. Otherwise
it's just too much of a mess to deal with inside-the-database values
like the data_directory setting. It looks like you are using some
single-byte encoding (probably a Windows code page?) for your
filesystem names, so you should do the same for initdb's -E option.
Or switch to an all-ASCII path name.

regards, tom lane