Prev: Form fields
Next: Does anyone Actually Use Word's Table of Authorities Feature for Real Work
From: faceman28208 on 29 Jan 2010 23:35
I experimented today on the user's problem. It is really string how
Word behaves. If I cut the text from the TOC field and paste it, World
absolutely refuses to hyphenate it.
If I paste special as text, then apply TOC styles to it,Word justifies
the text. It looks like something get set behind the scenes that
cannot be unset.
From: Suzanne S. Barnhill on 30 Jan 2010 08:32
You have to realize that text in the TOC is part of a field, so its behavior
is governed by whatever laws are applied to fields. But are we talking about
justifying text or hyphenating it? Those will be two entirely different
things. Keep in mind that the TOC entries, if they include page numbers, are
going to include a right-aligned tab stop and a tab character, which would
prevent them from being justified. And it may be that the style (or the
field) is formatted as "Do not check spelling or grammar," which would
prevent hyphenation. When you apply the TOC style to text that is not in a
table of contents, it does not include the tab stop for page numbers (which
is generated dynamically) nor the tab character (ditto), so it would behave
differently outside the TOC. Regardless of whether the headings themselves
are justified, I can see absolutely no defense of trying to have the TOC
entries justified.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
http://word.mvps.org

<faceman28208(a)yahoo.com> wrote in message
news:6ff1b8eb-c4c8-4642-8ad1-3f2e8343e3f3(a)q6g2000vbi.googlegroups.com...
>I experimented today on the user's problem. It is really string how
> Word behaves. If I cut the text from the TOC field and paste it, World
> absolutely refuses to hyphenate it.
> If I paste special as text, then apply TOC styles to it,Word justifies
> the text. It looks like something get set behind the scenes that
> cannot be unset.
>

From: faceman28208 on 30 Jan 2010 14:58
On Jan 30, 8:32 am, "Suzanne S. Barnhill" <sbarnh...(a)mvps.org> wrote:
> You have to realize that text in the TOC is part of a field, so its behavior
> is governed by whatever laws are applied to fields. But are we talking about
> justifying text or hyphenating it? Those will be two entirely different
> things. Keep in mind that the TOC entries, if they include page numbers, are
> going to include a right-aligned tab stop and a tab character, which would
> prevent them from being justified. And it may be that the style (or the
> field) is formatted as "Do not check spelling or grammar," which would
> prevent hyphenation. When you apply the TOC style to text that is not in a
> table of contents, it does not include the tab stop for page numbers (which
> is generated dynamically) nor the tab character (ditto), so it would behave
> differently outside the TOC. Regardless of whether the headings themselves
> are justified, I can see absolutely no defense of trying to have the TOC
> entries justified.

What is weird is that the paragraphs will not hyphenate even AFTER
being cut and pasted out of the field or the link to the field is
broken. However, they will hyphenate if you do a paste special as text
and apply the TOC.

styles.

I wish I could convince users to do things the easy way....but I can't.
From: Terry Farrell on 30 Jan 2010 17:05
The only way to do this is to create your TOC, then with the cursor in the
TOC (so that it selected) use the UnLinkField command (Ctrl+Shft+F9) which
unlinks the field and effectively turn the TOC (field) into text
(non-field).

This will let you do whatever you like with the formatting but has the
obvious disadvantages that if the document is edited, the TOC has to be
recreated from scratch and justified/hyphenated it will look
unconventionally ghastly.

--
Terry Farrell - MSWord MVP

<faceman28208(a)yahoo.com> wrote in message
news:c062924b-fbcb-49f2-97cd-8c8687ccc8e7(a)k41g2000yqm.googlegroups.com...
> On Jan 30, 8:32 am, "Suzanne S. Barnhill" <sbarnh...(a)mvps.org> wrote:
>> You have to realize that text in the TOC is part of a field, so its
>> behavior
>> is governed by whatever laws are applied to fields. But are we talking
>> about
>> justifying text or hyphenating it? Those will be two entirely different
>> things. Keep in mind that the TOC entries, if they include page numbers,
>> are
>> going to include a right-aligned tab stop and a tab character, which
>> would
>> prevent them from being justified. And it may be that the style (or the
>> field) is formatted as "Do not check spelling or grammar," which would
>> prevent hyphenation. When you apply the TOC style to text that is not in
>> a
>> table of contents, it does not include the tab stop for page numbers
>> (which
>> is generated dynamically) nor the tab character (ditto), so it would
>> behave
>> differently outside the TOC. Regardless of whether the headings
>> themselves
>> are justified, I can see absolutely no defense of trying to have the TOC
>> entries justified.
>
> What is weird is that the paragraphs will not hyphenate even AFTER
> being cut and pasted out of the field or the link to the field is
> broken. However, they will hyphenate if you do a paste special as text
> and apply the TOC.
>
> styles.
>
> I wish I could convince users to do things the easy way....but I can't.

From: faceman28208 on 31 Jan 2010 01:57
On Jan 30, 5:05 pm, "Terry Farrell" <terryfarr...(a)msn.com> wrote:
> The only way to do this is to create your TOC, then with the cursor in the
> TOC (so that it selected) use the UnLinkField command (Ctrl+Shft+F9) which
> unlinks the field and effectively turn the TOC (field) into text
> (non-field).
>
> This will let you do whatever you like with the formatting but has the
> obvious disadvantages that if the document is edited, the TOC has to be
> recreated from scratch and justified/hyphenated it will look
> unconventionally ghastly.

Even after you unlink the TOC it STILL will not hyphenate.

The only thing I have found that makes it hyphenate is to paste
special as text and they apply at TOC style.
First  |  Prev  | 
Pages: 1 2
Prev: Form fields
Next: Does anyone Actually Use Word's Table of Authorities Feature for Real Work