From 16c93d9147d3e1fb710b6f8a8c4b56d22ec37ca6 Mon Sep 17 00:00:00 2001 From: Daiki Ueno Date: Wed, 10 Feb 2016 15:50:39 +0900 Subject: doc: Mention the behavior stripping *.in * gettext-tools/doc/gettext.texi (Preparing ITS Rules): Add footnote explaining the matching behavior if the input file name has the .in suffix. Suggested by Jan Synacek. --- gettext-tools/doc/gettext.texi | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'gettext-tools') diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi index c87fb72..e5d2aec 100644 --- a/gettext-tools/doc/gettext.texi +++ b/gettext-tools/doc/gettext.texi @@ -12351,7 +12351,12 @@ an ITS rule with an XML file. If the above ITS file is saved as The @code{locatingRule} element must have a @code{pattern} attribute, which denotes either a literal file name or a wildcard pattern of the -XML file. The @code{locatingRule} element can have child +XML file@footnote{Note that the file name matching is done after +removing any @code{.in} suffix from the input file name. Thus the +@code{pattern} attribute must not include a pattern matching @code{.in}. +For example, if the input file name is @file{foo.msg.in}, the pattern +should be either @code{*.msg} or just @code{*}, rather than +@code{*.in}.}. The @code{locatingRule} element can have child @code{documentRule} element, which adds checks on the content of the XML file. -- cgit v1.1