I've noticed this problem for quite some time now and was hoping that recent updates might have corrected the issue but the problems still remain. I'll try to keep this post simple and not overcomplicate the issue but I'm afraid that in describing it, it does get complicated.
There are two problems. I'll keep this post about only one of the problems to keep things simple for now. (1) Some source citations contain an extraneous "\iO" after any text in italics, which HTML savy people will recognize as an erroneous method of turning off the italics font attribute (should be merely "/I"). Notice the backslash instead of the forward slash and the trailing letter O which I have no idea why it appears there. Here is an example. This post to LUG is in plain text but the words "FamilySearch" appears in italics as does "index and images". This example comes from GEDCOM output and appears on Ancestry's servers. Title: 1880 U.S. census, FamilySearch\i0, index and images Publication: https://familysearch.org/search/collection/1417683: National Archives and Records Administration, n.d. Page: T9, roll 0398, Gore Township, Sumner County, Kansas, enumeration district (ED) 189, p. 8D, dwelling 64, family 67,... This problem occurs on each and every citation of a Census event. And as stated, since this example is coming from a GEDCOM on Ancestry's servers, I'm not exactly 100% that the problem lies with Legacy's creation of the GEDCOM, or Ancestry's interpretation and display of the GEDCOM data. When I create WEB PAGES from within Legacy, there is no problem with the extraneous info on any census event. However, even within the WEB PAGES created by Legacy, I find the extraneous info in the following citation: Find A Grave\i0, digital images (http://www.findagrave.com/ : accessed 9 Jan 2014), http://www.findagrave.com/cgi-bin/fg.cgi?page=gr&GRid=33135636... On this example, everything appears in italics. As a title to the web site, you'd expect Find A Grave to be in italics but the \iO does NOT turn off italics and therefore everything else appears in italics. Since the problem is duplicated in Legacy's own WEB PAGES, I'd say that it is not a problem with Ancestry's interpretation and display of any GEDCOM that is the cause of the problem, but rather it originates from within Legacy. Why the census events come out OK on WEB PAGES and not on GEDCOM output is beyond me but I know that Legacy has some special routines for recognizing census events and manipulating the data. Anyone care to take the effort to duplicate the problem? Anyone from support care to chime in? Brian in CA 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
