Thanks Brian. That explains it - it renders like html so I didn't even
think of it being rtf.  Like I said, it's not a big deal but it was
something I had always scratched my head over.

At least with that in the pasted text - it's very easy to spot where I need
to make sure it is italics.

On Mon, Jan 26, 2015 at 10:16 PM, Brian/Support <[email protected]>
wrote:

> Legacy does not use HTML codes for special attributes like Italic, bold
> etc. We use the coding scheme used in RTF format reports in all our text
> coding except HTML Reports and Web pages.The RTF re recognized by most
> word processors.
>
> Brian
> Customer Support
> Millennia Corporation
> [email protected]
> http://www.LegacyFamilyTree.com
>
> On 26/01/2015 10:59 PM, Jackie King wrote:
> > Actually we are talking about Legacy.  When I do a source in Source
> Writer
> > and then go to copy it for Wikitree - i go to the detail - then the
> > overrides tab, it gives me the source nicely written out - and I SHOULD
> be
> > able to just cut and paste it but I get the crazy Ital -
> >
> > "Attention!," \i Washington Federalist\i0, 10 Dec 1800, p. 2; digital
> > images, \i GenealogyBank.com\i0  (http://www.genealogybank.com :
> accessed
> > 18 Mar 2012), Historic Newspapers.
> >
> > So I copy and paste it anyway but have to change the ital markings. It's
> > not a big thing but it does take extra time and I had just never seen
> html
> > done that way and wondered which version of HTML Legacy was using.
> >
> > If I copy and paste just from the normal printout - I still have to put
> in
> > the Ital markings because wiki doesn't recognize the italics until you
> put
> > in the html script.
> >
> > Jackie
> >
> > On Mon, Jan 26, 2015 at 9:48 PM, Pat Hickin <[email protected]> wrote:
> >
> >> I don't quite understand this part of your email -- what do you mean by
> "i
> >> can just pull the source within my database"?
> >>
> >> "But this brings up an interesting question - I choose to footnote my
> >> bios - and for sourcing i can just pull the source within my database
> with
> >> one problem. Until Legacy I had never seen an html italic done as /i
> >> instead of an i surrounded by carets.  I have to change those which
> slows
> >> things down.  Can anyone tell me where the /i comes from?"
> >>
> >> But couldn't you just copy whatever from Legacy into your word processor
> >> and do a search and replace and *then *paste into Wikitree?
> >>
> >> Unless we're talking about Legacy I suppose we should carry on this
> >> conversation outside of the LUG email group.
> >>
> >> Pat
> >>
> >> On Mon, Jan 26, 2015 at 9:40 PM, Jackie King <[email protected]>
> wrote:
> >>
> >>> Pat -
> >>>
> >>> You and I share the Pricketts and I also post to Wikitree.
> >>>
> >>> I began posting before they allowed inline photos and I have chosen to
> >>> add my photos in the photo area which means I can share them between
> people
> >>> a bit easier.
> >>>
> >>> I have also chosen to hand enter my data - which as you say makes it a
> >>> lot slower but in doing so I find errors in my database that for one
> reason
> >>> or another I didn't catch before.
> >>>
> >>> But this brings up an interesting question - I choose to footnote my
> bios
> >>> - and for sourcing i can just pull the source within my database with
> one
> >>> problem. Until Legacy I had never seen an html italic done as /i
> instead of
> >>> an i surrounded by carets.  I have to change those which slows things
> >>> down.  Can anyone tell me where the /i comes from?
> >>>
> >>> Jackie
> >>>
> >>> On Mon, Jan 26, 2015 at 8:14 PM, Pat Hickin <[email protected]> wrote:
> >>>
> >>>> I am posting a lot of family data on Wikitree, whichn doesn't import
> >>>> events in any sort of very readable format.
> >>>>
> >>>> They do have a section where you can have an essay, pictures, and
> >>>> sources.
> >>>>
> >>>> I'd love some ideas for the best way to transfer information from
> Legacy
> >>>> to Wikitree?
> >>>>
> >>>> So I've been creating an individual report (without sources so that I
> >>>> won't have to cope with footnote numbers), copying it to my word
> processor,
> >>>> editing it, copying it into Wikitree.  (Then at some point I add the
> >>>> images, etc.)
> >>>>
> >>>> Then I create an individual report *with* sources, copy the sources to
> >>>> my word processor, edit them, and copying that as well into Wikitree.
> >>>>
> >>>> Does post to Wikitree or have any ideas *in re* the best way to
> >>>> accomplish this?  Needless to say, it's tedious and time-consuming --
> >>>> though I also find it fun to do.
> >>>>
> >>>> Here is one I did for a 4x gr-grand-father.
> >>>> http://www.wikitree.com/index.php?title=Prickett-2&public=1
> >>>>
> >>>> I'll really appreciate suggestions/ideas, etc.
> >>>>
> >>>> Pat
> >>>>
> >>>>
> >>>> Legacy User Group guidelines:
> >>>> http://www.LegacyFamilyTree.com/Etiquette.asp
> >>>> Archived messages after Nov. 21 2009:
> >>>> http://www.mail-archive.com/[email protected]/
> >>>> Archived messages from old mail server - before Nov. 21 2009:
> >>>> http://www.mail-archive.com/[email protected]/
> >>>> 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
> >>>
> >>>
> >>>
> >>>
> >>> Legacy User Group guidelines:
> >>> http://www.LegacyFamilyTree.com/Etiquette.asp
> >>> Archived messages after Nov. 21 2009:
> >>> http://www.mail-archive.com/[email protected]/
> >>> Archived messages from old mail server - before Nov. 21 2009:
> >>> http://www.mail-archive.com/[email protected]/
> >>> 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
> >>>
> >>
> >>
> >>
> >> Legacy User Group guidelines:
> >> http://www.LegacyFamilyTree.com/Etiquette.asp
> >> Archived messages after Nov. 21 2009:
> >> http://www.mail-archive.com/[email protected]/
> >> Archived messages from old mail server - before Nov. 21 2009:
> >> http://www.mail-archive.com/[email protected]/
> >> 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
> >>
> >
> >
> >
> >
> > Legacy User Group guidelines:
> >
> > http://www.LegacyFamilyTree.com/Etiquette.asp
> >
> > Archived messages after Nov. 21 2009:
> >
> > http://www.mail-archive.com/[email protected]/
> >
> > Archived messages from old mail server - before Nov. 21 2009:
> >
> > http://www.mail-archive.com/[email protected]/
> >
> > 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
> >
>
>
>
>
> Legacy User Group guidelines:
>
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> Archived messages after Nov. 21 2009:
>
> http://www.mail-archive.com/[email protected]/
>
> Archived messages from old mail server - before Nov. 21 2009:
>
> http://www.mail-archive.com/[email protected]/
>
> 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
>
>




Legacy User Group guidelines:

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

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/[email protected]/

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

http://www.mail-archive.com/[email protected]/

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