Tickets :: [#1559] problem with brazilian portuguese charset?

6.0.0-beta1

7/26/25

Summary	problem with brazilian portuguese charset?
Queue	IMP
Queue Version	4.0.2
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	marcus (at) underlinux (dot) com (dot) br
Created	03/16/2005 (7437 days ago)
Due
Updated	05/26/2005 (7366 days ago)
Assigned	03/16/2005 (7437 days ago)
Resolved	03/17/2005 (7436 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

05/26/2005 01:40:30 PM	plencastre (at) ovosmoles (dot) net	Comment #11	Reply to this comment
I have the same problem, did you resolvet, please awnser

03/18/2005 03:31:47 PM	Jan Schneider	Comment #10	Reply to this comment
Of course! If you send a text in a charset that you didn't specify in the message header, or that you specified wrong, how should it properly be displayed?

03/18/2005 02:46:03 PM	marcus (at) underlinux (dot) com (dot) br	Comment #9	Reply to this comment
This message i receved with Content-Type: text/plain; charset=ISO-8859-1 and á é í ó ú and ç dont WORK To: bugs@lists.horde.org From: bugs@coyote.horde.org Subject: [Tickets ~~#1559~~] RESOLVED: problem with brazilian portuguese charset? Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <20050318144215.9332034E55@coyote.horde.org> Date: Fri, 18 Mar 2005 06:42:15 -0800 (PST) X-Virus-Scanned: ClamAV 0.83/764/Wed Mar 16 20:50:20 2005 on gaucha.resenet.com.br X-Virus-Status: Clean DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: http://bugs.horde.org/ticket/?id=1559 ----------------------------------------------------------------------- Ticket \| 1559 Updated By \| marcus@underlinux.com.br Summary \| problem with brazilian portuguese charset? Queue \| IMP Version \| 4.0.2 State \| Bogus Priority \| 1. Low Type \| Bug Owners \| ----------------------------------------------------------------------- marcus@underlinux.com.br (2005-03-18 06:42) wrote: Jan when message come with Content-Type: text/plain; charset=UTF-8; format=flowed the ? ? ? ? ? and ? WORK if not come with Content-Type: text/plain; charset=UTF-8; format=flowed the ? ? ? ? ? and ? DONT WORK they on screen ? ? ? ? ? and ? Understand now ??? this is not problem with my fonts.

03/18/2005 02:42:14 PM	marcus (at) underlinux (dot) com (dot) br	Comment #8	Reply to this comment
Jan when message come with Content-Type: text/plain; charset=UTF-8; format=flowed the á é í ó ú and ç WORK if not come with Content-Type: text/plain; charset=UTF-8; format=flowed the á é í ó ú and ç DONT WORK they on screen ? ? ? ? ? and ? Understand now ??? this is not problem with my fonts.

03/17/2005 08:57:40 AM	Jan Schneider	Comment #7 State ⇒ Not A Bug	Reply to this comment
This only confirms Michael's presumption that it is a font issue on your system.

03/16/2005 08:33:08 PM	marcus (at) underlinux (dot) com (dot) br	Comment #6 New Attachment: screenshot2.jpg	Reply to this comment
same problem on internet explorer look screenshot

03/16/2005 08:24:47 PM	Michael Slusarz	Comment #5	Reply to this comment
Looks like the font you are using doesn't contain those characters - thus, your browser will display garbage for those characters.

03/16/2005 06:14:56 PM	marcus (at) underlinux (dot) com (dot) br	Comment #4 New Attachment: screenshot.jpg	Reply to this comment
look this screenshot

03/16/2005 06:08:16 PM	marcus (at) underlinux (dot) com (dot) br	Comment #3	Reply to this comment
when words have ç ã á ô imp dont show this and show strange caracteres like � � � � on subject and on body of message

03/16/2005 03:26:14 PM	Jan Schneider	Comment #2 Summary ⇒ problem with brazilian portuguese charset? State ⇒ Feedback	Reply to this comment
Please use more words and tell us exactly what your problem is.

03/16/2005 01:49:00 PM	marcus (at) underlinux (dot) com (dot) br	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ problem with brazilian portuguese charset ?? Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
IMP MAKE THIS -> Subject: Voc� recebeu um cart�o da uol. abra e leia! CORRECT -> Subject: Você recebeu um cartão da uol. abra e leia! how can i resolve this ??? i'm using $nls['defaults']['language'] = 'pt_BR'; $nls['defaults']['charset'] = 'ISO-8859-1';