libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        /usr/bin/python -s /usr/bin/itstool -m messages.mo ../C/bug-filing.page ../C/change-board-size.page ../C/change-theme.page ../C/commandline.page ../C/develop.page ../C/documentation.page ../C/fast-moves.page ../C/index.page ../C/license.page ../C/play.page ../C/rules.page ../C/scores.page ../C/shortcuts.page ../C/strategy.page ../C/translate.page
executable:     /usr/bin/itstool
kernel:         3.1.8-2.fc16.i686
reason:         itstool:336:_check_errors:parserError:  Entity: line 1:  parser  error :  Opening and ending tag mismatch: gui line 1 and key
time:           Mi 18 Jan 2012 20:12:06 CET
uid:            1000
username:       mariobl

backtrace:
:itstool:336:_check_errors:parserError:  Entity: line 1:  parser  error :  Opening and ending tag mismatch: gui line 1 and key
: mittelbar angewendet und für den nächsten Start von <gui>Fünf oder mehr</key>
:                                                                                ^
:
:
:Traceback (most recent call last):
:  File "/usr/bin/itstool", line 974, in <module>
:    doc.merge_translations(translations, opts.lang)
:  File "/usr/bin/itstool", line 657, in merge_translations
:    self._check_errors()
:  File "/usr/bin/itstool", line 336, in _check_errors
:    raise libxml2.parserError(self._xml_err)
:parserError:  Entity: line 1:  parser  error :  Opening and ending tag mismatch: gui line 1 and key
: mittelbar angewendet und für den nächsten Start von <gui>Fünf oder mehr</key>
:                                                                                ^
:
:
:Local variables in innermost frame:
:self: <__main__.Document object at 0x9366c2c>

comment:
:First I tried to create translated versions of the *.page files in help/C using the following command:
:
:$ msgfmt de.po && itstool -m messages.mo ../C/*.page
:
:But there was an additional legal.xml in help/C which was not translated. This caused the error. The following command worked:
:
:$ msgfmt de.po && itstool -m messages.mo ../C/*.xml ../C/*.page
:
:In general, there should be a convenient way to detect such missing files correctly, or we should prohibit such "mixed mode" *.page and *.xml files in the same folder by appropriate rules in the build toolchain. Would be simple to migrate legal.xml to legal.page, wouldn't it?