I have read information on showing special characters on reports but I couldn't find an example where the text that contains the special character originates from DB2.

We have text that is housed in DB2 that we query for and show on our HTML or PDF output. How do we code the registered trademark symbol and the copyright symbol within our DB2 table so that it is translated properly on both HTML and PDF output?

This message has been edited. Last edited by: Stacie Stone,

You need to set correct code page for DB so that it accepts special characters. Other option is to encode special characters while inserting into DB and decode it while reading from WebFOCUS. But this will be costly this decode needs to be performed for each record.

Thanks,
Ram

Stacie, for html output, the code for copyright and for registration mark

 
&|copy; &|reg;

note the pipe after the ampersand, that's the escape character that tells focus that this is not a dialogue manager variable.
For PDF, this wont work; the only thing i can suggest is take a screen shot of the two, make images.
pita, i know, but it will work.

I think that © and ® are standard characters in most fonts.

Hex, A9 or 169 is ©
Hex, AE or 174 is ®

You can enter these via the keyboard with alt+nnnn.

So alt+0169 give you © and alt+0174 gives you ®

From the WebFOCUS side, once you have the data in your database, as long as you use the correct code pages in WebFOCUS these characters will be visible in all outputs. Use 137 not 437 on the server and 137 on the client.

With WF 8, you can display superscripts (copyright symbol) on Report Data, Heading, and Footing Lines.

The following code will display the copyright symbol.
SUPCOPY/A20= '^{'||HEXBYT(169,'A2')||'}';

Note: In the StyleSheet, every component that will display a superscript has the attribute
MARKUP=ON.

Looking into the WF-8 documentation will help you better.

If the data is coming from the database, unless you have the correct code page on the reporting server, special characters will not display correctly.

We ended up reporting a case with IBI for help with this due to our code page set-up. Will post again when we have a resolution. Thanks everyone for your input to my question!

Worked with IBI for resolution. Updated our Client Code Page from 437 to 137. Thanks again to everyone for your input! ~Stacie