##// END OF EJS Templates
help/dates: use DATE as place-holder in help and abort texts...
help/dates: use DATE as place-holder in help and abort texts The use of "{datetime}" was unfortunate since I as a user never knew if I was expected to do hg log -d '>{2011-04-01}' or hg log -d '>2011-04-01' The word "datetime" is also confusing -- calling it a date it much simpler.

File last commit:

r12427:f933b99e default
r13886:fe48c573 default
Show More
test-gendoc.t
54 lines | 1.5 KiB | text/troff | Tads3Lexer
Test document extraction
$ "$TESTDIR/hghave" docutils || exit 80
$ HGENCODING=UTF-8
$ export HGENCODING
$ for PO in C $TESTDIR/../i18n/*.po; do
> LOCALE=`basename $PO .po`
> echo
> echo "% extracting documentation from $LOCALE"
> echo ".. -*- coding: utf-8 -*-" > gendoc-$LOCALE.txt
> echo "" >> gendoc-$LOCALE.txt
> LC_ALL=$LOCALE python $TESTDIR/../doc/gendoc.py >> gendoc-$LOCALE.txt 2> /dev/null || exit
>
> # We call runrst without adding "--halt warning" to make it report
> # all errors instead of stopping on the first one.
> echo "checking for parse errors"
> python $TESTDIR/../doc/runrst html gendoc-$LOCALE.txt /dev/null
> done
% extracting documentation from C
checking for parse errors
% extracting documentation from da
checking for parse errors
% extracting documentation from de
checking for parse errors
% extracting documentation from el
checking for parse errors
% extracting documentation from fr
checking for parse errors
% extracting documentation from it
checking for parse errors
% extracting documentation from ja
checking for parse errors
% extracting documentation from pt_BR
checking for parse errors
% extracting documentation from ro
checking for parse errors
% extracting documentation from sv
checking for parse errors
% extracting documentation from zh_CN
checking for parse errors
% extracting documentation from zh_TW
checking for parse errors