* Gedcom Export to Legacy FT

[ronk]

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 picture description.

Will try v.2.5 next.

1.jpg (122.43 KiB) Viewed 9731 times

Ron

[ronk]

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' prefix remaining. However, I had a gedcom created on Feb 26 which did not.

As you can see from the prior message, the caption prefix appears on every line, whereas before it didn't exist at all. Am I doing something wrong? Or were there possibly some changes since Feb 26 to the plugin? I will do more checking but right now I'm stumped.

Ron

[ronk]

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 well. This was after re-downloaded successfully the 2.5 plugin from Feb 25th. Other plugins seem to run OK. Hovering over desktop (Windows 7) shows a 2nd plugin window which is shown below.

I've made no changes to FH today at all. Rebooting didn't help. Cant export with the plugin at all

1.jpg (80.26 KiB) Viewed 9717 times

2.jpg (119.88 KiB) Viewed 9716 times

Ron

[ronk]

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 detected no errors along the way. I've lost 2 hours of Live data input from yesterday, which is a lesser concern. Fortunately I've not gone 'Live' yet to TNG. I've only exported to TNG on my 'Wamp' Windows based server emulation for testing so far.

Any ideas? I had thought the plugin is a 'readonly' as far as the FH files are concerned, so don't know what could have happened. All the other plugins I've tried (less than 10) run OK, it seems.

Update: Found a backup which seems to work.

Ron

[tatewise]

I will double-check the Plugin tomorrow. Bear in mind it is a prototype version under test here before publishing publicly.

As explained in plugins:help:export_gedcom_file:output_media_style|> Output Media Style the only option that includes EVERY Caption Note is FULL~ABS Full Frame Media Records.

Yes, this Plugin should only read the FH GEDCOM file.

On a point of fact. You have performed data entry today by editing the Named Lists, which are saved in the GEDCOM File.

You can add to fhugdownloads:index|> Downloads and Links via fhugdownloads:add_downloads|> How to Add Downloads and Links. Don't worry if you don't get all the details just right, as any of the Moderators can make corrections.

[ronk]

OK, did find a backup...

Thanks,

Ron

[ronk]

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, using 2.5.3 or 2.5, I'm still seeing 'caption' text in the output. I know this worked the first time I used the plugin a few days ago.

1.jpg (128.14 KiB) Viewed 9700 times

I finally 'unfroze' the export plugin by deleting the 'plugin data' folder in the project. Not sure how the plugin data folder got messed up.

Point taken about FH gedcom modification as I did delete the namelists earlier, ..thought maybe that was kept in settings. Also, sorry, your are right about the 'pre-release' nature of the plugin. Actually, the data I input was 'pre-live' so to speak, since it the first real test of actual data input. Up until now just importing and getting familiar with the various screens.

I may have overreacted when the lockup occurred perhaps.

Anyway, still having an issue with the TNG export caption text. Your help has been appreciated.

Ron

[tatewise]

Ron, I think I can explain what has been happening.

When we started this journey the Plugin was at Version 2.4.
That would have included all Link/Note Captions in FILE~REL mode (although they did not have the Caption Note: labels then).
However, your Projects did NOT have Link/Note Captions at that time, so nothing would have appeared in the TNG exported Media records.

We then explored LFT exports and updated the Plugin to Version 2.5.
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.
In an oversight by me in FILE~REL mode, the Plugin excluded all Link/Note Captions for each Media record that had any link with a Part (Face/Detail) Frame defined. But if a Media record has no Part Frame links, then all those new Link/Note Captions will get included as Caption Note: text. This is in line with the Plugin concept of trying to include as much of the FH database as possible.

The current Plugin prototype Version 2.5.3 has added some new rules for LFT style Note record tabs.
On reverting back to earlier Plugin versions, those new rules may have confused the Plugin Data > Export Gedcom File.dat file in which the Rule Options are preserved, and that is what caused the frozen Plugin problem. I have occasionally had a similar problem with Plugins that change their Plugin Data. Deleting the associated .dat file resolves the problem, and effectively that is what you did by deleting the whole folder. The Project Gedcom file was never affected.

I need to fix the FILE~REL oversight mentioned above before releasing the Plugin.

However, you need a solution to your Caption Note: scenario for TNG.
One option is to use the same strategy as for LFT and use the images exported by the Plugin to upload to TNG, which is what other TNG users appear to do, using the method in the Help and Advice.
An alternative may be to use FULL~LMO mode, which solves the Caption Note: problem. There are no Media records, but each Local Media Object has a FILE tag link to the absolute path of the Media file.
I presume in FILE~REL mode, you converted each Media record FILE tag relative file path to a TNG file path.
In FULL~LMO mode, you would convert each LMO FILE tag absolute file link to a TNG Media file path.
Would that work?

[ronk]

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.

Actually, no, very few link/note Captions were added. Except for the data input I mentioned (clumsily added, since still gaining familiarity with the product), nothing changed since import from LFT.

An alternative may be to use FULL~LMO mode, which solves the Caption Note: problem. There are no Media records, but each Local Media Object has a FILE tag link to the absolute path of the Media file.
I presume in FILE~REL mode, you converted each Media record FILE tag relative file path to a TNG file path.
In FULL~LMO mode, you would convert each LMO FILE tag absolute file link to a TNG Media file path.
Would that work?

I will try the FULL-LMO mode, if it doesn't export media records (I thought it did), but still includes a media link. After export (from Legacy before) any media paths are ignored when I import to TNG. I manually, by my own keywords, put them in appropriate folders for TNG. One reason I handle this myself is I apply watermarks outside FH (or Legacy), then FTP the files to the proper folders on my host.

In the export to LFT, I use the FILE-REL, because the same media folders are used as for FH, and that works fine.

Thanks again.

[ronk]

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 exported and it didn't include the 'CAPTION' labels (and of course the export is speedy).

In an oversight by me in FILE~REL mode, the Plugin excluded all Link/Note Captions for each Media record that had any link with a Part (Face/Detail) Frame defined. But if a Media record has no Part Frame links, then all those new Link/Note Captions will get included as Caption Note: text.

Is this to say I will have a similar CAPTION label issue with LFT export as well, when the 'oversight' is corrected?

Ron

[tatewise]

I must sincerely apologise Ron. I have mixed you up with the other Ron (rfield) who prompted the Caption Note: and Picture Note: changes in Plugin V2.5.

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 note text following the label is perfectly OK?

If that is all, then your prowess with RJ TextEd should be able to swiftly eliminate those labels.

FILE~REL (and all other Media modes) should work the same way regardless of the target product (LFT or TNG).

BTW: Regarding exporting the image files, the Plugin is only 'slow' on the first export. Subsequently, it only exports files that have changed since the previous export as explained in plugins:help:export_gedcom_file:the_faq|> Export Gedcom File ~ Frequently Asked Questions.

[ronk]

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 note text following the label is perfectly OK? If that is all, then your prowess with RJ TextEd should be able to swiftly eliminate those labels. FILE~REL (and all other Media modes) should work the same way regardless of the target product (LFT or TNG).

A bit confused, perhaps by the versions. Even with 2.5.3, caption labels were not exported with LFT FILE-REL option, but they are with the TNG option, but weren't with version 2.4. And, yes, I was going to remove them with RJ TextED, but saw the additional lines there with the FILE-REL. I can remove them as well and test that.
1 NOTE Caption Note:
1 CHAN
2 DATE 25 FEB 2016
3 TIME 14:09:40

However, with the FULL-LMO option, only the first label is there, but not the CHAN items.

1 NOTE Caption Note:

So, may try both options to see if they yield same results in TNG>

[tatewise]

Now we are on the same wavelength, I will investigate why there are differences between LFT and TNG in FILE~REL mode. It may be associated with my 'oversight' mentioned earlier. Will let you know what I discover.

As you are perhaps realising, it is quite a complex Plugin having to cope with so many Gedcom dialects.

[ronk]

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 failed for me. Not because of the 'Caption' labels; I removed them, but the filenames have prefixes on them like '0O154' in sequence throughout. I cannot remove them with the editor. Maybe I have a setting missed or something?

I was curious on the caption label, how is anyone else using those within TNG? Perhaps naive, but could their be an option (yet another) to not export them?

I'm going to now try working with the editor on the other FILE-REL 2.5.3 export gedcom.

Ron

[ronk]

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 thumbnails myself. I do this because TNG is a bit fussy on thumbnail file sizes and I use EZthumb to create them. I just usually don't get any errors.

I suspect something different in the gedcom is causing this, don't know what, just will be a bit difficult to ferret out legitimate errors.

So, some progress with 2.5.3,..but with version 2.4 I didn't have to edit, and had no thumbnail errors except legitimate ones.

Ron

[ronk]

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

[tatewise]

When reviewing the original V2.4 to V2.5 changes I discovered that V2.4 mishandled Link/Note Caption text. When more than one in a single Media record, it did not collect them all together, with one at the beginning of the Media Note and the rest later after any Picture Note:, etc. So that neeeded to be fixed, and adding the Caption Note: label was the easiest solution, and made them consistent with all the other labelled Note text used extensively throughout.

I suspect users who export to TNG, like most FH users, do NOT use Link/Note Caption text much, if at all. It is only rarely needed in native FH Projects to override the default image captions produced by FH in Reports.

When you start using FH more comprehensively, your Media records will gain Media Dates, Picture Notes, and Keywords, each of which will produce labelled text in exported Media Notes.

[ronk]

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 will likely need to use same editing procedure with the export LFT gedcom as I did with TNG, right?

As to my media, my import brought in no 'picture notes', only 'picture titles' and at this time don't plan on using it. However, I do use 'link notes' quite a bit, which in Legacy were below the picture title. These were essentially my 'picture notes'. They are bit less visible in FH than Legacy, seemingly buried down in an expandable pop up window.

Thanks,

Ron

[tatewise]

You are largely correct.

Regarding the visibility of Link/Note Captions, if you drill down to that Edit Media Item dialogue from the Media tab, then its Link/Note Caption should appear in the unlabelled box bottom left. Tick the Use Note as Caption option and it gets visibly added to the thumbnails in the Media tab. It also replaces the FH generated image caption in Reports.

[ronk]

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, Legacy did display html properly. It's note page does have a side option to 'strip html' but that wouldn't help.

Thanks again, I now have workable procedures to export to both to Legacy and TNG.

Ron

Update: I read the post http://www.fhug.org.uk/forum/viewtopic.php?f=32&t=11903 and see HTML and text formatting is a bit of a sore spot with some users.

I see also html code is not recognized within FH either, so that's fine, as long as I can continue to enter it in the few situations I use it so it looks a bit better in TNG . Don't spend any time on it. I expect someday FH may support it.

[tatewise]

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 regarding Media.

Regarding Legacy HTML codes, it has an export option to Convert formatting codes to HTML style that I presume you have selected?
For example that converts «b»Bold Text«/b» to <b>Bold Text</b>.
So to get those codes back into Legacy requires the reverse mapping.
i.e. < becomes « and > becomes » but only where they occur in pairs.
Is that something you can easily perform, or should it be incorporated into the Plugin?

I am considering whether to remove the Update CHAN timestamps from Legacy Note records, but conditional on the Extra Options setting for Update 1 CHAN being Remove entirely which would remove the timestamps from all other records too?

[ronk]

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 regarding Media.

OK, will give that a test, to see if my edit routine will be the same as with TNG export.

Regarding Legacy HTML codes, it has an export option to Convert formatting codes to HTML style that I presume you have selected?
For example that converts «b»Bold Text«/b» to <b>Bold Text</b>.
So to get those codes back into Legacy requires the reverse mapping.
i.e. < becomes « and > becomes » but only where they occur in pairs.
Is that something you can easily perform, or should it be incorporated into the Plugin?

1.jpg (65.03 KiB) Viewed 9593 times

Yes I select as shown here. You're probably right about the need to be reverse the pairs. I believe I could do it with RJ TextEd, would have to see how to do regular expressions to find the pairs. If not difficult would be nice to have in the LFT plugin. Why doesn't TNG have this issue with html code, is it doing the reversing perhaps on an assumption maybe?

I am considering whether to remove the Update CHAN timestamps from Legacy Note records, but conditional on the Extra Options setting for Update 1 CHAN being Remove entirely which would remove the timestamps from all other records too?

Having that option for LFT export would be good. I don't see Legacy using the timestamps. BTW..in both LFT and TNG export, removed ticks as noted:

2.jpg (172.1 KiB) Viewed 9593 times

Let me know if you wish me to pursue editing the reverse map; might be interesting.

Thanks,

Ron

[tatewise]

OK, give me a day or so to sort out the changes.

TNG does not have the problem because it uses the HTML characters < and > in their native form. It is only Legacy that demands the special characters « and » (presumably to avoid any conflict with genuine < and >) and translates them when outputing HTML scripts.

If you do not use that Legacy export HTML option then the « and » appear in the Gedcom file and will import back into Legacy.

[ronk]

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 would recognize either, I presume.

Hmm..I could do that, ..all I would lose would be the data input to FH since my original export, which I have a way to recover that I think.

Another approach to save data; I can check, but does FH permit exporting just a branch, and then re-importing later? Then I could do this fairly easily.

I'm willing to do either way.

Thanks,

Ron

[ronk]

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 (Krzmarzick) Tauer's - Krzmarzick Family History (~1999)
1 CONT ÙC/bÙD

What are those codes?

And if you check neither, all is stripped:

1 CONC Top of the KRZMARZICK Tree, a place for HISTORY from various sources.
1 CONT
1 CONT EXCERPT from Peggy (Krzmarzick) Tauer's - Krzmarzick Family History (~1999)
1 CONT

I don't see the <<>> you mentioned so don't know if that reverse mapping would work. Or did you test this with your copy of Legacy?


Mike, Perhaps just leave the plugin as is re: HTML. My only concern was for TNG, and that is working fine. In fact, I will have to add the <> in order to bold in FH now, vs. a button in Legacy to turn bolding or underlining on or off. My use of it has been limited to that.



Ron