Click to See Complete Forum and Search --> : Superscripts not Superrules
dh@uc
12-19-2007, 03:30 PM
I am in the Pharmaceutical industry. We have switched from QXP to ID. Developing product information requires underlined words in sentences and or paragraphs. However, some words have superscrcipt characters. When I turn on the underline feature for a word that has a superscript "® " the underline jumps up to the superscript character. The only other option that I am aware of is a paragraph rule. Problem with this is the rule runs the full legnth of the text box or column. Any suggestions on how to avoid this problem and underline particualr words that inlcude superscripts?
CkretAjint
12-19-2007, 03:34 PM
You shouldn't be using the font style commands (P, B, U, I), they don't always go through the RIP correctly and cause more issues then they are worth.
If you choose to ignore the above statement, just select the beginning portion of the word and use your underline then. Should solve your issue at hand, just make sure the ® isn't selected.
Two-Toe Tom
12-19-2007, 03:49 PM
here's a workaround: make your own character style for underlined superscripts where you have a smaller pt size, raise the vertical height, and, under 'underline options' offset the underline to the appropriate amount
urstwile
12-20-2007, 04:45 AM
You shouldn't be using the font style commands (P, B, U, I), they don't always go through the RIP correctly and cause more issues then they are worth.
If you choose to ignore the above statement, just select the beginning portion of the word and use your underline then. Should solve your issue at hand, just make sure the ® isn't selected.
I don't think that InDesign deals with underlines the same way as Quark did, Ckret. You can set underline style options in InDesign, I believe that by default, Quark used a styled font solution, and you could get around that with plug-ins, but InDesign seems to go outside using a styled font solution and allows you to set things like rule offset and weight.
In terms of the original poster's question, I think Tom's solution is probably the most workable.