problems with (decode-coding-region 'utf-8: ' gives &#39

Uwe Brauer oub at mat.ucm.es
Fri May 8 04:54:37 EDT 2009


>>>>> "Stephen" == Stephen J Turnbull <stephen at xemacs.org> writes:

   > Uwe Brauer writes:
   >> In turns out that  Xemacs (21.4.21. Or 21.5.18) cannot deal correctly
   >> with the ' any more. (While GNU emacs can!)
   >> 
   >> Look at the following example:
   >> Ich war heute  in Paris 
   ---> 
   >> J&#39;étais aujourd&#39;hui à Paris
   >> instead of 
   >> J'étais aujourd'hui à Paris
   >> 
   >> The relevant code line is 
   >> (decode-coding-region (point-min) (point-max) 'utf-8)

   > That has nothing to do with it.

   > Those are HTML character entities,
   > they are composed of perfectly valid ASCII characters,
   > Google put them there, not XEmacs, and
   > the utf-8 coding system must leave them alone.

   > The problem is that babel.el isn't doing anything about translating
   > them to characters.  Try adding

   >                          (require 'w3-parse)
   >                          (goto-char (point-min))
   >                          (while (progn
   >                                   (skip-chars-forward "^&")
   >                                   (not (eobp)))
   >                            (w3-expand-entity-at-point-maybe))

Thanks but which version of w3 are you using? I have 1.33
In mine  (w3-expand-entity-at-point-maybe) is not a function 
but from w3-parse
(defsubst w3-expand-entity-at-point-maybe ()
and
therefore when running your code I obtain 

Debugger entered--Lisp error: (void-function w3-expand-entity-at-point-maybe)
  w3-expand-entity-at-point-maybe()
  babel-url-retrieve("http://translate.google.com/translate_t")
  babel-google-fetch("Ich war heute  in Paris " "de" "fr")
etc etc

Uwe 




More information about the XEmacs-Beta mailing list