|
From: Petr M. <mi...@ph...> - 2006-12-13 22:55:26
|
> > If I take an older file from my OS/2 times with cp852, and pass it > > through gnuplot, I expected there will be the same output. Not that > > it will use UTF8 encoding of my Linux box. Same for files copied from > > a current Windows box. > > Then I am afraid you are out of luck. You can only use an encoding > that you have installed. How can that possibly be any other way? > If you send me a cp852 script, and I run it on my non-cp852 machines, > how are they to magically figure out this mysterious encoding? No, we use it -- there are so many Czech encodings :-)) If you get a file with cp852 and run it through gnuplot, the postscript terminal will render the correct output. You have many encodings installed. Use e.g. kate or gedit and Menu -> Encoding and voila, you can edit file in any encoding. > I agree with that part. I'm trying to point out that we are not > in that situation currently. As it stands today, the encoding > information in the output file header is not guaranteed to match > the actual file contents. If someone intentionally breaks it... > I think what you are asking for is that the gnuplot script itself > be marked with an encoding. That may be reasonable, and we could > add that to the output of "save", but it wouldn't help older > pre-existing scripts that don't have such a header record. Only if 8bit chars are used. If old files don't have set encoding, then they are not portable anyway. --- PM |