> > need yet another one.
> >
> PLEASE, PLEASE, PLEASE explain how I am could tune my VLM.EXE OR NET.EXE to
> handle koi8-r in filenames! And the same about Mac AppleTalk client...
I don't know.
[skipped]
> > understanding the data in their files.
> >
> You are completely wrong. Our web (and not only our!) server has (on server
> side) files in both windows-1251 and koi8-r encoding. And in near future
> there will be Mac encoding (Mac users are just connected and there is still
> no content from them on web :-)
I am talking about mounted filesystems that aren't going to change
charsets of the file content on the fly, but are used by the same users
both locally and remotely through NFS/SMB/CODA/whatever -- in that
situation user has to choose one encoding for himself. And once you have
mentioned web servers, if you do any kind of code conversion, *PLEASE*
remove <META> tags with charsets from those files -- stupid FrontPage
always inserts them, and once in browser cache, those tags override real
charset.
-- Alex
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu