After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 402909 - Inconsistent spelling of start and end tag for xmllint error messages
Inconsistent spelling of start and end tag for xmllint error messages
Status: RESOLVED OBSOLETE
Product: libxml2
Classification: Platform
Component: general
2.6.26
Other All
: High critical
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-31 18:12 UTC by elharo
Modified: 2021-07-06 07:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description elharo 2007-01-31 18:12:47 UTC
Consider these xmllint error messages:

http://www.aw-bc.com/:118: parser error : Couldn't find end of Start 
Tag TD line 118
<TD class="headerBg" bgcolor="#004F99" nowrap align="left">
                                              ^
http://www.aw-bc.com/:120: parser error : Opening and ending tag 
mismatch: IMG line 120 and A



Notice the inconsistency:

Start Tag
Opening tag
Ending tag

I suggest changing these to be in sync with the XML 1.0 recommendation. That is use the spelling, capitalization, and terminology 

start-tag
end-tag

Other information:
Comment 1 GNOME Infrastructure Team 2021-07-05 13:26:00 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/libxml2/-/issues/

Thank you for your understanding and your help.
Comment 2 elharo 2021-07-05 18:11:35 UTC
mass closing bugs is user hostile
Comment 3 André Klapper 2021-07-05 20:09:22 UTC
See the previous message... Blocking migration is developer hostile too? :)
Comment 4 elharo 2021-07-05 22:21:51 UTC
Throwing data away isn't migration. Quite the opposite.
Comment 5 André Klapper 2021-07-06 07:19:06 UTC
We decided against mass-migrating every ancient ticket as this would increase backlog bankruptcy even more. If this report is still an issue 14 years later and the reporter still cares, then it's acceptable to ask the reporter to take action again (or provide a patch if you really really care).
Do NOT reopen this ticket. Thanks for your understanding.