FM12 has char format in xref been fixed?
Can anyone tell me if FM12 has fixed the problem in which character formats in source text are lost in cross-references to that source text? That one little fix would be a tipping point for me to upgrade to FM12. If not, has anyone found a better workaround than the one in the Frame archives that requires defining in maker.ini an entirely new version of the font for every font face that uses italics? Carol ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
Carol, You wrote: Can anyone tell me if FM12 has fixed the problem in which character formats in source text are lost in cross-references to that source text? That one little fix would be a tipping point for me to upgrade to FM12. If not, has anyone found a better workaround than the one in the Frame archives that requires defining in maker.ini an entirely new version of the font for every font face that uses italics? Behavior in FM12 is as in previous versions; this is probably by design and not something listed to be fixed/changed. As to a workaround: not necessarily feasible for your work, but if your character format uses a different font family, the italic/bold etc will be carried over. Shlomo Perets MicroType, http:// microtype.com http://%20microtype.com FrameMaker/Acrobat/Captivate training consulting * FM-to-Acrobat TimeSavers/Assistants Feb. 4 webinar: Effective PDF bookmarks with FM-to-Acrobat TimeSavers, https://www3.gotomeeting.com/register/691211894 Feb. 5 webinar: Authoring a fully-functional PDF form in FrameMaker, https://www3.gotomeeting.com/register/885499830 ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
Best practice for setting up character formats is to set everything As Is except the feature that you want the character tag to control. That would include setting the Font Family to As Is. So for Emphasis, for example, the font family would be set to As Is and only the Angle set to Italic. This enables the character tag to be applied to any text, regardless of its paragraph usage. I can apply Emphasis to text defined as Times Roman, Arial, etc., and the font is retained and only the Angle changed. For Adobe to ignore this in cross-references and require a unique Character tag for each different usage of a font family (e.g., Times Roman Emphasis, Arial Emphasis) is insane. Someone at Adobe, please look into this. Carol At 10:42 AM 2/4/2014, Shlomo Perets wrote: Carol, You wrote: Can anyone tell me if FM12 has fixed the problem in which character formats in source text are lost in cross-references to that source text? That one little fix would be a tipping point for me to upgrade to FM12. If not, has anyone found a better workaround than the one in the Frame archives that requires defining in maker.ini an entirely new version of the font for every font face that uses italics? Behavior in FM12 is as in previous versions; this is probably by design and not something listed to be fixed/changed. As to a workaround: not necessarily feasible for your work, but if your character format uses a different font family, the italic/bold etc will be carried over. Shlomo Perets MicroType, http://%20microtype.comhttp:// microtype.com FrameMaker/Acrobat/Captivate training consulting * FM-to-Acrobat TimeSavers/Assistants Feb. 4 webinar: Effective PDF bookmarks with FM-to-Acrobat TimeSavers, https://www3.gotomeeting.com/register/691211894 Feb. 5 webinar: Authoring a fully-functional PDF form in FrameMaker, https://www3.gotomeeting.com/register/885499830 ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Frame 9 Crash - Conditional Text Issues
I received a request for help from my counterparts at a sister company in Denmark. I know they are running unstructured Frame 9 but I don't know if it's all patched. At least one system is a 64 bit Windows 7 Pro machine. This is the gist of the description I was given - I've asked for further details. There's not a lot to go on, but if it sounds familiar to anyone, your suggestions would be appreciated. We had some serious problems highlighting text to make it conditional. Files crashed and are now corrupt. We can't do anything with conditional text in them anymore. Thanks, Alison Alison Craig | Technical Documentation Lead Ultrasonix | 130-4311 Viking Way | Richmond, BC V6V 2K9 | analogicultrasound.comhttp://www.analogicultrasound.com T 604-279-8550 ext 127 | F 604-279-8559 ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
At 11:56 -0700 4/2/14, Carol J. Elkins wrote: Best practice for setting up character formats is to set everything As Is except the feature that you want the character tag to control. That would include setting the Font Family to As Is. So for Emphasis, for example, the font family would be set to As Is and only the Angle set to Italic. This enables the character tag to be applied to any text, regardless of its paragraph usage. I can apply Emphasis to text defined as Times Roman, Arial, etc., and the font is retained and only the Angle changed. This is absolutely true, but not the problem you originally reported ;-) Referring to your original problem, in the ancient version of FrameMaker that I'm currently using (7), character tagging is indeed lost in xrefs. It may be intended behavior, or just an accidental side-effect of the power of FrameMaker's cross-reference formatting. As it's got xref builders that can themselves apply formatting, it can't honor any formatting in the source text. I.e, $paratext means just that - the text of the source paragraph, and only the text. The question would be, if FrameMaker *did* honor character formatting in the source of the xref, how would it combine that with formatting applied in the xref format definition? I can think of some clunky workarounds, but they're just that: clunky. One approach is clearly to avoid character formatting of the the xref source if possible. If you can't, then maybe break the xref source up using inlines so that you can 'restore' the required formatting in the xref format by building the xref in bits with the formatting you want? I.e. the source text would be something like ParaWithTextasInlineACharFormattedBitasInlineParaWithTextasInlineA, and your xref format(s) would be something like $paratext (to part A)Emphasis (for char formatted bit$paratext (to part B). But then all xrefs would actually be three xrefs, tripling your workload and adding maintenance issues. How you got about it all depends on the context. I would guess from your original post that you want to use $paratext and get the text *and* any character formatting applied to it. But FrameMaker doesn't work like that: you can't 'recover' character formatting from an xref source's text. I don't know about maker.ini fixes, as FrameMaker 7 for Mac doesn't use maker.ini. If all the above is nonsense, or completely off-base, I apologize: I'm trying to think in the midst of a gale that's trying to take the roof off. -- Steve [Trim e-mails: use less disk, use less power, use less planet] ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
At 14:08 -0600 4/2/14, Craig Ede wrote: The essence of the workaround that was described is based on the fact that font family changes are respected in xrefs (try formatting part of a line with WingDings, for instance). Thus the kludge that allows you to define a family that incorporates formatting like bold, or italics, or blue, or whatever by simply making it look like a different font family. (Disclaimer: I have never done this.) Ah... clever. There are good arguments (as the one you make) for ignoring such formatting as bold, ital and the like in an xref, but ignoring a ZapfDingbat or symbol font char format could be disastrous. Imagine a mu becoming an m within an xref. So FrameMaker is designed not to ignore that. The wonderful thing is that you can use that feature to accomplish (albeit with a bit of work) what is desired by the original poster. Never a day goes past without my learning something new about FrameMaker, even after more than 20 years of using it. Makes life interesting, I guess ;-) -- Steve ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
A slight correction to Steve's statement: $paratext means just that - the text of the source paragraph, and only the text. This is not true in all contexts. For example the $paratext building block in generated lists does honor any character formats applied within the paragraph text. In my opinion, what Carol is experiencing is an annoying, long-time FrameMaker bug. I think this is underscored by the fact that if the character format uses a different font family, the styling WILL be carried over. Unfortunately, from my experience, it is not Adobe's policy to fix long-standing bugs like this. Rick Rick Quatro Carmen Publishing Inc. 585-366-4017 r...@frameexpert.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
Thanks, Steve. My struggle right now is with cross-references to paragraphs that, in addition to regular text, house hypertext links formatted with a Character tag that makes the text blue; and cross-references that house an italicized citation to a book. The character-formatted text in those cross-refs lose their character formatting. I use cross-references because I want to single-source the source text. I can't avoid character formatting in these instances. And as you stated, breaking one cross-ref into three separate cross-refs to access the text before and after the character-formatted text is impractical. Just as I can import text insets and retain their formatting, I would hope that eventually Adobe will give me the option to use cross-refs while retaining the source formatting. Call it a feature enhancement. Carol At 12:54 PM 2/4/2014, you wrote: At 11:56 -0700 4/2/14, Carol J. Elkins wrote: Best practice for setting up character formats is to set everything As Is except the feature that you want the character tag to control. That would include setting the Font Family to As Is. So for Emphasis, for example, the font family would be set to As Is and only the Angle set to Italic. This enables the character tag to be applied to any text, regardless of its paragraph usage. I can apply Emphasis to text defined as Times Roman, Arial, etc., and the font is retained and only the Angle changed. This is absolutely true, but not the problem you originally reported ;-) Referring to your original problem, in the ancient version of FrameMaker that I'm currently using (7), character tagging is indeed lost in xrefs. It may be intended behavior, or just an accidental side-effect of the power of FrameMaker's cross-reference formatting. As it's got xref builders that can themselves apply formatting, it can't honor any formatting in the source text. I.e, $paratext means just that - the text of the source paragraph, and only the text. The question would be, if FrameMaker *did* honor character formatting in the source of the xref, how would it combine that with formatting applied in the xref format definition? I can think of some clunky workarounds, but they're just that: clunky. One approach is clearly to avoid character formatting of the the xref source if possible. If you can't, then maybe break the xref source up using inlines so that you can 'restore' the required formatting in the xref format by building the xref in bits with the formatting you want? I.e. the source text would be something like ParaWithTextasInlineACharFormattedBitasInlineParaWithTextasInlineA, and your xref format(s) would be something like $paratext (to part A)Emphasis (for char formatted bit$paratext (to part B). But then all xrefs would actually be three xrefs, tripling your workload and adding maintenance issues. How you got about it all depends on the context. I would guess from your original post that you want to use $paratext and get the text *and* any character formatting applied to it. But FrameMaker doesn't work like that: you can't 'recover' character formatting from an xref source's text. I don't know about maker.ini fixes, as FrameMaker 7 for Mac doesn't use maker.ini. If all the above is nonsense, or completely off-base, I apologize: I'm trying to think in the midst of a gale that's trying to take the roof off. -- Steve [Trim e-mails: use less disk, use less power, use less planet] ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FM12 has char format in xref been fixed?
Thanks, Steve. My struggle right now is with cross-references to paragraphs that, in addition to regular text, house hypertext links formatted with a Character tag that makes the text blue; and cross-references that house an italicized citation to a book. The character-formatted text in those cross-refs lose their character formatting. I use cross-references because I want to single-source the source text. I can't avoid character formatting in these instances. And as you stated, breaking one cross-ref into three separate cross-refs to access the text before and after the character-formatted text is impractical. Just as I can import text insets and retain their formatting, I would hope that eventually Adobe will give me the option to use cross-refs while retaining the source formatting. Call it a feature enhancement. Carol At 12:54 PM 2/4/2014, you wrote: This is absolutely true, but not the problem you originally reported ;-) Referring to your original problem, in the ancient version of FrameMaker that I'm currently using (7), character tagging is indeed lost in xrefs. It may be intended behavior, or just an accidental side-effect of the power of FrameMaker's cross-reference formatting. As it's got xref builders that can themselves apply formatting, it can't honor any formatting in the source text. I.e, $paratext means just that - the text of the source paragraph, and only the text. The question would be, if FrameMaker *did* honor character formatting in the source of the xref, how would it combine that with formatting applied in the xref format definition? ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
