Re: po file charset via auto-coding-functions

[Kenichi Handa <handa@m17n.org>]

In article <87mzkz3c23.fsf@zip.com.au>, Kevin Ryde <user42@zip.com.au> writes:

> Kenichi Handa <handa@m17n.org> writes:
>> 
>>  But, it seems that the current po.el doesn't do that but expects
>>  that it is called only on PO file.

> Yes, that's so.  That's why I tightened it up with a looking-at to
> demand a msgid "" + msgstr "", then the "Content-Type" in that header
> block.  It's always possible a non-po file could start that way, but
> it should be unlikely.

I see.

>>  especially when we can fix the problem by the other method (as in my
>>  previous mail).

> I think jka-compr is also affected, try visiting a compressed
> vi.po.gz.

It seems that this additional patch will fix it.  But I
admit that that this change is rather tricky compared with
the previous ones.  :-(

*** jka-compr.el	08 Aug 2005 10:13:24 +0900	1.87
--- jka-compr.el	24 Oct 2005 11:38:27 +0900	
***************
*** 500,509 ****
  	     (delete-file local-copy)))
  
  	  (unless notfound
  	    (decode-coding-inserted-region
  	     (point) (+ (point) size)
! 	     (jka-compr-byte-compiler-base-file-name file)
! 	     visit beg end replace))
  
  	  (and
  	   visit
--- 500,513 ----
  	     (delete-file local-copy)))
  
  	  (unless notfound
+ 	    (let ((buffer-file-name
+ 		   (concat file "!"
+ 			   (jka-compr-byte-compiler-base-file-name file))))
+ 
  	    (decode-coding-inserted-region
  	     (point) (+ (point) size)
! 	     buffer-file-name
! 	     visit beg end replace)))
  
  	  (and
  	   visit

---
Kenichi Handa
handa@m17n.org