FUDforum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » FUDforum » FUDforum Suggestions » Getting Non Printable Characters In Post (How To Get Rid of the Black Dimaond Question Marks?)
Show: Today's Messages :: Unread Messages :: Show Polls :: Message Navigator
| Subscribe to topic | Bookmark topic 
Switch to threaded view of this topic Create a new topic Submit Reply
Getting Non Printable Characters In Post [message #36750] Thu, 05 April 2007 14:12 Go to next message
jeffrey is currently offline  jeffrey   United States
Messages: 36
Registered: June 2006
Location: Atlanta, GA
Karma: 0
Member
add to buddy list
ignore all messages by this user

Do you get black diamonds in your posts?[ 2 votes ]
1.
2.
 

I'm getting little black diamonds on my board as a result of non-ascii characters getting into the list.

I do filter for any of these characters but it appears these were somehow (MIME?) encoded into the email message before it got posted. In the process of posting, the non-ascii characters showed up.

So I'm not totally sure how to rid my board of these special characters. Anyone know of a script that can convert email from Windows/Outlook that's encoded in whatever format it uses, to convert it into ASCII text? I would like to make this part of my filter before I hand it over to FUDforum.

To give you an idea of what I'm talking about, here's what the message looked like in the email:

Quote:

Subject: [ShelbyUSERS] =?iso-8859-1?q?Processing_Shelby_PO=92s_in_AP?=
Reply-To: ShelbyUSERS(at)yahoogroups(dot)com
X-Yahoo-Newman-Property: groups-email-ff
Content-Type: multipart/alternative;
boundary="zFJvW24Dcz0JINr7vYFTA8FlasqtrBQVRuko3Tv"
X-Spam-Status: No
X-Scanned-By: MIMEDefang 2.56 on 63.247.91.82
Status: R

--zFJvW24Dcz0JINr7vYFTA8FlasqtrBQVRuko3Tv
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

We have been gradually moving from manual PO's to Shelby PO's. Our
business administrator loves approving the PO's into the system and
tracking encumbrances. I thought our AP processor would appreciate
the reduced data entry, but at this point the change has had some
frustrations. Here's our current issue=85



Notice the =92 in the subject I think that's an apostrophe. Also notice the =85 at the end, that's a question mark. All these end up looking like black diamonds on the page:

http://www.thompsonic.com/~jeffrey/non-ascii.jpg
Re: Getting Non Printable Characters In Post [message #36774 is a reply to message #36750] Sun, 08 April 2007 11:34 Go to previous message
Ilia is currently offline  Ilia   Canada
Messages: 13241
Registered: January 2002
Karma: 0
Senior Member
Administrator
Core Developer
add to buddy list
ignore all messages by this user
=# is caused by "quoted-printable" the forum tries to decode those upon import. However, you may also need to use iconv() to convert foreign chars into the charset used by your forum.

FUDforum Core Developer
Quick Reply
Formatting Tools:   
  Switch to threaded view of this topic Create a new topic
Previous Topic: Easily Add a Non-FUDforum URL to the Main Menu
Next Topic: Sticky Postings
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Dec 14 19:53:43 EST 2017

Total time taken to generate the page: 0.00650 seconds