Your message dated Sun, 27 Apr 2025 12:42:01 +0200
with message-id <10e96b3a-43e9-41d2-85e1-669a8c787...@sury.org>
and subject line Closing old tidy-html5 bugs
has caused the Debian Bug report #158015,
regarding tidy: How do you expect a big5 document to contain legal &#number;
references?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
158015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=158015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tidy
Version: 20020301-1
Severity: normal
First, html-t...@w3.org is closed to me because I use an 'Asian spam'
ISP or something.
But mainly, consider
http://jidanni.org/lang/pinyin/19970607tai_ke.html
I had to do in a Makefile
#avoid HTML-tidy -raw from mangling my unicode enitites!
#final processor [of my tidyed doc]:
19970607tai_ke.html: tai_ke_src.html
sed 's/@\(x\?[0-9a-fA-F]\+\)@/\&#\1;/g' $? > $@
So, am I not right in asking that I should be given a way to get
&#numlber; references thru tidy unscathed?
I even tried the aug 2002 tidy.
Consider the ü in
http://jidanni.org/lang/pinyin/20000527roadsigns.html
How does one expect to prevent it from being ruined on a -raw run, in
my charset=big5 document.
Am I not correct in saying that you have denied the use of any Unicode
above char 127 for big5 or other Asian 'charset=' users??
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux debian 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5
Versions of packages tidy depends on:
ii libc6 2.2.5-6 GNU C Library: Shared libraries an
--- End Message ---
--- Begin Message ---
Version: 2:5.8.0-1
I am closing all the bugs that had been filled before 5.8.0 upstream version
that are **upstream** issues.
If the bug that you've reported can still be found in 5.8.0, please retest this,
make sure that the upstream bugs are actually filled upstream and reopen
the bug in Debian BTS and correctly set the "forwarded" attribute on the
issue.
Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org
--- End Message ---
