# 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>
If this file is generated regularly, it becomes easier for translators to keep up with changes to the source code. (Or, at least changes with accompanying gettext calls).
This was generated with:
# for i in `git grep --name-only 'gettext' | grep -v 'pot$'` ; do
# xgettext -j -o ./src/share/locale/en/LC_MESSAGES/OPNsense.pot "${i}"
# done
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
xgettext(1) is obviously much simpler than creating the canonical .pot file by hand. (If only I'd have known better before I started this :)
This .pot file was generated from the source code via:
# for i in `git grep --name-only 'gettext' | grep -v 'pot$'` ; do
# xgettext -j -o ./src/share/locale/en/LC_MESSAGES/OPNsense.pot "${i}"
# done
For this commit, the old header was retained- it will be deleted in the next commit, for ease of scriptable maintinence of the canonical english .pot file.
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
Adds controller functionality to read form definitions from an xml file in [Controller]/forms/ directory to keep Volt template code a bit cleaner an more understandable.
