1TL;DR: Run update_unicode.sh after the publication of a new Unicode 2standard and commit the resulting unicode_widths.h file. 3 4The long version 5================ 6 7The Git source code ships the file unicode_widths.h which contains 8tables of zero and double width Unicode code points, respectively. 9These tables are generated using update_unicode.sh in this directory. 10update_unicode.sh itself uses a third-party tool, uniset, to query two 11Unicode data files for the interesting code points. 12 13On first run, update_unicode.sh clones uniset from Github and builds it. 14This requires a current-ish version of autoconf (2.69 works per December 152016). 16 17On each run, update_unicode.sh checks whether more recent Unicode data 18files are available from the Unicode consortium, and rebuilds the header 19unicode_widths.h with the new data. The new header can then be 20committed.