On Mon, 11 Sep 2017 11:49:29 -0500, Paul Gilmartin (0000000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: More musings about Unicode, UTF-8, etc." (in <0662287305026690.wa.paulgboulderaim....@listserv.ua.edu>):
> On Mon, 11 Sep 2017 16:41:18 +0100, David W Noon wrote: >> >> I have added these strings to my code and the results are the same as >> yours. I suspect the rendering software does not handle CJK characters >> very well in Indo-European locales. >> > I'm calling it a font problem: The CJK characters display double-width, You are correct. I am using a fixed pitch font, but it uses 2 character cells for the CJK characters. [snip] >> There is a Makefile included that can build the source code using either >> GCC or CLANG using gmake. Those who use other C/C++ compilers will have >> to work out their own build sequence. >> > Fails for me with: > > 525 $ make > make: gcc-config: Command not found > make: gcc-config: Command not found Which operating system are you using? You should have received the gcc-config command as part of your GCC toolchain(s). This command allows you to select from multiple versions of GCC installed. I developed the code on Gentoo Linux. Such a system can have 5 or 6 GCC toolchains installed concurrently, so gcc-config is a must have. > make: Warning: File 'Unicode_test.cpp' has modification time 19042 s in the > future I'm in the BST timezone, so I'm 5 hours ahead of NYC and 8 hours ahead of LA/SF (and Redmond, WA, for that matter). > /g++ -o Unicode_test -pipe -std=gnu++14 -Wall -Wextra -O2 > -fomit-frame-pointer Unicode_test.cpp -Wl,--as-needed,--strip-all > make: /g++: Command not found > Makefile:13: recipe for target 'Unicode_test' failed > make: *** [Unicode_test] Error 127 If you edit the Makefile to remove the shell subcommands that invoke gcc-config and remove the slash separator, you should then access gcc and g++ through your PATH environment variable. > o I'm surprised that the fake text file survived network newline conversions. I concluded that Listserv was pretty dumb, so I felt that an attachment with a filename ending in .txt would survive. > o .zip is timezone-ignorant. Yes, it's derived from an old MS-DOS/PC-DOS command and those systems did not know for timezones when PKZIP was written. The archive file format does not permit timezone data. -- Regards, Dave [RLU #314465] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* david.w.n...@googlemail.com (David W Noon) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
