Re: [Bug: 21.4.10] error translating mule entities
On Thu, 2003-02-13 at 23:17, Kevin Quick wrote:
The upstream version you sent below works fine. (VM + Xemacs is
great... I simply set the cursor to the end of the defun expression in
your message, hit C-X C-E, and then jumped to view one of the
"problem" emails)
Cool:)
Sorry, but your message also generates a couple of questions for me:
No problem, but it would have been even better if you hadn't snipped
xemacs-beta from the Cc...[re-added]
1) "upstream" implies that y'all are working on w3
changes that aren't
available as a current package because I tried to verify I was
running the latest w3 before reporting the problem. If this is
incorrect, let me know.
I guess you are running an up to date w3. But "upstream" nowadays is at
<http://savannah.gnu.org/projects/w3> and
<http://savannah.gnu.org/projects/url>;, it has been split. We'll be
monitoring what happens there and updating the XEmacs package version
whenever there is a new release and someone finds time to do that.
I have no objections to your suggested fix, but following upstream (even
though obsoleted in this case) would be the preferred way to go if the
fixes are equally good. What do you think?
2) "obsolete there as well" implies that mule translation
is being
done elsewhere. Is VM behind or is this a general rework?
The latter. IIRC when browsing the upstream CVS, I noticed that
mule-sysdp.el was first removed from the w3 CVS with a note that it's
been obsoleted in favor of the one in the new url package, but it has
been removed from url CVS with a note of it being obsolete. If you're
interested, browse the URLs from 1) above to find out more.
3) Will we have better translation for these in the future? For
example, ’ is an apostrophe, “ is open-double-quotes,
” is close-double-quotes, à is a slash, and · is a
dash (AFAIK). There are reasonable plaintext versions for these.
I'm not familiar enough with that stuff to be able to answer that.
Maybe contacting the upstream authors would be a good idea. Or someone
else from xemacs-beta?
Glad the problem is already mostly fixed, and sorry to have wasted
your bandwidth, but I appreciate the response.
My pleasure, thanks for testing and feedback. I'll be updating the
XEmacs w3 package soon with this change, just let me know which version
(yours or the upstream one) should be applied.
Cheers,
--
\/ille Skyttä
scop at xemacs.org