bug? DeviceInfo ColorDepth ignored for TIFF image

Hello!
I have a problem generating report (format = IMAGE) using following
DeviceInfo settings:
<DeviceInfo>
<ColorDepth>1</ColorDepth>
<OutputFormat>TIFF</OutputFormat>
</DeviceInfo>
Using this settings, generated report (TIFF) always has 24 bit color
depth which is default value, and I wanted to generate black & white
report (1 bit)
Documentation states that ColorDepth could be changed only for TIFF,
but it is not true, it always applies the default value and ignores
user settings ?!
Is this a bug in reporting server?
Any ideas on how to generate TIFF 1-bit with Reporting Server are
welcome...
Thanks,
JohnYour observation is correct and yes, this is a known bug. I have passed your
comments along to the appropriate parties.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Smith" <ng950@.yahoo.com> wrote in message
news:de84550e.0408200420.287ad689@.posting.google.com...
> Hello!
> I have a problem generating report (format = IMAGE) using following
> DeviceInfo settings:
> <DeviceInfo>
> <ColorDepth>1</ColorDepth>
> <OutputFormat>TIFF</OutputFormat>
> </DeviceInfo>
> Using this settings, generated report (TIFF) always has 24 bit color
> depth which is default value, and I wanted to generate black & white
> report (1 bit)
> Documentation states that ColorDepth could be changed only for TIFF,
> but it is not true, it always applies the default value and ignores
> user settings ?!
> Is this a bug in reporting server?
> Any ideas on how to generate TIFF 1-bit with Reporting Server are
> welcome...
> Thanks,
> John

BUG: Leading Spaces in PDF stripped

Hello
We are currently generating reports in PDF format and leading spaces are now
being stripped from printed reports. This started to happen when when we
applied SP2. Has anyone else encountered this problem and if so how did you
get around it.
Much appreciated,
Kevin Weir
DirectWest PublishersI'm a little surprised no one has had a similar problem. Leading spaces are
definetly stripped from ALL strings when rendering to PDF. This started to
happen after SP2 was installed.
If someone from Microsoft sees this post are you aware this is an actual bug.
Regards
Kevin Weir
DirectWest Publishers
"Kevin Weir" wrote:
> Hello
> We are currently generating reports in PDF format and leading spaces are now
> being stripped from printed reports. This started to happen when when we
> applied SP2. Has anyone else encountered this problem and if so how did you
> get around it.
> Much appreciated,
> Kevin Weir
> DirectWest Publishers
>|||Kevin,
I have experienced the same thing, I posted a few oddities after applying
SP2 and I have not received any help. Unfortunatley I don't have a
workaround for this one except to redesign. This is very aggravating as I
had to go in to a number of reports to fix once this SP was applied. It was
the only way I could combine bold font with normal and now that does not work
either.
I will continue my search, if I found I will update this post, please do the
same.
"Kevin Weir" wrote:
> Hello
> We are currently generating reports in PDF format and leading spaces are now
> being stripped from printed reports. This started to happen when when we
> applied SP2. Has anyone else encountered this problem and if so how did you
> get around it.
> Much appreciated,
> Kevin Weir
> DirectWest Publishers
>|||Hello
I will certainly let you know if I find a solution.
Now if I could just find link/e-mail address where I could let Microsoft
know about this bug.
"DigitalVixen" wrote:
> Kevin,
> I have experienced the same thing, I posted a few oddities after applying
> SP2 and I have not received any help. Unfortunatley I don't have a
> workaround for this one except to redesign. This is very aggravating as I
> had to go in to a number of reports to fix once this SP was applied. It was
> the only way I could combine bold font with normal and now that does not work
> either.
> I will continue my search, if I found I will update this post, please do the
> same.
> "Kevin Weir" wrote:
> > Hello
> >
> > We are currently generating reports in PDF format and leading spaces are now
> > being stripped from printed reports. This started to happen when when we
> > applied SP2. Has anyone else encountered this problem and if so how did you
> > get around it.
> >
> > Much appreciated,
> >
> > Kevin Weir
> > DirectWest Publishers
> >

Bug using FOR XML AUTO with columns with type char(1)

Hello,
Having some problems with generating xml with "FOR XML AUTO". Rows with
a column with a value char(0) seems to terminate the row!
Try to run the following:
SELECT
*
FROM (
SELECT
1 AS orderItemId,
1 AS orderId,
CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
UNION
SELECT
2 AS orderItemId,
1 AS orderId,
CHAR(49) AS orderItemStatus
) AS orderItem
FOR XML AUTO
Generates:
<orderItem orderItemId="1" orderId="1" orderItemStatus="
Should be(?):
<orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
orderItemId="2" orderId="1" orderItemStatus="1"/>
Anyone seen this before?
Regards, Nils
CHAR(0) is not a valid XML character. In FOR XML, we do not detect invalid
characters for performance reasons, so you will pass the XML anyway.
Depending on what the client code uses to read the XML, it may see the
CHAR(0) and decide that it is the end of the string (for instance, if the
client code uses the standard C/C++ string types).
So the recommendation is: Do not generate XML containing invalid characters
such as CHAR(0) since they are not supported by compliant XML parsers and
may result in other unforeseen behaviour.
Best regards
Michael
<nilsflemstrom@.gmail.com> wrote in message
news:1125047051.277443.138730@.z14g2000cwz.googlegr oups.com...
> Hello,
> Having some problems with generating xml with "FOR XML AUTO". Rows with
> a column with a value char(0) seems to terminate the row!
> Try to run the following:
> SELECT
> *
> FROM (
> SELECT
> 1 AS orderItemId,
> 1 AS orderId,
> CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
> UNION
> SELECT
> 2 AS orderItemId,
> 1 AS orderId,
> CHAR(49) AS orderItemStatus
> ) AS orderItem
> FOR XML AUTO
> Generates:
> <orderItem orderItemId="1" orderId="1" orderItemStatus="
> Should be(?):
> <orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
> orderItemId="2" orderId="1" orderItemStatus="1"/>
> Anyone seen this before?
> Regards, Nils
>

Bug using FOR XML AUTO with columns with type char(1)

Hello,
Having some problems with generating xml with "FOR XML AUTO". Rows with
a column with a value char(0) seems to terminate the row!
Try to run the following:
SELECT
*
FROM (
SELECT
1 AS orderItemId,
1 AS orderId,
CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
UNION
SELECT
2 AS orderItemId,
1 AS orderId,
CHAR(49) AS orderItemStatus
) AS orderItem
FOR XML AUTO
Generates:
<orderItem orderItemId="1" orderId="1" orderItemStatus="
Should be(?):
<orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
orderItemId="2" orderId="1" orderItemStatus="1"/>
Anyone seen this before?
Regards, NilsCHAR(0) is not a valid XML character. In FOR XML, we do not detect invalid
characters for performance reasons, so you will pass the XML anyway.
Depending on what the client code uses to read the XML, it may see the
CHAR(0) and decide that it is the end of the string (for instance, if the
client code uses the standard C/C++ string types).
So the recommendation is: Do not generate XML containing invalid characters
such as CHAR(0) since they are not supported by compliant XML parsers and
may result in other unforeseen behaviour.
Best regards
Michael
<nilsflemstrom@.gmail.com> wrote in message
news:1125047051.277443.138730@.z14g2000cwz.googlegroups.com...
> Hello,
> Having some problems with generating xml with "FOR XML AUTO". Rows with
> a column with a value char(0) seems to terminate the row!
> Try to run the following:
> SELECT
> *
> FROM (
> SELECT
> 1 AS orderItemId,
> 1 AS orderId,
> CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
> UNION
> SELECT
> 2 AS orderItemId,
> 1 AS orderId,
> CHAR(49) AS orderItemStatus
> ) AS orderItem
> FOR XML AUTO
> Generates:
> <orderItem orderItemId="1" orderId="1" orderItemStatus="
> Should be(?):
> <orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
> orderItemId="2" orderId="1" orderItemStatus="1"/>
> Anyone seen this before?
> Regards, Nils
>