Re: [Framers] Learning Structure and Prefix (and more)

[cuc tu]

Thanks for that, Rick.


I suppose that could work. I think it means I would need to create new para 
formats for each description element to house the 'numbering' text (the 
headings are short, such as "Description:", Settings:" etc.). This seems about 
as effective as using an inline text insert and text range formatting. Either 
of the two can almost accomplish what I want, which is a side-head alignment 
effect using RunInHeading, right justified, and the indented body is left 
justified with a large left margin.


With inline text (or numbering?), I thought I could use a tab with decimal (:) 
alignment and mimic the side-head effect, but that did not format as desired so 
I used a tab and first/second indents. I also use ePublisher  to produce HTML 
and tabs get replaced with spaces, so there is no alignment there. Maybe I 
don't know enough about ePublisher to fix that?


I'm not sure if it would be better to ask the engineers to add the heading text 
in a generic subhead element, a unique element for each heading text, or to 
make the description element just a container by wrapping the text range in a 
generic para element.


What would any of you do?

Thanks
C2

--

Message: 6
Date: Wed, 5 Sep 2018 08:40:26 -0400
From: "Rick Quatro" 
To: "'An email list for people using Adobe FrameMaker software.'"
    
Subject: Re: [Framers] Learning Structure and Prefix (and more)
Message-ID: <001801d44515$9fb50f20$df1f2d60$@rickquatro.com>
Content-Type: text/plain;   charset="us-ascii"

Hi C2,

Can you use an autonumber instead of a prefix?

Rick

Rick Quatro
Carmen Publishing Inc.
r...@frameexpert.com
585-729-6746 NEW!



-Original Message-
From: Framers  On
Behalf Of cuc tu
Sent: Tuesday, September 04, 2018 8:01 PM
To: framers@lists.frameusers.com
Subject: Re: [Framers] Learning Structure and Prefix (and more)

Howdy Framers,

I'm still trying to get heading paragraphs inserted by my EDD when opening
xml content. I guess I must ask if this is even possible with the xml
example below? For example, the XML description elements need to have a
heading run-in para with the heading text inserted.


Model 1
Spa description1
Spa description2
Spa description3


Formatted should look like:

Model 1
Heading1: Spa description1
Heading2: Spa description2
Heading3: Spa description3

___

This message is from the Framers mailing list

Send messages to framers@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 listad...@frameusers.com

Re: [Framers] Learning Structure and Prefix (and more)

[Rick Quatro]

Hi C2,

Can you use an autonumber instead of a prefix?

Rick

Rick Quatro
Carmen Publishing Inc.
r...@frameexpert.com
585-729-6746 NEW!



-Original Message-
From: Framers  On
Behalf Of cuc tu
Sent: Tuesday, September 04, 2018 8:01 PM
To: framers@lists.frameusers.com
Subject: Re: [Framers] Learning Structure and Prefix (and more)

Howdy Framers,

I'm still trying to get heading paragraphs inserted by my EDD when opening
xml content. I guess I must ask if this is even possible with the xml
example below? For example, the XML description elements need to have a
heading run-in para with the heading text inserted.


Model 1
Spa description1
Spa description2
Spa description3


Formatted should look like:

Model 1
Heading1: Spa description1
Heading2: Spa description2
Heading3: Spa description3


After reading: https://forums.adobe.com/thread/315301 , it seems to not be
possible (the engineers will be displeased), but then I got the idea to use
autoinsertions. I created a para element and that is referenced as a child
insert in each description element.

It does not work when opening the XML file, but it works fine if I manually
add the elements and content from Frame. I did not test that on all the
other approaches I tried since I am not able to edit the xml files, but at
least I got to see some things I tried may actually be correct.

I tried a myriad of different prefixs, such as in the spa element, defining
a prefix with the description elements as the context. The context rules
work for formatting, but I could not get the prefix to show. I tried it in
the para element, and as noted before in the description elements. I can get
the prefix and formatted the way I want, but the description content is
always part of the same paragraph, so it's just an in-line text insert.

As far as structure, if the above is not possible, Would it make sense to
just tell the engineers to wrap the description text in another para
element? With that, I get the prefixes the way I want by adding them to the
description elements.

Thanks
C2
___

This message is from the Framers mailing list

Send messages to framers@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 listad...@frameusers.com

___

This message is from the Framers mailing list

Send messages to framers@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 listad...@frameusers.com

Re: [Framers] Learning Structure and Prefix (and more)

[cuc tu]

Howdy Framers,

I'm still trying to get heading paragraphs inserted by my EDD when opening xml 
content. I guess I must ask if this is even possible with the xml example 
below? For example, the XML description elements need to have a heading run-in 
para with the heading text inserted.


Model 1
Spa description1
Spa description2
Spa description3


Formatted should look like:

Model 1
Heading1: Spa description1
Heading2: Spa description2
Heading3: Spa description3


After reading: https://forums.adobe.com/thread/315301 , it seems to not be 
possible (the engineers will be displeased), but then I got the idea to use 
autoinsertions. I created a para element and that is referenced as a child 
insert in each description element.

It does not work when opening the XML file, but it works fine if I manually add 
the elements and content from Frame. I did not test that on all the other 
approaches I tried since I am not able to edit the xml files, but at least I 
got to see some things I tried may actually be correct.

I tried a myriad of different prefixs, such as in the spa element, defining a 
prefix with the description elements as the context. The context rules work for 
formatting, but I could not get the prefix to show. I tried it in the para 
element, and as noted before in the description elements. I can get the prefix 
and formatted the way I want, but the description content is always part of the 
same paragraph, so it's just an in-line text insert.

As far as structure, if the above is not possible, Would it make sense to just 
tell the engineers to wrap the description text in another para element? With 
that, I get the prefixes the way I want by adding them to the description 
elements.

Thanks
C2
___

This message is from the Framers mailing list

Send messages to framers@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 listad...@frameusers.com

Re: [Framers] Learning Structure and Prefix (and more)

[cuc tu]

Reading the dev guide again, it occurred to me that the prefix rules needed to 
be in a parent element, so I tried:


Element (Container): SYSTEM
General rule: (|Description1|Description2)*
Prefix rules
If context is: SYSTEM
Prefix: SYSTEM Heading
Else, if context is: Description1
Prefix: Desc1 Heading
Else, if context is: Description2
Prefix: Desc2 Heading
Text format rules
If context is: SYSTEM
Use paragraph format: ChapterHeading
Else, if context is: Description1
Use paragraph format: Heading4
Else, if context is: Description2
Use paragraph format: Heading4


Same for the SPA element, and that removed every prefix.

C2

From: cuc tu 
Sent: Wednesday, August 29, 2018 10:34 AM
To: framers@lists.frameusers.com
Subject: Re: Learning Structure and Prefix (and more)


Hi All,


I had replied to the board and forgot to change the subject line, so this is 
continuing that topic. The short question is, how can I get the Subheading 
element's prefix text to appear as a full paragraph before the Description 
element's text?

I've build a small sample for this discussion and was trying to get a full 
paragraph heading inserted before the contents of a text element, based off the 
parent elements name. Also, it took quite a while to figure out how to make a 
mixed content model not throw errors, and I still really do not understand how 
else that sequence could be structured.

The SYSTEM and SPA elements insert the prefix text. However, I would think the 
structure should be: (,Description1&,Description2&)*
I don't understand the need for the wrapper and termination, but that's what I 
found by trial and error. Separating the elements this way does not work. In 
the end, there will be many optional "Description" elements and they will have 
mixed order.

Description1 and Description2 do not insert the Subheading prefix text. 
Further, it seems I would need to have the Subheading element before the  
element, since Subheading needs to be inserted before the Description element's 
text (or data).

Below are the EDD and xml source data, which all validates and could be usable, 
except for the missing prefix Subheading.


EDD Version is 12.0
Automatically create formats on import.
Element (Container): File
Valid as the highest-level element.
General rule: File_Title, (SYSTEM?,SPA?)
Element (Container): File_Title
General rule: 
Text format rules
In all contexts.
Use paragraph format: Title
Element (Container): SYSTEM
General rule: (|Description1|Description2)*
Prefix rules
In all contexts.
Prefix: SYSTEM Heading
Text format rules
In all contexts.
Use paragraph format: ChapterHeading
Element (Container): SPA
General rule: (|Description1|Description2)*
Prefix rules
In all contexts.
Prefix: SPA Heading
Text format rules
In all contexts.
Use paragraph format: ChapterHeading
Element (Container): Description1
General rule: (|Subheading)*
Text format rules
In all contexts.
Use paragraph format: Indented4
Element (Container): Description2
General rule: (|Subheading)*
Text format rules
In all contexts.
Use paragraph format: Indented4
Element (Container): Subheading
General rule: 
Prefix rules
If context is: Description1
Prefix: Insert Description1
Else, if context is:
Prefix: Insert Description2
Text format rules
In all contexts.
Use paragraph format: Heading4







File Title

SYSTEM description1
SYSTEM description2


SPA description1
SPA description2




Thanks
C2


From: Framers  on 
behalf of framers-requ...@lists.frameusers.com 

Sent: Tuesday, August 28, 2018 1:02 PM
To: framers@lists.frameusers.com
Subject: Framers Digest, Vol 149, Issue 21

Send Framers mailing list submissions to framers@lists.frameusers.com
To subscribe or unsubscribe, visit
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com You
Framers Info Page - Adobe 
FrameMaker
lists.frameusers.com
About the Framers email list. The purpose of this list is to share information 
about using Adobe Framemaker. We welcome experienced users, newcomers, and 
people simply wanting to know more about the software.



can reach the person managing the list at
framers-ow...@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. Re:  FM 2017 Columns and Continued Lines (Wim Hooghwinkel - idtp)
   2.  FM2019 Doesn't Print to PDF (Corcoran, Susan)
   3. Re:  Framers Digest, Vol 149, Issue 20 (cuc tu)
   4.  Kudos for Adobe Support (Lea Rush)
   5. Re:  Framers Digest, Vol 149, Issue 20 (Roger Shuttleworth)


--

Message: 1
Date: Mon, 27 Aug 2018 22:24:51 +0200
From: Wim Hooghwinkel - idtp 
To: framers@lists.frameusers.com
Cc: julie.sigr...@airbornemx.com
Subject: Re: [Framers] FM 2017 Columns and Continued Lines
Message-ID: <16dfd6c2-321b-4c45-ae11-b73e1c80c...@idtp.eu>

Re: [Framers] Learning Structure and Prefix (and more)

[cuc tu]

Hi All,


I had replied to the board and forgot to change the subject line, so this is 
continuing that topic. The short question is, how can I get the Subheading 
element's prefix text to appear as a full paragraph before the Description 
element's text?

I've build a small sample for this discussion and was trying to get a full 
paragraph heading inserted before the contents of a text element, based off the 
parent elements name. Also, it took quite a while to figure out how to make a 
mixed content model not throw errors, and I still really do not understand how 
else that sequence could be structured.

The SYSTEM and SPA elements insert the prefix text. However, I would think the 
structure should be: (,Description1&,Description2&)*
I don't understand the need for the wrapper and termination, but that's what I 
found by trial and error. Separating the elements this way does not work. In 
the end, there will be many optional "Description" elements and they will have 
mixed order.

Description1 and Description2 do not insert the Subheading prefix text. 
Further, it seems I would need to have the Subheading element before the  
element, since Subheading needs to be inserted before the Description element's 
text (or data).

Below are the EDD and xml source data, which all validates and could be usable, 
except for the missing prefix Subheading.


EDD Version is 12.0
Automatically create formats on import.
Element (Container): File
Valid as the highest-level element.
General rule: File_Title, (SYSTEM?,SPA?)
Element (Container): File_Title
General rule: 
Text format rules
In all contexts.
Use paragraph format: Title
Element (Container): SYSTEM
General rule: (|Description1|Description2)*
Prefix rules
In all contexts.
Prefix: SYSTEM Heading
Text format rules
In all contexts.
Use paragraph format: ChapterHeading
Element (Container): SPA
General rule: (|Description1|Description2)*
Prefix rules
In all contexts.
Prefix: SPA Heading
Text format rules
In all contexts.
Use paragraph format: ChapterHeading
Element (Container): Description1
General rule: (|Subheading)*
Text format rules
In all contexts.
Use paragraph format: Indented4
Element (Container): Description2
General rule: (|Subheading)*
Text format rules
In all contexts.
Use paragraph format: Indented4
Element (Container): Subheading
General rule: 
Prefix rules
If context is: Description1
Prefix: Insert Description1
Else, if context is:
Prefix: Insert Description2
Text format rules
In all contexts.
Use paragraph format: Heading4







File Title

SYSTEM description1
SYSTEM description2


SPA description1
SPA description2




Thanks
C2


From: Framers  on 
behalf of framers-requ...@lists.frameusers.com 

Sent: Tuesday, August 28, 2018 1:02 PM
To: framers@lists.frameusers.com
Subject: Framers Digest, Vol 149, Issue 21

Send Framers mailing list submissions to framers@lists.frameusers.com
To subscribe or unsubscribe, visit
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com You
Framers Info Page - Adobe 
FrameMaker
lists.frameusers.com
About the Framers email list. The purpose of this list is to share information 
about using Adobe Framemaker. We welcome experienced users, newcomers, and 
people simply wanting to know more about the software.



can reach the person managing the list at
framers-ow...@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. Re:  FM 2017 Columns and Continued Lines (Wim Hooghwinkel - idtp)
   2.  FM2019 Doesn't Print to PDF (Corcoran, Susan)
   3. Re:  Framers Digest, Vol 149, Issue 20 (cuc tu)
   4.  Kudos for Adobe Support (Lea Rush)
   5. Re:  Framers Digest, Vol 149, Issue 20 (Roger Shuttleworth)


--

Message: 1
Date: Mon, 27 Aug 2018 22:24:51 +0200
From: Wim Hooghwinkel - idtp 
To: framers@lists.frameusers.com
Cc: julie.sigr...@airbornemx.com
Subject: Re: [Framers] FM 2017 Columns and Continued Lines
Message-ID: <16dfd6c2-321b-4c45-ae11-b73e1c80c...@idtp.eu>
Content-Type: text/plain;   charset=us-ascii

Hi Julie,

you could use a (one column) table for each Part Number and the belonging 
references. Put the Part Number paragraph in the table header (or table title) 
and add the table continued variable. This will be repeated at the top of each 
column where the table breaks.


Vriendelijke groet / Kind regards,

Wim Hooghwinkel


FontoXML  | DITAToo  | 
FrameMaker  | edc 
 | AEM 

 | MiramoPDF 

Phone   +31652036811
Skype   wimhooghwinkel
Twitter @idtp
Web