[Framers] Framers Digest, Vol 163, Issue 9
Philo Calhoun
island at luxsci.me
Wed Oct 30 13:34:09 PDT 2019
Re CSS code jockey:
I switched most of my documents from structured Framemaker to Flare after encountering problems with Framemaker exports to web and ebook formats. But even with Flare, editing of CSS is cumbersome. I now do all edits in Adobe Brackets. It is much easier to fix and organize.
Sent from my iPhone
> On Oct 30, 2019, at 1:02 PM, framers-request at lists.frameusers.com wrote:
>
> Send Framers mailing list submissions to framers at lists.frameusers.com
> To subscribe or unsubscribe, visit
> http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com You
> can reach the person managing the list at
> framers-owner at lists.frameusers.com When replying, please edit your
> Subject line so it is more specific than "Re: Contents of Framers
> digest..."
>
> Today's Topics:
>
> 1. OT: CSS Code Jockey? (tammyvb at spectrumwritingllc.com)
> 2. Structure Emphasis and Xref elements break lines (cuc tu)
> 3. Re: Structure Emphasis and Xref elements break lines
> (Lynne A. Price)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 Oct 2019 11:04:12 -0600
> From: <tammyvb at spectrumwritingllc.com>
> To: <framers at lists.frameusers.com>
> Subject: [Framers] OT: CSS Code Jockey?
> Message-ID: <000001d58f44$0e0e1650$2a2a42f0$@spectrumwritingllc.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hey All,
>
>
>
> I am stuck in RoboH*ll using RH 2019's not even remotely for primetime tool
> to develop OLH for a client. (It is a client-mandated tool and I do NOT have
> an option to switch!) I desperately need a CSS code jockey to assist me in
> modifying the CSS for this project - it's an absolute nightmare between
> having to use an inherited CSS as well as Adobe thinking that they are
> "helping" you by automatically sticking in CSS where they think it's
> appropriate based on manual edits that I am making and not being able to
> make this tool NOT do this blasted automatic coding.
>
>
>
> I know that this is the FM list, but hopefully, that means there are some RH
> users on this list as well that might be able to point me to a resource.
>
>
>
> TIA!!
>
>
>
> Tammy Van Boening
>
> Tammy dot vanboening at spectrumwritingllc dot com
>
> www.spectrumwritingllc.com
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 30 Oct 2019 17:16:33 +0000
> From: cuc tu <cuc2u at hotmail.com>
> To: "framers at lists.frameusers.com" <framers at lists.frameusers.com>
> Subject: [Framers] Structure Emphasis and Xref elements break lines
> Message-ID:
> <BYAPR05MB49984411A0EF3D622D85DE84FD600 at BYAPR05MB4998.namprd05.prod.outlook.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Howdy Framers,
>
> I have emphasis and xref elements defined as containers without any formatting. They break the line as a new paragraph, so how do I get them to be inline? I thought of having them use an inline heading paragraph format, but the emphasis styling is applied as an attribute so I would not see a difference between bold and italic. That might be OK as I'm not really interested in a fully formatted document, just something easier to edit. I send XML output as the deliverable.
>
> Also, how do changes to the EDD and template get applied to an existing structured fm file? For example, I changed the EDD <step> element to use a numbered paragraph format, but that seemed to have no affect. My FM doc does not ask for a structured app, but it seems to follow the one I've applied.
>
> Thanks,
> C2
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 30 Oct 2019 11:48:59 -0700
> From: "Lynne A. Price" <lprice at txstruct.com>
> To: framers at lists.frameusers.com
> Subject: Re: [Framers] Structure Emphasis and Xref elements break
> lines
> Message-ID: <65dc6338-3849-61f8-663d-619360daea5e at txstruct.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
>> On 10/30/2019 10:16 AM, cuc tu wrote:
>> Howdy Framers,
>>
>> I have emphasis and xref elements defined as containers without any formatting. They break the line as a new paragraph, so how do I get them to be inline? I thought of having them use an inline heading paragraph format, but the emphasis styling is applied as an attribute so I would not see a difference between bold and italic.
>
> C2,
> ??? Use a TextRangeFormatting element in a text format rule to specify
> that a container is a text range in the current paragraph. You can
> specify individual font properties or apply a character format within
> such a rule. And you can format the element based on an attribute. You
> might want to use something like:
>
> 1.? If context is: [emphasis="bold"]
> ????????? Text range.
> ????????? Font properties
> ????????????? Weight: Bold
> ???? Else, if context is [emphasis="italic"]
> ?????????? Text range
> ?????????? Font properties
> ?????????????? Angle: Italic
>
> which has the structure:
>
> <ContextRule>
> ??? <If>
> <Specification>[emphasis="bold"]</Specification>
> ?????????????? <TextRangeFormatting>
> ????????????????????? <TextRange/>
> ????????????????????? <PropertiesFont>
> ?????????????????????????? <Weight>
> ??????????????????????????????? <Bold/>
> ?????????????????????????? </Weight>
> ????????????????????? </PropertiesFont>
> ??????????????? </TextRangeFormatting>
> ? ? </If>
> ??? <ElseIf>
> <Specification>[emphasis="italic"]</Specification>
> ?????????????? <TextRangeFormatting>
> ????????????????????? <TextRange/>
> ????????????????????? <PropertiesFont>
> ?????????????????????????? <Angle>
> ??????????????????????????????? <Italic/>
> ?????????????????????????? </Angle>
> ????????????????????? </PropertiesFont>
> ??????????????? </TextRangeFormatting>
> </ContextRule></TextFormatRules></Container></Element>
>> Also, how do changes to the EDD and template get applied to an existing structured fm file? For example, I changed the EDD <step> element to use a numbered paragraph format, but that seemed to have no affect. My FM doc does not ask for a structured app, but it seems to follow the one I've applied.
>>
> Open the EDD, template, and structured document. If you have not already
> done so, make the template the current document and use File > Import >?
> Element Definitions to update the template to use the element
> definitions defined in the EDD. Save the template. Then switch to the
> structured document. Use File > Import > Formats to import all formats
> into the structured document. Next, use File > Import > Element
> Definitions to import the element definitions from the template into the
> structured document. Make sure to check the box to remove format overrides.
>
> Note 1: You could import element definitions from the EDD, but then FM
> would display any relevant warning messages again.
>
> Note 2: You can import templates before importing element definitions,
> but then any assignment of paragraph or character properties made in the
> EDD will be lost. You can always remove such overrides by importing
> element definitions from the current document and checking the box to
> remove overrides.
>
> ??? --Lynne
>
> --
> Lynne A. Price
> Text Structure Consulting, Inc.
> Specializing in structured FrameMaker consulting, application development, and training
> lprice at txstruct.com http://www.txstruct.com
> voice/fax: (510) 583-1505 cell phone: (510) 421-2284
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
>
> This daily digest is from the Framers mailing list
>
> Send messages to framers at lists.frameusers.com
> Visit the list's homepage at http://www.frameusers.com
> Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
> Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
> Send administrative questions to listadmin at frameusers.com
>
> ------------------------------
>
> End of Framers Digest, Vol 163, Issue 9
> ***************************************
>
More information about the Framers
mailing list