sapling/tests/test-gendoc-ro.t

#require docutils gettext

Error: the current ro localization has some rst defects exposed by
moving pager to core. These two warnings about references are expected
until the localization is corrected.
  $ $TESTDIR/check-gendoc ro
  checking for parse errors
  gendoc.txt:58: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.
  gendoc.txt:58: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.
tests: splitting test-gendoc.t into per file tests Localizers can now run test-gendoc-$LOCALE.t instead of test-gendoc.t. After this change, test-gendoc.t only checks whether there is some localization for the expected set of languages and no others. Whenever a locale i18n/$LOCALE.po is added, someone needs to add test-gendoc-$LOCALE.t 2016-01-06 23:45:50 +03:00			`#require docutils gettext`

pager: move more behavior into core This moves the global flag and the --pager=yes logic into core. Only functionality change is that users now always get a --pager flag and can enable the pager via the flag without the extension active. Moving the flag into core exposes a defect in the ro localization, which will have to be corrected later. 2017-02-16 01:47:57 +03:00			`Error: the current ro localization has some rst defects exposed by`
			`moving pager to core. These two warnings about references are expected`
			`until the localization is corrected.`
tests: splitting test-gendoc.t into per file tests Localizers can now run test-gendoc-$LOCALE.t instead of test-gendoc.t. After this change, test-gendoc.t only checks whether there is some localization for the expected set of languages and no others. Whenever a locale i18n/$LOCALE.po is added, someone needs to add test-gendoc-$LOCALE.t 2016-01-06 23:45:50 +03:00			`$ $TESTDIR/check-gendoc ro`
			`checking for parse errors`
color: add the definition of '--color' in core If we want to be able to move the initialisation in core, we need core to be aware of that '--color' flag at all time. So we now have the definition in core. That flag is currently unprocessed without the extensions (will be fixed soon). In addition the default value for this flag in core is 'never'. Enabling the extensions change that default value to 'auto'. 2017-02-21 20:09:21 +03:00			`gendoc.txt:58: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.`
			`gendoc.txt:58: (WARNING/2) Inline interpreted text or phrase reference start-string without end-string.`