aaron.kempf@gmail.com wrote:
> yeah.. it looks like reporting services only supports the ASCII / ANSI
> character set..
>
> I wonder how the people in China do it?
>
> -Aaron
>
>
>
> punjab_tom@hotmail.com wrote:
> > my friend Hari told me that Reporting Services only supports the Ascii
> > character set.. is this true?
> >
> > -Tom
> >
> >
> >
> >
> > aaron.kempf@gmail.com wrote:
> > > anyone?
> > >
> > > does anyone else have reports that have this at top?
> > > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> > > or does everyone else have
> > > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> > >
> > > you see this is the piece that's a buch of crap; microsoft is blocking
> > > my posts.. just because I speak the truth.
> > >
> > > Piece of shit ass company supports CENSORSHIP-- not in China-- but he=
re
> > > in their own backyard
> > >
> > > -Aaron
> > >
> > >
> > >
> > >
> > > aaron.kempf@gmail.com wrote:
> > > > Hey we've been building some reports.. occassionally the build / ch=
ange
> > > > team complains when we use 'special characters' in our reports..
> > > >
> > > > I opened up our RDLs; and I noted that we have this as the first li=
ne
> > > > <?xml version=3D"1.0" encoding=3D"utf-8"?>
> > > >
> > > >
> > > > I was thinking that we might need to change to 16 in order to allow
> > > > 'special characters'
> > > >
> > > > <?xml version=3D"1.0" encoding=3D"utf-16"?>
> > > >
> > > > In other words; we are using SSRS 2005 in order to 'print letters' =
for
> > > > mass-mailing.. and we have some letters that people are printing ou=
t=2E
> > > >
> > > > We just want to be able to use a simple character for a box-- as in=
a
> > > > simple checkbox-- that they can print off; fill out.. and snailmail
> > > > back in
> > > >
> > > >
> > > > I just have this gut feeling that I'm going to break our build proc=
ess
> > > > if I send in a special character.. because 70% of our breaks have b=
een
> > > > the result of special characters so far.
> > > >
> > > > So am I limited to the ASCII set? Can I use Unicode characters?
> > > > So I need to set the UTF8 flag at the top of our reports to UTF16?
> > > >
> > > > Thanks
> > > >=20
> > > >=20
> > > > -Aaron
> > > >=20
> > > > =E2=80=AB