From 33f591aa6dfcfe5dca82c3f467027aa35eefb9a2 Mon Sep 17 00:00:00 2001 From: Eike Rathke Date: Mon, 14 Nov 2011 21:41:26 +0100 Subject: [PATCH] adapt doctype url to reality --- i18npool/source/localedata/data/locale.dtd | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/i18npool/source/localedata/data/locale.dtd b/i18npool/source/localedata/data/locale.dtd index d47d4ad26edc..c18ca8d34453 100644 --- a/i18npool/source/localedata/data/locale.dtd +++ b/i18npool/source/localedata/data/locale.dtd @@ -20,19 +20,14 @@ A second possiblity is: - temporarily (!) change the DOCTYPE of your file to read (all on one line) - + - upload it to the form available at http://www.validome.org/ - This will validate the file against the HEAD revision of locale.dtd on the - DEV300 development code line, for other revisions you'll have to specify - the corresponding tags or cws branch instead. For example, to validate - against a modified locale.dtd in CWS locales33 you would use - - + This will validate the file against the HEAD revision of locale.dtd - Please test locale data files either in a non-product (!) build, which + Please test locale data files either in an --enable-dbgutil build, which implements some checks and pops up assertion message boxes if the tests fail, or by setting the environment variable OOO_ENABLE_LOCALE_DATA_CHECKS to 'Y' or 'Yes' (or any other string starting with 'Y') or '1' before