Re: po file charset via auto-coding-functions

[Stefan Monnier]

>     IIUC currently the argument passed is "vi.po" but that is not the argument
>     passed to operation either.

> Perhaps we should fix that.

>     As a matter of fact I think passing
>     "/home/handa/x.tgz!vi.po" is more correct: if we assume that
>     a suitable file-name-handler is installed it's perfectly correct.

> But I don't think we should install such a handler, because it would
> be an incompatible change in file name syntax.

Then maybe another syntax should be used, but currently that's the syntax
chosen: this is the value used for buffer-file-name.  In any case even if
you don't like this syntax, it's not "incompatible" since all it takes is to
make sure the file-name-handler makes expand-file-name,
file-name-nondirectory, and friends work correctly.

Myself, I don't care much about which particular syntax is used but
simply that "/full/pseudoname/to/vi.po" is no worse than "vi.po".

> And if we don't install such a handler, the argument isn't correct at all.

But it currently isn't correct either.  We're just passing more info.


        Stefan