Message.getSubject() with ISO-8859-1

Hello,
I'm trying to read the subject of a javax.mail.Message called message into a String:
String sTxtRequest=this.byteArrayToString(message.getSubject().getBytes("ISO-8859-1"));
public String byteArrayToString(byte[] bA)throws IOException{
String s=new String(bA, "ISO-8859-1");
return s;
Problem is, I never get german Umlaute (�, �, � etc) right.
I suppose that with calling message.getSubject() not ISO-8859-1 is used as a charset, but the platform's default character encoding. Is there any way to force the application to use ISO-8859-1 instead (without changing the default character encoding)?
Thank you,
rs

should be...
((MimeMessage)msg).setSubject(m_subject, "big5");
Message class has
abstract void setSubject(java.lang.String subject)
MimeMessage class has
void setSubject(java.lang.String subject, java.lang.String charset)

Similar Messages

Hi! Ihave a problems with ISO-8859-1

we define the communications channel type file with file encoding ISO-8859-1, when the messages see in the sxmb_moni is correct the characters is correct and the sign but when you test the message in the id.
when the messages is send have error with de characters and sign the message have a mistake.
Someone know something have one idea..

I've had the same problems with a File Adapter in my XI. If that is your case you have to change your encoding to the encoding of the XI server. I tried with ISO-8859-15(try with it, you never knows) and it worked. Its funny that the encoding in the CC parametrization its the encoding of the server

JasperReports Integration PDF is created with ISO-8859-1 instead of UTF-8

Hi,
This is a strange problem i'm struggling with. Since about one month the PDF's are created with the wrong character set. Instead of UTF-8 (this is also given as a parameter calling the procedure as you see below) the PDF are always created with ISO-8859-1.
declare
l_jasper_report_url VARCHAR2(100) DEFAULT 'http://localhost:8180/JasperReportsIntegration/report';
l_rep_name VARCHAR2(80) DEFAULT'SLRReports/SLR_Statistic_Service_Level_Report_Monat';
l_rep_format VARCHAR2(10) DEFAULT 'pdf';
l_data_source VARCHAR2(20) DEFAULT 'default';
l_rep_locale VARCHAR2(10) DEFAULT 'de_CH';
l_rep_encoding VARCHAR2(10) DEFAULT 'UTF-8';
l_StartDate DATE;
l_EndDate DATE;
l_MinDowntime INTEGER DEFAULT 1;
l_ServiceHour CHAR DEFAULT 'Y';
l_name VARCHAR2(50);
l_typ VARCHAR2(20) DEFAULT 'monatsreport_ccps';
l_additional_params VARCHAR2(200);
l_mime_type VARCHAR2(30);
l_blob BLOB;
BEGIN
l_StartDate := to_date('01.'||to_char( add_months(SYSDATE,-12),'MM.YYYY'),'DD.MM.YYYY');
l_EndDate := to_date('30.'||to_char( add_months(SYSDATE,-1),'MM.YYYY'),'DD.MM.YYYY');
l_name := 'slr-statistik-'||to_char(l_StartDate,'YYYY-MM')||'.pdf';
l_additional_params := 'UserName=SYSTEM'||chr(38)||'String_StartDate='||to_char(l_StartDate,'dd.mm.yyyy')||chr(38)||'String_EndDate='||to_char(l_EndDate,'dd.mm.yyyy')||chr(38)||'SLR_MinDowntime='||l_MinDowntime||chr(38)||'SLR_ServiceHour='||chr(38)||l_ServiceHour;
xlog ('PRC_GET_REPORT_TUNNEL', 'url (orig):' || l_rep_name||':'||l_additional_params);
-- generate the report and return in BLOB
xlib_jasperreports.set_report_url (l_jasper_report_url);
xlib_jasperreports.get_report (
p_rep_name => l_rep_name,
p_rep_format => l_rep_format,
p_data_source => l_data_source,
p_rep_locale => l_rep_locale,
p_rep_encoding => l_rep_encoding,
p_additional_params => l_additional_params,
p_out_blob => l_blob,
p_out_mime_type => l_mime_type );
dbms_output.put_line('p_out_mime_type: '||l_mime_type);
-- insert into report (id,name,typ,mime_type,lob_text,datum) values (p_report_seq.nextval,l_name,l_typ,l_mime_type,l_blob,sysdate);
-- commit;
-- apex_application.g_unrecoverable_error := TRUE;
EXCEPTION
WHEN OTHERS THEN
xlog ('PUT_BLB', SQLERRM, 'ERROR');
RAISE;
END;
It looks like the procedure UTL_HTTP.get_header ignores the encoding parameter and overwrites it with ISO-8859-1. I also tried to set it with UTL_HTTP.set_header before calling UTL_HTTP.get_header buth that didn't help either.
Then I started the JVM is started with the UTF-8 option and that made no change.
There were no new installation on Oracle, tomcat or JasperReports side. So I'm wondering what has caused this string behaviour.
Does anyone had this problem before or has a solution for it?
I appreciate your help very much.
Thanks and regards,
Chris

Hi,
As my understanding, you could choose the encoding ways by yourself:
Change your Internet Explorer 9 language
encoding settings
Alex Zhao
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Problems with reading XML files with ISO-8859-1 encoding

Hi!
I try to read a RSS file. The script below works with XML files with UTF-8 encoding but not ISO-8859-1. How to fix so it work with booth?
Here's the code:
import java.io.File;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.net.*;
* @author gustav
public class RSSDocument {
    /** Creates a new instance of RSSDocument */
    public RSSDocument(String inurl) {
        String url = new String(inurl);
        try{
            DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
            Document doc = builder.parse(url);
            NodeList nodes = doc.getElementsByTagName("item");
            for (int i = 0; i < nodes.getLength(); i++) {
                Element element = (Element) nodes.item(i);
                NodeList title = element.getElementsByTagName("title");
                Element line = (Element) title.item(0);
                System.out.println("Title: " + getCharacterDataFromElement(line));
                NodeList des = element.getElementsByTagName("description");
                line = (Element) des.item(0);
                System.out.println("Des: " + getCharacterDataFromElement(line));
        } catch (Exception e) {
            e.printStackTrace();
    public String getCharacterDataFromElement(Element e) {
        Node child = e.getFirstChild();
        if (child instanceof CharacterData) {
            CharacterData cd = (CharacterData) child;
            return cd.getData();
        return "?";
}And here's the error message:
org.xml.sax.SAXParseException: Teckenkonverteringsfel: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (radnumret kan vara f�r l�gt).
    at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
    at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
    at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
    at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
    at getrss.RSSDocument.<init>(RSSDocument.java:25)
    at getrss.Main.main(Main.java:25)

I read files from the web, but there is a XML tag
with the encoding attribute in the RSS file.If you are quite sure that you have an encoding attribute set to ISO-8859-1 then I expect that your RSS file has non-ISO-8859-1 character though I thought all bytes -128 to 127 were valid ISO-8859-1 characters!
Many years ago I had a problem with an XML file with invalid characters. I wrote a simple filter (using FilterInputStream) that made sure that all the byes it processed were ASCII. My problem turned out to be characters with value zero which the Microsoft XML parser failed to process. It put the parser in an infinite loop!
In the filter, as each byte is read you could write out the Hex value. That way you should be able to find the offending character(s).

.replaceAll("[a-zA-Z]", " ") with iso-8859-1

Hi im using the swedish �� letters. I want to replace parts in a text String with
" .replaceAll("[^a-zA-Z_0-9]", " ")" but the problem is that it replaces the �� letters to. I want to use the iso-8859-1 standard. But how?? Please help...

sorry the latters i wanted to use is: ö ä
But the forum didnt support them.

DB2 with iso-8859-15 text encoding

Hi,
I develop an application on weblogic server configure with a db2 data source. The application is using hibernate 3 (jpa). I cannot write correcly some characters in the database. Text encoding is not converted from utf-16 (java string) to iso-8859-15. Weblogic is installed with the last db2 jdbc driver (9.7).
Is there a data source property that inform the driver to convert utf-16 to the db2 encoding ?

Is the value (text) of header outputText a static text or it is binded to some bindings attribute or backing bean attribute?
If it is a static text then probably the JSF page encoding (not only the JSP tag specifying the encoding, but the whole file) may be broken. Once I had similar issues, and the only thing that helped was to Ctrl+A, Ctrl+X, Ctrl+V (cut all content of file and paste it back - it restores messed-up utf-8 encoding).
If it is not a static text, then check the "source" of the text: it should be the java class file also encoded in utf-8 (also, check Compiler options for your projects - plural). Also, chcek the default IDE encoding... Finally, the database also should have utf-8 encoding (if you are retrieving data from database to show in these header outputTexts).
As I stated before, I had a lot of issues and finally I learned that EVERYTHING should be set correctly to utf-8 in order not to have these strange effects...
Have in mind that Java is very complex in terms of string/text encodings, much more complex than e.g. MS.Net. Internally, Java uses utf-16 encoded strings while most of web applications use utf-8 (for efficiency reasons). So, the gap between Java and web is present, and legacy Java encodings support is quite impractical in modern applications where no one should ever have reason to use anything else than utf-8!

Problem with charset ISO-8859 with dinamic action

Hello
I migrated my application that was Apex 3.2, and now Apex is 4.2.3, but a have a problem when I'm use Dynamic Action with ISO-8859.
When I used a filter "ação" in dinamic action filter mounted by the apex presents 'aÃ § Ã £ o.'
If I force use of PlsqlNLSLanguage = BRAZILIAN PORTUGUESE_BRAZIL.UTF8 in Dads, works correct.
Please, Help me! I need to keep ISO-8859!
Thanks

Using another example to illustrate the problem… I
found an apparent solution using "encodeURI".
It sees:
quote:
BEFORE:
function SaveMsg()
if (document.sender.message == "" )
return false;
var mensagem=document.sender.message.value;
ds2.setURL('responsexml.asp?action=add'&msg='+mensagem);
ds2.loadData();
document.sender.message.value="";
document.sender.message.focus();
When the entrance of the changeable "mensagem" was
“João” was recorded in archive XML as
“Joo” ...
input: "João"
output: "Joo"
quote:
AFTER:
function SaveMsg()
if (document.sender.message == "" )
return false;
var mensagem=encodeURI(document.sender.message.value);
ds2.setURL('responsexml.asp?action=add'&msg='+mensagem);
ds2.loadData();
document.sender.message.value="";
document.sender.message.focus();
Now ...
input: "João"
output: "João"
This would be a good solution? I will not have problems,
right? Some opinion/suggestion on this solution?

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

ISO-8859-1 / Invalid UTF8 encoding

Hello!
I have nearly the same problem like V Prakash (ISO8859 & UTF 8
default encoding)
I am parsing a XML-Document with ISO-8859-1 encoding. The file
has no XML-Declaration.
I use the "setEncoding(String)"-method of class
oracle.xml.parser.v2.XMLDocument to set the right encoding.
The result is a
java.io.UTFDataFormatException: Invalid UTF8 encoding
What's wrong with my code or is it a bug in Oracle XMLParser
v2.0.0.2 ?
Thanks
Peter
null

Attachments: "1|type=application/octet-stream|desc=UTF-8 Encoding Error|2719|file=epm00001.xml|"
Interesting...again, the web page said I didn't have permission.
Here goes nothing...
Oracle XML Team wrote:
: Scott Sosna (guest) wrote:
: : No go...I'm going to try to attach the files, but the last
: time
: : I tried to do so, it didn't work.
: : Oracle XML Team wrote:
: : : Scott Sosna (guest) wrote:
: : : : Here's the test case you wanted.
: : : : <!ELEMENT B (#PCDATA|PERF)*>
: : : : <!ELEMENT I (#PCDATA|ALBUM|RATING|B)*>
: : : : <!ELEMENT P (#PCDATA|B|I|RATING)*>
: : : : <!ELEMENT EPM (ARTICLE*)>
: : : : <!ELEMENT ARTICLE
: : : : (HEADWORD,BIOGRAPHY,
: : : (DISCOGRAPHY|VIDEOGRAPHY|BIBLIOGRAPHY|FILMOG
: : : : RAPHY|COMPILATIONS)*,COPYRIGHT)>
: : : : <!ATTLIST ARTICLE Performer CDATA
#IMPLIED>
: : : : <!ATTLIST ARTICLE ArtID CDATA #IMPLIED>
: : : : <!ELEMENT HEADWORD (P)>
: : : : <!ELEMENT BIOGRAPHY (#PCDATA|P)*>
: : : : <!ELEMENT DISCOGRAPHY (I|P)*>
: : : : <!ELEMENT COPYRIGHT (P)>
: : : : <!ELEMENT PERF (#PCDATA)>
: : : : <!ATTLIST PERF LINK CDATA
#REQUIRED>
: : : : <!ELEMENT ALBUM (#PCDATA|B)*>
: : : : <!ATTLIST ALBUM LINK CDATA
#REQUIRED>
: : : : <!ELEMENT RATING (#PCDATA)*>
: : : : <!ATTLIST RATING rank CDATA
#REQUIRED>
: : : : <!ATTLIST RATING text CDATA
#REQUIRED>
: : : : <!ELEMENT FILMOGRAPHY (P)>
: : : : <!ELEMENT COMPILATIONS (P)>
: : : : <!ELEMENT BIBLIOGRAPHY (P)>
: : : : <!ELEMENT VIDEOGRAPHY (P)>
: : : : <?xml version="1.0" standalone="no"?>
: : : : <!DOCTYPE EPM SYSTEM "epm.dtd">
: : : : <EPM>
: : : : <ARTICLE Performer="Johansson, Jan"
: : : : ArtID="13994"><HEADWORD>
Johansson,
: : : : Jan</P></HEADWORD><BIOGRAPHY>
b. 16 September 1931,
: : : Swderhamn,
: : : : Sweden, d. 9 November 1968, Stockholm, Sweden. Johansson
: was
: : a
: : : : pianist, composer and arranger who became known to
: European
: : : : audiences as a member of <PERF LINK="Getz, Stan">Stan
: : : : Getz</PERF> ís quartet touring with <PERF
: : : : LINK="Granz, Norman">Norman Granz</PERF> ís
JATP
: : : : concerts in 1960. The following year he joined Arne
: : : : Domn...rus ís band, and also the Swedish Radio
: Jazz
: : : : Group, in 1967, composing and arranging for both.
: Johansson
: : : also
: : : : wrote for film, theatre, ballet (e.g. Rwrelser )
: and
: : : : television (e.g. the Pippi Lngstrwmpa tune). He reached
a
: : : broad
: : : : audience with sensitive renditions of Swedish folk
songs.
: : His
: : : : considerable talents as composer and arranger were
: : especially
: : : : apparent in his experimental writing for the Radio Jazz
: : Group,
: : : : which fused and reinterpreted European art music, folk
and
: : : jazz
: : : : in ways that went beyond the <PERF LINK="Basie,
: : : Count">Count
: : : : Basie</PERF> or <PERF LINK="Kenton, Stan">Stan
: : : : Kenton</PERF> formats for big band jazz ( Den
Korta
: : : : Fristen ). As a jazz pianist in a trio context,
: : Johansson
: : : : adopted a swinging <PERF LINK="Kelly, Wynton">Wynton
: : : : Kelly</PERF> -like style, but his skill in fully
: : exploring
: : : : the potentialities of a song far exceeded the American
: : : musician
: : : : (e.g. ëWillow Weep For Meí on 8 Bitar
: : Not
: : : to
: : : : be confused with Jan Johansson, the guitarist and music
: : : : teacher.</P></BIOGRAPHY>
: : : : <DISCOGRAPHY>
Rwrelser (Megafon, 1963)<RATING
: : : : rank="3" text="Good" >***</RATING>, Jazz P
Svenska
: : : : (Megafon 1964), Younger Than Springtime (Artist
: : : : 1972)<RATING rank="4" text="Excellent" >****</RATING>,
: 8
: : : : Bitar/Innertrio (Megafon 1989)<RATING rank="3"
: : text="Good"
: : : : >***</RATING>, Jan Johansson & Radiojazzgruppen:
: Den
: : : : Korte Fristen (Megafon 1991)<RATING rank="3"
: text="Good"
: : : : >***</RATING>, 300.000 Km/h (Heptagon
1994)<RATING
: : : : rank="4" text="Excellent" >****</RATING>, Musik Genom
: : Fyra
: : : : Sekler Med Jan Johansson (Heptagon 1994)<RATING
: rank="3"
: : : : text="Good" >***</RATING>, Jan Johansson Spelar Musik
: P
: : : Sitt
: : : : Eget Vis (Heptagon 1995)<RATING rank="3" text="Good"
: : : : >***</RATING>, En Resa I Jazz Och Folkton
(Heptagon
: : : : 1995)<RATING rank="3" text="Good" >***</RATING>, Jazz
: P
: : : : Ungerska/In Pleno (Heptagon 1996)<RATING rank="3"
: : : : text="Good" >***</RATING>.</P></DISCOGRAPHY>
: : : : <COPYRIGHT>
Encyclopedia of Popular Music
: : : : Copyright Muze UK Ltd. 1989 -
: 1999</P></COPYRIGHT></ARTICLE>
: : : : </EPM>
: : : You need to start with
: : : <?xml version="1.0" standalone="no"
encoding="ISO-8859-1"?>
: : : otherwise it will use UTF-8 as the default encoding. If
this
: : : does not solve your problem please post a new message
using
: : the
: : : Attach File option as we have found the act of cutting and
: : : pasting from a message can "fix" encoding problems.
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
: It worked the last time with your DTD File as I see it as an
: attachement. Simply start a new thread and attach the XML
file.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
null

=?iso-8859-1?Q?Problems_with_strange_characters_=C2=A3_?=

This is a multi-part message in MIME format.
------=_NextPart_000_0006_01C8C7C0.CA3D6A90
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 8bit
Hi there all,
I now think I'm going totally mad :)
I had a problem where a site I was developing was displaying
Â£ instead of
£. "Something to do with page encoding" I thought.
But not so, it seems.
I stripped the a page back to its bare essentials, and now I
have 2 pages
with exactly the same code (both are attached).
test2.aspx outputs £ £ £ £ £ £
and test3.aspx outputs Â£ Â£ Â£
Â£ Â£ Â£
Could anybody please test to see if they get the same thing
happen with
these 2 files?
If so, what the hell is going on?!?!?!?!?
Would really appreciate any help at all because I've spent
hours on this and
a little bit of time in therapy too :o)
Big thanks,
@ndyB
------=_NextPart_000_0006_01C8C7C0.CA3D6A90
Content-Type: application/xml;
name="test2.aspx"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="test2.aspx"
=EF=BB=BF<%@ Page Language=3D"VB"
ContentType=3D"text/html" =
ResponseEncoding=3D"utf-8" Buffer=3D"False" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" =
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns=3D"
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html;
charset=3Dutf-8" =
/>
<title>Untitled Document</title>
</head>
<body>
<p>
=C2=A3 =C2=A3 =C2=A3 =C2=A3 =C2=A3 =C2=A3
</p>
</body>
</html>
------=_NextPart_000_0006_01C8C7C0.CA3D6A90
Content-Type: application/xml;
name="test3.aspx"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="test3.aspx"
<%@ Page Language=3D"VB" ContentType=3D"text/html" =
ResponseEncoding=3D"utf-8" Buffer=3D"False" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" =
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns=3D"
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html;
charset=3Dutf-8" =
/>
<title>Untitled Document</title>
</head>
<body>
<p>
=C2=A3 =C2=A3 =C2=A3 =C2=A3 =C2=A3 =C2=A3
</p>
</body>
</html>
------=_NextPart_000_0006_01C8C7C0.CA3D6A90--

I've had the same problems with a File Adapter in my XI. If that is your case you have to change your encoding to the encoding of the XI server. I tried with ISO-8859-15(try with it, you never knows) and it worked. Its funny that the encoding in the CC parametrization its the encoding of the server

How to store UTF-8 characters in an iso-8859-1 encoded oracle database?

How can we store UTF-8 characters in an iso-8859-1 encoded oracle database? We can NOT change the database encoding but need to store e.g. Polish or Russian characters besides other European languages.
Is there any stable sollution with good performance?
We use Oracle 8.1.6 with iso-8859-1 encoding, Bea WebLogic 7.0, JDK 1.3.1 and the following thin driver: "Oracle JDBC Driver version - 9.0.2.0.0".

There are a couple of unsupported options, but I wouldn't consider using them on a production database running other critical applications. I would also strongly discourage their use unless you understand in detail how Oracle National Language Support (NLS) works, otherwise you could end up with corrupt data or worse.
In a sense, you've been asked to do the impossible. The existing databas echaracter sets do not support encoding the data you've been asked to store.
Can you create a new database with an appropriate database character set and deploy your application there? That's probably the easiest solution.
If that isn't an option, and you really need to store data in this database, you could use one of the binary data types (RAW and BLOB), but that would mean that it would be exceptionally difficult for applications other than yours to extract the data. You would have to ensure that the data was always encoded in the same character set, otherwise you wouldn't be able to properly decode it later. This would also add a lot of complexity to your application, since you couldn't send or recieve string data from the database.
Unfortunately, I suspect you will have to choose from a list of bad options.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

[svn:fx-trunk] 7661: Change from charset=iso-8859-1" to charset=utf-8" and save file with utf-8 encoding.

Revision: 7661
Author:   [email protected]
Date:     2009-06-08 17:50:12 -0700 (Mon, 08 Jun 2009)
Log Message:
Change from charset=iso-8859-1" to charset=utf-8" and save file with utf-8 encoding.
QA Notes:
Doc Notes:
Bugs: SDK-21636
Reviewers: Corey
Ticket Links:
    http://bugs.adobe.com/jira/browse/iso-8859
    http://bugs.adobe.com/jira/browse/utf-8
    http://bugs.adobe.com/jira/browse/utf-8
    http://bugs.adobe.com/jira/browse/SDK-21636
Modified Paths:
    flex/sdk/trunk/templates/swfobject/index.template.html

same problem here with wl8.1
have you sold it and if yes, how?
thanks

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.

ISO-8859-1 Message in JMS queue

Hello,
I have a scenario JMS>PI>JMS.
The ISO-8859-1 data is coming from JMS queue.
I am using content conversion and i have give text/xml;charset=ISO-8859-1.
I have tried CCSID as 819, 850 and blank but still error is coming.....
2009-11-05 06:29:51 Error Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: sun.io.MalformedInputException; nested exception caused by: sun.io.MalformedInputException
2009-11-05 06:29:51 Error MP: Exception caught with cause com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
Thanks and Regards
Hemant

Hello,
Now I m using AF_Modules/TextCodepageConversionBean Conversion.charset.
Now these modeule is ignoring the encoding type
MP: Processing local module localejbs/AF_Modules/TextCodepageConversionBean
Conversion: ignoring non text payload
MP: Processing local module localejbs/AF_Modules/MessageTransformBean
Transform: using Transform.Class: com.sap.aii.messaging.adapter.Conversion
Transform: transforming the payload ...
Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: sun.io.MalformedInputException; nested exception caused by: sun.io.MalformedInputException
MP: Exception caught with cause com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
Thanks and Regards
Hemant

Sun Java System Messaging Server doesn't support some ISO 8859 charsets

Hello,
I couldn't find any link to report bugs on the Sun Java System Messaging Server, so i guess i'll report it here:
Sun Java System Messaging Server currently doesn't support the ISO 8859-13 charset, which is the standard charset in the Baltic states. When a person recieves an email in that charset, every non-ASCII character in the message becomes absolutely unreadable when displayed in this webmail application.
This has been tested with this version of the product:
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.01 (built Jun 24 2004)
Furthermore, you can test the case by yourself using this link: http://www.lietuvybe.org/testas/. You can enter your e-mail address there to get a few sample messages in Baltic and Cyrillic charsets. You will see that the Sun Java System Messaging Server passes all those tests except this particular one. So, it's a very nice product. :)
It would be very very very cool if Sun would fix this small, but very important issue.
regards,
Rimas Kudelis

Hey! :)
I am feeling some bad vibes, here.Hey, sorry, I didn't want you to think it's personal. I didn't really mean to hurt you or whatever. You are trying to help and I do appreciate that. I really do.
The reason i'm a bit sad is about the policy of others:
First, i am not a provider of that webmail service i'm talking about. A big Lithuanian company is. Personally, I rarely use webmail apps at all, and even when i do, i use an app i internationalized myself. :). Meanwhile, i install Horde IMP as a webmail application for my small servers, and i'm satisfied with it.
The problem i described is literally not my problem. It's a problem of that big Lithuanian company mentioned above (and the users of its webmail system). I suppose this company does have that account already and, furthermore, they are the ones who should post to this forum or file a support request., and they are the ones who should be worried about that bug. However, reality differs. In reality, big companies in Lithuania don't care about correctness of their webmail apps too much. However, there are a few maniacs like me who do. We test their webmail apps, we contact them and describe them their problems and ask them to fix those problems. Sometimes, they do that, but in most cases we either don't get a reply at all, or we get something like "we'll take a look at it later". For example, lately, we had an issue with one of the most popular webmail providers in Lithuania skipping a MIME-version header. Fixing this issue is just a single line of code. However, we had to push them annoyingly for kinda few months until they finally fixed it.
That was the first aspect.
The second is that i don't really like to create hundreds of accounts for myself just to ocasionally report bugs like this one. If only Sun would let me to simply file a bug, and forget that, i would gladly do it. But no, i have to find a deeply hiden support page, then fill a form, create myself an account and a password, then log on, then fill some misterious support request... Do I have to do that for a company that won't even consider thanking me? I think that's too much. Furthermore, every party on the net enforces it's own username and password restrictions. That sucks too. I wish i could just log on as "rq" everywhere like this forum, using the same password i could easily remember. However, i have to use "rq", "er-ku" or "erku" or "rq@something" as my username on different platforms, and sometimes even my (long enough) password is not accepted. It's hard to track such accounts, and in most cases like this one, i don't really want to have an account at all, as i'm just passing by.
To summarize the post: I'm NOT a licenced user, and all I wanted was to file a bug, which affects licenced users and ordinary people.
How do i remove my account from this forum now? :)

Message.getSubject() with ISO-8859-1

Similar Messages

Maybe you are looking for