Brian:

New Update 473 "fixed" the problem, but introduced another one.  I wanted
to bold and underline "Eliza Jane', and after saving, here's what I got:
"\ulEliza Jane\ulnone"  When I tried just to bold it, it worked.  The
problem appears to only be when trying to underline.

Gene
===================

On Thu, Feb 26, 2015 at 2:32 PM, Brian/Support <br...@legacyfamilytree.com>
wrote:

> The problem you reported below has been fixed and will be available in
> the next update to Legacy 8.0. I do not know when that update will be
> issued. You can check for updates by selecting the Legacy Home tab. The
> updates section will tell you when a new update is available and, if you
> have the deluxe version, allow you to update from within Legacy.
> Standard version users will have to obtain the update from our web site.
>
> Brian
> Customer Support
> Millennia Corporation
> br...@legacyfamilytree.com
> http://www.LegacyFamilyTree.com
>
> On 26/02/2015 1:49 PM, Gene Wheeler wrote:
> > I'm using v8.0.0.467, Win7.  This latest release has introduced a problem
> > in creating event notes.  When I try to highlight a portion of a sentence
> > by making it bold and/or underlined, a couple of extra spaces are
> > introduced before that portion of the sentence as well as after it, but
> > before the comma or semicolon leading to the rest of the sentence.  This
> > has not happened before.  Those extra sentences are also underlined if
> u/l
> > is used.
> >
> > Does anyone else see this happening?  For example:
> >
> > He was head of a household that included his wife, Elza, age 39; and
> > children Samantha, age 17;...etc.  This becomes: He was head of a
> household
> > that included his*  wife, Elza, age 39 *; and children Samantha, age
> > 17..... etc.
> >
> > This unfortunate error occurs only after one saves the event.  Opening it
> > again will display the problem.  This error is repeatable.  It does not
> > appear when I open an existing event that already has some highlighting
> of
> > this type.  However if I undo the highlighting there, and then redo it,
> the
> > error appears.  Thus it appears to me that the problem was introduced by
> > release 467.
> >
> > Gene
> >
> >




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

Online technical support: http://support.legacyfamilytree.com

Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).

To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Reply via email to