Upgrade to Frame 8

[Jeff Schweiner]

Hi Joyce,

I've also experienced this feature and have come across a repeatable pattern 
of failure.
Can others try this and report back whether it fails for them also?

I'm experiencing problems with dropped characters in text lines. Also, I've 
noticed the history doesn't seem to log all changes made to text lines. The 
problem can be duplicated as follows: 

1. Open a new portrait blank document and add an anchored frame. (recorded in 
history) 
2. Add a text line inside the anchored frame from the Tools Palette. In the 
text line, type 1234 (recorded in history). 
3. Save the file. (history cleared) 
4. Click the cursor after the 4 in the text line and hit a carriage return to 
create a new text line. (not recorded in history) 
5. In the new text line, type 1234567890(not recorded in history) 
6. Save the file. 
7. Refresh the screen (cntl l) and the second text line now reads 12346890 
(dropped the 5 and 7). Printing the file in steps 5 and 6 also show the 5 and 7 
are missing. 
8. Add a new text line inside the anchored frame from the Tools Palette. In the 
text line, type 12345 (recorded in history). 
9. Save the file. (history cleared) 
10. Click the cursor after the 5 in the text line from step 8 and hit a 
carriage return to create a new text line. (not recorded in history) 
11. In the new text line, type 1234567890(not recorded in history) 
12. Save the file. 
13. Refresh the screen and the second text line now reads 12345790 (dropped 
the 6 and 8). 

I get this to fail every time running the trial version 8.0p273 on two 
different XP SP2 systems.



Joyce wrote:

All -

I have noticed both the issues reported by John, and have another to
add.

When I use the text tool to add a callout inside an anchored frame - as
I've done for years with previous versions of FrameMaker - the text
changes. That is, random letters disappear. I've seen it happen several
times, even after saving. But if I place the callout inside a text frame
(inside the anchored frame), it's OK.  

Has anyone else experienced this feature?

Joyce


--
Jeff Schweiner
Hardware Engineering Writer
Cray Inc.
(715) 726-4801

___


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: Upgrade to Frame 8

[Jim Owens]

I just tried this with my trial FM 8.0p273, and it is exactly as you 
describe.

Jeff Schweiner wrote:

 I've also experienced this feature and have come across a repeatable 
 pattern of failure.
 Can others try this and report back whether it fails for them also?
 
 I'm experiencing problems with dropped characters in text lines. Also, I've 
 noticed the history doesn't seem to log all changes made to text lines. The 
 problem can be duplicated as follows: 
 
 1. Open a new portrait blank document and add an anchored frame. (recorded in 
 history) 
 2. Add a text line inside the anchored frame from the Tools Palette. In the 
 text line, type 1234 (recorded in history). 
 3. Save the file. (history cleared) 
 4. Click the cursor after the 4 in the text line and hit a carriage return 
 to create a new text line. (not recorded in history) 
 5. In the new text line, type 1234567890(not recorded in history) 
 6. Save the file. 
 7. Refresh the screen (cntl l) and the second text line now reads 12346890 
 (dropped the 5 and 7). Printing the file in steps 5 and 6 also show the 5 and 
 7 are missing. 
 8. Add a new text line inside the anchored frame from the Tools Palette. In 
 the text line, type 12345 (recorded in history). 
 9. Save the file. (history cleared) 
 10. Click the cursor after the 5 in the text line from step 8 and hit a 
 carriage return to create a new text line. (not recorded in history) 
 11. In the new text line, type 1234567890(not recorded in history) 
 12. Save the file. 
 13. Refresh the screen and the second text line now reads 12345790 (dropped 
 the 6 and 8). 
 
 I get this to fail every time running the trial version 8.0p273 on two 
 different XP SP2 systems.
 

___


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: Upgrade to Frame 8

[Syed.Hosain]

I see the same problem ... quite repeatable. Characters get eliminated
from the text line following a carriage return (even later entries!).

1. Doing a control-L before the save does NOT show any problems.

2. Starting, saving a file, closing it, and then re-opening the file (no
control-L) shows the problem.

3. A single line by itself (1234567890) does NOT show problem.

Basically, to me, it appears that the act of entering a carriage return
at the end of a textline, entering a new line, and saving the file is
causing the problem ...

Definitely a bug of some sort!!! Needs a fix.

Z

 -Original Message-
 From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
 Jeff Schweiner
 Sent: Wednesday, April 02, 2008 8:49 AM
 To: framers@lists.frameusers.com
 Subject: Upgrade to Frame 8
 
 Hi Joyce,
 
 I've also experienced this feature and have come across a repeatable
pattern of failure.
 Can others try this and report back whether it fails for them also?
 
 I'm experiencing problems with dropped characters in text lines. Also,
I've noticed the history
 doesn't seem to log all changes made to text lines. The problem can be
duplicated as follows:
 
 1. Open a new portrait blank document and add an anchored frame.
(recorded in history)
 2. Add a text line inside the anchored frame from the Tools Palette.
In the text line, type 1234
 (recorded in history).
 3. Save the file. (history cleared)
 4. Click the cursor after the 4 in the text line and hit a carriage
return to create a new text
 line. (not recorded in history)
 5. In the new text line, type 1234567890(not recorded in history)
 6. Save the file.
 7. Refresh the screen (cntl l) and the second text line now reads
12346890 (dropped the 5 and 7).
 Printing the file in steps 5 and 6 also show the 5 and 7 are missing.
 8. Add a new text line inside the anchored frame from the Tools
Palette. In the text line, type
 12345 (recorded in history).
 9. Save the file. (history cleared)
 10. Click the cursor after the 5 in the text line from step 8 and
hit a carriage return to create a
 new text line. (not recorded in history)
 11. In the new text line, type 1234567890(not recorded in history)
 12. Save the file.
 13. Refresh the screen and the second text line now reads 12345790
(dropped the 6 and 8).
 
 I get this to fail every time running the trial version 8.0p273 on two
different XP SP2 systems.
 


 
 Joyce wrote:
 
 All -
 
 I have noticed both the issues reported by John, and have another to
 add.
 
 When I use the text tool to add a callout inside an anchored frame -
as
 I've done for years with previous versions of FrameMaker - the text
 changes. That is, random letters disappear. I've seen it happen
several
 times, even after saving. But if I place the callout inside a text
frame
 (inside the anchored frame), it's OK.
 
 Has anyone else experienced this feature?
 
 Joyce
 
 
 --
 Jeff Schweiner
 Hardware Engineering Writer
 Cray Inc.
 (715) 726-4801
 
 ___
 
 
 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/syed.hosain%40aeris.
net
 
 Send administrative questions to [EMAIL PROTECTED] Visit
 http://www.frameusers.com/ for more resources and info.
___


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: Upgrade to Frame 8

[Syed.Hosain]

One additional observation:

The previous line where you do the carriage return, has to be shorter
than the next line to see the problem.

I.e., 12345, cr, 1234567890 shows the problem, but 1234567890,
cr, 12345 does NOT.

Z

-
 Syed Zaeem HosainSVP, Engineering 
 Chief Technical Officer

 Aeris Communications, Inc. t: +1 (408) 557-1905
 2680 Zanker Road   f: +1 (408) 557-1925
 San Jose, CA 95134-2100.  [EMAIL PROTECTED]
-


 -Original Message-
 From: Syed Zaeem Hosain ([EMAIL PROTECTED])
 Sent: Wednesday, April 02, 2008 10:05 AM
 To: 'Jeff Schweiner'; framers@lists.frameusers.com
 Subject: RE: Upgrade to Frame 8
 
 I see the same problem ... quite repeatable. Characters get
eliminated from the text line following
 a carriage return (even later entries!).
 
 1. Doing a control-L before the save does NOT show any problems.
 
 2. Starting, saving a file, closing it, and then re-opening the file
(no control-L) shows the problem.
 
 3. A single line by itself (1234567890) does NOT show problem.
 
 Basically, to me, it appears that the act of entering a carriage
return at the end of a textline,
 entering a new line, and saving the file is causing the problem ...
 
 Definitely a bug of some sort!!! Needs a fix.
 
 Z
 
  -Original Message-
  From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
 Of
  Jeff Schweiner
  Sent: Wednesday, April 02, 2008 8:49 AM
  To: framers@lists.frameusers.com
  Subject: Upgrade to Frame 8
 
  Hi Joyce,
 
  I've also experienced this feature and have come across a
repeatable pattern of failure.
  Can others try this and report back whether it fails for them also?
 
  I'm experiencing problems with dropped characters in text lines.
Also, I've noticed the history
  doesn't seem to log all changes made to text lines. The problem can
be duplicated as follows:
 
  1. Open a new portrait blank document and add an anchored frame.
(recorded in history)
  2. Add a text line inside the anchored frame from the Tools Palette.
In the text line, type 1234
  (recorded in history).
  3. Save the file. (history cleared)
  4. Click the cursor after the 4 in the text line and hit a
carriage return to create a new text
  line. (not recorded in history)
  5. In the new text line, type 1234567890(not recorded in history)
  6. Save the file.
  7. Refresh the screen (cntl l) and the second text line now reads
12346890 (dropped the 5 and 7).
  Printing the file in steps 5 and 6 also show the 5 and 7 are
missing.
  8. Add a new text line inside the anchored frame from the Tools
Palette. In the text line, type
  12345 (recorded in history).
  9. Save the file. (history cleared)
  10. Click the cursor after the 5 in the text line from step 8 and
hit a carriage return to create
 a
  new text line. (not recorded in history)
  11. In the new text line, type 1234567890(not recorded in history)
  12. Save the file.
  13. Refresh the screen and the second text line now reads 12345790
(dropped the 6 and 8).
 
  I get this to fail every time running the trial version 8.0p273 on
two different XP SP2 systems.
 
 

 
  Joyce wrote:
 
  All -
 
  I have noticed both the issues reported by John, and have another to
  add.
 
  When I use the text tool to add a callout inside an anchored frame -
as
  I've done for years with previous versions of FrameMaker - the text
  changes. That is, random letters disappear. I've seen it happen
several
  times, even after saving. But if I place the callout inside a text
frame
  (inside the anchored frame), it's OK.
 
  Has anyone else experienced this feature?
 
  Joyce
 
 
  --
  Jeff Schweiner
  Hardware Engineering Writer
  Cray Inc.
  (715) 726-4801
 
  ___
 
 
  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/syed.hosain%40aeris.
net
 
  Send administrative questions to [EMAIL PROTECTED] Visit
  http://www.frameusers.com/ for more resources and info.
___


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.

Upgrade to Frame 8

[Jeff Schweiner]

Hi Joyce,

I've also experienced this "feature" and have come across a repeatable pattern 
of failure.
Can others try this and report back whether it fails for them also?

I'm experiencing problems with dropped characters in text lines. Also, I've 
noticed the history doesn't seem to log all changes made to text lines. The 
problem can be duplicated as follows: 

1. Open a new portrait blank document and add an anchored frame. (recorded in 
history) 
2. Add a text line inside the anchored frame from the Tools Palette. In the 
text line, type "1234" (recorded in history). 
3. Save the file. (history cleared) 
4. Click the cursor after the "4" in the text line and hit a carriage return to 
create a new text line. (not recorded in history) 
5. In the new text line, type "1234567890"(not recorded in history) 
6. Save the file. 
7. Refresh the screen (cntl l) and the second text line now reads "12346890" 
(dropped the 5 and 7). Printing the file in steps 5 and 6 also show the 5 and 7 
are missing. 
8. Add a new text line inside the anchored frame from the Tools Palette. In the 
text line, type "12345" (recorded in history). 
9. Save the file. (history cleared) 
10. Click the cursor after the "5" in the text line from step 8 and hit a 
carriage return to create a new text line. (not recorded in history) 
11. In the new text line, type "1234567890"(not recorded in history) 
12. Save the file. 
13. Refresh the screen and the second text line now reads "12345790" (dropped 
the 6 and 8). 

I get this to fail every time running the trial version 8.0p273 on two 
different XP SP2 systems.



Joyce wrote:

All -

I have noticed both the issues reported by John, and have another to
add.

When I use the text tool to add a callout inside an anchored frame - as
I've done for years with previous versions of FrameMaker - the text
changes. That is, random letters disappear. I've seen it happen several
times, even after saving. But if I place the callout inside a text frame
(inside the anchored frame), it's OK.  

Has anyone else experienced this "feature"?

Joyce


--
Jeff Schweiner
Hardware Engineering Writer
Cray Inc.
(715) 726-4801

Upgrade to Frame 8

[Jim Owens]

I just tried this with my trial FM 8.0p273, and it is exactly as you 
describe.

Jeff Schweiner wrote:

> I've also experienced this "feature" and have come across a repeatable 
> pattern of failure.
> Can others try this and report back whether it fails for them also?
> 
> I'm experiencing problems with dropped characters in text lines. Also, I've 
> noticed the history doesn't seem to log all changes made to text lines. The 
> problem can be duplicated as follows: 
> 
> 1. Open a new portrait blank document and add an anchored frame. (recorded in 
> history) 
> 2. Add a text line inside the anchored frame from the Tools Palette. In the 
> text line, type "1234" (recorded in history). 
> 3. Save the file. (history cleared) 
> 4. Click the cursor after the "4" in the text line and hit a carriage return 
> to create a new text line. (not recorded in history) 
> 5. In the new text line, type "1234567890"(not recorded in history) 
> 6. Save the file. 
> 7. Refresh the screen (cntl l) and the second text line now reads "12346890" 
> (dropped the 5 and 7). Printing the file in steps 5 and 6 also show the 5 and 
> 7 are missing. 
> 8. Add a new text line inside the anchored frame from the Tools Palette. In 
> the text line, type "12345" (recorded in history). 
> 9. Save the file. (history cleared) 
> 10. Click the cursor after the "5" in the text line from step 8 and hit a 
> carriage return to create a new text line. (not recorded in history) 
> 11. In the new text line, type "1234567890"(not recorded in history) 
> 12. Save the file. 
> 13. Refresh the screen and the second text line now reads "12345790" (dropped 
> the 6 and 8). 
> 
> I get this to fail every time running the trial version 8.0p273 on two 
> different XP SP2 systems.
> 

Upgrade to Frame 8

[syed.hos...@aeris.net]

I see the same problem ... quite repeatable. Characters get "eliminated"
from the text line following a carriage return (even later entries!).

1. Doing a control-L before the save does NOT show any problems.

2. Starting, saving a file, closing it, and then re-opening the file (no
control-L) shows the problem.

3. A single line by itself ("1234567890") does NOT show problem.

Basically, to me, it appears that the act of entering a carriage return
at the end of a textline, entering a new line, and saving the file is
causing the problem ...

Definitely a bug of some sort!!! Needs a fix.

Z

> -Original Message-
> From: framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of
> Jeff Schweiner
> Sent: Wednesday, April 02, 2008 8:49 AM
> To: framers at lists.frameusers.com
> Subject: Upgrade to Frame 8
> 
> Hi Joyce,
> 
> I've also experienced this "feature" and have come across a repeatable
pattern of failure.
> Can others try this and report back whether it fails for them also?
> 
> I'm experiencing problems with dropped characters in text lines. Also,
I've noticed the history
> doesn't seem to log all changes made to text lines. The problem can be
duplicated as follows:
> 
> 1. Open a new portrait blank document and add an anchored frame.
(recorded in history)
> 2. Add a text line inside the anchored frame from the Tools Palette.
In the text line, type "1234"
> (recorded in history).
> 3. Save the file. (history cleared)
> 4. Click the cursor after the "4" in the text line and hit a carriage
return to create a new text
> line. (not recorded in history)
> 5. In the new text line, type "1234567890"(not recorded in history)
> 6. Save the file.
> 7. Refresh the screen (cntl l) and the second text line now reads
"12346890" (dropped the 5 and 7).
> Printing the file in steps 5 and 6 also show the 5 and 7 are missing.
> 8. Add a new text line inside the anchored frame from the Tools
Palette. In the text line, type
> "12345" (recorded in history).
> 9. Save the file. (history cleared)
> 10. Click the cursor after the "5" in the text line from step 8 and
hit a carriage return to create a
> new text line. (not recorded in history)
> 11. In the new text line, type "1234567890"(not recorded in history)
> 12. Save the file.
> 13. Refresh the screen and the second text line now reads "12345790"
(dropped the 6 and 8).
> 
> I get this to fail every time running the trial version 8.0p273 on two
different XP SP2 systems.
> 
>

> 
> Joyce wrote:
> 
> All -
> 
> I have noticed both the issues reported by John, and have another to
> add.
> 
> When I use the text tool to add a callout inside an anchored frame -
as
> I've done for years with previous versions of FrameMaker - the text
> changes. That is, random letters disappear. I've seen it happen
several
> times, even after saving. But if I place the callout inside a text
frame
> (inside the anchored frame), it's OK.
> 
> Has anyone else experienced this "feature"?
> 
> Joyce
> 
> 
> --
> Jeff Schweiner
> Hardware Engineering Writer
> Cray Inc.
> (715) 726-4801
> 
> ___
> 
> 
> You are currently subscribed to Framers as Syed.Hosain at aeris.net.
> 
> 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/syed.hosain%40aeris.
net
> 
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.

Upgrade to Frame 8

[syed.hos...@aeris.net]

One additional observation:

The previous line where you do the carriage return, has to be shorter
than the next line to see the problem.

I.e., "12345", , "1234567890" shows the problem, but "1234567890",
, "12345" does NOT.

Z

-
 Syed Zaeem HosainSVP, Engineering &
 Chief Technical Officer

 Aeris Communications, Inc. t: +1 (408) 557-1905
 2680 Zanker Road   f: +1 (408) 557-1925
 San Jose, CA 95134-2100.  Syed.Hosain at aeris.net
-


> -Original Message-
> From: Syed Zaeem Hosain (Syed.Hosain at aeris.net)
> Sent: Wednesday, April 02, 2008 10:05 AM
> To: 'Jeff Schweiner'; framers at lists.frameusers.com
> Subject: RE: Upgrade to Frame 8
> 
> I see the same problem ... quite repeatable. Characters get
"eliminated" from the text line following
> a carriage return (even later entries!).
> 
> 1. Doing a control-L before the save does NOT show any problems.
> 
> 2. Starting, saving a file, closing it, and then re-opening the file
(no control-L) shows the problem.
> 
> 3. A single line by itself ("1234567890") does NOT show problem.
> 
> Basically, to me, it appears that the act of entering a carriage
return at the end of a textline,
> entering a new line, and saving the file is causing the problem ...
> 
> Definitely a bug of some sort!!! Needs a fix.
> 
> Z
> 
> > -Original Message-
> > From: framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf
> Of
> > Jeff Schweiner
> > Sent: Wednesday, April 02, 2008 8:49 AM
> > To: framers at lists.frameusers.com
> > Subject: Upgrade to Frame 8
> >
> > Hi Joyce,
> >
> > I've also experienced this "feature" and have come across a
repeatable pattern of failure.
> > Can others try this and report back whether it fails for them also?
> >
> > I'm experiencing problems with dropped characters in text lines.
Also, I've noticed the history
> > doesn't seem to log all changes made to text lines. The problem can
be duplicated as follows:
> >
> > 1. Open a new portrait blank document and add an anchored frame.
(recorded in history)
> > 2. Add a text line inside the anchored frame from the Tools Palette.
In the text line, type "1234"
> > (recorded in history).
> > 3. Save the file. (history cleared)
> > 4. Click the cursor after the "4" in the text line and hit a
carriage return to create a new text
> > line. (not recorded in history)
> > 5. In the new text line, type "1234567890"(not recorded in history)
> > 6. Save the file.
> > 7. Refresh the screen (cntl l) and the second text line now reads
"12346890" (dropped the 5 and 7).
> > Printing the file in steps 5 and 6 also show the 5 and 7 are
missing.
> > 8. Add a new text line inside the anchored frame from the Tools
Palette. In the text line, type
> > "12345" (recorded in history).
> > 9. Save the file. (history cleared)
> > 10. Click the cursor after the "5" in the text line from step 8 and
hit a carriage return to create
> a
> > new text line. (not recorded in history)
> > 11. In the new text line, type "1234567890"(not recorded in history)
> > 12. Save the file.
> > 13. Refresh the screen and the second text line now reads "12345790"
(dropped the 6 and 8).
> >
> > I get this to fail every time running the trial version 8.0p273 on
two different XP SP2 systems.
> >
> >

> >
> > Joyce wrote:
> >
> > All -
> >
> > I have noticed both the issues reported by John, and have another to
> > add.
> >
> > When I use the text tool to add a callout inside an anchored frame -
as
> > I've done for years with previous versions of FrameMaker - the text
> > changes. That is, random letters disappear. I've seen it happen
several
> > times, even after saving. But if I place the callout inside a text
frame
> > (inside the anchored frame), it's OK.
> >
> > Has anyone else experienced this "feature"?
> >
> > Joyce
> >
> >
> > --
> > Jeff Schweiner
> > Hardware Engineering Writer
> > Cray Inc.
> > (715) 726-4801
> >
> > ___
> >
> >
> > You are currently subscribed to Framers as Syed.Hosain at aeris.net.
> >
> > 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/syed.hosain%40aeris.
net
> >
> > Send administrative questions to listadmin at frameusers.com. Visit
> > http://www.frameusers.com/ for more resources and info.

RE: Upgrade to Frame 8?

[David Kuhn]

There are members on my team with Frame 8 that complain that Frame still
crashes even after p273. I'm still working with version 7.2 and we have
not identified yet what might be causing it to crash.


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp

___


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: Upgrade to Frame 8?

[Yves Barbion]

There are also some issues related to Unicode and special characters.
You'll find them in this framers group if you look for the word bug.

I also found the following bug recently:

   1. Type a word which has special characters like the ë in
   technologieën (which is quite common in Dutch).
   2. Set the dictionary to Nederlands (Dutch) and switch on hyphenation.
   3. FrameMaker 8 cannot hyphenate this word correctly and replaces the
   ë with a question mark; it works fine in FrameMaker 7.2.



On Sat, Mar 22, 2008 at 2:04 PM, Fred Skillman [EMAIL PROTECTED]
wrote:

 I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
 8.0and Acrobat
 8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
 conversions. I see that some of you are having problems with Frame 8  Can
 you comment on your experiences? Is an upgrade worth it?
 Thanks,
 Fred Skillman
 ___


 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/yves.barbion%40gmail.com

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

___


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: Upgrade to Frame 8?

[Michael Müller-Hillebrand]

Hi Yves,

it works with the old Nederlands dictionary (assuming it should be  
hyphenated as technologie-ën) and so it reminds me of the problems  
with the change from German to German (neu) -- the new dictionaries  
were of serious low quality.

It seems to be a technical problem with the adaption of the  
Nederlands (nieuw) dictionary to UTF-8 encoding. Bad.

- Michael

Am 26.03.2008 um 10:27 schrieb Yves Barbion:
 There are also some issues related to Unicode and special  
 characters.
 You'll find them in this framers group if you look for the word bug.

 I also found the following bug recently:

1. Type a word which has special characters like the ë in
technologieën (which is quite common in Dutch).
2. Set the dictionary to Nederlands (Dutch) and switch on  
 hyphenation.
3. FrameMaker 8 cannot hyphenate this word correctly and  
 replaces the
ë with a question mark; it works fine in FrameMaker 7.2.


--
___
Michael Müller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
Lösungen und Training, FrameScript, XML/XSL, Unicode
http://cap-studio.de/ -- Tel. +49 (9131) 28747



___


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: Upgrade to Frame 8?

[Yves Barbion]

Hi Jain,

thank you for your prompt reply.

I'm also using FM 8.0p273. The problem seems to occur only with the 
dictionary Nederlands (nieuw), which is the new spelling of Dutch. It 
doesn't happen with the dictionary Nederlands, but you can remove this 
dictionary from the list because it's no longer used.

Kind regards

Yves Barbion 
Documentation Architect
Adobe-Certified FrameMaker Instructor


Scripto bvba
Asselsstraat 65
9031 Gent
Belgium
T: +32 494 12 01 89
F: +32 9 366 50 23
BTW (VAT) BE 0886.192.394
skype: yves.barbion




Pulkit Jain wrote:
 Yves,

 The problem you have mentioned couldn't be produced on FM 8.0p273. Can you 
 specify which build you are using and if possible can you send across your FM 
 file in which you are having the problem to [EMAIL PROTECTED]

 Thanks,
 Pulkit Jain

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yves Barbion
 Sent: Wednesday, March 26, 2008 2:58 PM
 To: Fred Skillman
 Cc: framers@lists.frameusers.com
 Subject: Re: Upgrade to Frame 8?

 There are also some issues related to Unicode and special characters.
 You'll find them in this framers group if you look for the word bug.

 I also found the following bug recently:

1. Type a word which has special characters like the ë in
technologieën (which is quite common in Dutch).
2. Set the dictionary to Nederlands (Dutch) and switch on hyphenation.
3. FrameMaker 8 cannot hyphenate this word correctly and replaces the
ë with a question mark; it works fine in FrameMaker 7.2.



 On Sat, Mar 22, 2008 at 2:04 PM, Fred Skillman [EMAIL PROTECTED]
 wrote:

   
 I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
 8.0and Acrobat
 8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
 conversions. I see that some of you are having problems with Frame 8  Can
 you comment on your experiences? Is an upgrade worth it?
 Thanks,
 Fred Skillman
 ___


 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/yves.barbion%40gmail.com

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

 
 ___


 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/pulkit%40adobe.com

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


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.

Upgrade to Frame 8?

[David Kuhn]

There are members on my team with Frame 8 that complain that Frame still
crashes even after p273. I'm still working with version 7.2 and we have
not identified yet what might be causing it to crash.


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp

Upgrade to Frame 8?

[Yves Barbion]

There are also some "issues" related to Unicode and special characters.
You'll find them in this framers group if you look for the word "bug".

I also found the following bug recently:

   1. Type a word which has special characters like the ? in
   "technologie?n" (which is quite common in Dutch).
   2. Set the dictionary to Nederlands (Dutch) and switch on hyphenation.
   3. FrameMaker 8 cannot hyphenate this word correctly and replaces the
   ? with a question mark; it works fine in FrameMaker 7.2.



On Sat, Mar 22, 2008 at 2:04 PM, Fred Skillman 
wrote:

> I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
> 8.0and Acrobat
> 8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
> conversions. I see that some of you are having problems with Frame 8  Can
> you comment on your experiences? Is an upgrade worth it?
> Thanks,
> Fred Skillman
> ___
>
>
> You are currently subscribed to Framers as yves.barbion at gmail.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/yves.barbion%40gmail.com
>
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
>

Upgrade to Frame 8?

[Michael Müller-Hillebrand]

Hi Yves,

it works with the "old" Nederlands dictionary (assuming it should be  
hyphenated as technologie-?n) and so it reminds me of the problems  
with the change from German to German (neu) -- the "new" dictionaries  
were of serious low quality.

It seems to be a technical problem with the adaption of the  
Nederlands (nieuw) dictionary to UTF-8 encoding. Bad.

- Michael

Am 26.03.2008 um 10:27 schrieb Yves Barbion:
> There are also some "issues" related to Unicode and special  
> characters.
> You'll find them in this framers group if you look for the word "bug".
>
> I also found the following bug recently:
>
>1. Type a word which has special characters like the ? in
>"technologie?n" (which is quite common in Dutch).
>2. Set the dictionary to Nederlands (Dutch) and switch on  
> hyphenation.
>3. FrameMaker 8 cannot hyphenate this word correctly and  
> replaces the
>? with a question mark; it works fine in FrameMaker 7.2.
>

--
___
Michael M?ller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
L?sungen und Training, FrameScript, XML/XSL, Unicode
 -- Tel. +49 (9131) 28747

Upgrade to Frame 8?

[Yves Barbion]

Hi Jain,

thank you for your prompt reply.

I'm also using FM 8.0p273. The problem seems to occur only with the 
dictionary Nederlands (nieuw), which is the new spelling of Dutch. It 
doesn't happen with the dictionary Nederlands, but you can remove this 
dictionary from the list because it's no longer used.

Kind regards

Yves Barbion 
Documentation Architect
Adobe-Certified FrameMaker Instructor


Scripto bvba
Asselsstraat 65
9031 Gent
Belgium
T: +32 494 12 01 89
F: +32 9 366 50 23
BTW (VAT) BE 0886.192.394
skype: yves.barbion




Pulkit Jain wrote:
> Yves,
>
> The problem you have mentioned couldn't be produced on FM 8.0p273. Can you 
> specify which build you are using and if possible can you send across your FM 
> file in which you are having the problem to pulkit at adobe.com.
>
> Thanks,
> Pulkit Jain
>
> -Original Message-
> From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at 
> lists.frameusers.com] On Behalf Of Yves Barbion
> Sent: Wednesday, March 26, 2008 2:58 PM
> To: Fred Skillman
> Cc: framers at lists.frameusers.com
> Subject: Re: Upgrade to Frame 8?
>
> There are also some "issues" related to Unicode and special characters.
> You'll find them in this framers group if you look for the word "bug".
>
> I also found the following bug recently:
>
>1. Type a word which has special characters like the ? in
>"technologie?n" (which is quite common in Dutch).
>2. Set the dictionary to Nederlands (Dutch) and switch on hyphenation.
>3. FrameMaker 8 cannot hyphenate this word correctly and replaces the
>? with a question mark; it works fine in FrameMaker 7.2.
>
>
>
> On Sat, Mar 22, 2008 at 2:04 PM, Fred Skillman 
> wrote:
>
>   
>> I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
>> 8.0and Acrobat
>> 8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
>> conversions. I see that some of you are having problems with Frame 8  Can
>> you comment on your experiences? Is an upgrade worth it?
>> Thanks,
>> Fred Skillman
>> ___
>>
>>
>> You are currently subscribed to Framers as yves.barbion at gmail.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/yves.barbion%40gmail.com
>>
>> Send administrative questions to listadmin at frameusers.com. Visit
>> http://www.frameusers.com/ for more resources and info.
>>
>> 
> ___
>
>
> You are currently subscribed to Framers as pulkit at adobe.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/pulkit%40adobe.com
>
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
>   

Re: Upgrade to Frame 8? (Fred Skillman)

[Austin Meredith]

Upgrade to Frame 8? (Fred Skillman)

Fred, patch 273 took account of our open issues. We are not having 
any problems at all subsequent to the successful installation of that 
patch. All systems are go with Frame 8.0p273 on a WindowsXP system 
with Service Pack 2. Dive in at the middle and swim both ways.

By the way, does anyone on this list know of a way to suppress the 
gray alert dialog box that warns us that we are converting a FM7 file 
into a FM8 file? Clicking past that gray dialog box a thousand times 
a day does get a tad annoying (since our decision is always to accept 
this conversion)! 


___


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: Upgrade to Frame 8? (Fred Skillman)

[Art Campbell]

I don't think that there's a way to suppress it, but you could
probably buy or create a FrameScript that would let you batch convert
directories or books and have the script acknowledge the warning

Art

On Tue, Mar 25, 2008 at 7:27 AM, Austin Meredith
[EMAIL PROTECTED] wrote:

  Upgrade to Frame 8? (Fred Skillman)

  Fred, patch 273 took account of our open issues. We are not having
  any problems at all subsequent to the successful installation of that
  patch. All systems are go with Frame 8.0p273 on a WindowsXP system
  with Service Pack 2. Dive in at the middle and swim both ways.

  By the way, does anyone on this list know of a way to suppress the
  gray alert dialog box that warns us that we are converting a FM7 file
  into a FM8 file? Clicking past that gray dialog box a thousand times
  a day does get a tad annoying (since our decision is always to accept
  this conversion)!


  ___


-- 
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: Upgrade to Frame 8? (Fred Skillman)

[Rene Stephenson]

What if you use the Open all files in book silently script and then 
shift-alt-F, S?
 
Rene L. Stephenson






- Original Message 
From: Austin Meredith [EMAIL PROTECTED]
To: framers@lists.frameusers.com
Sent: Tuesday, March 25, 2008 7:27:54 AM
Subject: Re: Upgrade to Frame 8? (Fred Skillman)


Upgrade to Frame 8? (Fred Skillman)

Fred, patch 273 took account of our open issues. We are not having 
any problems at all subsequent to the successful installation of that 
patch. All systems are go with Frame 8.0p273 on a WindowsXP system 
with Service Pack 2. Dive in at the middle and swim both ways.

By the way, does anyone on this list know of a way to suppress the 
gray alert dialog box that warns us that we are converting a FM7 file 
into a FM8 file? Clicking past that gray dialog box a thousand times 
a day does get a tad annoying (since our decision is always to accept 
this conversion)! 


___


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/rinnie1%40yahoo.com

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



___


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: Upgrade to Frame 8?

[Mike Wickham]

 I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
 8.0and Acrobat
 8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
 conversions. I see that some of you are having problems with Frame 8  Can
 you comment on your experiences? Is an upgrade worth it?

I upgraded from 7.1 to 8.0. I use unstructured only, 100% PDF output. There 
were some bugs that appear to have been fixed in the latest patch. So, I 
can't think of any bugs that are biting me at the moment.

However, there was a problem with lines not breaking properly after em and 
en dashes in an earlier release. The latest release fixed the problem for 
new em and en dashes, but didn't reset the line breaks for those already in 
the document, that were displaying improperly. I had to do a bookwide find 
and replace, replacing em dashes with em dashes, and en dashes with en 
dashes to cause the lines to reflow properly. All is good from then on.

Mike


___


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.

Upgrade to Frame 8

[Johnson, Joyce]

All -

I have noticed both the issues reported by John, and have another to
add.

When I use the text tool to add a callout inside an anchored frame - as
I've done for years with previous versions of FrameMaker - the text
changes. That is, random letters disappear. I've seen it happen several
times, even after saving. But if I place the callout inside a text frame
(inside the anchored frame), it's OK.  

Has anyone else experienced this feature?

Joyce





Message: 2
Date: Sun, 23 Mar 2008 08:16:47 -0400
From: John Pilla [EMAIL PROTECTED]
Subject: FM 8
To: framers@lists.frameusers.com
Message-ID:

[EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII

Our company just upgraded to FM 8 from FM 7. 

I noticed strange feature behaviours. 

1.)  When I delete a paragraph, the paragraph below the deleted
paragraph 
takes on the properties, the paragraph tag of the paragraph above the 
deleted paragraph. 
This is very annoying, and wastes a lot of extra time in having to 
re-apply a paragraph tag every time a paragraph is deleted! 

2.)  Even though a paragraph tag, universally applied, and not
over-ridden 
has a Next Para Tag of a different one than itself, 
when we press Enter for the new paragraph, the next paragraph is not the

one designated as the Next Para Tag, but the same para tag as the one we

were on when Enter was pressed. 
This, too is most annoying and does not seem to be consistent.  For at 
times it does appear to work; however, I have not been able to nail down

the conditions when it behaves as it should and when it does not. 

Any one know if a patch is coming out for these? 
 
~ John ~ 
Sr. Learning Specialist 
[EMAIL PROTECTED] 
Home Office Phone: +1.603.864.6797   
IBM Tivoli Provisioning and Maximo Enablement 
 
Maximo 5 Certified 
IBM Certified Deployment Professional - Maximo V6 EAM 
IBM Certified Deployment Professional - Maximo V6 ITSM 
Foundation Certificate in IT Service Management 
 


--

___


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.

Upgrade to Frame 8? (Fred Skillman)

[Austin Meredith]

>Upgrade to Frame 8? (Fred Skillman)

Fred, patch 273 took account of our open issues. We are not having 
any problems at all subsequent to the successful installation of that 
patch. All systems are go with Frame 8.0p273 on a WindowsXP system 
with Service Pack 2. Dive in at the middle and swim both ways.

By the way, does anyone on this list know of a way to suppress the 
gray alert dialog box that warns us that we are converting a FM7 file 
into a FM8 file? Clicking past that gray dialog box a thousand times 
a day does get a tad annoying (since our decision is always to accept 
this conversion)! 

Upgrade to Frame 8? (Fred Skillman)

[Art Campbell]

I don't think that there's a way to suppress it, but you could
probably buy or create a FrameScript that would let you batch convert
directories or books and have the script acknowledge the warning

Art

On Tue, Mar 25, 2008 at 7:27 AM, Austin Meredith
 wrote:
>
>  >Upgrade to Frame 8? (Fred Skillman)
>
>  Fred, patch 273 took account of our open issues. We are not having
>  any problems at all subsequent to the successful installation of that
>  patch. All systems are go with Frame 8.0p273 on a WindowsXP system
>  with Service Pack 2. Dive in at the middle and swim both ways.
>
>  By the way, does anyone on this list know of a way to suppress the
>  gray alert dialog box that warns us that we are converting a FM7 file
>  into a FM8 file? Clicking past that gray dialog box a thousand times
>  a day does get a tad annoying (since our decision is always to accept
>  this conversion)!
>
>
>  ___
>

-- 
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

Upgrade to Frame 8? (Fred Skillman)

[Rene Stephenson]

What if you use the "Open all files in book silently" script and then 
shift-alt-F, S?

Rene L. Stephenson






- Original Message 
From: Austin Meredith <ashley_mered...@brown.edu>
To: framers at lists.frameusers.com
Sent: Tuesday, March 25, 2008 7:27:54 AM
Subject: Re: Upgrade to Frame 8? (Fred Skillman)


>Upgrade to Frame 8? (Fred Skillman)

Fred, patch 273 took account of our open issues. We are not having 
any problems at all subsequent to the successful installation of that 
patch. All systems are go with Frame 8.0p273 on a WindowsXP system 
with Service Pack 2. Dive in at the middle and swim both ways.

By the way, does anyone on this list know of a way to suppress the 
gray alert dialog box that warns us that we are converting a FM7 file 
into a FM8 file? Clicking past that gray dialog box a thousand times 
a day does get a tad annoying (since our decision is always to accept 
this conversion)! 


___


You are currently subscribed to Framers as rinnie1 at yahoo.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/rinnie1%40yahoo.com

Send administrative questions to listadmin at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Upgrade to Frame 8?

[Mike Wickham]

> I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
> 8.0and Acrobat
> 8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
> conversions. I see that some of you are having problems with Frame 8  Can
> you comment on your experiences? Is an upgrade worth it?

I upgraded from 7.1 to 8.0. I use unstructured only, 100% PDF output. There 
were some bugs that appear to have been fixed in the latest patch. So, I 
can't think of any bugs that are biting me at the moment.

However, there was a problem with lines not breaking properly after em and 
en dashes in an earlier release. The latest release fixed the problem for 
new em and en dashes, but didn't reset the line breaks for those already in 
the document, that were displaying improperly. I had to do a bookwide find 
and replace, replacing em dashes with em dashes, and en dashes with en 
dashes to cause the lines to reflow properly. All is good from then on.

Mike

Upgrade to Frame 8

[Johnson, Joyce]

All -

I have noticed both the issues reported by John, and have another to
add.

When I use the text tool to add a callout inside an anchored frame - as
I've done for years with previous versions of FrameMaker - the text
changes. That is, random letters disappear. I've seen it happen several
times, even after saving. But if I place the callout inside a text frame
(inside the anchored frame), it's OK.  

Has anyone else experienced this "feature"?

Joyce





Message: 2
Date: Sun, 23 Mar 2008 08:16:47 -0400
From: John Pilla 
Subject: FM 8
To: framers at lists.frameusers.com
Message-ID:


Content-Type: text/plain; charset="US-ASCII"

Our company just upgraded to FM 8 from FM 7. 

I noticed strange "feature" behaviours. 

1.)  When I delete a paragraph, the paragraph below the deleted
paragraph 
takes on the properties, the paragraph tag of the paragraph above the 
deleted paragraph. 
This is very annoying, and wastes a lot of extra time in having to 
re-apply a paragraph tag every time a paragraph is deleted! 

2.)  Even though a paragraph tag, universally applied, and not
over-ridden 
has a Next Para Tag of a different one than itself, 
when we press Enter for the new paragraph, the next paragraph is not the

one designated as the Next Para Tag, but the same para tag as the one we

were on when Enter was pressed. 
This, too is most annoying and does not seem to be consistent.  For at 
times it does appear to work; however, I have not been able to nail down

the conditions when it behaves as it should and when it does not. 

Any one know if a patch is coming out for these? 
 
~ John ~ 
Sr. Learning Specialist 
John.Pilla at us.ibm.com 
Home Office Phone: +1.603.864.6797   
IBM Tivoli Provisioning and Maximo Enablement 
 
Maximo 5 Certified 
IBM Certified Deployment Professional - Maximo V6 EAM 
IBM Certified Deployment Professional - Maximo V6 ITSM 
Foundation Certificate in IT Service Management 
 


--

Upgrade to Frame 8?

[Fred Skillman]

I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
8.0and Acrobat
8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
conversions. I see that some of you are having problems with Frame 8  Can
you comment on your experiences? Is an upgrade worth it?
Thanks,
Fred Skillman
___


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.

Upgrade to Frame 8?

[Fred Skillman]

I am looking at upgrading from Frame 7.0/7.1, Acrobat 7.0 Pro to Frame
8.0and Acrobat
8.0 Pro. Our output is 90% pdf, but we do use ePub Pro for our online help
conversions. I see that some of you are having problems with Frame 8  Can
you comment on your experiences? Is an upgrade worth it?
Thanks,
Fred Skillman

For ePub 9.2 Users who want to upgrade to Frame 8

[Flato, Gillian]

For all of you who want to upgrade to Frame 8 and who use ePub 9.2...

Frame 8 is NOT compatible with ePub 9.2. 

It is also not compatible with Frame 7 files made from Frame 8. In other
words, you can't have Frame 8 on the Tool, save your files as Frame 7,
and then expect ePub to work. It won't.

ePub 9.3 is scheduled to be out by the end of August. ePub 9.3 WILL be
compatible with Frame 8.

Thank you,

 

mailto:[EMAIL PROTECTED] 

Gillian Flato

Technical Writer (Software)

nanometrics

1550 Buckeye Dr. 

Milpitas, CA. 95035

(408.545.6316

7  408.232.5911

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

 
___


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.

For ePub 9.2 Users who want to upgrade to Frame 8

[Flato, Gillian]

For all of you who want to upgrade to Frame 8 and who use ePub 9.2...

Frame 8 is NOT compatible with ePub 9.2. 

It is also not compatible with Frame 7 files made from Frame 8. In other
words, you can't have Frame 8 on the Tool, save your files as Frame 7,
and then expect ePub to work. It won't.

ePub 9.3 is scheduled to be out by the end of August. ePub 9.3 WILL be
compatible with Frame 8.

Thank you,



<mailto:gflato at nanometrics.com> 

Gillian Flato

Technical Writer (Software)

nanometrics

1550 Buckeye Dr. 

Milpitas, CA. 95035

(408.545.6316

7  408.232.5911

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