Encoding issues sending accentuated characters
Hi,
My company operates in a French market within North America and a lot of people from our sales department use accentuated characters (é,à, û, etc.) within their emails. Some complain about characters being translated into ? (question mark) signs when customers reply, and they have a look at their original response that was sent using their blackberry machine. My sales team wonders if our customers receive the emails with? signs or as they originally typed it in the first place (i.e. with é, à, û, etc.).
I have looked at the documentation, and all I can find regarding encoding is about the blackberry browser encoding, but nothing concerning outgoing emails.
We are not using MS Exchange mail server.
Any thoughts?
Thanks much.
Pierre
hi
i have the same problem like you only in html emails.
Did you ffind an issue ?
Ciao
Similar Messages
-
Encoding issues sending accentuated characters Options
Hi, My users are use accentuated characters (é,à, û, etc.) within their emails. Some complain about characters being translated into ? (question mark) signs when customers reply, and they have a look at their original response that was sent using their blackberry machine. My sales team wonders if our customers receive the emails with? signs or as they originally typed it in the first place (i.e. with é, à, û, etc.). I have looked at the documentation, and all I can find regarding encoding is about the blackberry browser encoding, but nothing concerning outgoing emails. We are not using MS Exchange mail server. Any thoughts?
Thankshi
i have the same problem like you only in html emails.
Did you ffind an issue ?
Ciao -
Encoding issue in email send from SAP
Hi,
I am currently having encoding issue in email send by SRM .
Can some one help me ?
My problem :
When i key in my SC subject/desc through IE7 with encoding unicode (UHT-8). Everything look fine.
After i order the SC, Email will be sending out to the approver.
The email received by approver is including strange character.
Example desciption i putting on SC : Testing Encoding from IE7
Result : Email which received by approver : Testing Encoding from IE7Â.
Can some one advice me on this?
Thanks,
VaneceHello Vanece,
>
Vanece Hee wrote:
> (...)
> They look fine in BBP_PD as well.
>
> when i trace them in SOST, the word will be look weird.
> (...)
Problem could come from internal and external data format.
Depending on your SRM release, check OSS notes for report you used to generate approval mail ( RSWUWFMLEC, RBBP_NOTIFICATION_APP, etc.).
>
Vanece Hee wrote:
> (...)
> When i change the encoding setting in outlook to unicode for the email, it work for some email only.
> (...)
Ask to your Outlook team to have a look at Outlook settings.
You can also check OSS note 1319517 - Unicode Collection Note.
Regards.
Laurent. -
Change of Encoding in Sender JMS Adapter
Hi,
My scenario is like that:-
FTP->MQ Queue->JMS Queue->XI->R/3
From JMS Queue IDOC xml is coming in UTF-8 encoding to XI. In that IDOC xml certain special characters are there, say, some Latin or European character. But for the scenario XI->R/3, data are not getting posted to R/3. In XI side, it is not giving any error, but it is giving a flag (in QRFC Monitor) which is Error between two Character Sets.
I am unable to rectify this error. One solution I have guessed that is, it will be possible to resolve this issue if I can change the encoding in XI to ISO-8859-1. But I dont know how to change the encoding in Sender JMS Adapter in XI. Could you please help me to resolve this issue?
BR
Soumya BHi,
Check following:
1. In SXMB_MONI, what is the XML structure generated for inbound and outbound message. Check the encoding used in both. This could be checked by looking at the first line of XML generated. For UTF encoding, usually, the first line should look as follows:
<?xml version="1.0" encoding="UTF-8" ?>
2. If the encoding for both is different, try to figure out which encoding is used for Message Type in XI. For matching the encodings, you could change the XSD used for creating message type in XI. This way, the character encoding could be changed. And this solution should suffice if the problem has occured between XI to R3 scenario.
Also, for learning more about character encodings, you could visit following link:
http://www.cs.tut.fi/~jkorpela/chars.html
Hope it helps.
Bhavish.
Reward points if comments found useful:-) -
Encoding Issue : JMS and Mapping : utf-8 iso8859-1
Hi All,
I am facing some problem with encoding issue.
Scenario : JMS --> SAP PI --> JMS
Requirment : Input plain text file contain some special characters,"©®" . Based on this condition,In Java Mapping
we check the Payload and changed the 'encoding' tag to UTF-8 or ISO8859-1.
: <?xml version="1.0" encoding="UTF-8"?> in the target XML output.
While testing in Operation mapping our Java mapping works fine. as the encodeing tag changes from
UTF-8 to ISO8859-1 if the special character exists.But if I test the same in Integration Directory(Test Configuration)
or did a end to end testing. The encoding tag did'nt changes.
For testing we had to a set of Plain Text files with UTF-8 and ISO8859-1 .
I tried the options of using beans in Adapter modules in Sender JMS channel.
MessageTransformBean, TextCodepageConversionBean, XmlAnonymizerBean
These doc & threads ,was also referred[How to Handle Encoding in PI|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]
Regards,
Ashutosh RHi
public static boolean fixSpecialCharforWeb(String text) {
int i = 0;
Character c = null;
char[] ctext = null;
StringBuffer newText = new StringBuffer("");
//boolean encodingType = false;
if ((text == null) || (text.trim().length() == 0)) {
return encodingType;
} else {
try {
for (i = 0; i < text.trim().length(); i++) {
ctext = text.trim().substring(i, i + 1).toCharArray();
c = new Character(ctext[0]);
//Single quote
if ((text.trim().substring(i, i + 1).equals("'")) || (c.hashCode() == 8217) || (text.trim().substring(i, i + 1).equals("?")) || (c.hashCode() == 146) || (c.hashCode() == 145)) {
//newText.append("'");
encodingType = true;
return encodingType;
//Double quotes
if ((c.hashCode() == 8220) || (c.hashCode() == 8221) || (c.hashCode() == 147) || (c.hashCode() == 148)) {
//newText.append(""");
encodingType = true;
return encodingType;
// bullet point
if ((c.hashCode() == 8226) || (c.hashCode() == 149)){
encodingType = true;
return encodingType;
// tilde
if ((c.hashCode() == 732) || (c.hashCode() == 152)){
encodingType = true;
return encodingType;
// Soft Hypen
if (c.hashCode() == 173){
encodingType = true;
return encodingType;
// En-Dash
if ((c.hashCode() == 8211) || (c.hashCode() == 150)) {
encodingType = true;
return encodingType;
// Em-Dash
if ((c.hashCode() == 8212) || (c.hashCode() == 151)) {
encodingType = true;
return encodingType;
// Euro Sign
if ((c.hashCode() == 8364) || (c.hashCode() == 128)) {
encodingType = true;
return encodingType;
// Yen Sign
if (c.hashCode() == 165) {
encodingType = true;
return encodingType;
// Pound Sign
if (c.hashCode() == 163) {
encodingType = true;
return encodingType;
// 1/2 sign
if (c.hashCode() == 189) {
encodingType = true;
return encodingType;
// 1/4 sign
if (c.hashCode() == 188) {
encodingType = true;
return encodingType;
// 3/4 sign
if (c.hashCode() == 190) {
encodingType = true;
return encodingType;
// Sword/dagger
if ((c.hashCode() == 8224) || (c.hashCode() == 134)) {
encodingType = true;
return encodingType;
// Trademark
if ((c.hashCode() == 8482) || (c.hashCode() == 153)) {
encodingType = true;
return encodingType;
// Ampersand &
if ((text.trim().substring(i, i+1).equals("&")) || (c.hashCode() == 38)) {
encodingType = true;
return encodingType;
//Registered mark
if ((text.trim().substring(i, i + 1).equals("?")) || (c.hashCode() == 174)) {
//newText.append("®");
encodingType = true;
return encodingType;
//Copyright mark
if ((text.trim().substring(i, i + 1).equals("?")) || (c.hashCode() == 169)) {
encodingType = true;
return encodingType;
// Question.
if (c.hashCode() == 63 && c.toString().equals("?")){
//newText.append("?");
encodingType = true;
return encodingType;
//handling symbol ?
if ((text.trim().substring(i, i+1).equals("?")) || (c.hashCode() == 233)) {
encodingType = true;
return encodingType;
if ((text.trim().substring(i, i+1).equals("?")) || (c.hashCode() == 232)) {
encodingType = true;
return encodingType;
if (c.hashCode() == 144) {
encodingType = true;
return encodingType;
} catch (Exception e) {
e.printStackTrace();
return encodingType; -
I've written a PL/SQL package for emailing.
The issue that I'm having is that the final encoded stream has extra characters ( exclamation mark + new line + space ) "randomly" scattered throughout it.
If the email is plain-text, it's not a big deal, it just looks messy and unprofessional.
However, when sending HTML formatted emails, those extra characters can break HTML tag logic and thus, visually, hide some data/text.
This package allows for the creation of nicely formatted HTML alert emails which have a common look-and-feel.
However, when I view the email in my email viewer (+MS Outlook 2007+), there are additional characters inserted in the email source. However, if I user DBMS_OUTPUT.PUT_LINE( ... ) to view the dynamically created HTML code, created at run-time, it's clean.
I had previously created a similar process in UNIX Shell Script and a 2nd in webMethods.
The webMethods version also had some issues with the encoding (+we had to use base64 encoding to fix that+), however using base64 didn't fix the issue that I'm having in ORACLE.
My package code can be found at:
[http://www.mediafire.com/?sharekey=5b5b57bc23b48b866e7203eb87368129f0607387acaaf72db99f3f1679ee9294]
Any help would be greatly appreciated.
To reproduce my issues:
BEGIN
WM_EMAIL_HANDLER.SEND_ALERT ( in_processName => 'Test Maker',
in_msg => 'Something gone done broke. You''d better fix it.',
in_subject_msg => 'Something Broke',
in_threatLevel => 5,
in_to => WM_EMAIL_HANDLER.ARRAY( '[email protected]' ),
in_from => '[email protected]',
in_fromName => 'Oracle Database Account <[email protected]>',
in_smtp_hostname => 'yourMailHost',
in_smtp_portnum => 'yourMailHostPort' );
END;
Extra Info:
<ul>
<li>Oracle 10g running on Solaris UNIX</li>
<li>MS Exchange Server is our MAIL server</li>
<li>We're using mail host port 25</li>
</ul>Could you post the code which you are using to send the mail. I need to send mail from a oracle procedure. I posted a thread with subject "sending mail from oracle procedure".
Many thanks in advance. -
I'm using the below give code to send mail in Trukish language.
MimeMessage msg = new MimeMessage(session);
msg.setText(message, "utf-8", "html");
msg.setFrom(new InternetAddress(from));
Transport.send(msg);
But my customer says that he gets sometime unreadable characters in mail. I'm not able to understand how to solve this character encoding issue.
Should i ask him to change his mail client's character encoding settings?
If yes which one he should set.Send the same characters using a different mailer (e.g., Thunderbird or Outlook).
If they're received correctly, come the message from that mailer with the message
from JavaMail. Most likely other mailers are using a Turkish-specific charset instead
of UTF-8. -
Problem with accentuated characters in XLIFF file (no problem anymore)
Sorry, the following turned out to be a non-problem. XLIFF editor understands accentuated characters in the translation file very well :o)
I am trying to translate an APEX v 2.2 application from french to german.
Generated xlf file header reads:
<file original="f101_102_fr-ch_de.xlf" source-language="fr-ch" target-language="de" datatype="html">
All french diacritical characters in the file are replaced by something like é. Something similar happens when one exports CSV file to Excel with Automatic CSV Encoding set to "No".
Application main language can be swiss french (fr-ch) or french french (fr), with the same result.
Application Language Derived From is "Use application primary language"
Automatic CSV Encoding is set to "Yes".
Is there a possibility to export non-english characters correctly?
Thank you.
Message was edited by: kortchnoi
kortchnoiWell... In a way, it was my fault. I have created xliff file and looked at its contents using CodeWright text editor. Using CW's regular expressions and macros, one could process translation fairly easily.
However, in this file foreign characters are scrambled (=> my post).
Then, I decided to install and try XLIFF editor. The one recomended by SUN handled all diacritical characters nicely.
So, as long as I don't try to proceed to direct translation of the xlf file, but through XLIFFF editor, I don't have to worry about french and german accents. At least, I hope so (I still have to import the german translation to be sure).
Igor
Message was edited by: I. Kortchnoi
kortchnoi -
Z10 encoding issue in outgoing email
Hoping someone can help me. I've been an avid bb fan for years and my husband and I both handed in our bonds a week ago to move to the z10. We are both loving it. While my husband has had no issues with his I am very close to having no issues - except for one major one that affects me and my clients greatly. I have 2 email accounts - gmail (working without any issue at all - was up and running within a matter of minutes of receiving my z10). The other however has not been a fun or even manageable experience. My work email is web based and took a few days for me to even get it up and running. With my bold I was able to connect via Exchange but am no longer able to do so. I was told to connect via Active sync however my employer does not have this functionality and it is not supported. Following that I was told to connect using either IMAP or POP. And while I have been finally able to connect and receive my email when I SEND email it is a disaster!!!!! My out going mail seems to be adding in all of the encoding and so it becomes "unreadable" for lack of a better term. I have no idea where to turn on this. I have been constantly surfing and searching and and all forums that I can in hopes to find a resolution but have not yet found one - this is my last resort - otherwise sadly ....... Very, very sadly I will have to return my phone. Any suggestions at all would be much appreciated! Sorry for the "long-winded ness"
lesedwards wrote:
I agree. I run my own business in fact two business and I cannot be sending emails out from some half **bleep** address how professional does that look. Everything has worked perfect for 10 years and then I bought this piece of **bleep** called a Z10 and it even worked on it until the OS update.
Wow lesedwards.. you are on fire. Jacking your issue into every email thread and getting **bleep**ed constantly.
This thread was about an encoding issue, and from your other posts you are simply having connection issues.
@Sarealex - I haven't seen this issue with any of my email accounts over IMAP, what software version are you currently using?
-: DrewRead :-
Can't find an app on Blackberry World yet? Tweet the developer and ask when they will #GetWithBB10 !!
"Like it" if you like it. -
[SOLVED] File name encoding issue
Hi all,
I have a large series of files with accented characters, they were all displayed nicely, but at some point, when I copied them to another computer, the characters were replaced by codes, for instance: "ó" --> "ó".
+Renaming ie. "Pasó" (bad encoding of "Pasó") --> Pasó, while writing it, it shows the correct character, but when pressing enter the name remains ("Pasó")
+If I rename the file to something else and then to the correct name, it will accept it: Pasó --> Pas --> Pasó will display correctly.
I don't know if it's a system wide encoding issue because new files are displayed correctly, but I would like to know if I have to change file names manually to make them right.
PS. When copying bad encoded files to another FS (like a USB drive), nautilus and bash refuse to copy them.
Last edited by Wasser (2012-09-17 21:10:52)My fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# /dev/sda2 LABEL=ROOT
UUID=d2243d9c-b8e7-442a-8446-5a43a4d9221b / ext4 rw,relatime,data=ordered 0 1
# /dev/sda5 LABEL=HOME
UUID=e67f5cfa-3ec3-4c06-9c2c-62c4cc188ffe /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda3 LABEL=VAR
UUID=caac4924-2a13-4c97-9926-668ac0595ba3 /var reiserfs rw,relatime 0 2
# /dev/sda1 LABEL=UEFI
UUID=1E70-6485 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda4
UUID=14993c2e-4bc4-42e4-b2e5-9dbc286abb4c none swap defaults 0 0
Files in question are in /dev/sda5 (HOME)
Last edited by Wasser (2012-09-16 08:37:52) -
Apple Mail cannot encoding issues (Chinese Asian Language)
I've abandon Mail for almost 2 years, 2 issues I had before is the 'disappearing mail' and the encoding problem.
Now with my new MBP 17" I decided to use Mail again. I am getting the encoding problem again.
Things I tried already:
1. set the default encoding using Terminal to "BIG5"
2. check under 'Composing' preference for 'Plain Text', uncheck 'use the same message format as the original message'
3. Tried manually setting the encoding before sending. But in few instance Apple Mail tells me that there is an Error and cannot change the encoding. Even I succeeded in changing the encoding, there is no guarantee that the other side can read it properly.
This usually happens when I 'reply' or 'forward' a Chinese email to someone. So far it happens to the HTML type email.
Still I am getting problem sending mail that Outlook can properly decode by itself. To fix this from the Oulook side, they need to open the message by double click, select encoding for the message, and pick either UTF-8 or BIG5 (if the message is BIG5, select UTF-8 and vise versa) then the message will display properly.
I know this could be an Outlook problem (probably is) but I cannot tell my customer to change encoding each time. I really need a way to do this from the Apple Mail side.
The following is just one example of HTML email I replied and turns out to be BIG-5 under Outlook, but user need to select UTF-8 to view it.
In-Reply-To: <050201c7154d$3fa791c0$bcdd123d@SN012345678912>
References: <[email protected]> <050201c7154d$3fa791c0$bcdd123d@SN012345678912>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: multipart/alternative;
boundary=Apple-Mail-1--121729776
Message-Id: <[email protected]>
Cc: =?BIG5?B?RXZhSG/EX7XY?= <[email protected]>,
=?BIG5?B?SG9sbHlfUG9sYXLEX7XYs6Ks9cRS?= <[email protected]>,
=?BIG5?B?U3VzYW5hU29vxF+12A==?= <[email protected]>,
=?BIG5?B?UGh5bGxpc8Rftdg=?= <[email protected]>,
=?BIG5?B?S0VOLkpJQbjrvuWoyA==?= <[email protected]>,
"Viv Lee" <[email protected]>,
=?BIG5?B?SmFuZUNoZW6zr6Tlr3U=?= <[email protected]>,
=?BIG5?B?RWR3aW5ZYW+rwKWuxe8=?= <[email protected]>,
=?BIG5?B?MDA3NDalVMBzrvw=?= <[email protected]>
From: James Yao <[email protected]>
Subject: =?BIG5?B?UmU6IMRftdizbqT7pdarfr3osN3DRA==?=
Date: Sat, 2 Dec 2006 07:42:27 +0800
To: =?BIG5?B?vki0ZqzCIEpvYW4gVGFuZw==?= <[email protected]>
--Apple-Mail-1--121729776
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=BIG5;
delsp=yes;
format=flowed
Hi xxxx...... (body of the message)
I need help here, I still like the operation in Apple Mail but this is killing me. Please help.Thanks but I tried these already. Didn't seem to work.
I switched to Thunderbird. Took a while to convert my mailboxes (30+ of them) from emlx to mbox and loaded into Thunderbird.
Thunderbird is ok, address book really ***** since it doesn't work with the OSX Address book at all. I had to use vcf2ldif to convert address book but the Chinese character in the Address Book all became ??? in Thunderbird. And the time it takes to convert 400+ address is long (I already filtered the address book from my 1000+ contact)
Font setting in Thunderbird is not good as well. Emails in my folders are in different fonts all the time due to the difference in encoding. I just need to get used to it.
If Apple Mail can just handle encoding better, I will never switch. Both my customer and my family are having same problem, (because we all read/send Chinese Traditional email) Apple should do something. Already send email regarding this to Apple, and if there are other people with the same problem as me, pleas let Apple know about this. -
I'm trying to export my data in to Excel file. When I open the excel file the Japanese characters looks garbled.
iResponse.setHeader("attachment ; filename = \"" + reportFileName() + "\" ", "content-disposition");
iResponse.setHeader("application/vnd.ms-excel;","content-type");
iResponse.setHeader("UTF-8","Content-Encoding");
By Googling I learnt that Excel doesn't like UTF-8 format. Is there any other way I can export the data.
Thanks.Specifying the content encoding for a binary format like Excel is pointless. You are producing native Excel format, aren't you? If you're producing a CSV file and claiming it's Excel, you should have mentioned that.
Anyway: you're producing native Excel using something like Apache POI, I suppose? I would have thought it handled encoding issues, but check its documentation or its FAQ to see if that's really the case.
Another option, which may or may not be feasible, is to use the new Office 2007 format. It's based on XML, so all of the encoding issues are automatically handled. -
Hi Experts,
I need some insights for the character encoding.
The legacy system is sending nordic characters ( öä) in a fixed length flat to PI. We are using JMS adapter to receive the data.
The character set of Legacy system is
WE8MSWIN1252.
we have some outbound interfaces also with the same legacy system.
In receiver JMS communication channel I have used
CCSID = 1252
under module ( AF_Modules/MessageTransformationBean)
Transform.ContentType = text/xml;charset = UTF-8
With this setting Legacy system is able to view the nordic characters .
But for the inbound interfaces it is not working .
I have used following CCSID's
00819
1208
1252
used TextCodepageConversionBean but unsuccesfull.
We are getting junk characters in place of nordic when we see in comm channel monitoring, MONI or in IDoc.
Can anyone tell why its not working,
Regards
Biplab Das
Edited by: biplab das on Jul 28, 2011 2:57 PMOk let me explain.
the end to end flow is
Legacy system (oracle DB) -> MQ->PI->SAP
i have asked the MQ guys to hold the message in MQ and they did it and saved the text file as default encoding type (ANSI).
then i used a file adapter to pick the file from local server. it was not working with all combination i used.
Then i opend the file and changed the encoding to UTF-8 while saving. Then it worked.
But i can understand this is not a proper testing as i will get the data from Legacy system with char set WE8MSWIN1252.
What i am not getting here is outbound one worked... why the inbound not working.
Stefan - what u suggest?
Regards
Biplab -
Shockwave to Javascript - character encoding issue !
Hi !
I have resigned from sending messages from JavaScript to
Shockwave movie
as I have found all existing methods unreliable (at worst
scenario Flash
blocker is installed and using localConnection trick with
Flash gateway
fails).
But in the consequence, I have to send message (a search
string) from
Shockwave to JavaScript.
That seems easy with the following Lingo:
goToNetPage("javascript:void myJSfunction('" & aString
But the problem is with encoding possible non-ASCII
characters.
I presume the browser page is using charset=UTF-8.
Any idea how to properly encode 'aString' so it will preserve
non-ASCII
characters while being transfered to JavaScript?
It is really urgent!
Rgs,
Ziggi> I have resigned from sending messages from JavaScript to
Shockwave movie
I replied a little late to your earlier thread, but take a
look at
<
http://dasdeck.de/staff/valentin/lingo/dir_js/> -
POST using REST - encoding issue
Hi guys,
We have a REST web service that uses the Jersey API, running on a WebLogic Portal 10.0 server. This service must receive data that includes accentuated characters, such as e acute (é), populate an entity and store in a database. Using an HTML form to test, we observe the following behavior:
1. On the 1st submit, accentuated characters are replaced with reversed question marks in the database - clearly an encoding error.
2. On the 2nd and subsequent submits, accentuated characters are interpreted properly and saved correctly in the database.
HTTP request analysis shows that the only difference between the 2 requests is that the 2nd request includes a JSESSIONID cookie, so basically the session cookie. Removing the cookie after a successful submit then resubmitting the form produces again garbled characters in the database. This behavior can be reproduced on servers running on Windows and Linux (Red Hat).
Can anybody explain this behavior to me? How does having an HttpSession open change how character encoding is performed?
Thanks.Since UploadedFile.getInputStream() returns an InputStream, you can impose the character encoding when you wrap it with a Reader.
Maybe you are looking for
-
DVD Studio Pro saying m2v files are incompatible
I have a ProRes 422 QT file that I have compressed using the DVD presets (Best Quality 90 Min) in Compressor. I have used the same preset with no problems on other similar files, but now DVDSP refuses to import the file claiming it is an incompatible
-
How to cast StyledDocument in to String
Hi there, I would like to know if it is possible to put a StyledDocument variable in to a String and how I can do this. Casting???
-
Windows XP Using iTunes with Multiple Identities
Hi. I'm using Windows XP and iTunes 7. I have my music files on an external drive, but all my library files are in My Music folders. I'd like to share all the music with other users of this PC (my kids) from their own identities. I was able to import
-
Dear All, I have the following problem of getting the output table from the input table below. Do you have any idea of doing this with the help of analytic sql? p.s. I have done this by using pure plsql block which is too slow to run with high amount
-
Add new depreciation to existing assets
hi experts can we add new depreciation to existing assets , while creating new assets i can see the depreciation that i have created recently. but for the existing assets i want to add this new depreciation. venkat