Jump to content

Jim Byram

Moderators
  • Content count

    7,774
  • Joined

  • Last visited

Everything posted by Jim Byram

  1. I asked for help on July 10 (see the reply above) and sent an email or PM to each of the four above persons who have the 'structure version missing' issue a few days later. So far I've heard nothing from anyone willing to help test this issue.
  2. Embedding text in jpeg files

    Paint Shop Pro X does. iMatch recognizes the WinXP Author, Comments, Keywords, Subject and Title fields as EXIF data. iMatch has the most extensive support of image metadata of any program that I'm aware of (IPTC, EXIF, XMP, all variants, other metadata as well) and can display 339 different possible image metadata fields if my count was correct.
  3. Embedding text in jpeg files

    That's not exactly right. Most EXIF fields are read-only but some such as the default Subject field are editable. The Win XP Title and Win XP Subject fields are legal custom EXIF fields and are editable. They are legal EXIF fields but you're right in that they only apply to certain files. EXIF per se is not specific to image files either. The more exhibit filetypes supported, the better. There is no reason to limit metadata to image files. From testing of the Win XP Title and Win XP Subject fields (this will not be complete)... WinXP supports these fields for: DCX, EPS, JPG, PCT, PCX, PSD, TIF, TGA, WPG images. WinXP does not support this data for BMP, GIF, and PNG images. And title only is supported for several a/v files (MP3, WMA, WMV). Title and subject are supported for MID and RMI. Win XP does not support this data for WAV. The title and subject are also supported for TXT and PDF files. Note that WinVista supports the same data as WinXP. The title and subject are displayed in the Windows Explorer status bar in WinVista. Now... The reason that I suggested supporting the WinXP EXIF data is that the feature is available for every WinXP user now and, in the future, for every WinVista user. Users can add a title and, in most cases, subject to most of the possible exhibit file types so that this data would automatically be added to the Topic and Caption fields when the exhibit is added to TMG. Since the operating system stores this WinXP EXIF data, there will be APIs to retrieve the data. According to PhotoShop CS help, XMP is supported for TIFF, JPEG, EPS and PDF files. Period. Whether EXIF or XMP is used in your graphics software or photo organizing software is not the issue because of the uneven support between different programs. The issue is maximizing the benefits to TMG users.
  4. Embedding text in jpeg files

    Wholly Genes Software
  5. Embedding text in jpeg files

    Freeimage.dll is used by VCF, I believe. Exhibits use the Leadtools library. 'Reneging' is not exactly right. MS Office 2007 Beta 2 does include the PDF export. It will not be included in the shipping version but will be available for download as an Office plug-in. So all that has changed is how the feature will get to users. Seems like the most useful thing to support would be the WinXP EXIF extensions since that would provide for title and caption on import and are supported by WinVista.
  6. Embedding text in jpeg files

    OK. I ran a little experiment. Used a test JPG. 1) Right-clicked on the image in WinXP. Properties. Added the Title: AB Added the Subject: ABC (These are added to the image file as EXIF customized fields. EXIF is extensible.) 2) Opened the image in Paint Shop Pro X. The Creator tab Image Title and Description fields are blank. Added the same data. The EXIF Information tab shows the information added in WinXP as: Win XP Title: AB WinXP Subject: ABC (PSP10 fully supports EXIF. The Creator tab info appears to be added as ICC info.) 3) Opened the image in Photo Shop Elements 3 and in Photo Shop CS (basically the same results in both). The ICC profile is ignored (PSE3 says this). However the PSP Description data appears in the 'Description Writer' field. Huh? The EXIF information from WinXP is not shown anywhere that I could find. The EXIF support is elemental compared to PSP10. Added the: Document Title: AB Description: ABC Cleared the Description Writer field. (The PhotoShop data is added using XMP.) 4) Checked the WinXP properties. The Title data is gone. Re-added AB to the title field. 5) Opened in Paint Shop Pro X again. The Creator tab Image title and Description data are gone. Don't see the data added in PhotoShop anywhere. More... Added the default EXIF image title in PSP10. Doesn't appear to show in any other program. I can find the title under various fields in PhotoShop but am not clear exactly the origin of the data. Advanced 1) PDF Properties / Subject 2) Adobe PhotoShop Properties / Caption 3) TIFF Properties / ImageDescription (alt-container) / x-default 4) XMP Core Properties / Description (alt-container) / x-default 5) Dublin Core Properties / description (alt-container) / x-default This all appears to be coming from the PSE3/PS description field. Now... Exactly what is it that TMG is supposed to do with which data? EXIF can also have different 'Title' and 'Subject' fields depending on whether the defaults or extensions are being used. WinVista uses the same EXIF extensions used by WinXP and the title / caption data are shown in the Windows Explorer status bar in WinVista.
  7. Creating GEDCOM for paternal surname

    Something like this... Use the Project Explorer. Filter the Project Explorer. ID# = (nn) OR ( Is an Ancestor of ID# (nn) AND SEX = M AND Surname = (surname) ) END Also tick primary names only (cleaner but not necessary) (nn) is the ID# of the base person. (surname) is the surname of interest. You can then use the names in the PE or add them to a focus group. To add them to a focus group... Open the Focus Group window and make sure that it's empty. Then right-click in the PE and select 'Add all names to the Focus Group'. then either... 1) Select all names in the Project Explorer. Run the GEDCOM export and on Step 4, select 'Selected people on the Project Explorer'. or 1) Run the GEDCOM export and on Step 4, select 'People in the Focus Group'. Lots of small differences to do what you want but you should get the idea. The idea is to select the appropriate group of people and then to export that group. It gets more complicated if the ancestors have changed surnames. In that case, you might want to use the Focus Group approach and change the surname in the PE filter as necessary and add any additional ancestors to the focus group until you get them all. The nice thing about a focus group is, once you get everyone into it that you want, you can save it for future use.
  8. Sorry. I missed the CSV part. Yes, that's the case and clearly appears to be by design. It happens with output to any spreadsheet format.
  9. I had no problem setting up 30-character wide flag column and having it stick and show up in the output 30 characters wide. However, a flag is a single-character attribute. It seems wasteful to have a 30-character column for 1-character data. You should have a short creative heading label for your column and minimize the column width. Even 10 characters seems like too much wasted white space to me.
  10. Windows Vista

    Updated 11 Jul 2006, 01:46 PM
  11. Please update to the current program version. This error does not occur with v6.09.000.
  12. The reason this issue is still out there is that it can't be replicated. One beta tester got the issue on his notebook and now can't get it any more. I need one or two people who get the issue on a regular basis to help me. Contact me directly and I will sent you download instructions and detailed instructions to test this. The download will be about 6.5 Mb. Basically, you will be using a Tmg.exe build which will create a log file when the 'structure version missing' message occurs. Write me by clicking on the link below: Jim Byram Update: Could each of you please send me the PJC file from the project giving the 'structure version missing' message so that I can check the file.
  13. missing images in secondary output project

    That doesn't make sense. If the path is correct and the file exists, the image should display. There is some more information needed here. When you create a new project, you need to set the preferences for that new project. To identify missing external exhibits... Go to Preferences and turn off the thumbnails. Current Project Options / Advanced / untick 'Save image thumbnails' Run optimize to remove the thumbnails from the data tables. File / Maintenance / Optimize Open the Exhibit Log. Change the focus to 'All exhibits' Look for the two with a frowny face icon. Select each. Look in the lower right of the Exhibit Log to identify how the exhibit is used. Right-click and select Properties. Look at the path at the bottom of the General tab to identify the file. Once done, go back to Preferences and re-enable thumbnails. Also, you should use the Validate File Integrity / Exhibits tool to find missing exhibits. However, in v6.09, it has a bug if multiple paths are selected for the search. Also, after running the VFI exhibits tool, check the Last_VFI.log in your program folder. Missing exhibits are noted at the top of the file.
  14. Not as you describe. Accenting is by person only.
  15. Migrating from FTW to TMG

    The problem is how FTM exports the SSN fact. 1 SSN 2 PLAC 123-45-6789 TMG imports this correctly as structured but that's not what is wanted. A correct GEDCOM SSN tag should be: 1 SSN 123-45-6789 TMG will import this with the SSN going to the memo field of the SSN tag. The FTM GEDCOM can be corrected by a global search and replace in Word which allows wildcards. Search for: '1 SSN*PLAC' and replace with: '1 SSN' Using wildcards in Word allows many global GEDCOM edits that would be impossible otherwise. The edited GEDCOM file must be saved as an ANSI text file and the final GEDCOM must have a filetype of .GED. Whether this approach can be applied to other FTM facts that were exported to GEDCOM depends on the GEDCOM tag and the subordinate tags. Most others are much more difficult to correct than SSN and may not be amenable to the global search and replace approach.
  16. Migrating from FTW to TMG

    The issue is subtle changes in the FTM database from version to version and trying to get the import code to deal with those changes. The problem is the need to check every event in the GEDCOM to determine if the data for that event is comment or place. Since it has to be done event-by-event, I don't see how a utility could be designed to help.
  17. Migrating from FTW to TMG

    This is a known issue. It's a problem with citation import, not source import. The mssing sources are a side-effect. In some instances, citations are lost or point to source #0. This results in all sources with no citations to the source being omitted. The programmer has been working on this for some time. He 'fixes' it, I break it. Hopefully, this will be resolved soon. The only work-around, for the moment, is to use GEDCOM import. That's the case. Importing from FTM to anything is plagued by this issue of FTM using one field for two data types.
  18. UTF support?

    The language features are summarized in a series of articles by Terry Reigel. http://tmg.reigelridge.com/Language.htm UTF-8 is not yet supported but is a priority. The question is when Microsoft FoxPro will allow full UTF-8 support.
  19. GEDCOM import issues

    Oops! Sorry. You're right that the GEDCOM 5.5 specs support a person source. I was having a dim moment. The person source is not a name source and the name might have sources which differ. If you added the person sources to the primary name, how would you know which sources were the name sources and which were the person sources? The import attempts to preserve and identify the person sources. The only real issue is whether these can be consolidated if more than one exists. Huh? The 'full information contained in the subtags' (the citation detail) is located in the citation after import.
  20. GEDCOM import issues

    A 'person source' in not supported in TMG. The import is by design to preserve the data. The reason that it happened four times is shown by your example. This individual had 4 'person sources'. I think that it would be difficult to consolidate these but we'll see. The 1 TEMP tag is legal in the GEDCOM. I'll have to see if this could be adjusted on import. Address group? It would go to the temple field of the place for the LDS event being imported. I'll revise this after we get a chance to look at the issues.
  21. Exhibits

    I'm not sure what you meant by that. When you open the Exhibit Log from the Person View and link an exhibit, it's linked to the person. When you open an event Tag Entry screen and then open the Exhibit Log from that tag and link an exhibit, it's linked to the event. Keep in mind that if you link an image multiple times (event, person, etc.), when you generate a Journal report, for example, the same image might appear in the report multiple times.
  22. GEDCOM import issues

    No. This is from the submitter record in the GEDCOM. You could delete the submitter person and the source after import. I'd need to see a clip from the GEDCOM to understand what you are saying. Again, I'd need to see a clip from the GEDCOM to understand the issue.
  23. GenBridge SDK

    Paraphrasing an earlier response regarding GenBridge from Bob Velke... The GenBridge Software Development Kit (SDK) is a tool that Wholly Genes makes available to software developers. Support for the GenBridge SDK is offered through gbdeveloper@whollygenes.com. Please write to that address if you have any questions relating to the GenBridge Software Development Kit (SDK). Thanks.
  24. No except by combining the output of a number of box charts. A box chart is intended to flow from one point of origin(person) up, down or in both directions. You want to flow from multiple points of origin in both directions.
  25. Accents in ancestor chart

    I can't get accents in the box charts based on the Ancestor Interest or Descendant Interest flags unless I'm missing something. Tried the SEX flag and some other flags and they worked perfectly. I searched and found this was reported some time ago and the fix is still pending. My suggestion is to create new custom flags to accomplish the same thing. For example, I made a new flag Desc_Int with settings of ?,1,2,3,4. Used the List of people report to transfer the settings from the Descendant Interest flag to the Desc_int flag. Filter by the Descendant Interest flag setting and use the LOP secondary output to set the Desc_Int flag setting. Or filter more directly for how you want to set the Desc_Int flag setting. This approach completely bypasses the problem and gives you your accents.
×