Hi,
We have problem with somne of our national letters like Ő and Ű. They don't appear in the RichText view. In the database the covreted (to text) data is OK. When I turn off the rich text feature i can download the original html as an attachment which has the right letters (right acute keywords and codes).
Just an example:
közelgÅ tél jelentÅs fűtésszámlája
which should be
közelgő tél jelentős fűtésszámlája
You see, only the ű and ő are problematic.
Our otrs version is 3.0.11.
We didn't have this problem with 2.3.
Regards,
Robert
[ SOLVED ] No Ő and Ű in ArticleMailContent
Moderator: crythias
[ SOLVED ] No Ő and Ű in ArticleMailContent
Last edited by silkgoat on 06 Dec 2011, 15:05, edited 1 time in total.
Re: No Ő and Ű in ArticleMailContent
Some result of my further investigation yesterday:
I sent an HTML letter to one of our queues/mail addresses. We use fetchmail->procmail->postmaster to deliver mails to the proper queues.
1. I turned off fetchmail and used telnet to examine mails in the mailbox. The characters are there (ő,ű)
2. Turned on fetchmail, but turned off procmail. Checking otrs local mailbox showed me that the characters are there.
3. Sent the mail through a pipe to otrs.Postmaster.pl. The created ticket was messed.
4. The coverted plain text/clear text in the database contains the ő,ű.
5. The database collation and charset is set to utf-8
Can you explain me the workflow of the ticket creation. Which module is responsible to parse the content/mailbody?
Regards,
Robert
I sent an HTML letter to one of our queues/mail addresses. We use fetchmail->procmail->postmaster to deliver mails to the proper queues.
1. I turned off fetchmail and used telnet to examine mails in the mailbox. The characters are there (ő,ű)
2. Turned on fetchmail, but turned off procmail. Checking otrs local mailbox showed me that the characters are there.
3. Sent the mail through a pipe to otrs.Postmaster.pl. The created ticket was messed.
4. The coverted plain text/clear text in the database contains the ő,ű.
5. The database collation and charset is set to utf-8
Can you explain me the workflow of the ticket creation. Which module is responsible to parse the content/mailbody?
Regards,
Robert
Re: No Ő and Ű in ArticleMailContent
Hi,
I solved the problem with changing Encode.pm fallback parameter from 'iso-8859-1' to 'utf-8';
Regards,
Robert
I solved the problem with changing Encode.pm fallback parameter from 'iso-8859-1' to 'utf-8';
Regards,
Robert