Default UTF-8 encode to Iso-8859-1 How to?

Excused my English, I have a problem with JCreator 2 early access, when, in JSP page, change encode it from Utf-8 to Iso-8859-1 JCreator of default restores to Utf-8, as I can make? I cannot use Italian chars as "� "
Thanks to who will want to help me.

Hi,
Please post the queries related to creator 2EA to the creator 2 EA discussion at https://feedbackprograms.sun.com/login.html
regards

Similar Messages

UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

Convert a UTF-8 string to ISO-8859-1 string

Hello. As you can see from my other post, I am working on internationalization. I could not find an appropriate entry in the forum already.
I want to convert form data (submitted from an HTML UTF-8 charset page) from the UTF-8 format to ISO-8859-1 format. How do I do that?
I.e.
String utfFormat="視聴者";
String isoFormat="";
// Do magic here
System.out.println(isoFormat); // out: "しての" (or whatever it is)
Can you help?
Dailysun
null

As I said in the other thread (did you read that, BTW?), you shouldn't have to bother with actual character-set conversions. You just tell the InputStream what the Charset is when you read it in, and the OutputStream what Charset to use when you write it out.
What you're doing is escaping characters by replacing them with numeric entity references--the opposite of what you asked in the other thread. The process is just as simple: cast the char to an int, convert that to a string with String.valueOf(int), and add the "&#" and ";". You can use a regex-based approach like I did over there, but going in this direction, it will be just as easy without them.
Hiwa, check out that other thread; I think you'll find it amusing (in light of that second link you posted).

Message mapping : UDF parameter string type versus default UTF-8 encoding

Hi,
I'm facing an issue with character encoding when using an UDF to transform into base64 encoding.
While thinking about the subject, I'm not 100% sure if it's possible to get it to work corerctly :
Given :
-The input XML is encoded UTF-8 ( with a special characeter )
-The UDF is generated with java parameter type 'string' ( = set of 16bit unicode characters )
Doubts :
-What is supposed to happen when a node content ( of message encoded in UTF-8 ) is used as input for the UDF string type parameter ? Is the node content decoded/encoded correctly by PI automatically ( at input/output versus the internal 16bit unicode character string ) ?
( I would assume yes )
-Is the default charset of the underlying JVM relevant ? Or does pi always use explicit charsets when encoding/decoding ?
( I would assume it's not relevant )
The UDF java code considers the string as a array of chars while processing them. It uses methods .length and .charat on the input string.
The result is that I have a ISO-8859 encoded string ! ( after decoding it back from the base64 )
What could cause this ?
regards
Dirk
PS If I simply use default functions ( concat etc..) then the resulting xml stays correctly encoded...

Hi,
But that would mean that an UTF-8 encoded byte array would be passed unconverted to the UTF-16 unicode string parameter ?
Shouldn't that trigger an exception ?
I'm going to make some tests and see if it enlights my knowledge ( empirical )
Keep you updated,
thanks
dirk

Problem when setting encoding to ISO-8859-1

Hi. Is there something I'm missing when it comes to setting
encoding? Here are the code in the mxml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
</Application>
In the html-template I'm setting:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1" />
The code for sending data from the app:
<mx:HTTPService
id="service"
url="encoding.jsp"
method="post"
showBusyCursor="true"
result="onResult(event)"
resultFormat="xml"
contentType="application/xml"
fault="onFault(event)"
useProxy="false" />
public function send():void {
var xml:XML = <Data>{data.text}</Data>;
service.send(xml);
But still the respons jsp I have made says it receives the
data in UTF-8 format? What am I doing wrong?
Servercode:
don't work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is ) );
work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is, "UTF-8") );

Are there no-one who have the same problem? I've tried
everything imaginable, and still the serverside receives the data
as UTF-8.
Is it supported at all to set the encoding of the
request?

How to switch DB string storage format from/to UTF-8 to/from ISO 8859-1 ?

As far as I understand strings in tables are stored by default in an Oracle DB in ISO 8859-1 format.
How can I switch the storage to UTF-8 format?
Do I have to change just a parameter (which ?) or do I have to setup/install the whole DB again?
If just a parameter switching is necessary:
How can I change already existing strings from one format to another?
Does it take place automatically or do I have to issue and explicite convert command (which ?).
Peter

Please refer to
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#sthref157
And
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#sthref1476
Sybrand Bakker
Senior Oracle DBA

Flat file transformation to xml with encoding in iso-8859-1

We have a BPEL process that picks up a flat fle (fixed length), transforms it to xml and emails it. The flat file is in iso-8859-1 (when I look at special characters like e-accent's in hex).
The basic transformation that you get from (the wizards) of BPEL don't do the trick, the special characters are corrupted and unreadable.
After that I changed all the encoding's (in xsd's and xsl's) from utf-8 into iso-8859-1 but doesn't help either. I also added an xsl:output section to my xsl (with "encoding="iso-8859-1") but that also fails...
Does anyone have a clue? We're using SOA Suite 10.1.3.1.
greetings,
Jan

just tried that but the problem is still there
I suspect that the output of the file adapter (reading the flat file) is already corrupted, you should be able to tell the file adapter what encoding the input file is...

Encoding Characters ISO-8859-2

You say:
You need to set your $ORACLE_HOME environment variable point to the database of interest.
I mean:
We work under WinNT(SP4) with MS DevStudio 6.0. What can I do to encoding Character ?
I put line <?xml version="1.0" encoding="ISO-8859-2"?> in the XML-Header, but the oracle-parser say ' LPX-00201 '.
Help, I need somebody help ? Thanks Matthias

I've found a solution. Yes, the problem was, when I've written polish characters into Excel file it encoded them as a rubbish. The problem was, I didn't set the cell encodding. So my code after I've fixed the problem looks like:
HSSFCell cell = row.createCell((short)0);
// And below is the line I was looking for
cell.setEncoding(HSSFCell.ENCODING_UTF_16);
cell.setCellValue("Some text with polish characters");
Now it works great. Thanks anyway.

XML data encoding iso-8859-1 . Currently utf-16 is default encoding

Hello ABAP Gurus ,
Need a help from you .
Scenario : We have SAP4.7 enterprise version which we have now converted to Unicode system . There is a BSP application which talks to an external web application (Non Unicode) thru HTTP protocol and sends data thru XML.
Problem : Problem is at the time when BSP application prepares the XML While preparing XML data , before converting to Unicode environment the encoding was "iso-8859-1" . But now after Unicode conversion , the encoding is "UTF-16".
The XML data looks like
<?xml version="1.0" encoding="utf-16"?><DATA><ACTION>CREATE_TICKET</ACTION><CRI
I have tried replacing "utf-16" by "iso-8859-1 " . The interface works . But at the recieving end , ie external web application , the German umlauts appear as some garbage values .
I know we need to enforce encoding . I have tried with the following code but could not suceed . The encoding appears as "utf-16".
Following is the section of code which I have written in BSP application.
Daten in DOM-Baum wandeln
 CALL FUNCTION 'SDIXML_DATA_TO_DOM'
 EXPORTING
 name = 'DATA'
 dataobject = ls_cr_xml
 IMPORTING
 data_as_dom = if_dom
 CHANGING
 document = if_document
 EXCEPTIONS
 OTHERS = 1.
 IF sy-subrc NE 0.
 error_out text-f47 text-f48 space space.
 ENDIF.
DOM-Baum in Character-Stream wandeln
 if_pixml = cl_ixml=>create( ).
 IF if_pixml IS INITIAL.
 error_out text-f50 text-f53 space space.
 ENDIF.
 if_pstreamfact = if_pixml->create_stream_factory( ).
 IF if_pstreamfact IS INITIAL.
 error_out text-f51 text-f53 space space.
 ENDIF.
 if_postream = if_pstreamfact->create_ostream_cstring( string = xml_doc ).
 IF if_pstreamfact IS INITIAL.
 error_out text-f52 text-f53 space space.
 ENDIF.
--Encoding--
data: gv_str type string.
data: gv_l_xml_encoding type ref to if_ixml_encoding.
data gv_l_resultb type boolean.
gv_str = 'ISO-8859-1' .
clear gv_l_xml_encoding.
 call method if_pixml->create_encoding
 EXPORTING
 byte_order = 0
 character_set = gv_str
 RECEIVING
 rval = gv_l_xml_encoding.
 clear gv_l_resultb.
 call method gv_l_xml_encoding->set_character_set
 EXPORTING
 charset = gv_str
 RECEIVING
 rval = gv_l_resultb.
 call method if_document->set_encoding
 EXPORTING
 encoding = gv_l_xml_encoding.
----Append child -
CALL METHOD if_document->append_child
 EXPORTING
 new_child = if_dom
 RECEIVING
 rval = lv_return.
 IF lv_return NE 0.
 error_out text-f47 text-f49 space space.
 ENDIF.
--Render the XML data to output stream--
 CALL METHOD if_document->render
 EXPORTING
 ostream = if_postream.
After this section of code is executed , the variable xml_doc gets filled up with XML data .
<?xml version="1.0" encoding="utf-16"?><DATA><ACTION>CREATE_TICKET</ACTION><CRI
Can anybody help how to enforce encoding ?
Regards,
Laxman Nayak.

Hi Aslam Riaz,
Did you find any solution..?
Kindly help me on this issue.
Thanks and Regards,
Shailaja Chityala

WSDL Generating in ISO-8859-1 encoding want in UTF - 8

Hi XI Geeks,
 When I am using "Define Web Service" tool in Integration Directory, the WSDL file is being created with encoding ISO-8859-1, but we want in "UTF-8".
 Is there any setting we need to change in WAS which will change this default.
Any ideas are welcome and thanks in advance.
Regards
Sujan

Hi Vishnu,
 We already did that for the time being. But the client wants it be consistent.
 In another client engagement the WSDL is created in "UTF-8" format we double checked twice.
 We are running on SP12.
If any of the SP12 guys can generated a WSDL and let us know that it is created in "ISO-8859-1" encoding.
Regards
Sujan

XML Encoding Issue - Format UTF-16 to ISO-8859-1

Dear Groupmates,
I have data in my Internal table which i am converting to XML using custom Transformation.
Data is going to third party.The third party system requires data in ISO-8859-1 Format but SAP is generating the same in UTF-16 Format.I have been able to change the format of file from
utf-16 to ISO-8859-1 format but after conversion i am getting invalid tag information in form of characters
like &lt , &gt etc..in my file.
Here is the code i have used to set the encoding to ISO-8859-1 :-
DATA: xmlout TYPE xstring.
DATA: ixml TYPE REF TO if_ixml,
streamfactory TYPE REF TO if_ixml_stream_factory,
encoding TYPE REF TO if_ixml_encoding,
ixml_ostream TYPE REF TO if_ixml_ostream.
ixml = cl_ixml=>create( ).
streamfactory = ixml->create_stream_factory( ).
ixml_ostream = streamfactory->create_ostream_xstring( xmlout ).
encoding = ixml->create_encoding(
character_set = 'ISO-8859-1' byte_order = 0 ).
ixml_ostream->set_encoding( encoding = encoding ).
Sample Output :-
<?xml version="1.0" encoding="iso-8859-1"?>
<AMS_DOC_XML_EXPORT_FILE><AMS_DOCUMENT AUTO_DOC_NUM="FALSE" DOC_CAT="CA" DOC_CD="CA" DOC_DEPT_CD="045" DOC_ID="XR10281060830400001" DOC_IMPORT_MODE="OE" DOC_TYP="CH" DOC_UNIT_CD ="NULL" DOC_VERS_NO="01">
<CH_DOC_HDR AMSDataObject="Y">
<DOC_CAT Attribute="Y"><![CDATA[CA]]></DOC_CAT>
<DOC_TYP Attribute="Y"><![CDATA[CH]]></DOC_TYP>
Please let me know if anyone has idea how i can get rid of the invalid tag information.
Thanks !
With Regards,
Darshan Mulmule

Darshan,
Did you get an answer for this question? We have same requirement to create XML file in ISO-8859-1 format with Attributes is set to "Y" and CDATA is being used for data.
Can you please let me know if you still remember how did you achieve it?
Satyen...

Changing the xml encoding from UTF-8 to ISO-8859-1

Hi,
I have created an xml file in xMII transaction that I feed into a webservice as input. As of now, the data in the xml file is entirely english text (it would be changing to have European text soon). I gave the encoding as UTF-8.
I get an error on the webservice side(not xMII code) that the its not able to parse. The error is 'SaxParseException: Invalid 1 of 1-byte UTF-8 sequence). I know that an easy fix is if tI change the encoding to iso-8859-1.
But the reference document doesnot let me put anythign other than UTF-8. Even if I put <?xml version="1.0" encoding="iso-8859-1"?> as the first line, when I save it and open it back, i see <?xml version="1.0" encoding="UTF-8"?>
Is there any way to change the encoding? Or better still, anyway idea why this invalid sequence is coming from?
Thanks,
Ravi.

Hi Ravi,
We have encountered scenarios where we needed to take the <?xml version="1.0" encoding="UTF-8"?> out completely. As xMII was providing the Web Service, it needed a workaround.
In your case, it seems that you wish to pass it from xMII to an external Web Service provider. One option might be to pass the XML document as string.
Once you convert it to a string, it may escape all XMl characters (i.e. '<' into '<'). You could perform a string manipulation and remove the <?xml version="1.0" encoding="UTF-8"?> from the string. You may also need to play around with xmlDecode( string ) function in the Link Editor.
I would suggest that before you try this option, create a string variable will the contents, but without the <?xml version="1.0" encoding="UTF-8"?> and try assigning it to the input.
You may also wish to try a string variable that has <?xml version="1.0" encoding="iso-8859-1"?> as the first line. If this works, you should be able to perform string manipulations to convert your XML document into this modified string.
Cheers,
Jai.

Encoding autodetection chooses ISO-8859-5 instead of UTF-8

A certain site producing HTML in UTF-8 without meta tags. The Firefox detects the encoding as ISO-8859-5, an absolutely dead and useless 'standard'. How to exclude it from the autodetection and maki it proper unicode?

It's a strange guess, if it's a guess. Are you sure the server isn't sending a header specifying that encoding? To view the content-type header, you can use an add-on (or if it's not a secure page, an external proxy):
* Live HTTP Headers extension: https://addons.mozilla.org/en-us/firefox/addon/live-http-headers/
* Firebug extension: https://addons.mozilla.org/en-US/firefox/addon/firebug/
* Fiddler debugging proxy: http://www.fiddler2.com/fiddler2/

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
 StringBuffer xmlStrBuf = new StringBuffer();
 TransformerFactory tFactory = null;
 Transformer transformer = null;
 Document document = null;
 public void performTest()
 xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
 .append("<TESTXML>\n")
 .append("<ELEM ATT1=\"Yes\" />\n")
 .append("</TESTXML>\n");
 // the encoding is set to iso-8859-1 in the xml declaration.
 System.out.println("initial xml = \n" + xmlStrBuf.toString());
 try
 //Test1: Use the transformer to ouput the xmlStrBuf.
 // This shows the xml encoding result from the transformer which will change to UTF-8
 tFactory = TransformerFactory.newInstance();
 transformer = tFactory.newTransformer();
 StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
 System.out.println("Test1 result = ");
 transformer.transform( ss, new StreamResult(System.out));
 //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
 DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = dfactory.newDocumentBuilder();
 document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
 // skip adding attribute since it does not affect the test result
 // Use a Transformer to output the DOM document. the encoding becomes UTF-8
 DOMSource source = new DOMSource(document);
 StreamResult result = new StreamResult(System.out);
 System.out.println("\n\nTest2 result = ");
 transformer.transform(source, result);
 catch (Exception e)
 System.out.println("<performTest> Exception caught. " + e.toString());
 public static void main( String arg[])
 XmlEncodingTest xmlTest = new XmlEncodingTest();
 xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
 StringBuffer xmlStrBuf = new StringBuffer();
 TransformerFactory tFactory = null;
 Document document = null;
 public void performTest()
 xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
 .append("<TESTXML>\n")
 .append("<ELEM ATT1=\"Resoluci�n\">\n")
 .append("Special charatered attribute test")
 .append("\n</ELEM>")
 .append("\n</TESTXML>\n");
 // the encoding is set to iso-8859-1 in the xml declaration.
 System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
 try
 //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
 //Test1: Use the transformer to ouput the xmlStrBuf.
 tFactory = TransformerFactory.newInstance();
 Transformer transformer = tFactory.newTransformer();
 byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
 StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
 ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
 Properties transProperties = transformer.getOutputProperties();
 transProperties.list( System.out); // prints out current transformer properties
 System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
 transformer.setOutputProperty("encoding", "ISO-8859-1");
 transformer.transform( streamSource, new StreamResult( xmlBaos));
 System.out.println("**** Test1 result = ");
 System.out.println(xmlBaos.toString("ISO-8859-1"));
 //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
 DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = dfactory.newDocumentBuilder();
 document = builder.parse( new ByteArrayInputStream( xmlbytes));
 // skip adding attribute since it does not affect the test result
 // Use a Transformer to output the DOM document.
 DOMSource source = new DOMSource(document);
 xmlBaos.reset();
 transformer.transform( source, new StreamResult( xmlBaos));
 System.out.println("\n\n****Test2 result = ");
 System.out.println(xmlBaos.toString("ISO-8859-1"));
 //xmlBaos.flush();
 //xmlBaos.close();
 catch (Exception e)
 System.out.println("<performTest> Exception caught. " + e.toString());
 finally
 public static void main( String arg[])
 XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
 xmlTest.performTest();
}

Nerving Problem with UTF-8 and ISO-8859-1

Hi,
I´m looking for a solution to serve this problem for many hours now, maybe someone can help me:
1.) We need to send our Mails with the ISO-8859-1-Charset because otherwise Windows-Users get the text in the message twice: once as plain, and after a question mark formated. So I changed the NSPreferredMailCharset in the com.apple.mail.plist to ISO-8859-1:
defaults write com.apple.mail NSPreferredMailCharset "ISO-8859-1"
2.) So far so good. It works until I add an attachment to a message. Adding an attachment forces the sending of the mail again as Unicode (UTF-8). I could change the encoding manual, but thats not the way we can work in our company.
My question is: is there any way to force mail to encode as ISO-8859-1? It can´t be that we have to change the encoding for every message.
Thanks a lot
florian
PS: I´m not sure if this is important: we use the osx in German.

I was thinking that since he is from Austria & references a company, there is a very strong possibility that the character "€" (the Euro currency symbol, Unicode 20AC, UTF-8 E2 82 AC) would frequently appear in messages.
Even if he sets a preference for ISO-8859-1 as the default with Terminal, or manually changes messages to ISO-8859-1, it would not be possible to include this symbol in such messages, since there is no "€" in ISO-8859-1.
Similar problems would occur with other symbols sometimes used in business (for example "™"), in engineering ("Ω"), in mathematics ("∑"), or even with some general punctuation marks such as the dagger ("†").
Other possible problems are the use of other currency symbols the Euro replaced (the franc's "₣" or the lira's "₤") or others still in use (the Israeli new sheqel's "₪ or rupee's "₨"). Ligatures in an international environment would really complicate things as well, as this Wikipedia article about the Œthel illustrates.
Note that in none of these cases would the presence or absence of an attachment matter -- ISO-8859-1 simply isn't up to the task.
I suspect that in some cases, if it is possible, setting the default to Windows-1252 (Windows Latin 1 in Mail's list?) would help, since it does include at least the Euro & dagger. I haven't played around with this much, but I do note that in a new message window containing "€" in the body, if I set the text encoding to Windows Latin 1, Automatic, or UTF-8, Mail doesn't complain, but if I set it to ISO Latin 1, I get an error saying the message can't be saved & an "Invalid Text Encoding" alert if I try to send it.
As for how messages are received at the other end, Windows apps (not just Outlook) are notorious for continuing to use non-Unicode API's even after the OS itself has long since moved to Unicode as its internal standard. Some of them employ bass-ackwards fixes like deciding ISO-8859-1 declarations are supposed to be Windows-1252 ones. Worse, Windows itself sometimes seems to interpret a few Windows-1252 code positions as their ISO-8859-1 control equivalents!
All this makes life that much more complicated for people trying to avoid problems like the above.

Default UTF-8 encode to Iso-8859-1 How to?

Similar Messages

Maybe you are looking for