Unicode in package name causes build failure

[edsko]

When I named my package Query书法字典, reading the generated paths module goes wrong:

# cabal new-build all
Build profile: -w ghc-8.6.3 -O1
In order, the following will be built (use -v for more details):
 - Query书法字典-0.1.0.0 (exe:Query书法字典) (first run)
/home/edsko/personal/doc/calligraphy/Query书法字典/dist-newstyle/build/x86_64-linux/ghc-8.6.3/Query书法字典-0.1.0.0/x/Query书法字典/build/Query书法字典/autogen/Paths_Query书法字典.hs: hGetContents: invalid argument (invalid byte sequence)

[phadej]

To be sure, if you have a package with non-generated non-ascii module name, those work ok? on your OS (seems linux) / file-system

[edsko]

Just tried. Created a package with non-ASCII characters in the package name but nowhere else. It fails somewhere else now:

[head 8.6.3 ~/personal/doc/calligraphy/t]
# cabal new-build all
Resolving dependencies...
Build profile: -w ghc-8.6.3 -O1
In order, the following will be built (use -v for more details):
 - Q嘿-0.1.0.0 (exe:Qhei) (first run)
Configuring executable 'Qhei' for Q嘿-0.1.0.0..
Saved package config file header is corrupt. Re-run the 'configure' command.

Not entirely sure why the difference (maybe it's just not building the paths module)?

[edsko]

Mind you, this is not exactly high priority :)

[phadej]

I see. So I tried locally and unicode module names are completely ok, but it's indeed the package-name which makes cabal not work.

It's indeed not high priority as Hackage forbids non-Ascii package names.

[edsko]

Ah, didn't even realize that. In that case I guess the only thing to do here is better error reporting.

[phadej]

It would be good if they would work. Properly upporting unicode in the executable / library would highlight places were we implicitly make assumptions which we shouldn't (at least in 2018+)

In any case, if someone wants to see what's corrupted, the

cabal-version: 2.4
name: package-олег
version: 0

library
  default-language: Haskell2010
  build-depends: base

is a single file reproducible case.

[edsko]

Turns out probably not a duplicate after all; see #5804 (comment) .

[hvr]

@edsko yes, it appears there are multiple bugs at play here :-)

[edsko]

Once you start using Chinese names in Haskell projects you start to realize quite how Western-biased we are :)