PDF export can't handle special characters?

I have a field on my report which needs to show an amount in Euros, so I have the Euro (â?¬) symbol in the report. This looks fine when I render the report in HTML and Excel, but when I render in PDF the text is all messed up. This also happens for some other characters with an ASCII code above 127...
Is this a known problem and how can we solve it?
Thanks,
VincentRelated posts:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=a199e6c6-c2e4-40d6-a89d-3f991a02cf3e
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=be0ab01e-7550-42c1-9617-13f3fb442cef
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Vincent" <Vincent@.discussions.microsoft.com> wrote in message
news:9D40C734-F1A8-47CA-809E-2008EFD6E338@.microsoft.com...
> I have a field on my report which needs to show an amount in Euros, so I
have the Euro (â?¬) symbol in the report. This looks fine when I render the
report in HTML and Excel, but when I render in PDF the text is all messed
up. This also happens for some other characters with an ASCII code above
127...
> Is this a known problem and how can we solve it?
> Thanks,
> Vincent
>|||Thanks for the related posts. This is indeed related to the version of the Acrobat Reader (works as of version 6.0), but I have also found a workaround for people who can only use Acrobat Reader 5.0:
Avoid the usage of Arial, Courier and Times New Roman as font type, since these are the fonts that can not be displayed properly with the euro symbol. Alternative could be Arial Unicode MS, Garamond, Microsoft Sans Serif or Verdana, these all look OK when I tested this.
I will also update the other posts, since this is interesting stuff!
"Ravi Mumulla (Microsoft)" wrote:
> Related posts:
> http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=a199e6c6-c2e4-40d6-a89d-3f991a02cf3e
> http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=be0ab01e-7550-42c1-9617-13f3fb442cef
> --
> Ravi Mumulla (Microsoft)
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Vincent" <Vincent@.discussions.microsoft.com> wrote in message
> news:9D40C734-F1A8-47CA-809E-2008EFD6E338@.microsoft.com...
> > I have a field on my report which needs to show an amount in Euros, so I
> have the Euro (ââ'¬) symbol in the report. This looks fine when I render the
> report in HTML and Excel, but when I render in PDF the text is all messed
> up. This also happens for some other characters with an ASCII code above
> 127...
> >
> > Is this a known problem and how can we solve it?
> >
> > Thanks,
> > Vincent
> >
>
>|||I am having the same problem in displaying Greek. Works fine on acrobat 6
and I am using Courier New. My problem is that I can not avoid Courier
because I need the font to be fixed font instead of True Type (I am
displaying text that need to be aligned). Is there another Fixed Type font
that will work with Greek (or special characters) for Acrobat 5?
"Vincent" wrote:
> Thanks for the related posts. This is indeed related to the version of the Acrobat Reader (works as of version 6.0), but I have also found a workaround for people who can only use Acrobat Reader 5.0:
> Avoid the usage of Arial, Courier and Times New Roman as font type, since these are the fonts that can not be displayed properly with the euro symbol. Alternative could be Arial Unicode MS, Garamond, Microsoft Sans Serif or Verdana, these all look OK when I tested this.
> I will also update the other posts, since this is interesting stuff!
> "Ravi Mumulla (Microsoft)" wrote:
> > Related posts:
> > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=a199e6c6-c2e4-40d6-a89d-3f991a02cf3e
> > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=be0ab01e-7550-42c1-9617-13f3fb442cef
> >
> > --
> > Ravi Mumulla (Microsoft)
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > "Vincent" <Vincent@.discussions.microsoft.com> wrote in message
> > news:9D40C734-F1A8-47CA-809E-2008EFD6E338@.microsoft.com...
> > > I have a field on my report which needs to show an amount in Euros, so I
> > have the Euro (ââ'¬) symbol in the report. This looks fine when I render the
> > report in HTML and Excel, but when I render in PDF the text is all messed
> > up. This also happens for some other characters with an ASCII code above
> > 127...
> > >
> > > Is this a known problem and how can we solve it?
> > >
> > > Thanks,
> > > Vincent
> > >
> >
> >
> >

PDF Errors

When generating a report it looks fine on the web, but if I export it to a
pdf and then open it, if it has certain characters in it eg â?¬ when I open in
acrobat the text beyond the character is corrupted, this only happens in
acrobat v5, in v6 its OK. If I create a word document with the same
character, export it to a pdf it looks ok when viewed in V5 or V6 of acrobat.
Any ideas'
ThanksWe have made a requirement that all our users are to use Adobe Acrobat 7 to
get the correct UNICODE output - plus there are bugs in Adobe 5 & 6 that are
fixed in 7. I find Adobe 7 to load much faster as well.
=-Chris
"RS newbie" <RS newbie@.discussions.microsoft.com> wrote in message
news:AD232AE8-97A2-46AA-A47E-09B8FCC365DB@.microsoft.com...
> When generating a report it looks fine on the web, but if I export it to a
> pdf and then open it, if it has certain characters in it eg ? when I open
> in
> acrobat the text beyond the character is corrupted, this only happens in
> acrobat v5, in v6 its OK. If I create a word document with the same
> character, export it to a pdf it looks ok when viewed in V5 or V6 of
> acrobat.
> Any ideas'
> Thanks|||We are using Reporting Services to distribute multiple reports in PD
form.
We have found that most of our users don't have Acrobat version
installed on their computers, so they can't open the reports withou
upgrading, which many of them are unwilling to take the time to do.
In addition, we've found that a few of the PDF files that have bee
created are corrupt - we can't open them from Acrobat 7 or any othe
version of Acrobat. We're not sure why this is happening. We'r
able to re-run the corrupted reports and export to PDF from Repor
Manager with no problem
My questions are, is there any alternative to requiring that user
have installed Adobe 7, and can you tell me anything about corrup
PDF files being generated
Thanks|||I am having the same problem. But its not specific to PDF - happens with XLS
as well. Did you find a fix for this?
"jillpeterson" wrote:
> We are using Reporting Services to distribute multiple reports in PDF
> form.
> We have found that most of our users don't have Acrobat version 7
> installed on their computers, so they can't open the reports without
> upgrading, which many of them are unwilling to take the time to do.
>
> In addition, we've found that a few of the PDF files that have been
> created are corrupt - we can't open them from Acrobat 7 or any other
> version of Acrobat. We're not sure why this is happening. We're
> able to re-run the corrupted reports and export to PDF from Report
> Manager with no problem.
> My questions are, is there any alternative to requiring that users
> have installed Adobe 7, and can you tell me anything about corrupt
> PDF files being generated?
> Thanks!
>|||I am having the same problem with PDF and Excel arriving corrupt but work
fine rendered directly in report manager. I have not found a fix, but perhaps
someone from MS will chime in at some point. I am using an external
non-Exchange SMTP server(Communigate Pro and Ironport spam/virus scanning
appliance). I don't know if something in the mail exchange is corrupting the
MIME type or something. I'm going to look through the mail logs to see if I
find anything.
Forrest
"comet61" wrote:
> I am having the same problem. But its not specific to PDF - happens with XLS
> as well. Did you find a fix for this?
> "jillpeterson" wrote:
> > We are using Reporting Services to distribute multiple reports in PDF
> > form.
> >
> > We have found that most of our users don't have Acrobat version 7
> > installed on their computers, so they can't open the reports without
> > upgrading, which many of them are unwilling to take the time to do.
> >
> >
> > In addition, we've found that a few of the PDF files that have been
> > created are corrupt - we can't open them from Acrobat 7 or any other
> > version of Acrobat. We're not sure why this is happening. We're
> > able to re-run the corrupted reports and export to PDF from Report
> > Manager with no problem.
> >
> > My questions are, is there any alternative to requiring that users
> > have installed Adobe 7, and can you tell me anything about corrupt
> > PDF files being generated?
> >
> > Thanks!
> >
> >|||I think Im going to repost this and see if I get a response.
"forrestsjs" wrote:
> I am having the same problem with PDF and Excel arriving corrupt but work
> fine rendered directly in report manager. I have not found a fix, but perhaps
> someone from MS will chime in at some point. I am using an external
> non-Exchange SMTP server(Communigate Pro and Ironport spam/virus scanning
> appliance). I don't know if something in the mail exchange is corrupting the
> MIME type or something. I'm going to look through the mail logs to see if I
> find anything.
> Forrest
> "comet61" wrote:
> > I am having the same problem. But its not specific to PDF - happens with XLS
> > as well. Did you find a fix for this?
> >
> > "jillpeterson" wrote:
> >
> > > We are using Reporting Services to distribute multiple reports in PDF
> > > form.
> > >
> > > We have found that most of our users don't have Acrobat version 7
> > > installed on their computers, so they can't open the reports without
> > > upgrading, which many of them are unwilling to take the time to do.
> > >
> > >
> > > In addition, we've found that a few of the PDF files that have been
> > > created are corrupt - we can't open them from Acrobat 7 or any other
> > > version of Acrobat. We're not sure why this is happening. We're
> > > able to re-run the corrupted reports and export to PDF from Report
> > > Manager with no problem.
> > >
> > > My questions are, is there any alternative to requiring that users
> > > have installed Adobe 7, and can you tell me anything about corrupt
> > > PDF files being generated?
> > >
> > > Thanks!
> > >
> > >|||I am still having the problem. I ruled out the Ironport Mail
gateway...sending the mail directly to the Communigate Pro mail server. I
still end up with corrupted attachments, pdf or excel. They still work fine
when created inside the web frontend.
A regular email with an excel attachment that
works(sent from me to me) has something like this in the header
Mime-Version: 1.0
Content-Type: multipart/mixed;
boundary="=====================_694514546
==_"
This failed emails have something like
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="--
=_NextPart_000_004A_01C5A315.F220E550"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE
V6.00.3790.1830
Which is produced by Reporting Services. I'm guessing there is something
non-standard about Microsoft's Mime encoding with this mailer. I'm not quite
sure how to fix it. There are not many mail options in the RepSvc's config.
I'm not sure what I can do on the mail server side of things. This probably
works fine with Exchange...but that doesn't help the rest of us. --Forrest
"comet61" wrote:
> I think Im going to repost this and see if I get a response.
> "forrestsjs" wrote:
> > I am having the same problem with PDF and Excel arriving corrupt but work
> > fine rendered directly in report manager. I have not found a fix, but perhaps
> > someone from MS will chime in at some point. I am using an external
> > non-Exchange SMTP server(Communigate Pro and Ironport spam/virus scanning
> > appliance). I don't know if something in the mail exchange is corrupting the
> > MIME type or something. I'm going to look through the mail logs to see if I
> > find anything.
> >
> > Forrest
> >
> > "comet61" wrote:
> >
> > > I am having the same problem. But its not specific to PDF - happens with XLS
> > > as well. Did you find a fix for this?
> > >
> > > "jillpeterson" wrote:
> > >
> > > > We are using Reporting Services to distribute multiple reports in PDF
> > > > form.
> > > >
> > > > We have found that most of our users don't have Acrobat version 7
> > > > installed on their computers, so they can't open the reports without
> > > > upgrading, which many of them are unwilling to take the time to do.
> > > >
> > > >
> > > > In addition, we've found that a few of the PDF files that have been
> > > > created are corrupt - we can't open them from Acrobat 7 or any other
> > > > version of Acrobat. We're not sure why this is happening. We're
> > > > able to re-run the corrupted reports and export to PDF from Report
> > > > Manager with no problem.
> > > >
> > > > My questions are, is there any alternative to requiring that users
> > > > have installed Adobe 7, and can you tell me anything about corrupt
> > > > PDF files being generated?
> > > >
> > > > Thanks!
> > > >
> > > >|||I've discovered the attachments work fine in Outlook...just not Eudora Pro. I
do not think it is a email server issue..I tried sending through communigate
pro and exim with the same result. I think it is a Eudora issue in that it is
not RFC compliant in understanding UTF-8 encoded emails. The MS reportsvc
docs say that the subscription mailer encodes only in UTF-8 and cannot be
changed. I found a eudora plugin that can convert the body of a message from
utf-8 to our charset but it does not seem to help with the attachment. Blogs
say Eudora may fix the problem in future releases...but Eudora Paid 6.2.3 is
not working for me yet.
"forrestsjs" wrote:
> I am still having the problem. I ruled out the Ironport Mail
> gateway...sending the mail directly to the Communigate Pro mail server. I
> still end up with corrupted attachments, pdf or excel. They still work fine
> when created inside the web frontend.
> A regular email with an excel attachment that
> works(sent from me to me) has something like this in the header
> Mime-Version: 1.0
> Content-Type: multipart/mixed;
> boundary="=====================_694514546
> ==_"
> This failed emails have something like
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
> boundary="--
> =_NextPart_000_004A_01C5A315.F220E550"
> Content-Transfer-Encoding: 7bit
> X-Mailer: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE
> V6.00.3790.1830
> Which is produced by Reporting Services. I'm guessing there is something
> non-standard about Microsoft's Mime encoding with this mailer. I'm not quite
> sure how to fix it. There are not many mail options in the RepSvc's config.
> I'm not sure what I can do on the mail server side of things. This probably
> works fine with Exchange...but that doesn't help the rest of us. --Forrest
>
> "comet61" wrote:
> > I think Im going to repost this and see if I get a response.
> >
> > "forrestsjs" wrote:
> >
> > > I am having the same problem with PDF and Excel arriving corrupt but work
> > > fine rendered directly in report manager. I have not found a fix, but perhaps
> > > someone from MS will chime in at some point. I am using an external
> > > non-Exchange SMTP server(Communigate Pro and Ironport spam/virus scanning
> > > appliance). I don't know if something in the mail exchange is corrupting the
> > > MIME type or something. I'm going to look through the mail logs to see if I
> > > find anything.
> > >
> > > Forrest
> > >
> > > "comet61" wrote:
> > >
> > > > I am having the same problem. But its not specific to PDF - happens with XLS
> > > > as well. Did you find a fix for this?
> > > >
> > > > "jillpeterson" wrote:
> > > >
> > > > > We are using Reporting Services to distribute multiple reports in PDF
> > > > > form.
> > > > >
> > > > > We have found that most of our users don't have Acrobat version 7
> > > > > installed on their computers, so they can't open the reports without
> > > > > upgrading, which many of them are unwilling to take the time to do.
> > > > >
> > > > >
> > > > > In addition, we've found that a few of the PDF files that have been
> > > > > created are corrupt - we can't open them from Acrobat 7 or any other
> > > > > version of Acrobat. We're not sure why this is happening. We're
> > > > > able to re-run the corrupted reports and export to PDF from Report
> > > > > Manager with no problem.
> > > > >
> > > > > My questions are, is there any alternative to requiring that users
> > > > > have installed Adobe 7, and can you tell me anything about corrupt
> > > > > PDF files being generated?
> > > > >
> > > > > Thanks!
> > > > >
> > > > >