Ron, I understand that Legacy does not open 'non-picture' files. However, it seems totally unnecessary to add a data element (the buttons for picture, file, audio, video) when the file extension already gives more than enough information to determine what type of action is required.
Take the button for file, for example. That doesn't really tell Legacy anything. Let's say we both link a PDF and use the 'file button'. Since your system and mine might very well have different programs for opening PDF's, the system needs to go to Windows file associations anyway. I just don't see what these buttons do other than cause problems when the 'button' chosen conflicts with the actual file type. Two data elements (the file extension and the Legacy file type button), when one would do just introduces the possibility of data inconsistency, in my view for no benefit. That being said, not a big deal but........ Paul Gray -----Original Message----- From: Ron Ferguson [mailto:[email protected]] Sent: May-02-13 11:38 AM To: [email protected] Subject: Re: [LegacyUG] GEDCOM 5.5 Import problems with media file links Paul, The difference is that whereas Legacy itself opens a picture format it does not open your data files. These it refers to your registered (or default) software eg. WORD, OpenOffice, Adobe, Notepad++ etc.. As a consequence they cannot be included in reports, webpages or other media. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Paul Gray Sent: Thursday, May 02, 2013 4:03 PM To: [email protected] Subject: RE: [LegacyUG] GEDCOM 5.5 Import problems with media file links Ward, What puzzles me about this whole issue is why Legacy requires a multimedia link to be *categorized* in the first place. I can't see that Legacy treats a link that is a 'file', or 'audio' or 'video' any differently, so why make the distinction in the first place? In all those cases, will Legacy not just use the 'Windows file association' to pick the appropriate program to open the file anyway. I think identifying a picture as such may indicate to Legacy that the picture can be opened within the Picture Gallery, but surely that can be derived directly from the file extension without using a separate data element. Paul Gray -----Original Message----- From: Ward Walker [mailto:[email protected]] Sent: May-02-13 8:28 AM To: [email protected] Subject: Re: [LegacyUG] GEDCOM 5.5 Import problems with media file links Brian, is this the same problem? In the problem that we are talking about, a link IS created; it's just that nothing is distinguishing the pictures from the other types of multimedia -- they are all imported as if pictures. (Maybe the problem report that you found was half fixed?) I don't know whether this idea of treating pictures differently from other files is unique to Legacy, in terms of how they can be opened/viewed within the program. My guess is that FTM must treat them all the same, or else its export would somehow differentiate them. Even if this is an FTM failing, perhaps Legacy could recognize the filename extension in the GEDCOM and take the appropriate action on import. Ward -----Original Message----- From: Brian/Support Sent: Thursday, May 02, 2013 8:13 AM To: [email protected] Subject: Re: [LegacyUG] GEDCOM 5.5 Import problems with media file links We do have a problem report in our system for this issue of importing multimedia links from FTM 2012. The issue is still shown as outstanding. According to the problem report FTM 2012 uses a custom GEDCOM Tag to identify the link to the media when linking it to people. Legacy does not recognize this custom tag so it, naturally, does not know what to do with it so the multimedia link is not created. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com -- 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://www.LegacyFamilyTree.com/Help.asp 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
