Re: [Framers] Pronouns (was Re: Paragraph numbering)

[Lin Sims]

No need to apologize, there was no way for you to know without my telling
you, especially as it's a nickname.

On Tue, Jun 15, 2021 at 4:36 PM Lynne A. Price  wrote:

> I'm so sorry, Lin. My parents always told me that Lynn could be either a
> man's name or a woman's, but Lynne was always a woman's. They didn't
> mention other spellings and certainly never anticipated that
> gender-specific terminology would become a social flaw.
>
>  --Lynne
>
> On 6/15/2021 1:27 PM, Lin Sims wrote:
> > (And I'm female, btw. Not that it's easy to tell from my name!)
>
> --
> Lynne A. Price
> Text Structure Consulting, Inc.
> Specializing in structured FrameMaker consulting, application development,
> and training
> lpr...@txstruct.comhttp://www.txstruct.com
> voice/fax: (510) 583-1505  cell phone: (510) 421-2284
>
> ___
>
> 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



-- 
Lin Sims
___

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] Paragraph numbering

[Peter Gold]

When I was a trainer, I always showed the FM outline template example files
in class, alongside the numbering pane of the paragraph designer. IOW, we
went to the source.

IIRC, web searches for FrameMaker auto numbering find good examples.

HTH

On Tue, Jun 15, 2021, 3:28 PM Lin Sims  wrote:

> In addition to Lynne's excellent explanation, I'd like to add that while
> you can leave the trailing placeholders out of your autonumber definitions,
> it is generally recommended that they be used so that you have a visual
> reminder of how many characters are included. This becomes really important
> when you try to set up a single series to handle, for example, heading
> levels, tables, and graphics.
>
> So where she has:
>
>   s: increments and displays the first level and resets the
> > second and third levels to 0
> >   s:. displays the first level without changing it,
> > increments and displays the second level, and resets the third level to 0
> >   s:.. displays the first and second levels without
> > changing them, increments and displays the third level
>
>
> I would use:
>
> s:.< =0>.< =0>
> s:..< =0>
> s:..
>
> The end result is the same, but you now have a visual reminder that there
> are other tags using this series that may require updating.
>
> (And I'm female, btw. Not that it's easy to tell from my name!)
>
> On Tue, Jun 15, 2021 at 9:58 AM Lynne A. Price 
> wrote:
>
> > Debbie,
> >
> >  Lin's example uses some options in FrameMaker's counter support
> > that you didn't mention in your post:
> >
> > 1. Different sequences. If a paragraph's autonumber starts with a single
> > character followed by a colon, it uses counters that are independent of
> > those in other sequences. One solution in your case would be to use:
> >
> >   x: and x: for numbered items
> >   y: and y: for lettered items
> >
> > I've used the x and y sequences in this example to emphasize that the
> > sequence identifiers are independent of the way you are formatting the
> > counter values. Of course, using n and a (or N and A) is probably more
> > natural.
> >
> > Different sequences can be used for different numbered constructs. For
> > example, you might use one sequence for list numbers and a different one
> > for section numbers.
> >
> > 2. Using multiple levels in one sequence. For example, documents with
> > three levels of sections can use the first counter for main sections,
> > the second for subsections, and the third for subsubsections with
> > autonumbers such as:
> >
> >   s: for main sections
> >   s:. for subsections
> >   s:.. for subsubsections
> >
> > The counter for any level that is not mentioned is reset to 0. Thus,
> >
> >   s: increments and displays the first level and resets the
> > second and third levels to 0
> >   s:. displays the first level without changing it,
> > increments and displays the second level, and resets the third level to 0
> >   s:.. displays the first and second levels without
> > changing them, increments and displays the third level
> >
> > 3. Displaying a counter in different ways. Building blocks indicate the
> > format in which counters are displayed (n for Arabic numerals, a for
> > lowercase letters and so forth), but the counter value depends on how
> > that level of that sequence was set in previous paragraphs and not by
> > how it was displayed previously. It is up to the user to make sure that
> > the same format is used consistently in all paragraphs.
> >
> > One way to "display" a counter is not to show it at all. That's done by
> > using a space instead of a visible character (such as n or a) for the
> > format. Lin is using the L sequence for items in lists with the first
> > level of that sequence for numbered items in the main list and the
> > second level of that sequence for lettered items in numbered lists. So
> > his L:< >\t, where the space between the first pair of angle
> > brackets is important, means to save but not display the value of the
> > first counter level and to increment and display the second level as a
> > letter. Without < >, the autonumber would be referring to the first
> > level and the numbers and letters for both list levels would be confused.
> >
> > Hope this helps,
> >
> >  --Lynne
> >
> > On 6/15/2021 5:09 AM, Lin Sims wrote:
> > > These are the contents of my Autonumbers for a similar list. I suspect
> > > you've not got your placeholders set up correctly.
> > >
> > > 1st Level, Reset: L:< =0>\t
> > > 1st Level: L:< =0>\t
> > > 2nd Level, Reset: L:< >\t
> > > 2nd Level: L:< >\t
> > >
> > > On Mon, Jun 14, 2021 at 8:11 PM DJ Layton 
> > wrote:
> > >>
> > >> The second part of the numbered list seems to be incrementing the
> > >> ALPHABETIC value rather than the preceding NUMERIC value.
> > >>
> > >> I used the standard , , and ,  building blocks.
> > >> I cannot figure this out!!!
> > >>
> > >>
> > >>
> > >
> > --
> > Lynne A. Price
> > Text Structure Consulting, Inc.
> > 

[Framers] Pronouns (was Re: Paragraph numbering)

[Lynne A. Price]

I'm so sorry, Lin. My parents always told me that Lynn could be either a 
man's name or a woman's, but Lynne was always a woman's. They didn't 
mention other spellings and certainly never anticipated that 
gender-specific terminology would become a social flaw.


    --Lynne

On 6/15/2021 1:27 PM, Lin Sims wrote:

(And I'm female, btw. Not that it's easy to tell from my name!)


--
Lynne A. Price
Text Structure Consulting, Inc.
Specializing in structured FrameMaker consulting, application development, and 
training
lpr...@txstruct.comhttp://www.txstruct.com
voice/fax: (510) 583-1505  cell phone: (510) 421-2284

___

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] Paragraph numbering

[Lin Sims]

In addition to Lynne's excellent explanation, I'd like to add that while
you can leave the trailing placeholders out of your autonumber definitions,
it is generally recommended that they be used so that you have a visual
reminder of how many characters are included. This becomes really important
when you try to set up a single series to handle, for example, heading
levels, tables, and graphics.

So where she has:

  s: increments and displays the first level and resets the
> second and third levels to 0
>   s:. displays the first level without changing it,
> increments and displays the second level, and resets the third level to 0
>   s:.. displays the first and second levels without
> changing them, increments and displays the third level


I would use:

s:.< =0>.< =0>
s:..< =0>
s:..

The end result is the same, but you now have a visual reminder that there
are other tags using this series that may require updating.

(And I'm female, btw. Not that it's easy to tell from my name!)

On Tue, Jun 15, 2021 at 9:58 AM Lynne A. Price  wrote:

> Debbie,
>
>  Lin's example uses some options in FrameMaker's counter support
> that you didn't mention in your post:
>
> 1. Different sequences. If a paragraph's autonumber starts with a single
> character followed by a colon, it uses counters that are independent of
> those in other sequences. One solution in your case would be to use:
>
>   x: and x: for numbered items
>   y: and y: for lettered items
>
> I've used the x and y sequences in this example to emphasize that the
> sequence identifiers are independent of the way you are formatting the
> counter values. Of course, using n and a (or N and A) is probably more
> natural.
>
> Different sequences can be used for different numbered constructs. For
> example, you might use one sequence for list numbers and a different one
> for section numbers.
>
> 2. Using multiple levels in one sequence. For example, documents with
> three levels of sections can use the first counter for main sections,
> the second for subsections, and the third for subsubsections with
> autonumbers such as:
>
>   s: for main sections
>   s:. for subsections
>   s:.. for subsubsections
>
> The counter for any level that is not mentioned is reset to 0. Thus,
>
>   s: increments and displays the first level and resets the
> second and third levels to 0
>   s:. displays the first level without changing it,
> increments and displays the second level, and resets the third level to 0
>   s:.. displays the first and second levels without
> changing them, increments and displays the third level
>
> 3. Displaying a counter in different ways. Building blocks indicate the
> format in which counters are displayed (n for Arabic numerals, a for
> lowercase letters and so forth), but the counter value depends on how
> that level of that sequence was set in previous paragraphs and not by
> how it was displayed previously. It is up to the user to make sure that
> the same format is used consistently in all paragraphs.
>
> One way to "display" a counter is not to show it at all. That's done by
> using a space instead of a visible character (such as n or a) for the
> format. Lin is using the L sequence for items in lists with the first
> level of that sequence for numbered items in the main list and the
> second level of that sequence for lettered items in numbered lists. So
> his L:< >\t, where the space between the first pair of angle
> brackets is important, means to save but not display the value of the
> first counter level and to increment and display the second level as a
> letter. Without < >, the autonumber would be referring to the first
> level and the numbers and letters for both list levels would be confused.
>
> Hope this helps,
>
>  --Lynne
>
> On 6/15/2021 5:09 AM, Lin Sims wrote:
> > These are the contents of my Autonumbers for a similar list. I suspect
> > you've not got your placeholders set up correctly.
> >
> > 1st Level, Reset: L:< =0>\t
> > 1st Level: L:< =0>\t
> > 2nd Level, Reset: L:< >\t
> > 2nd Level: L:< >\t
> >
> > On Mon, Jun 14, 2021 at 8:11 PM DJ Layton 
> wrote:
> >>
> >> The second part of the numbered list seems to be incrementing the
> >> ALPHABETIC value rather than the preceding NUMERIC value.
> >>
> >> I used the standard , , and ,  building blocks.
> >> I cannot figure this out!!!
> >>
> >>
> >>
> >
> --
> Lynne A. Price
> Text Structure Consulting, Inc.
> Specializing in structured FrameMaker consulting, application development,
> and training
> lpr...@txstruct.comhttp://www.txstruct.com
> voice/fax: (510) 583-1505  cell phone: (510) 421-2284
>
> ___
>
> 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 

Re: [Framers] Paragraph numbering

[Lynne A. Price]

Debbie,

    Lin's example uses some options in FrameMaker's counter support 
that you didn't mention in your post:


1. Different sequences. If a paragraph's autonumber starts with a single 
character followed by a colon, it uses counters that are independent of 
those in other sequences. One solution in your case would be to use:


 x: and x: for numbered items
 y: and y: for lettered items

I've used the x and y sequences in this example to emphasize that the 
sequence identifiers are independent of the way you are formatting the 
counter values. Of course, using n and a (or N and A) is probably more 
natural.


Different sequences can be used for different numbered constructs. For 
example, you might use one sequence for list numbers and a different one 
for section numbers.


2. Using multiple levels in one sequence. For example, documents with 
three levels of sections can use the first counter for main sections, 
the second for subsections, and the third for subsubsections with 
autonumbers such as:


 s: for main sections
 s:. for subsections
 s:.. for subsubsections

The counter for any level that is not mentioned is reset to 0. Thus,

 s: increments and displays the first level and resets the 
second and third levels to 0
 s:. displays the first level without changing it, 
increments and displays the second level, and resets the third level to 0
 s:.. displays the first and second levels without 
changing them, increments and displays the third level


3. Displaying a counter in different ways. Building blocks indicate the 
format in which counters are displayed (n for Arabic numerals, a for 
lowercase letters and so forth), but the counter value depends on how 
that level of that sequence was set in previous paragraphs and not by 
how it was displayed previously. It is up to the user to make sure that 
the same format is used consistently in all paragraphs.


One way to "display" a counter is not to show it at all. That's done by 
using a space instead of a visible character (such as n or a) for the 
format. Lin is using the L sequence for items in lists with the first 
level of that sequence for numbered items in the main list and the 
second level of that sequence for lettered items in numbered lists. So 
his L:< >\t, where the space between the first pair of angle 
brackets is important, means to save but not display the value of the 
first counter level and to increment and display the second level as a 
letter. Without < >, the autonumber would be referring to the first 
level and the numbers and letters for both list levels would be confused.


Hope this helps,

    --Lynne

On 6/15/2021 5:09 AM, Lin Sims wrote:

These are the contents of my Autonumbers for a similar list. I suspect
you've not got your placeholders set up correctly.

1st Level, Reset: L:< =0>\t
1st Level: L:< =0>\t
2nd Level, Reset: L:< >\t
2nd Level: L:< >\t

On Mon, Jun 14, 2021 at 8:11 PM DJ Layton  wrote:


The second part of the numbered list seems to be incrementing the
ALPHABETIC value rather than the preceding NUMERIC value.

I used the standard , , and ,  building blocks.
I cannot figure this out!!!






--
Lynne A. Price
Text Structure Consulting, Inc.
Specializing in structured FrameMaker consulting, application development, and 
training
lpr...@txstruct.comhttp://www.txstruct.com
voice/fax: (510) 583-1505  cell phone: (510) 421-2284

___

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] Paragraph numbering

[Lin Sims]

If you look closely, you'll see that the building blocks for the numbers
(the "upper" level) are in the first set of brackets and the building block
for the letters (the "lower" level) are in the second set of brackets. This
lets you use the upper level to restart numbering for the lower level and
also "remembers" the value for the upper level to continue it when coming
out of the lower level.

There's an excellent explanation of using a series to control numbering
here:
https://www.rockymountaintraining.com/adobe-framemaker-numbered-headings-continued/

On Tue, Jun 15, 2021 at 9:37 AM Harding, Dan  wrote:

> Shouldn't the different list levels be different sequences, i.e., 2nd
> level should be a sequence other than L?
>
> -Dan
>
>
>
>
> -Original Message-
> From: Framers 
> On Behalf Of Lin Sims
> Sent: Tuesday, June 15, 2021 7:09 AM
> To: An email list for people using Adobe FrameMaker software. <
> framers@lists.frameusers.com>
> Subject: Re: [Framers] Paragraph numbering
>
> These are the contents of my Autonumbers for a similar list. I suspect
> you've not got your placeholders set up correctly.
>
> 1st Level, Reset: L:< =0>\t
> 1st Level: L:< =0>\t
> 2nd Level, Reset: L:< >\t
> 2nd Level: L:< >\t
>
> On Mon, Jun 14, 2021 at 8:11 PM DJ Layton 
> wrote:
>
> > I've been using FrameMaker since 2000, and I am puzzled with the
> > result I'm getting in the 2020 version that I have now.
> >
> > I started a numbered list, and inserted some indented alphabetic
> > sub-items, then returned to the numbered list. I expected to get
> > something like this:
> > 1
> > 2
> > 3
> > a
> > b
> > c
> > d
> > e
> > 4
> > 5
> > 6
> >
> > Instead I got this:
> > 1
> > 2
> > 3
> > a
> > b
> > c
> > d
> > e
> > 6
> > 7
> > 8
> >
> > The second part of the numbered list seems to be incrementing the
> > ALPHABETIC value rather than the preceding NUMERIC value.
> >
> > I used the standard , , and ,  building blocks.
> > I cannot figure this out!!!
> >
> > Can anyone help??
> >
> > Thanks in advance.
> > Debbie in Oregon
> > ___
> >
> > This message is from the Framers mailing list
> >
> > Send messages to framers@lists.frameusers.com Visit the list's
> > homepage at
> > https://urldefense.com/v3/__http://www.frameusers.com__;!!DZ3fjg!qLCZU
> > G9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_yn4TJw4$
> > Archives located at
> > https://urldefense.com/v3/__http://www.mail-archive.com/framers*40list
> > s.frameusers.com/__;JQ!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWr
> > sXRIoOuaanuM9wU3LpQ9_sBVzs60$
> > Subscribe and unsubscribe at
> > https://urldefense.com/v3/__http://lists.frameusers.com/listinfo.cgi/f
> > ramers-frameusers.com__;!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnP
> > WrsXRIoOuaanuM9wU3LpQ9_Q_2EDNw$ Send administrative questions to
> > listad...@frameusers.com
> >
>
>
> --
> Lin Sims
> ___
>
> This message is from the Framers mailing list
>
> Send messages to framers@lists.frameusers.com Visit the list's homepage
> at
> https://urldefense.com/v3/__http://www.frameusers.com__;!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_yn4TJw4$
> Archives located at
> https://urldefense.com/v3/__http://www.mail-archive.com/framers*40lists.frameusers.com/__;JQ!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_sBVzs60$
> Subscribe and unsubscribe at
> https://urldefense.com/v3/__http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com__;!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_Q_2EDNw$
> 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
>


-- 
Lin Sims
___

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] Paragraph numbering

[Harding, Dan]

Shouldn't the different list levels be different sequences, i.e., 2nd level 
should be a sequence other than L?

-Dan
 
 


-Original Message-
From: Framers  On 
Behalf Of Lin Sims
Sent: Tuesday, June 15, 2021 7:09 AM
To: An email list for people using Adobe FrameMaker software. 

Subject: Re: [Framers] Paragraph numbering

These are the contents of my Autonumbers for a similar list. I suspect you've 
not got your placeholders set up correctly.

1st Level, Reset: L:< =0>\t
1st Level: L:< =0>\t
2nd Level, Reset: L:< >\t
2nd Level: L:< >\t

On Mon, Jun 14, 2021 at 8:11 PM DJ Layton  wrote:

> I've been using FrameMaker since 2000, and I am puzzled with the 
> result I'm getting in the 2020 version that I have now.
>
> I started a numbered list, and inserted some indented alphabetic 
> sub-items, then returned to the numbered list. I expected to get 
> something like this:
> 1
> 2
> 3
> a
> b
> c
> d
> e
> 4
> 5
> 6
>
> Instead I got this:
> 1
> 2
> 3
> a
> b
> c
> d
> e
> 6
> 7
> 8
>
> The second part of the numbered list seems to be incrementing the 
> ALPHABETIC value rather than the preceding NUMERIC value.
>
> I used the standard , , and ,  building blocks.
> I cannot figure this out!!!
>
> Can anyone help??
>
> Thanks in advance.
> Debbie in Oregon
> ___
>
> This message is from the Framers mailing list
>
> Send messages to framers@lists.frameusers.com Visit the list's 
> homepage at  
> https://urldefense.com/v3/__http://www.frameusers.com__;!!DZ3fjg!qLCZU
> G9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_yn4TJw4$
> Archives located at
> https://urldefense.com/v3/__http://www.mail-archive.com/framers*40list
> s.frameusers.com/__;JQ!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWr
> sXRIoOuaanuM9wU3LpQ9_sBVzs60$
> Subscribe and unsubscribe at
> https://urldefense.com/v3/__http://lists.frameusers.com/listinfo.cgi/f
> ramers-frameusers.com__;!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnP
> WrsXRIoOuaanuM9wU3LpQ9_Q_2EDNw$ Send administrative questions to 
> listad...@frameusers.com
>


--
Lin Sims
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com Visit the list's homepage at  
https://urldefense.com/v3/__http://www.frameusers.com__;!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_yn4TJw4$
Archives located at 
https://urldefense.com/v3/__http://www.mail-archive.com/framers*40lists.frameusers.com/__;JQ!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_sBVzs60$
Subscribe and unsubscribe at 
https://urldefense.com/v3/__http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com__;!!DZ3fjg!qLCZUG9V8-7sul6kKn83CEA-pByMGVBoeOsnPWrsXRIoOuaanuM9wU3LpQ9_Q_2EDNw$
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] Paragraph numbering

[Lin Sims]

These are the contents of my Autonumbers for a similar list. I suspect
you've not got your placeholders set up correctly.

1st Level, Reset: L:< =0>\t
1st Level: L:< =0>\t
2nd Level, Reset: L:< >\t
2nd Level: L:< >\t

On Mon, Jun 14, 2021 at 8:11 PM DJ Layton  wrote:

> I've been using FrameMaker since 2000, and I am puzzled with the result
> I'm getting in the 2020 version that I have now.
>
> I started a numbered list, and inserted some indented alphabetic
> sub-items, then returned to the numbered list. I expected to get something
> like this:
> 1
> 2
> 3
> a
> b
> c
> d
> e
> 4
> 5
> 6
>
> Instead I got this:
> 1
> 2
> 3
> a
> b
> c
> d
> e
> 6
> 7
> 8
>
> The second part of the numbered list seems to be incrementing the
> ALPHABETIC value rather than the preceding NUMERIC value.
>
> I used the standard , , and ,  building blocks.
> I cannot figure this out!!!
>
> Can anyone help??
>
> Thanks in advance.
> Debbie in Oregon
> ___
>
> 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
>


-- 
Lin Sims
___

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

[Framers] Paragraph numbering

[DJ Layton]

I've been using FrameMaker since 2000, and I am puzzled with the result I'm 
getting in the 2020 version that I have now.

I started a numbered list, and inserted some indented alphabetic sub-items, 
then returned to the numbered list. I expected to get something like this:
1
2
3
a
b
c
d
e
4
5
6

Instead I got this:
1
2
3
a
b
c
d
e
6
7
8

The second part of the numbered list seems to be incrementing the ALPHABETIC 
value rather than the preceding NUMERIC value.

I used the standard , , and ,  building blocks.
I cannot figure this out!!!

Can anyone help??

Thanks in advance.
Debbie in Oregon
___

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] Paragraph numbering with embedded return?

[Rick Quatro]

Hi Lin,

If you have to use two paragraph formats, use an "invisible" number on the
Chapter Title paragraph format that picks up the number from the Section
paragraph format. So if Section is  then Chapter Title is . That way
you only have to build a cross reference to the Chapter Title. There are
various ways to make an autonumber invisible. If you need specific help,
send me an email and I can give you some suggestions. Thanks.

Rick

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



-Original Message-
From: Framers  On
Behalf Of Lin Sims
Sent: Friday, August 17, 2018 2:31 PM
To: Frame Users 
Subject: [Framers] Paragraph numbering with embedded return?

The house style here is that each chapter starts with the following:

Section 
Chapter Title

(These are the only heading-type paragraphs with numbers.)

I am getting mortally tired of having to use two separate cross-references
when referring to a chapter. If I could figure out how to embed a return in
the autonumbering, I could drop a paragraph tag, add an xref tag, and go on
my merry way. I've already tried using \r in the Autonumber builder, but
Frame doesn't like that.

Is this even possible, or am I to remain woeful?

--
Lin Sims
___

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

[Framers] Paragraph numbering with embedded return?

[Lin Sims]

The house style here is that each chapter starts with the following:

Section 
Chapter Title

(These are the only heading-type paragraphs with numbers.)

I am getting mortally tired of having to use two separate cross-references
when referring to a chapter. If I could figure out how to embed a return in
the autonumbering, I could drop a paragraph tag, add an xref tag, and go on
my merry way. I've already tried using \r in the Autonumber builder, but
Frame doesn't like that.

Is this even possible, or am I to remain woeful?

-- 
Lin Sims
___

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] Small caps in paragraph numbering

[Lin Sims]

Most appendices use letters rather than numbers. This helps distinguish
them from the main body of the text. Even if we put "Chapter" or "Appendix"
in the label, it's still easy to confuse them if both use numbers.

Plus, if you're using numbered headings, you now have TWO sets of 1.1.3 and
can't tell where you are in the book.

On Tue, Jul 31, 2018 at 3:49 PM, Dennis Brunnenmeyer <
dennis.brunnenme...@gmail.com> wrote:

> Why not just number your appendices rather than using characters from the
> keyboard, like this:
>
> Appendix 1:   Specifications
>
> Dennis...
> --
> Dennis Brunnenmeyer
> Host | Nevada City Limits
> KVMR-FM / KCPC-FM Radio / KVMR.org
> 120 Bridge Street
> Nevada City, CA 95959
> p: (530) 477-9015
> m: (530) 320-9025
> dennis.brunnenme...@gmail.com
> or
> denn...@kvmr.org
>
>
> On Tue, Jul 31, 2018 at 10:33 AM Doug  wrote:
>
> > I'm trying to make the following heading using a paragraph format with
> the
> > Appendix A: part set up using paragraph autonumbering:
> >
> > Appendix A: Specifications
> >
> > However, the entire line needs to use Small Caps.  It all works great the
> > way I have it set up, EXCEPT that I can't figure out how to make the
> Small
> > Caps attribute apply to the autonumbered letter A.  It continues to stand
> > tall above the rest of the line.
> >
> > Ideas?
> >
> > Doug
> > ___
> >
> > 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
>



-- 
Lin Sims
___

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] Small caps in paragraph numbering

[Dennis Brunnenmeyer]

Why not just number your appendices rather than using characters from the
keyboard, like this:

Appendix 1:   Specifications

Dennis...
--
Dennis Brunnenmeyer
Host | Nevada City Limits
KVMR-FM / KCPC-FM Radio / KVMR.org
120 Bridge Street
Nevada City, CA 95959
p: (530) 477-9015
m: (530) 320-9025
dennis.brunnenme...@gmail.com
or
denn...@kvmr.org


On Tue, Jul 31, 2018 at 10:33 AM Doug  wrote:

> I'm trying to make the following heading using a paragraph format with the
> Appendix A: part set up using paragraph autonumbering:
>
> Appendix A: Specifications
>
> However, the entire line needs to use Small Caps.  It all works great the
> way I have it set up, EXCEPT that I can't figure out how to make the Small
> Caps attribute apply to the autonumbered letter A.  It continues to stand
> tall above the rest of the line.
>
> Ideas?
>
> Doug
> ___
>
> 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] Small caps in paragraph numbering

[Lin Sims]

OH! OK, I see what you mean. You're right, small caps doesn't affect
capital letters, only lowercase, and as far as I know that's how it's
always been since the idea was to substitute the lowercase glyphs with
glyphs that resembled the uppercase letters at a lower height and lighter
weight.

On Tue, Jul 31, 2018 at 2:58 PM, Doug  wrote:

> The problem is Small Caps doesn't work at all if the character was
> uppercase to begin with.  IMO it's a design flaw in the Small Caps concept,
> but that's just me.  Small Caps won't work unless the text is lowercase.
> And setting the chapter number to capital letters makes the variable hold
> an uppercase value.
>
> On Tue, Jul 31, 2018 at 2:53 PM, Lin Sims  wrote:
>
> > You're using <$chapnum>? I admit that I haven't been using the special
> > counters in anything, but while it should take its value from the
> numbering
> > properties of the document, set in either the document itself or the
> > bookfile, it's formatting should still be controlled by the Numbering tab
> > for the paragraph tag.
> >
> > In any case, how is what you're doing using a character tag to set the
> font
> > to all caps but 2 points smaller different from using a character tag to
> > set the font to small caps? Maybe I'm missing something, but to me it
> > sounds like we're both applying a character tag on the Numbering tab.
> >
> > On Tue, Jul 31, 2018 at 2:29 PM, Doug  wrote:
> >
> > > I think the problem is that the autonumber is set by the Chapter Number
> > and
> > > in this case it's set to capital letters (since it's an appendix).  I
> > > suppose I could set the numbering to lowercase letters but that would
> > cause
> > > problems elsewhere.
> > >
> > > The best workaround I've found is to define a character format that
> > changes
> > > the font to uppercase while reducing font size by 2 points, which has
> the
> > > same net effect.
> > >
> > >
> > > On Tue, Jul 31, 2018 at 2:18 PM, Lin Sims  wrote:
> > >
> > > > Create a specific character tag that for making text small caps with
> > > > everything else set to As-Is.
> > > >
> > > > Then on the Numbering tab of your paragraph tag, use the Character
> > Format
> > > > drop-down and select your new character format.
> > > >
> > > > On Tue, Jul 31, 2018 at 1:33 PM, Doug  wrote:
> > > >
> > > > > I'm trying to make the following heading using a paragraph format
> > with
> > > > the
> > > > > Appendix A: part set up using paragraph autonumbering:
> > > > >
> > > > > Appendix A: Specifications
> > > > >
> > > > > However, the entire line needs to use Small Caps.  It all works
> great
> > > the
> > > > > way I have it set up, EXCEPT that I can't figure out how to make
> the
> > > > Small
> > > > > Caps attribute apply to the autonumbered letter A.  It continues to
> > > stand
> > > > > tall above the rest of the line.
> > > > >
> > > > > Ideas?
> > > > >
> > > > > Doug
> > > > > ___
> > > > >
> > > > > 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
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Lin Sims
> > > > ___
> > > >
> > > > 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
> > >
> >
> >
> >
> > --
> > Lin Sims
> > ___
> >
> > 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 

Re: [Framers] Small caps in paragraph numbering

[Doug]

The problem is Small Caps doesn't work at all if the character was
uppercase to begin with.  IMO it's a design flaw in the Small Caps concept,
but that's just me.  Small Caps won't work unless the text is lowercase.
And setting the chapter number to capital letters makes the variable hold
an uppercase value.

On Tue, Jul 31, 2018 at 2:53 PM, Lin Sims  wrote:

> You're using <$chapnum>? I admit that I haven't been using the special
> counters in anything, but while it should take its value from the numbering
> properties of the document, set in either the document itself or the
> bookfile, it's formatting should still be controlled by the Numbering tab
> for the paragraph tag.
>
> In any case, how is what you're doing using a character tag to set the font
> to all caps but 2 points smaller different from using a character tag to
> set the font to small caps? Maybe I'm missing something, but to me it
> sounds like we're both applying a character tag on the Numbering tab.
>
> On Tue, Jul 31, 2018 at 2:29 PM, Doug  wrote:
>
> > I think the problem is that the autonumber is set by the Chapter Number
> and
> > in this case it's set to capital letters (since it's an appendix).  I
> > suppose I could set the numbering to lowercase letters but that would
> cause
> > problems elsewhere.
> >
> > The best workaround I've found is to define a character format that
> changes
> > the font to uppercase while reducing font size by 2 points, which has the
> > same net effect.
> >
> >
> > On Tue, Jul 31, 2018 at 2:18 PM, Lin Sims  wrote:
> >
> > > Create a specific character tag that for making text small caps with
> > > everything else set to As-Is.
> > >
> > > Then on the Numbering tab of your paragraph tag, use the Character
> Format
> > > drop-down and select your new character format.
> > >
> > > On Tue, Jul 31, 2018 at 1:33 PM, Doug  wrote:
> > >
> > > > I'm trying to make the following heading using a paragraph format
> with
> > > the
> > > > Appendix A: part set up using paragraph autonumbering:
> > > >
> > > > Appendix A: Specifications
> > > >
> > > > However, the entire line needs to use Small Caps.  It all works great
> > the
> > > > way I have it set up, EXCEPT that I can't figure out how to make the
> > > Small
> > > > Caps attribute apply to the autonumbered letter A.  It continues to
> > stand
> > > > tall above the rest of the line.
> > > >
> > > > Ideas?
> > > >
> > > > Doug
> > > > ___
> > > >
> > > > 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
> > > >
> > >
> > >
> > >
> > > --
> > > Lin Sims
> > > ___
> > >
> > > 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
> >
>
>
>
> --
> Lin Sims
> ___
>
> 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] Small caps in paragraph numbering

[Lin Sims]

You're using <$chapnum>? I admit that I haven't been using the special
counters in anything, but while it should take its value from the numbering
properties of the document, set in either the document itself or the
bookfile, it's formatting should still be controlled by the Numbering tab
for the paragraph tag.

In any case, how is what you're doing using a character tag to set the font
to all caps but 2 points smaller different from using a character tag to
set the font to small caps? Maybe I'm missing something, but to me it
sounds like we're both applying a character tag on the Numbering tab.

On Tue, Jul 31, 2018 at 2:29 PM, Doug  wrote:

> I think the problem is that the autonumber is set by the Chapter Number and
> in this case it's set to capital letters (since it's an appendix).  I
> suppose I could set the numbering to lowercase letters but that would cause
> problems elsewhere.
>
> The best workaround I've found is to define a character format that changes
> the font to uppercase while reducing font size by 2 points, which has the
> same net effect.
>
>
> On Tue, Jul 31, 2018 at 2:18 PM, Lin Sims  wrote:
>
> > Create a specific character tag that for making text small caps with
> > everything else set to As-Is.
> >
> > Then on the Numbering tab of your paragraph tag, use the Character Format
> > drop-down and select your new character format.
> >
> > On Tue, Jul 31, 2018 at 1:33 PM, Doug  wrote:
> >
> > > I'm trying to make the following heading using a paragraph format with
> > the
> > > Appendix A: part set up using paragraph autonumbering:
> > >
> > > Appendix A: Specifications
> > >
> > > However, the entire line needs to use Small Caps.  It all works great
> the
> > > way I have it set up, EXCEPT that I can't figure out how to make the
> > Small
> > > Caps attribute apply to the autonumbered letter A.  It continues to
> stand
> > > tall above the rest of the line.
> > >
> > > Ideas?
> > >
> > > Doug
> > > ___
> > >
> > > 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
> > >
> >
> >
> >
> > --
> > Lin Sims
> > ___
> >
> > 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
>



-- 
Lin Sims
___

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] Small caps in paragraph numbering

[Doug]

I think the problem is that the autonumber is set by the Chapter Number and
in this case it's set to capital letters (since it's an appendix).  I
suppose I could set the numbering to lowercase letters but that would cause
problems elsewhere.

The best workaround I've found is to define a character format that changes
the font to uppercase while reducing font size by 2 points, which has the
same net effect.


On Tue, Jul 31, 2018 at 2:18 PM, Lin Sims  wrote:

> Create a specific character tag that for making text small caps with
> everything else set to As-Is.
>
> Then on the Numbering tab of your paragraph tag, use the Character Format
> drop-down and select your new character format.
>
> On Tue, Jul 31, 2018 at 1:33 PM, Doug  wrote:
>
> > I'm trying to make the following heading using a paragraph format with
> the
> > Appendix A: part set up using paragraph autonumbering:
> >
> > Appendix A: Specifications
> >
> > However, the entire line needs to use Small Caps.  It all works great the
> > way I have it set up, EXCEPT that I can't figure out how to make the
> Small
> > Caps attribute apply to the autonumbered letter A.  It continues to stand
> > tall above the rest of the line.
> >
> > Ideas?
> >
> > Doug
> > ___
> >
> > 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
> >
>
>
>
> --
> Lin Sims
> ___
>
> 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] Small caps in paragraph numbering

[Lin Sims]

Create a specific character tag that for making text small caps with
everything else set to As-Is.

Then on the Numbering tab of your paragraph tag, use the Character Format
drop-down and select your new character format.

On Tue, Jul 31, 2018 at 1:33 PM, Doug  wrote:

> I'm trying to make the following heading using a paragraph format with the
> Appendix A: part set up using paragraph autonumbering:
>
> Appendix A: Specifications
>
> However, the entire line needs to use Small Caps.  It all works great the
> way I have it set up, EXCEPT that I can't figure out how to make the Small
> Caps attribute apply to the autonumbered letter A.  It continues to stand
> tall above the rest of the line.
>
> Ideas?
>
> Doug
> ___
>
> 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
>



-- 
Lin Sims
___

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

[Framers] Small caps in paragraph numbering

[Doug]

I'm trying to make the following heading using a paragraph format with the
Appendix A: part set up using paragraph autonumbering:

Appendix A: Specifications

However, the entire line needs to use Small Caps.  It all works great the
way I have it set up, EXCEPT that I can't figure out how to make the Small
Caps attribute apply to the autonumbered letter A.  It continues to stand
tall above the rest of the line.

Ideas?

Doug
___

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] Paragraph numbering...

[Urszula Witherell]

No... I just need to control the numbering of paragraphs starting point. That is
all.
 
Thanks very much for everyone's help. Sometimes it is easy not to see the
obvious. It was my turn today.
Urszula
 
 

> On February 4, 2016 at 11:01 AM Tim Pann <tp...@telecomsys.com> wrote:
>
>
> Would you then be safest naming this paragraph tag "step 17" or whatever to
> isolate it from any override resets?
>
> 
> From: Framers [framers-bounces+tpann=telecomsys@lists.frameusers.com] on
> behalf of Monique Semp [monique.s...@earthlink.net]
> Sent: Thursday, February 04, 2016 7:58 AM
> To: Bernard Aschwanden (Publishing Smarter); 'Urszula Witherell'; 'Framers'
> Subject: Re: [Framers] Paragraph numbering...
>
> > One approach is to use the code 

Re: [Framers] Paragraph numbering...

[Syed Zaeem Hosain]

In general, yes, as Monique mentioned ... 

Z

> -Original Message-
> From: Framers [mailto:framers-
> bounces+syed.hosain=aeris@lists.frameusers.com] On Behalf Of Tim
> Pann
> Sent: Thursday, February 4, 2016 08:01 AM
> To: Monique Semp <monique.s...@earthlink.net>; Bernard Aschwanden
> (Publishing Smarter) <bern...@publishingsmarter.com>; 'Urszula Witherell'
> <urszulawither...@jetsetcom.net>; 'Framers'
> <framers@lists.frameusers.com>
> Subject: Re: [Framers] Paragraph numbering...
> 
> Would you then be safest naming this paragraph tag "step 17" or whatever to
> isolate it from any override resets?
> 
> 
> From: Framers [framers-
> bounces+tpann=telecomsys@lists.frameusers.com] on behalf of
> Monique Semp [monique.s...@earthlink.net]
> Sent: Thursday, February 04, 2016 7:58 AM
> To: Bernard Aschwanden (Publishing Smarter); 'Urszula Witherell'; 'Framers'
> Subject: Re: [Framers] Paragraph numbering...
> 
> > One approach is to use the code 

Re: [Framers] Paragraph numbering...

[Bernard Aschwanden (Publishing Smarter)]

One approach is to use the code

Re: [Framers] Paragraph numbering...

[Monique Semp]

One approach is to use the code 

Re: [Framers] Paragraph numbering...

[Urszula Witherell]

Thanks very much Bernard and Rick,
 
Very simple.. works perfectly.
 
 
 
 

> On February 4, 2016 at 10:55 AM "Bernard Aschwanden (Publishing Smarter)"
>  wrote:
>
>
> One approach is to use the code
>
> 

Re: [Framers] Paragraph numbering...

[Tim Pann]

Would you then be safest naming this paragraph tag "step 17" or whatever to 
isolate it from any override resets?


From: Framers [framers-bounces+tpann=telecomsys@lists.frameusers.com] on 
behalf of Monique Semp [monique.s...@earthlink.net]
Sent: Thursday, February 04, 2016 7:58 AM
To: Bernard Aschwanden (Publishing Smarter); 'Urszula Witherell'; 'Framers'
Subject: Re: [Framers] Paragraph numbering...

> One approach is to use the code 

[Framers] Paragraph numbering...

[Urszula Witherell]

Hi Everyone,
 
In a number of documents I have to start a paragraph numbering in a document
with a very specific paragraph number. Is there a way to do that?
 
>From what I can see, FrameMaker only allows to specify volume, chapter, 
>section,
sub-section and page numbering to begin at a specific number, but not a
paragraph... 
 
I will appreciate any help.
 
Urszula
 
--
Urszula Witherell | JetSet Communications, Inc.
Certified Technical Trainer (CompTIA)
cell: 301.524.3165 www.jetsetcom.net | www.trainingonsite.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: Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Whites]

Hello All -
This is not just in FM 8.0
The bug exists to some extent in 7.2 as well,  and it is a pickle  
other ways. Recently I inadvertently included a numeric space in an  
autonumber and ePP 9.2 totally choked on it.
As to FM 7.2 and non-breaking hyphens in autonumbers, I've resorted  
to replacing them with periods - after I discovered that FM was  
changing the non-breaking hyphens into n-dashes - so now I have, for  
example, Fig. 9.2 rather than Fig. 9–2. (Before the bug FM used to  
give me Fig. 9-2).  It's amazing how little the readers care (or  
notice) the change.
Still, it would be nice to get what one asks for.

Will White
ViaLogy LLC


On Dec 13, 2007, at 12:46 AM, Shlomo Perets wrote:

 Sarah O'Keefe wrote:

 We are noticing a similar problem related to autonumbering even  
 without
 the MIF conversion you describe.

 For instance:

 1. Define a paragraph autonumber that includes an em space (\sm) and
 some text. (Note:\sm)
 2. Reopen the paragraph designer and change only the autonumber text
 (change Note to Tip).
 Notice that the \sm turns into something weird and renders as a ?? in
 your document.

 There appears to be a problem with special characters that are  
 inserted
 with a backslash (\).


 The problem seems to be present in all text fields in dialog boxes
 (variables, cross-references, pgf numbering, markers), with the
 backslash sequences  for a non-breaking hyphen (\+) and special
 spaces (\sm, \sn, \st, \s#) .

 When the dialog box definition is updated, a question mark appear in
 the document instead of the special character.

 To fix the problem, you need to edit the text in the dialog box
 (delete the box character and insert the backslash sequence again).


 Shlomo Perets

 MicroType, http://www.microtype.com
 Training, consulting  add-ons: FrameMaker, Structured FM and Acrobat



+++
There's the right way and the wrong way.
Then there's my way - which is like the wrong way, but faster.
+++




___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Whites]

Hello All -
This is not just in FM 8.0
The bug exists to some extent in 7.2 as well,  and it is a pickle  
other ways. Recently I inadvertently included a numeric space in an  
autonumber and ePP 9.2 totally choked on it.
As to FM 7.2 and non-breaking hyphens in autonumbers, I've resorted  
to replacing them with periods - after I discovered that FM was  
changing the non-breaking hyphens into n-dashes - so now I have, for  
example, Fig. 9.2 rather than Fig. 9?2. (Before the bug FM used to  
give me Fig. 9-2).  It's amazing how little the readers care (or  
notice) the change.
Still, it would be nice to get what one asks for.

Will White
ViaLogy LLC


On Dec 13, 2007, at 12:46 AM, Shlomo Perets wrote:

> Sarah O'Keefe wrote:
>
>> We are noticing a similar problem related to autonumbering even  
>> without
>> the MIF conversion you describe.
>>
>> For instance:
>>
>> 1. Define a paragraph autonumber that includes an em space (\sm) and
>> some text. (Note:\sm)
>> 2. Reopen the paragraph designer and change only the autonumber text
>> (change "Note" to "Tip").
>> Notice that the \sm turns into something weird and renders as a ?? in
>> your document.
>>
>> There appears to be a problem with special characters that are  
>> inserted
>> with a backslash (\).
>
>
> The problem seems to be present in all text fields in dialog boxes
> (variables, cross-references, pgf numbering, markers), with the
> backslash sequences  for a non-breaking hyphen (\+) and special
> spaces (\sm, \sn, \st, \s#) .
>
> When the dialog box definition is updated, a question mark appear in
> the document instead of the special character.
>
> To fix the problem, you need to edit the text in the dialog box
> (delete the box character and insert the backslash sequence again).
>
>
> Shlomo Perets
>
> MicroType, http://www.microtype.com
> Training, consulting & add-ons: FrameMaker, Structured FM and Acrobat
>
>

+++
There's the right way and the wrong way.
Then there's my way - which is like the wrong way, but faster.
+++

re: Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Shlomo Perets]

Sarah O'Keefe wrote:

We are noticing a similar problem related to autonumbering even without
the MIF conversion you describe.

For instance:

1. Define a paragraph autonumber that includes an em space (\sm) and
some text. (Note:\sm)
2. Reopen the paragraph designer and change only the autonumber text
(change Note to Tip).
Notice that the \sm turns into something weird and renders as a ?? in
your document.

There appears to be a problem with special characters that are inserted
with a backslash (\).


The problem seems to be present in all text fields in dialog boxes
(variables, cross-references, pgf numbering, markers), with the
backslash sequences  for a non-breaking hyphen (\+) and special
spaces (\sm, \sn, \st, \s#) .

When the dialog box definition is updated, a question mark appear in
the document instead of the special character.

To fix the problem, you need to edit the text in the dialog box
(delete the box character and insert the backslash sequence again).


Shlomo Perets

MicroType, http://www.microtype.com
Training, consulting  add-ons: FrameMaker, Structured FM and Acrobat

___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Shlomo Perets]

Sarah O'Keefe wrote:

>We are noticing a similar problem related to autonumbering even without
>the MIF conversion you describe.
>
>For instance:
>
>1. Define a paragraph autonumber that includes an em space (\sm) and
>some text. (Note:\sm)
>2. Reopen the paragraph designer and change only the autonumber text
>(change "Note" to "Tip").
>Notice that the \sm turns into something weird and renders as a ?? in
>your document.
>
>There appears to be a problem with special characters that are inserted
>with a backslash (\).


The problem seems to be present in all text fields in dialog boxes
(variables, cross-references, pgf numbering, markers), with the
backslash sequences  for a non-breaking hyphen (\+) and special
spaces (\sm, \sn, \st, \s#) .

When the dialog box definition is updated, a question mark appear in
the document instead of the special character.

To fix the problem, you need to edit the text in the dialog box
(delete the box character and insert the backslash sequence again).


Shlomo Perets

MicroType, http://www.microtype.com
Training, consulting & add-ons: FrameMaker, Structured FM and Acrobat

Re: Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Jeremy H. Griffith]

On Fri, 16 Nov 2007 09:51:43 +0100, Reng, Dr. Winfried 
[EMAIL PROTECTED] wrote:

I noticed that the dashes which I defined
in the paragraph numbering to mark the list items are
exchanged by: 'Äì

Actually the first char is the *baseline* single quote...
What happened is that the en dash, U+2013, was encoded
in UTF-8 (correctly) as bytes E2 80 93, so you see the
corresponding Frame characters...  The trouble, of course,
is that MIF pre-8.0 knows nothing of UTF-8.  It's a bug.

-- Jeremy H. Griffith, at Omni Systems Inc.
  [EMAIL PROTECTED]  http://www.omsys.com/
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

RE: Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Reng, Dr. Winfried]

Hi Sarah,

Yes. I noticed this em space problem also with
the running HF variables. (Already posted.)

Best regards

Winfried

 -Original Message-
 From: Sarah O'Keefe [mailto:[EMAIL PROTECTED]
 Sent: Friday, November 16, 2007 2:38 PM
 To: Reng, Dr. Winfried; [EMAIL PROTECTED]
 Subject: Re: Bug: FrameMaker 8 changes dash \= in paragraph 
 numbering of
 FM 7 MIF
 
 
 Hi there,
 
 We are noticing a similar problem related to autonumbering 
 even without
 the MIF conversion you describe.
 
 For instance:
 
 1. Define a paragraph autonumber that includes an em space (\sm) and
 some text. (Note:\sm)
 2. Reopen the paragraph designer and change only the autonumber text
 (change Note to Tip).
 Notice that the \sm turns into something weird and renders as a ?? in
 your document.
 
 There appears to be a problem with special characters that 
 are inserted
 with a backslash (\).
 
 Regards,
 
 Sarah O'Keefe
 
 Reng, Dr. Winfried wrote:
  Hi,
  
  Our translation agency uses Trados, which cannot
  handle FM 8 files yet. Therefore I converted everything
  to FM 7 MIF files (new option in Save As). When I got
  the files back, I noticed that the dashes which I defined
  in the paragraph numbering to mark the list items are
  exchanged by: 'Äì
  In FM 7 in the paragraph designer I had: \t\=\t
(it's a second level list).
  In the FM 8 binary file this was changed to: \t-\t
In the file the dash is displayed correctly.
  When I open a MIF 7.0 file this was changed to: \t'Äì\t
(paragraph designer)
  In the FM file of this MIF 7.0 file the numbering is
displayed as: squareÄìtab
(the square is here a character which FM cannot display)
  
  We use Univers (non-Unicode). And that's probably the
  reason. But still FM should not convert the dash.
  
  This is no problem with MIF 8.0 files. FM 8 opened
  also FM 7 binary files with this list numbering correctly.
  
  Best regards
  
  Winfried
 -- 
 ##
 ##
 Sarah O'Keefe Scriptorium Publishing Services, Inc.
 Blog: http://www.scriptorium.com/palimpsest
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Re: Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Whites]

I believe that using a numeric space in an autonumber will also cause  
ePP to crash.

Will White

On Nov 16, 2007, at 5:49 AM, Reng, Dr. Winfried wrote:

 Hi Sarah,

 Yes. I noticed this em space problem also with
 the running HF variables. (Already posted.)

 Best regards

 Winfried

 -Original Message-
 From: Sarah O'Keefe [mailto:[EMAIL PROTECTED]
 Sent: Friday, November 16, 2007 2:38 PM
 To: Reng, Dr. Winfried; [EMAIL PROTECTED]
 Subject: Re: Bug: FrameMaker 8 changes dash \= in paragraph
 numbering of
 FM 7 MIF


 Hi there,

 We are noticing a similar problem related to autonumbering
 even without
 the MIF conversion you describe.

 For instance:

 1. Define a paragraph autonumber that includes an em space (\sm) and
 some text. (Note:\sm)
 2. Reopen the paragraph designer and change only the autonumber text
 (change Note to Tip).
 Notice that the \sm turns into something weird and renders as a ?? in
 your document.

 There appears to be a problem with special characters that
 are inserted
 with a backslash (\).

 Regards,

 Sarah O'Keefe

 Reng, Dr. Winfried wrote:
 Hi,

 Our translation agency uses Trados, which cannot
 handle FM 8 files yet. Therefore I converted everything
 to FM 7 MIF files (new option in Save As). When I got
 the files back, I noticed that the dashes which I defined
 in the paragraph numbering to mark the list items are
 exchanged by: 'Äì
 In FM 7 in the paragraph designer I had: \t\=\t
   (it's a second level list).
 In the FM 8 binary file this was changed to: \t-\t
   In the file the dash is displayed correctly.
 When I open a MIF 7.0 file this was changed to: \t'Äì\t
   (paragraph designer)
 In the FM file of this MIF 7.0 file the numbering is
   displayed as: squareÄìtab
   (the square is here a character which FM cannot display)

 We use Univers (non-Unicode). And that's probably the
 reason. But still FM should not convert the dash.

 This is no problem with MIF 8.0 files. FM 8 opened
 also FM 7 binary files with this list numbering correctly.

 Best regards

 Winfried
 -- 
 ##
 ##
 Sarah O'KeefeScriptorium Publishing Services, Inc.
 Blog: http://www.scriptorium.com/palimpsest
 ___


 You are currently subscribed to Framers as [EMAIL PROTECTED]

 Send list messages to [EMAIL PROTECTED]

 To unsubscribe send a blank email to
 [EMAIL PROTECTED]
 or visit http://lists.frameusers.com/mailman/options/framers/ 
 whitefamily%40mac.com

 Send administrative questions to [EMAIL PROTECTED] Visit
 http://www.frameusers.com/ for more resources and info.

+++
There's the right way and the wrong way.
Then there's my way - which is like the wrong way, but faster.
+++




___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Re: Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Sarah O'Keefe]

Hi there,

We are noticing a similar problem related to autonumbering even without
the MIF conversion you describe.

For instance:

1. Define a paragraph autonumber that includes an em space (\sm) and
some text. (Note:\sm)
2. Reopen the paragraph designer and change only the autonumber text
(change Note to Tip).
Notice that the \sm turns into something weird and renders as a ?? in
your document.

There appears to be a problem with special characters that are inserted
with a backslash (\).

Regards,

Sarah O'Keefe

Reng, Dr. Winfried wrote:
 Hi,
 
 Our translation agency uses Trados, which cannot
 handle FM 8 files yet. Therefore I converted everything
 to FM 7 MIF files (new option in Save As). When I got
 the files back, I noticed that the dashes which I defined
 in the paragraph numbering to mark the list items are
 exchanged by: 'Äì
 In FM 7 in the paragraph designer I had: \t\=\t
   (it's a second level list).
 In the FM 8 binary file this was changed to: \t-\t
   In the file the dash is displayed correctly.
 When I open a MIF 7.0 file this was changed to: \t'Äì\t
   (paragraph designer)
 In the FM file of this MIF 7.0 file the numbering is
   displayed as: squareÄìtab
   (the square is here a character which FM cannot display)
 
 We use Univers (non-Unicode). And that's probably the
 reason. But still FM should not convert the dash.
 
 This is no problem with MIF 8.0 files. FM 8 opened
 also FM 7 binary files with this list numbering correctly.
 
 Best regards
 
 Winfried
-- 

Sarah O'Keefe   Scriptorium Publishing Services, Inc.
Blog: http://www.scriptorium.com/palimpsest
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Reng, Dr. Winfried]

Hi,

Our translation agency uses Trados, which cannot
handle FM 8 files yet. Therefore I converted everything
to FM 7 MIF files (new option in Save As). When I got
the files back, I noticed that the dashes which I defined
in the paragraph numbering to mark the list items are
exchanged by: 'Äì
In FM 7 in the paragraph designer I had: \t\=\t
  (it's a second level list).
In the FM 8 binary file this was changed to: \t-\t
  In the file the dash is displayed correctly.
When I open a MIF 7.0 file this was changed to: \t'Äì\t
  (paragraph designer)
In the FM file of this MIF 7.0 file the numbering is
  displayed as: squareÄìtab
  (the square is here a character which FM cannot display)

We use Univers (non-Unicode). And that's probably the
reason. But still FM should not convert the dash.

This is no problem with MIF 8.0 files. FM 8 opened
also FM 7 binary files with this list numbering correctly.

Best regards

Winfried
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Reng, Dr. Winfried]

Hi,

Our translation agency uses Trados, which cannot
handle FM 8 files yet. Therefore I converted everything
to FM 7 MIF files (new option in Save As). When I got
the files back, I noticed that the dashes which I defined
in the paragraph numbering to mark the list items are
exchanged by: '??
In FM 7 in the paragraph designer I had: \t\=\t
  (it's a second level list).
In the FM 8 binary file this was changed to: \t-\t
  In the file the dash is displayed correctly.
When I open a MIF 7.0 file this was changed to: \t'??\t
  (paragraph designer)
In the FM file of this MIF 7.0 file the numbering is
  displayed as: square??tab
  (the square is here a character which FM cannot display)

We use Univers (non-Unicode). And that's probably the
reason. But still FM should not convert the dash.

This is no problem with MIF 8.0 files. FM 8 opened
also FM 7 binary files with this list numbering correctly.

Best regards

Winfried

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Jeremy H. Griffith]

On Fri, 16 Nov 2007 09:51:43 +0100, "Reng, Dr. Winfried" 
 wrote:

>I noticed that the dashes which I defined
>in the paragraph numbering to mark the list items are
>exchanged by: '??

Actually the first char is the *baseline* single quote...
What happened is that the en dash, U+2013, was encoded
in UTF-8 (correctly) as bytes E2 80 93, so you see the
corresponding Frame characters...  The trouble, of course,
is that MIF pre-8.0 knows nothing of UTF-8.  It's a bug.

-- Jeremy H. Griffith, at Omni Systems Inc.
http://www.omsys.com/

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Sarah O'Keefe]

Hi there,

We are noticing a similar problem related to autonumbering even without
the MIF conversion you describe.

For instance:

1. Define a paragraph autonumber that includes an em space (\sm) and
some text. (Note:\sm)
2. Reopen the paragraph designer and change only the autonumber text
(change "Note" to "Tip").
Notice that the \sm turns into something weird and renders as a ?? in
your document.

There appears to be a problem with special characters that are inserted
with a backslash (\).

Regards,

Sarah O'Keefe

Reng, Dr. Winfried wrote:
> Hi,
> 
> Our translation agency uses Trados, which cannot
> handle FM 8 files yet. Therefore I converted everything
> to FM 7 MIF files (new option in Save As). When I got
> the files back, I noticed that the dashes which I defined
> in the paragraph numbering to mark the list items are
> exchanged by: '??
> In FM 7 in the paragraph designer I had: \t\=\t
>   (it's a second level list).
> In the FM 8 binary file this was changed to: \t-\t
>   In the file the dash is displayed correctly.
> When I open a MIF 7.0 file this was changed to: \t'??\t
>   (paragraph designer)
> In the FM file of this MIF 7.0 file the numbering is
>   displayed as: square??tab
>   (the square is here a character which FM cannot display)
> 
> We use Univers (non-Unicode). And that's probably the
> reason. But still FM should not convert the dash.
> 
> This is no problem with MIF 8.0 files. FM 8 opened
> also FM 7 binary files with this list numbering correctly.
> 
> Best regards
> 
> Winfried
-- 

Sarah O'Keefe   Scriptorium Publishing Services, Inc.
Blog: http://www.scriptorium.com/palimpsest

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Reng, Dr. Winfried]

Hi Sarah,

Yes. I noticed this em space problem also with
the running HF variables. (Already posted.)

Best regards

Winfried

> -Original Message-
> From: Sarah O'Keefe [mailto:okeefe at scriptorium.com]
> Sent: Friday, November 16, 2007 2:38 PM
> To: Reng, Dr. Winfried; framers at frameusers.com
> Subject: Re: Bug: FrameMaker 8 changes dash \= in paragraph 
> numbering of
> FM 7 MIF
> 
> 
> Hi there,
> 
> We are noticing a similar problem related to autonumbering 
> even without
> the MIF conversion you describe.
> 
> For instance:
> 
> 1. Define a paragraph autonumber that includes an em space (\sm) and
> some text. (Note:\sm)
> 2. Reopen the paragraph designer and change only the autonumber text
> (change "Note" to "Tip").
> Notice that the \sm turns into something weird and renders as a ?? in
> your document.
> 
> There appears to be a problem with special characters that 
> are inserted
> with a backslash (\).
> 
> Regards,
> 
> Sarah O'Keefe
> 
> Reng, Dr. Winfried wrote:
> > Hi,
> > 
> > Our translation agency uses Trados, which cannot
> > handle FM 8 files yet. Therefore I converted everything
> > to FM 7 MIF files (new option in Save As). When I got
> > the files back, I noticed that the dashes which I defined
> > in the paragraph numbering to mark the list items are
> > exchanged by: '??
> > In FM 7 in the paragraph designer I had: \t\=\t
> >   (it's a second level list).
> > In the FM 8 binary file this was changed to: \t-\t
> >   In the file the dash is displayed correctly.
> > When I open a MIF 7.0 file this was changed to: \t'??\t
> >   (paragraph designer)
> > In the FM file of this MIF 7.0 file the numbering is
> >   displayed as: square??tab
> >   (the square is here a character which FM cannot display)
> > 
> > We use Univers (non-Unicode). And that's probably the
> > reason. But still FM should not convert the dash.
> > 
> > This is no problem with MIF 8.0 files. FM 8 opened
> > also FM 7 binary files with this list numbering correctly.
> > 
> > Best regards
> > 
> > Winfried
> -- 
> ##
> ##
> Sarah O'Keefe Scriptorium Publishing Services, Inc.
> Blog: http://www.scriptorium.com/palimpsest

Bug: FrameMaker 8 changes dash \= in paragraph numbering of FM 7 MIF

[Whites]

I believe that using a numeric space in an autonumber will also cause  
ePP to crash.

Will White

On Nov 16, 2007, at 5:49 AM, Reng, Dr. Winfried wrote:

> Hi Sarah,
>
> Yes. I noticed this em space problem also with
> the running HF variables. (Already posted.)
>
> Best regards
>
> Winfried
>
>> -Original Message-
>> From: Sarah O'Keefe [mailto:okeefe at scriptorium.com]
>> Sent: Friday, November 16, 2007 2:38 PM
>> To: Reng, Dr. Winfried; framers at frameusers.com
>> Subject: Re: Bug: FrameMaker 8 changes dash \= in paragraph
>> numbering of
>> FM 7 MIF
>>
>>
>> Hi there,
>>
>> We are noticing a similar problem related to autonumbering
>> even without
>> the MIF conversion you describe.
>>
>> For instance:
>>
>> 1. Define a paragraph autonumber that includes an em space (\sm) and
>> some text. (Note:\sm)
>> 2. Reopen the paragraph designer and change only the autonumber text
>> (change "Note" to "Tip").
>> Notice that the \sm turns into something weird and renders as a ?? in
>> your document.
>>
>> There appears to be a problem with special characters that
>> are inserted
>> with a backslash (\).
>>
>> Regards,
>>
>> Sarah O'Keefe
>>
>> Reng, Dr. Winfried wrote:
>>> Hi,
>>>
>>> Our translation agency uses Trados, which cannot
>>> handle FM 8 files yet. Therefore I converted everything
>>> to FM 7 MIF files (new option in Save As). When I got
>>> the files back, I noticed that the dashes which I defined
>>> in the paragraph numbering to mark the list items are
>>> exchanged by: '??
>>> In FM 7 in the paragraph designer I had: \t\=\t
>>>   (it's a second level list).
>>> In the FM 8 binary file this was changed to: \t-\t
>>>   In the file the dash is displayed correctly.
>>> When I open a MIF 7.0 file this was changed to: \t'??\t
>>>   (paragraph designer)
>>> In the FM file of this MIF 7.0 file the numbering is
>>>   displayed as: square??tab
>>>   (the square is here a character which FM cannot display)
>>>
>>> We use Univers (non-Unicode). And that's probably the
>>> reason. But still FM should not convert the dash.
>>>
>>> This is no problem with MIF 8.0 files. FM 8 opened
>>> also FM 7 binary files with this list numbering correctly.
>>>
>>> Best regards
>>>
>>> Winfried
>> -- 
>> ##
>> ##
>> Sarah O'KeefeScriptorium Publishing Services, Inc.
>> Blog: http://www.scriptorium.com/palimpsest
> ___
>
>
> You are currently subscribed to Framers as whitefamily at mac.com.
>
> Send list messages to framers at lists.frameusers.com.
>
> To unsubscribe send a blank email to
> framers-unsubscribe at lists.frameusers.com
> or visit http://lists.frameusers.com/mailman/options/framers/ 
> whitefamily%40mac.com
>
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.

+++
There's the right way and the wrong way.
Then there's my way - which is like the wrong way, but faster.
+++

Paragraph numbering issue

[Fred Ridder]

It sounds to me like you have the book file has the numbering
properties set to restart the paragraph numbering in each chapter
files. It's important to remember that numbering properties set
in the book file (by highlighting components in the book window,
then right-clicking and shoosing Numbering Properties in the
context menu) override any settings that are made in the
individual files so that you can use the same component files
in multiple books that may have different numbering setups.

And are you remembering to execute the Update Book command
to refresh all the numbering after you make any changes in the
book-level numbering properties? The numbering does not update
on the fly when you chang ethe setup; you must explicitly tell
FrameMaker to perform the update.

-Fred Ridder


>From: William Abernathy 
>To: framers at lists.frameusers.com
>Subject: Paragraph numbering issue
>Date: Mon, 09 Jul 2007 11:07:09 -0700
>
>All: I'm having a difficult time finessing this one, and I think I need 
>someone to help me come at it from a different angle. I have chapterwise 
>paragraph numbers that I want to reset on every chapter break, and I have a 
>set of requirement numbers that I want to sustain across chapter 
>boundaries. Hence:
>
>...
>Section 5.10.6
>   blah blah
>   Requirement 47: Thou shalt Foo
>
>Chapter 6
>
>Section 6-1
>   blah-blah
>   Requirement 48: Thou shalt Bar
>
>The problem is that I still end up with:
>
>Section 6-1
>   blah-blah
>   Requirement 1: Thou shalt Bar
>
>The current Heading p-tags are: C:<$chapnum>.<n+>.< =0>< =0>< =0>< =0>< 
>=0>\t (for Heading1, outputting "N.1   [Section Title]" and resetting all 
>subheadings in the C: series). At the chapter break, the Chapter title 
>P-tag resets the entire series with C:<$chapnum>.< =0>< =0>< =0>< =0>< =0>< 
>=0>.
>
>The current Requirement p-tag is: R:Requirement <n+>
>
>I have set the paragraph numbering properties to continue paragraph 
>numbering from chapter to chapter, under the theory that the C: series will 
>be reset by the chapter title regardless. Nonetheless, the R: series 
>doggedly resets at the chapter breaks. As things stand, I'm having to cook 
>up a fudge p-tag setting at the chapter breaks, which is obviously 
>unacceptable.
>
>What am I doing wrong?
>
>--William
>___
>
>
>You are currently subscribed to Framers as DocuDoc at hotmail.com.
>
>Send list messages to framers at lists.frameusers.com.
>
>To unsubscribe send a blank email to 
>framers-unsubscribe at lists.frameusers.com
>or visit 
>http://lists.frameusers.com/mailman/options/framers/docudoc%40hotmail.com
>
>Send administrative questions to listadmin at frameusers.com. Visit
>http://www.frameusers.com/ for more resources and info.

_
Local listings, incredible imagery, and driving directions - all in one 
place! http://maps.live.com/?wip=69=MGAC01

Paragraph numbering issue

[William Abernathy]

Thank you Fred, Ann, and Jeremy for your replies. All suggested that I review 
the numbering properties at the book and document levels for consistency.

Fred, however, wins the scalp on this bug with the following suggestion:

"And are you remembering to execute the Update Book command
to refresh all the numbering after you make any changes in the
book-level numbering properties? The numbering does not update
on the fly when you change the setup; you must explicitly tell
FrameMaker to perform the update."

D'Oh!

Thanks!

--William


William Abernathy wrote:
> All: I'm having a difficult time finessing this one, and I think I need 
> someone to help me come at it from a different angle. I have chapterwise 
> paragraph numbers that I want to reset on every chapter break, and I 
> have a set of requirement numbers that I want to sustain across chapter 
> boundaries. Hence:
> 
> ...
> Section 5.10.6
> blah blah
> Requirement 47: Thou shalt Foo
> 
> Chapter 6
> 
> Section 6-1
> blah-blah
> Requirement 48: Thou shalt Bar
> 
> The problem is that I still end up with:
> 
> Section 6-1
> blah-blah
> Requirement 1: Thou shalt Bar
> 
> The current Heading p-tags are: C:<$chapnum>.<n+>.< =0>< =0>< =0>< =0>< 
> =0>\t (for Heading1, outputting "N.1   [Section Title]" and resetting 
> all subheadings in the C: series). At the chapter break, the Chapter 
> title P-tag resets the entire series with C:<$chapnum>.< =0>< =0>< =0>< 
> =0>< =0>< =0>.
> 
> The current Requirement p-tag is: R:Requirement <n+>
> 
> I have set the paragraph numbering properties to continue paragraph 
> numbering from chapter to chapter, under the theory that the C: series 
> will be reset by the chapter title regardless. Nonetheless, the R: 
> series doggedly resets at the chapter breaks. As things stand, I'm 
> having to cook up a fudge p-tag setting at the chapter breaks, which is 
> obviously unacceptable.
> 
> What am I doing wrong?
> 
> --William

Paragraph numbering issue

[William Abernathy]

All: I'm having a difficult time finessing this one, and I think I need someone 
to help me come at it from a different angle. I have chapterwise paragraph 
numbers that I want to reset on every chapter break, and I have a set of 
requirement numbers that I want to sustain across chapter boundaries. Hence:

...
Section 5.10.6
blah blah
Requirement 47: Thou shalt Foo

Chapter 6

Section 6-1
blah-blah
Requirement 48: Thou shalt Bar

The problem is that I still end up with:

Section 6-1
blah-blah
Requirement 1: Thou shalt Bar

The current Heading p-tags are: C:<$chapnum>.<n+>.< =0>< =0>< =0>< =0>< =0>\t 
(for Heading1, outputting "N.1   [Section Title]" and resetting all subheadings 
in the C: series). At the chapter break, the Chapter title P-tag resets the 
entire series with C:<$chapnum>.< =0>< =0>< =0>< =0>< =0>< =0>.

The current Requirement p-tag is: R:Requirement <n+>

I have set the paragraph numbering properties to continue paragraph numbering 
from chapter to chapter, under the theory that the C: series will be reset by 
the chapter title regardless. Nonetheless, the R: series doggedly resets at the 
chapter breaks. As things stand, I'm having to cook up a fudge p-tag setting at 
the chapter breaks, which is obviously unacceptable.

What am I doing wrong?

--William

Paragraph numbering issue

[Jeremy H. Griffith]

On Mon, 09 Jul 2007 11:07:09 -0700, William Abernathy  
wrote:

>I have set the paragraph numbering properties to continue paragraph numbering 
>from chapter to chapter, under the theory that the C: series will be reset by 
>the chapter title regardless. 

Haven't tested it, but that sounds right.

>Nonetheless, the R: series doggedly resets at the chapter breaks.

*Where* did you set the numbering properties?  The settings made
from the book file override those made from the chapter file.
Sounds like the book could be resetting the paragraph numbering.

-- Jeremy H. Griffith, at Omni Systems Inc.
http://www.omsys.com/

Paragraph numbering not restarting

[Alan Litchfield]

On Nov 4, 2006, at 11:31 AM, Gillian Flato wrote:

> I have a book file. The chapter and page numbering is updating just
> fine. The paragraph numbering is not even though it's set to "read  
> from
> previous file". We have a technical manual with numbered headings and
> the headings are restarting at 1 with each chapter which is not  
> what we
> want.
>
>

I assume your numbering is something like:
1.1
1.1.1
1.2.1
. 
. 
. 
2.1
2.1.1
. 
. 
. 


If you use <$chapnum>.<n+>, <$chapnum>.,<n+>, etc. this reads the  
chapter number as the number sequence. The paragraphs numbering  
follows along behind.

HIH
Alan

Paragraph numbering not restarting

[Gillian Flato]

Guys,
 
I have a book file. The chapter and page numbering is updating just
fine. The paragraph numbering is not even though it's set to read from
previous file. We have a technical manual with numbered headings and
the headings are restarting at 1 with each chapter which is not what we
want.
 
Any suggestions?
 

Thank you,

 

mailto:[EMAIL PROTECTED] 

Gillian Flato

Technical Writer (Software)

nanometrics

1550 Buckeye Dr. 

Milpitas, CA. 95035

(408.435.9600 x 316

7  408.232.5911

* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] .com
blocked::mailto:[EMAIL PROTECTED] 

 


This message (including any attachments) may contain confidential information 
intended for a specific individual and purpose. If you are not the intended 
recipient, delete this message. If you are not the intended recipient, 
disclosing, copying, distributing, or taking any action based on this message 
is strictly prohibited.
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Re: Paragraph numbering not restarting

[Art Campbell]

The usual way to force this to happen is to create two tags for each
level of headings, one to start the numbering at 1, and the other tag
to increment. If this scheme is in use, the book para setting will be
over-ridden.

So check the first heading in each chapter to see what that tag's
Numbering properties are... and if you're using the two-tag scheme.

Art

On 11/3/06, Gillian Flato [EMAIL PROTECTED] wrote:

Guys,

I have a book file. The chapter and page numbering is updating just
fine. The paragraph numbering is not even though it's set to read from
previous file. We have a technical manual with numbered headings and
the headings are restarting at 1 with each chapter which is not what we
want.

Any suggestions?


--
Art Campbell [EMAIL PROTECTED]
 ... In my opinion, there's nothing in this world beats a '52 Vincent
  and a redheaded girl. -- Richard Thompson
No disclaimers apply.
DoD 358
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]

or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Re: Paragraph numbering not restarting

[Alan Litchfield]

On Nov 4, 2006, at 11:31 AM, Gillian Flato wrote:


I have a book file. The chapter and page numbering is updating just
fine. The paragraph numbering is not even though it's set to read  
from

previous file. We have a technical manual with numbered headings and
the headings are restarting at 1 with each chapter which is not  
what we

want.




I assume your numbering is something like:
1.1
1.1.1
1.2.1
.
.
.
2.1
2.1.1
.
.
.


If you use $chapnum.n+, $chapnum.n,n+, etc. this reads the  
chapter number as the number sequence. The paragraphs numbering  
follows along behind.


HIH
Alan

___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]

or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Paragraph numbering not restarting

[Gillian Flato]

Guys,

I have a book file. The chapter and page numbering is updating just
fine. The paragraph numbering is not even though it's set to "read from
previous file". We have a technical manual with numbered headings and
the headings are restarting at 1 with each chapter which is not what we
want.

Any suggestions?


Thank you,



<mailto:gflato at nanometrics.com> 

Gillian Flato

Technical Writer (Software)

nanometrics

1550 Buckeye Dr. 

Milpitas, CA. 95035

(408.435.9600 x 316

7  408.232.5911

* gflato at nanometrics <mailto:gflato at nanometrics.com> .com
 




This message (including any attachments) may contain confidential information 
intended for a specific individual and purpose. If you are not the intended 
recipient, delete this message. If you are not the intended recipient, 
disclosing, copying, distributing, or taking any action based on this message 
is strictly prohibited.

Paragraph numbering not restarting

[Art Campbell]

The usual way to force this to happen is to create two tags for each
level of headings, one to start the numbering at 1, and the other tag
to increment. If this scheme is in use, the book para setting will be
over-ridden.

So check the first heading in each chapter to see what that tag's
Numbering properties are... and if you're using the two-tag scheme.

Art

On 11/3/06, Gillian Flato  wrote:
> Guys,
>
> I have a book file. The chapter and page numbering is updating just
> fine. The paragraph numbering is not even though it's set to "read from
> previous file". We have a technical manual with numbered headings and
> the headings are restarting at 1 with each chapter which is not what we
> want.
>
> Any suggestions?

-- 
Art Campbell art.campbell at 
gmail.com
  "... In my opinion, there's nothing in this world beats a '52 Vincent
   and a redheaded girl." -- Richard Thompson
 No disclaimers apply.
 DoD 358

Paragraph Numbering

[kgrace4715]

 I wanted to check with the newsgroup and see if anyone could assist me with a 
numbering issue that I have.  I would like to have paragraphs numbered as 
follows:
 
10.020 Apple
   10.020.1   l;kfjkf;jl
   10.020.2   fdjklfjklfl;fdklj;djlkklj;lk;jboaniiesuijnuifnlik
10.030  Orange 
   10.030.1   l;kfjkf;jl
   10.030.2   fdjklfjklfl;fdklj;djlkklj;lk;jboaniiesuijnuifnlik
10.045  Orange 
   10.045.1   l;kfjkf;jl
   10.045.2   fdjklfjklfl;fdklj;djlkklj;lk;jboaniiesuijnuifnlik
 
 
As you can see their are two things that I dont know how to do.
 
1.  Make numbers increment by variable increments
2.  Make the sub numbers ( 10.030.1 and 10.030.2) increment by one when using 
the first number as a base or root 10.030 and 10.045
 
Any help would be greatly appreciated.

Check out the new AOL.  Most comprehensive set of free safety and security 
tools, free access to millions of high-quality videos from across the web, free 
AOL Mail and more.
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Paragraph Numbering

[Combs, Richard]

kgrace4715 at aol.com wrote: 

> 1.  Make numbers increment by variable increments 2.  Make 
> the sub numbers ( 10.030.1 and 10.030.2) increment by one 
> when using the first number as a "base or root" 10.030 and 10.045

Well, you can't _autonumber_ a sequence that with arbitrary increments.
You could hard-code the Apple and Orange numbers -- just enter 10.020 in
the Autonumber Format box of Paragraph Designer -- just to get the
positioning and char formatting. 

Then, you could use autonumbering for the sequential subentries by
setting up a pgf format with autonumbering of 10.020.. Obviously,
you'd need a separate pfg format for each unique "fruit-level" number. 

Or maybe you should try rethinking this entirely and not use FM's
numbering at all. I assume you're not making up these numbers that
increment arbitrarily. If they're generated elsewhere, perhaps some form
of import (manual or scripted) would off-load the numbering to the
external source. 

HTH!
Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--

Paragraph Numbering

[kgrace4...@aol.com]

 I wanted to check with the newsgroup and see if anyone could assist me with a 
numbering issue that I have.  I would like to have paragraphs numbered as 
follows:

10.020 Apple
   10.020.1   l;kfjkf;jl
   10.020.2   fdjklfjklfl;fdklj;djlkklj;lk;jboaniiesuijnuifnlik
10.030  Orange 
   10.030.1   l;kfjkf;jl
   10.030.2   fdjklfjklfl;fdklj;djlkklj;lk;jboaniiesuijnuifnlik
10.045  Orange 
   10.045.1   l;kfjkf;jl
   10.045.2   fdjklfjklfl;fdklj;djlkklj;lk;jboaniiesuijnuifnlik


As you can see their are two things that I dont know how to do.

1.  Make numbers increment by variable increments
2.  Make the sub numbers ( 10.030.1 and 10.030.2) increment by one when using 
the first number as a "base or root" 10.030 and 10.045

Any help would be greatly appreciated.

Check out the new AOL.  Most comprehensive set of free safety and security 
tools, free access to millions of high-quality videos from across the web, free 
AOL Mail and more.