Family Historian User Group

After export with Gedcom Export to Legacy FT 2.5.4. The CHAN records are indeed removed.

But, the <x> I looked at are not converted.

Ron

Fascinating, confirms what I thought that FH was reading the gedcom file into memory in order to have the relational structures it needs. Cleverly written for speed. I suppose memory may be a constraint with really large files then, but there's always SSD's for paging/cache file. I have SSD for soft...

For my usage, don't worry about the HTML. I just ran a test and was able to convert the few characters I used quite easily. Looked fine in Legacy. However other users might use more of them, but I doubt there are many users making the 'round trip' as you put it, like I am.

Ron

OK, understood. So likely I may have to redo my initial export. Was considering doing that anyway. I can't be sure, but doubt my data uses many of the additonal characters. I will look over your Knowledge Base article carefully before doing a second migration, if I choose to do that. Is the FH unico...

Interesting...I was in RJ TextEd 'text' mode, and just tried loading the gedcom in MS Wordpad and Word, and none display the <b> code. Tried Windows Default, Western European. I must be missing something. Exported in ANSEL, first in the dropdown, neither ANSI nor UTF-8. Guess I should pay more atten...

That was quick. Not that FH really needs any more speed than it already has. One the primary reasons I'm switching to it from Legacy Family Tree. Thanks Mike. p.s.- Also noticed Lua SQL is used, isn't it. Oh, and the Lua site somewhere noted,..never type LUA, sounds to awkward or something, supposed...

Downloaded the trial for Family Historian V6 and purchased for Windows 7 64bit laptop. The installer placed the program files in C:\Program Files (x86)\Family Historian\Program\ folder. Curious, since have read that it is available in both 32 bit and 64 bit version (the LUA site): Where Lua Is Used:...

I checked Legacy (original HTML bolded text) with a couple export options. If you tick to embed, but don't tick toconvert html, then you get different codes. 0 @NI9121@ NOTE 1 CONC ÙCbÙDTop of the KRZMARZICK Tree, a place for HISTORY from various sources.ÙC/bÙD 1 CONT 1 CONT ÙCbÙDEXCERPT from Peggy ...

OK, I think I finally understand the issue. FH doesn't recognize either << >> or <>, so no change in FH handling. Exporting from my original pre-FH Legacy file without the ticked HTML code box, but with the 'embed' still on, then FH export back to LFT and all would be still HTML in Legacy. And TNG w...

I have resolved the problem with LFT Legacy FILE-REL mode. It was caused by a conflict between its particular rules for handling NOTE records for Research and Medical tabs, and the generic rules for handling Media NOTE Link/Note Captions. So Legacy will now behave the same as all other products reg...

Thanks for the information re:link/note captions. Hate to bring it up, since a small matter. Any luck on the html behavior? I say small because upon export to TNG, it looks fine, which is of most importance to me. Legacy on my laptop is for my eyes only. Just curious, because before export to FH, Le...

So my strategy for LFT and TNG is to continue using Gedcom Export 2.5.3 (rather than 2.5.2) until official release, of course realizing it is still in prototype/beta form. I will use FILE-REL with the earlier options set to my needs. So, once LFT code for captions is corrected to include them, I wil...

Well, I refreshed my thumbnails (regenerated them), re-imported the edited FILE-REL file, and now only getting legitimate errors within TNG. Not sure why that is, but right now this TNG procedure works.

Good.

Ron

The FILE-REL option, after fairly quick and easy editing to remove 'caption note:' from all NOTE, CONC, and CONT records, looks pretty good, though at first I thought not. In TNG, received 2950 errors on thumbnail generation, yet all thumbnails display properly since I have always created and placed...

Yes, I do realize and fully appreciate the considerable coding effort to accomodate all the options. I worked with assembler language back in the 70's ;>) So what language is this, 'C' ? TNG is php, and know just enough to be dangerous. Well, using the FULL-LMO 2.5.3 option and fixup with RJ TextEd ...

No problem...I actually learned a bit from the response and the bit about v.2.4 made sense as to the lockup, which happened again btw. Perhaps I may have misunderstood your complaint about the Caption Note: text. Is it just the Caption Note: label itself that you don't like, and all the subsequent n...

I gave the 2.5.3 FULL-LMO (to TNG) a try, and output from FULL-LMO included the media objects and copied all media files into the EXPORT folder (which I don't use or need), and the gedcom still included the 'CAPTION' labels. The reason I preferred the 2.4 FILE-REL is because only the links were expo...

Whew, a lot to wade through there, but glad you found an explanation for what happened. I had assumed the FH main file was OK. A couple observations: This modfied how Media Notes included Caption Note: and Picture Note: text. To get those benefits you added Link/Note Captions to many Media records. ...

As explained in Knowledge Base > Output Media Style the only option that includes EVERY Caption Note is FULL~ABS Full Frame Media Records. I have never chosen the the FULL-ABS Full Frame option; always use (File-Rel)-multimedia via Rel Links), since I handle all media file copying myself. However, ...

OK, did find a backup...

Thanks,

Ron

Somehow the FH file appears to have been corrupted, at least for export gedcom plugin usage. I rebuilt from an original Legacy export file and the plugin runs. I did not data input today except running the plugin repeatedly. Concerned now about the long term usage of FH, since the 'validate' routine...

Hmm...Strangest item yet, now gedcom export plugin doesn't seem to run. I select it, the opening screen appears, I hit 'run' and it locks up, with an indication it is 'running' to the right of the plugin name. I have to close the plugin window from windows 'close' and then returned to FH and all is ...

Note: This post belongs in the TNG export, but appended to this thread since we were working on the export for Legacy FT. Well, now even more confusion re: TNG caption note issue. I tried gedcom export tng 2.53, w options set and with default options set, and even version 2.5, all with the 'caption'...

Note: This post belongs in the TNG export, but appended to this thread since we were working on the export for Legacy FT. Whoops, now something new, using version 2.5.3 Export to TNG. Seeing this which wasn't there before, but I will have to verify. Note the caption note prefix on every line of pict...

Your 2nd screenshot is nothing to do with either of the above. It shows the FH Note record appended subsidiary fields that Legacy does not support. In this case the CHANged Date/Time of the Note record itself. If you inspect that Note record in FH Records Window you will see its Updated timestamp. ...