I wrote:
If you output to Windows-1252
then that doesn't have those control characters (as the space is taken
up with extra printing symbols) so you should get a fatal encoding error
telling you that you can't linearise character 128 into the windows
encoding
No, sorry: the system should produce & # 1 2 8; (so refering to the
control character) rather than produce byte 128 (which is the ero in the
windows encoding). If you browser displays both those things as a euro
then that is good or bad, depending on your point of view....
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--