If I correctly identified the documents in question, the listing already declares character encoding under a META tag in document HEAD. So I would suppose it should be unnecessary to provide for further translation (notably, & entities). The encoding declaration states that all symbols must be interpreted as ISO-8859-1. What else should be needed? A browser must be able to read characters above 7Fh and interpret then correctly according to provided information - and that info is being provided.

>tnx for the answer. converting between codepages is OK, and the result is of course that the resulting txt file never will contain anything else than characters represented by hex codes between 20h to FF.
>
>But my problem is, that the ISP wants &xxxxx coding for characters with hex values above 7F. And my main question then is about what format is the accepted standard format for uploading txt files for display on the web, in a browser?
>
>That browsers can't read characters above 7Fh is ok, but is it not the responsibility of the ISP to handle any required translation?
>
>I have not seen any references to any program for converting ascii text to browser, html -compatible text, except I can of course write the required code myself- but that is another piece of cake.
>
>Now, the ISP says that if we can't convert the text, we may run a script file that he provide in our home directory on the web to perform the conversion - but that again impose a requirement on us that we did not have to comply with before.
>
>Regards, Rolf