[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Deborah Snavely <dsnavely@xxxxxxxxxxx>
Subject: Re[2]: variables for a product name
From: Dennis Hays <dhays@xxxxxxxxxxxxxx>
Date: Thu, 31 Aug 2000 18:41:52 -0400
CC: "'framers@xxxxxxxxx'" <framers@xxxxxxxxx>
In-reply-To: <62A0D4874D47F646A7D69A00BB6A61E0455C34@POSTAL.aurigin.com>
Organization: Dennis Hays Information Design
References: <62A0D4874D47F646A7D69A00BB6A61E0455C34@POSTAL.aurigin.com>
Reply-To: Dennis Hays <dhays@xxxxxxxxxxxxxx>
Sender: owner-framers@xxxxxxxxx
Thursday, August 31, 2000, 6:33 PM Deborah, I hope I'm understanding you correctly. If WIDGET is all uppercase and 2000 is small caps size, then first create a character format in the same font family and style, but make certain you have the "small cap" checkbox enabled on the right side. Next go into Special|Variable and create a user variable. Assuming WIDGET is in the default font, Type the variable name and in the definition box type WIDGET and select the character format you created in the previous step(from the character format box), then type 2000 and finally select Default Font from the box on the lower right. One last item. You can vary the small cap proportion to the regular typeface by going into Format|Document|Text Options (in v. 5.5.6) and change the percentage. That should do it. Please let me know if this is what you wanted. Dennis < - - - Original message was - - - - > On Thursday, August 31, 2000, at 5:53 PM, you said: > Tom Regner asked: > Marketing Communications (MarComm) has laid down the edict > that the product name will have the alpha portion (WIDGET) in > full caps, and the numeric portion (2000) is to appear smaller > (smallcaps size). The product name is entered as a variable in > Frame, but we can't find any way to produce the desired result > using the variable dialog box, nor will the changes "take" any > other way we go about it. I was hoping that this limitation would > be fixed in version 6.0, but apparently it is not. > Possibilities that I can think of: > 1 use two variables with no space between, one upper case and one small > caps > 2 use a text inset from a tiny file instead of a variable (you can update > once to fix all instances without even importing variables!) > 3 use an x-ref to a file parked at the end of the book file (useful trick > for stashing various book-building FM files such as LORs to graphics and > fonts, keeping text-inset files associated with the project, etc.) > 4 create a text example on a reference page and copy and paste > (non-automated but portable) > Deborah Snavely, Senior Technical Writer, Aurigin Systems, Inc. > ** To unsubscribe, send a message to majordomo@omsys.com ** > ** with "unsubscribe framers" (no quotes) in the body. ** < - - - - - End Original message - - - > Regards, Dennis Dennis Hays Information Design http://www.haysdesign.com mailto:dhays@haysdesign.com ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **