This is basically the collection of information and conclusions from earlier discussions regarding the subject of names of entities, namespaces, packages, wrappers, etc. I collect this here to spare myself from searching for it again the next time a new wrapper is proposed (see #719).

For reference, please checkout #337 (comment) and the followup discussion as well as #204 (comment). If it were not for the limitation of not allowing '-' in some contexts and historical reasons, I'd prefer if it was called zxing-cpp (most of the time). Even though having different names for the same thing is far from ideal, each of the following has its merits or it's reasoning. I'll do my very best to make the situation not worse.

zxing-cpp:

• the main name nowadays as far as I'm concerned, mostly because of the discoverability of the github url
• (part of) the package name for the Android (mavencentral), iOS (cocoapods.org), Python (pypi.org) and Rust (crates.io) wrappers
• Android rootProject.name

zxingcpp:

• used everywhere where a '-' is not allowed but a lower-case name is idiomatic
• the android project name
• the python module name
• the rust crate name
• email: zxingcpp at gmail dot com

ZXingCpp:

• the C# namespace in the .NET wrapper
• the package name of the NuGet .NET package, since there are firm guidelines of how to name a package
• the SwiftPM name and the module name to be imported

ZXing:

• the C++ namespace where the core library code is found, since it is a C++ namespace there was no reason to call it ZXingCpp
• the name of the c++ library binary, still here merely for historical and backward compatibility reasons
• the prefix for all entities in the C-API
• the include directory name of the c/c++ header files
• the cmake project and library target (ZXing::ZXing)

ZXing-C++:

• the name used in documentation/README contexts only, this could go away rather easily

zxing:

• the name of WASM module (this should change)