And it's patently absurd to consider their argument that 1) they're still using trigraphs, but 2) intend to build against the C++17 spec. FFS, if you somehow f

And it's patently absurd to consider their argument that 1) they're still using trigraphs, but 2) intend to build against the C++17 spec. FFS, if you somehow find both of these to be true, preprocess your source to convert trigraphs to the corresponding glyphs, and to a character encoding that supports them. I can't possibly believe that they're running a C++17 compiler on a system that has no support for such a character set.