# for i in `git grep --name-only gettext | grep -v pot$` ; do
  #   xgettext -j -F -L PHP --from-code=UTF-8 \
  #     -o ./src/share/locale/en/LC_MESSAGES/OPNsense.pot "${i}"
  # done

For accuracy and simplicicity, the canonical english .pot file should be tracking source changes in this fashion.

Also, generating the base .pot file in this manner has an advantage for developers- if you make proper gettext calls in the code, you simply re-generate the .pot file, (instead of finding and inserting your changes by hand)...

One problem with the line above: the '-L PHP' flag makes a *ton* of C related warnings go away, but not all files in core are actually PHP...  Once this raises itself as a problem, a script generating this .pot file can get more sophicstocated to accomodate.  For now however, most things look like PHP syntax.
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>