Italic characters change to normal style when exported to PDF

In my reports, italic characters are changed to normal style when exported
to pdf.
Is there a way to prevent this style change?
Not : SP1 is installed.
Thanks...This is working in our tests. You might try switching fonts to see if it
makes a differnce. We do not embed fonts into the document.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"eralper" <eralper@.discussions.microsoft.com> wrote in message
news:6756039B-4452-4972-96E6-6D640D113777@.microsoft.com...
> In my reports, italic characters are changed to normal style when exported
> to pdf.
> Is there a way to prevent this style change?
>
> Not : SP1 is installed.
> Thanks...|||Hi,
Ok, problem occurs when Chinese italic characters are used in the exported
pdf documents.
I use "MS Arial Unicode" font.
"Brian Welcker [MSFT]" wrote:
> This is working in our tests. You might try switching fonts to see if it
> makes a differnce. We do not embed fonts into the document.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "eralper" <eralper@.discussions.microsoft.com> wrote in message
> news:6756039B-4452-4972-96E6-6D640D113777@.microsoft.com...
> >
> > In my reports, italic characters are changed to normal style when exported
> > to pdf.
> >
> > Is there a way to prevent this style change?
> >
> >
> > Not : SP1 is installed.
> >
> > Thanks...
>
>

Issue with full-text query (containstable)..

I've got a full-text index on a table 'items' with an image field
'item' into which I've imported word and pdf documents. I've only got
~10 docs imported currently, for testing. I know that each of these
documents, except for one, includes the term 'ontology' or
'ontologies'.
I've got the following query, which gives back only two of these
documents (1 word, 1 pdf):
select i.*, ct.rank as incl_ctr
from items i inner join
containstable(items, item,
' ("class*" and "info*") or "ontology" '
) ct on i.id = ct.[key]
where (ct.rank > 1) and i.incl_ext in ('.doc','.pdf')
order by ct.rank desc;
I know this is incomplete, based on the content of each document, which
is an issue I'd like to work out; but prior to that, if I write the
query with "onto*" as a prefix term instead of "ontology", it only
gives back one of the two docs (the pdf):
select i.*, ct.rank as incl_ctr
from items i inner join
containstable(items, item,
' ("class*" and "info*") or "onto*" '
) ct on i.id = ct.[key]
where (ct.rank > 1) and i.incl_ext in ('.doc','.pdf')
order by ct.rank desc;
I can't identify why this is. I'd be very interested in whatever input
I could get on this..
Installed evaluation version: 2000 - 8.00.194 on Windows XP.
Installing the pdf ifilter improves the circumstance described in the
initial post; yet I think it's odd that onto* yields fewer docs in that
query than ontology, which continues to be the case..

Issue with exporting to pdf

Hello,

I have a report that has some text with Chinese characters. When I run the report those Chinese characters are displayed perfectly on the screen. However, when I export the report to pdf instead of the Chinese characters question marks (?) are displayed. Any ideas what can I do so that the Chinese characters are displayed when exported to pdf?

Thank you.

Hi eleanagb80, may I ask how did you get the chinese characters displayed perfectly on screen?

What setting do you have in your SQL and reporting services?

Thanks

|||

This question has come up before.

I am not sure what the pdf settings are (when they generate the file, I mean). So I have to ask: when you look in the document properties in Adobe reader, under the File menu, do you see the font mappings you expect?

Also, were the fonts you used in the report True Type, or not? Were they Unicode, or not?

One thing: when they display on your screen, characters are displaying in your browser and some additional good stuff is going on client-side.

When they display in a PDF, the fonts are either embedded when the file is generated on the server or fonts are indicated but not embedded, or a subset of the characters in the font can be embedded. I really don't know how the RS generation process decides to do it, and if it's a subset how they decide what the subset is. I haven't done any tests with this.

IAC... if the fonts are embedded, then a lot depends on what was available on the server versus what fonts or font-mappings are available on the client, which is what matters to the browser/HTML presentation.

I know I'm not giving you a solution, just trying to help you see why there can be difference.

>L<

Issue with exporting to pdf

Hello,

I have a report that has some text with Chinese characters. When I run the report those Chinese characters are displayed perfectly on the screen. However, when I export the report to pdf instead of the Chinese characters question marks (?) are displayed. Any ideas what can I do so that the Chinese characters are displayed when exported to pdf?

Thank you.

Hi eleanagb80, may I ask how did you get the chinese characters displayed perfectly on screen?

What setting do you have in your SQL and reporting services?

Thanks

|||

This question has come up before.

I am not sure what the pdf settings are (when they generate the file, I mean). So I have to ask: when you look in the document properties in Adobe reader, under the File menu, do you see the font mappings you expect?

Also, were the fonts you used in the report True Type, or not? Were they Unicode, or not?

One thing: when they display on your screen, characters are displaying in your browser and some additional good stuff is going on client-side.

When they display in a PDF, the fonts are either embedded when the file is generated on the server or fonts are indicated but not embedded, or a subset of the characters in the font can be embedded. I really don't know how the RS generation process decides to do it, and if it's a subset how they decide what the subset is. I haven't done any tests with this.

IAC... if the fonts are embedded, then a lot depends on what was available on the server versus what fonts or font-mappings are available on the client, which is what matters to the browser/HTML presentation.

I know I'm not giving you a solution, just trying to help you see why there can be difference.

>L<