Robert Livingston wrote: > Just for the heck of it I took the burial tag of one of my > New Hampshire people at 42.982486, -70.842872 and put a leading > "-" in front in the LatLong field. As soon as I entered a > TAB key to get out of the field, TMG threw in a "\" AFTER the > leading "-" Bob, Interesting. That did not happen when I do it. I looked around in the TMG options to see if there was some preference setting that affected how TMG handles LatLong data entry. I found a display format option in Current Project Options > Places but changing to a different option there didn't trigger the incorrect "\". I also found the "Validate LAT/LONG value" option in the Program Options > Prompts section. That appears to be the culprit. With that checked, TMG adds the "\" character when it validates a lat/long value. Unfortunately, it adds the "\" in the wrong place. If you correct it and put the "\" in the correct place, TMG leaves it alone. So, there is a TMG bug. When the "Validate LAT/LONG value" preference is checked and the user enters a negative latitude (for the southern hemisphere), TMG adds the "\" character in an attempt to prevent the minus sign from being interpreted as a single-exclusion marker, but does so incorrectly and adds it as the second character when it should be first. The user may fix it manually by moving the "\" to the first character in the value. John
Just for the heck of it I took the burial tag of one of my New Hampshire people at 42.982486, -70.842872 and put a leading "-" in front in the LatLong field. As soon as I entered a TAB key to get out of the field, TMG threw in a "\" AFTER the leading "-" On Tuesday, August 13, 2019, 12:24:13 AM EDT, Jim Slade <[email protected]> wrote: John, In TMG, I key in the LatLong values to a Burial Tag in the field labeled LatLong. The values come from the LatLong values at the Find-a-grave website. Next, in order to be sure the coordinates point to the correct location, and to insure that I have entered them correctly, I copy & paste the those values from the Burial tag into a browser opened to Google Maps. At the time when I copied & pasted the values, there was no \ slash present in the values. However, after I closed the Burial tag, closed TMG, and opened SecondSite to create a site, the markers did not correctly appear on the map. I then went back, opened TMG to view the burial tag and discovered that all the Southern Hemisphere locations now had a \ slash inserted AFTER the leading minus sign. Placing the \ slash in front of the -minus sign lets SS function correctly. Jim On Mon, Aug 12, 2019 at 8:34 PM John Cardinal <[email protected]> wrote: > Jim Slade wrote, in part: > > John, TMG definitely added the \ AFTER the - sign for every > > Lat that began with -minus sign.. > > Jim, > > I couldn't reproduce that behavior. Where were you entering them, and were > you keying, using copying paste, or ? > > John > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
John, In TMG, I key in the LatLong values to a Burial Tag in the field labeled LatLong. The values come from the LatLong values at the Find-a-grave website. Next, in order to be sure the coordinates point to the correct location, and to insure that I have entered them correctly, I copy & paste the those values from the Burial tag into a browser opened to Google Maps. At the time when I copied & pasted the values, there was no \ slash present in the values. However, after I closed the Burial tag, closed TMG, and opened SecondSite to create a site, the markers did not correctly appear on the map. I then went back, opened TMG to view the burial tag and discovered that all the Southern Hemisphere locations now had a \ slash inserted AFTER the leading minus sign. Placing the \ slash in front of the -minus sign lets SS function correctly. Jim On Mon, Aug 12, 2019 at 8:34 PM John Cardinal <[email protected]> wrote: > Jim Slade wrote, in part: > > John, TMG definitely added the \ AFTER the - sign for every > > Lat that began with -minus sign.. > > Jim, > > I couldn't reproduce that behavior. Where were you entering them, and were > you keying, using copying paste, or ? > > John > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >
Jim Slade wrote, in part: > John, TMG definitely added the \ AFTER the - sign for every > Lat that began with -minus sign.. Jim, I couldn't reproduce that behavior. Where were you entering them, and were you keying, using copying paste, or ? John
Thank you Lee, Richard & John for the answer. By *beginning* the Lat value with escape character \ then the minus -, it works perfectly. John, TMG definitely added the \ AFTER the - sign for every Lat that began with -minus sign.. Seems weird, but that is where the slash was. Jim On Mon, Aug 12, 2019 at 3:15 PM John Cardinal <[email protected]> wrote: > Jim, > > For southern hemisphere coordinates, I think you must enter a leading "\" > character. Otherwise, a leading "-" character will mean "this field is > single-excluded". You described the "\" character as being *after* the "-", > but are you sure about that? > > I did a test using "-30.5283,151.6590" as the LatLong value. TMG accepted > the value and did not change it. SS produced a marker that was in the > ocean. > I think SS (by default) will load excluded LatLong values, and so it used > 30.5283,151.6590 as the coordinates. > > I did another test using "\-30.5283,151.6590" as the LatLong value. TMG > accepted the value and did not change it. SS produced a marker southwest of > Brisbane and evidently used -30.5283,151.6590 as the coordinates. > > John > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >
Jim, For southern hemisphere coordinates, I think you must enter a leading "\" character. Otherwise, a leading "-" character will mean "this field is single-excluded". You described the "\" character as being *after* the "-", but are you sure about that? I did a test using "-30.5283,151.6590" as the LatLong value. TMG accepted the value and did not change it. SS produced a marker that was in the ocean. I think SS (by default) will load excluded LatLong values, and so it used 30.5283,151.6590 as the coordinates. I did another test using "\-30.5283,151.6590" as the LatLong value. TMG accepted the value and did not change it. SS produced a marker southwest of Brisbane and evidently used -30.5283,151.6590 as the coordinates. John
At 8/12/2019 15:30, Jim Slade wrote >I use Lat/Long entries at cemetery locations in TMGv9.05 so that a marker >will show up in Google Maps when using Second Site v7.03. This has worked >great for North America and Europe. However, when values are entered for >Austrailian locations, they keep showing up completely wrong location in >Second Site. Upon examination, I see that TMG has changed the entry >slightly, apparently causing this problem. >Example: I entered what should be the correct LatLong into TMG : > -30.5283,151.6590 >However, when it did not show correctly, and I went back to examine my >entry, it appears correct as entered in the Master Place List, but when you >open Edit Place box, it appears that TMG has added a "\" after the "-" > in the Lat field, appearing thusly: > -\30.5283,151.6590, causing the marker to appear in the ocean just east of >Japan. > >Even when I edit and remove the "\" marker, TMG seems to add it back on >all my Australian & New Zealand locations. What is happening? What can >I do to correct or prevent this change? Jim, the backslash is an escape character and should be in front of the negative (dash) sign. See the TMG Help for LatLong. Lee
First guess is it is trying to not begin the field with a - which marks it as excluded but is messing up. Try entering the field as \-30.5283,151.6590 so you are escaping the - so it doesn’t act as an exclusion marker > On Aug 12, 2019, at 3:30 PM, Jim Slade <[email protected]> wrote: > > I use Lat/Long entries at cemetery locations in TMGv9.05 so that a marker > will show up in Google Maps when using Second Site v7.03. This has worked > great for North America and Europe. However, when values are entered for > Austrailian locations, they keep showing up completely wrong location in > Second Site. Upon examination, I see that TMG has changed the entry > slightly, apparently causing this problem. > Example: I entered what should be the correct LatLong into TMG : > -30.5283,151.6590 > However, when it did not show correctly, and I went back to examine my > entry, it appears correct as entered in the Master Place List, but when you > open Edit Place box, it appears that TMG has added a "\" after the "-" > in the Lat field, appearing thusly: > -\30.5283,151.6590, causing the marker to appear in the ocean just east of > Japan. > > Even when I edit and remove the "\" marker, TMG seems to add it back on > all my Australian & New Zealand locations. What is happening? What can > I do to correct or prevent this change? > Jim > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
I use Lat/Long entries at cemetery locations in TMGv9.05 so that a marker will show up in Google Maps when using Second Site v7.03. This has worked great for North America and Europe. However, when values are entered for Austrailian locations, they keep showing up completely wrong location in Second Site. Upon examination, I see that TMG has changed the entry slightly, apparently causing this problem. Example: I entered what should be the correct LatLong into TMG : -30.5283,151.6590 However, when it did not show correctly, and I went back to examine my entry, it appears correct as entered in the Master Place List, but when you open Edit Place box, it appears that TMG has added a "\" after the "-" in the Lat field, appearing thusly: -\30.5283,151.6590, causing the marker to appear in the ocean just east of Japan. Even when I edit and remove the "\" marker, TMG seems to add it back on all my Australian & New Zealand locations. What is happening? What can I do to correct or prevent this change? Jim
At 02:56 AM 8/11/2019 +0000, Andrew Clark wrote: >I use this rather than the “full” method where you can load up the files >to the phone. This I fear will stretch resources. > > > >I also had a mate who used GedStar Pro and was very happy with it however >this again uses up your memory. (Or did way back when I tried it). > > Don't know about Apple products, but I'm pretty sure practically all Android-based phones support the use of an SD card. My (admittedly old and rather small) Second Site files (only 161 files show in Windows property page) consume less than 6MB -- try finding an SD card with less than 4GB these days. 32GB is becoming common, and a phone that handles SDXC can exceed 64GB. Any properly written application (even if the application itself can only be installed to the phones hidden storage) should be able to access files on the SD card (especially a browser reading HTML pages). Anything using some form of database should also not require much memory -- it should only load the records currently being viewed. I really miss the WinCE "Pocket Genealogist" -- which actually synched to TMG using GenBridge functions, rather than having to export a GEDCOM. That easily ran on a PDA with only 65MB of internal memory and a 1GB SD card.
Steiner, I use and recommend the Second Site (lite) method, if I can call it that. Use SS and publish to the web then just store a shortcut on your Android homepage. I use this rather than the “full” method where you can load up the files to the phone. This I fear will stretch resources. I also had a mate who used GedStar Pro and was very happy with it however this again uses up your memory. (Or did way back when I tried it). Cheers, Andrew Clark Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ From: Steinar Vissebråten <[email protected]> Sent: Saturday, August 10, 2019 8:27:07 PM To: [email protected] <[email protected]> Subject: [TMG] Regarding Phone app Hi all. I have used TMG with great pleasure for all my work for many many years. I see that it might be a long time before I NEED to change for another software. But I am looking for an app to my Androide phone that can handle my big file. I have used the Heredis but now it does not work any more. Which software and app can handle most correctly the Gedcom file output from TMG? And which Genealogy software can take my Gedcom from TMG and use the best way without loosing the info I have for 30000 persons? Much appreciate any reply. Regards Steinar -- Steinar Vissebråten, Liavegen 149, N-3540 Nesbyen,NORWAY Phone: +47 32068733..............Mobil: +47 9069 3540 Internet: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vissebraaten.no%2F&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940129307&sdata=NnflphO20KcLaeQ%2BM8h%2BSetwozIyxuHH9yfxgxSTdq0%3D&reserved=0 https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rukkedalen.com%2F&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940129307&sdata=toXERvuhpnqM9rPEg7wJB5dSmII5jBsdTrS5UqAvnFc%3D&reserved=0 _______________________________________________ Email preferences: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940129307&sdata=83b0IYbIgjJ7uGRLb%2F%2FKL7tr%2Bvaf3RMUkiLVLWmzsGA%3D&reserved=0 Unsubscribe https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Ftmg%40rootsweb.com&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940129307&sdata=OTVoMIX3CqoI%2B9Un9pyx8jdw8%2B2uoyiZ%2B0WzV9u%2B1X4%3D&reserved=0 Privacy Statement: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940139312&sdata=wMentkBtWzsw%2F9cpBmV7MfdPR3enAW5SOQCbTxrYiu8%3D&reserved=0 Terms and Conditions: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940139312&sdata=5sZ40ueUnLkv8EsLGtWYGNWcgH6P2uvuYjIuNUhbZCo%3D&reserved=0 Rootsweb Blog: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7C2cbd23f8a56943cfb7f508d71d7d729d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637010296940139312&sdata=aBByHso%2FVwxA4QPMq9nvKZLrBurbM2dxqVRl%2BKutVVQ%3D&reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
[As this is separate from similar threads I started a new thread.] John Cardinal first made an excellent suggestion to construct custom Source Definitions for sources which are web sites. That way the overall URL to the site can be entered once in a Source Element in the Source Definition, and only the detailed web page reference within that site need be entered as text in a Citation Detail. This facilitates any changes the site may make in its overall URL (such as FindAGrave did last year) as that is stored only once in the Source Element. Then Toby Turner exposed TMG issues/bugs when trying to construct a Source Definition template to generate a web reference citation using a Source Element URL. The desire was to generate output appropriate in both TMG reports and Second Site. Many constructs which "should" have worked did work for Second Site but not in TMG reports. I have found what reliably works is to construct the Source Definition to output the Web code in two different parts: one for TMG reports and one for Second Site. This separaton can be accomplished by using the TMG codes [HID:][:HID] and the Second Site codes [SS:][:SS] and [SS-HID:][:SS-HID]. While several aspects of my example templates probably *"should"* not be necessary, they do work in both TMG reports and Second Site. These or similar templates may seem a bit complex, but can be carefully constructed just once in the Source Definition. I have added to my on-line book two FindAGrave custom Source Definitions which produce what I want in both TMG report citations and in Second Site citations. One is for citing an individual's memorial, the other for citing the record of the cemetery itself. The templates also include the target="_blank" parameter which FindAGrave requires if the link is within a framed page. https://www.mjh-nm.net/SRCTMPLS.HTML#FindAGrave Hopefully these templates will be helpful to others trying to construct something similar. Michael
Toby Turner wrote: > Here is the link used: > > < at \<a target="_blank" > href="http://www.findagrave.com/memorial/[CD5]">...</a> Toby, I am not John, but I think you are missing some backslash escape characters? \<a target="_blank" href="http://www.findagrave.com/memorial/[CD5]"\>...\</a\> Could that be the issue? Michael
I strongly agree with the Second Site recommendation. It is platform independent on the viewing end. As long as you have a browser, you can view your data. On the creation side, you need a PC. Second Site is not supported in the Mac world. Try viewing https://www.moffatfamilyhistory.com/ on your phone to see how my site looks. It is not fancy, but that is my choice. SS supports many features that I have yet to explore. Rick Sent from my iPhone > On Aug 10, 2019, at 3:27 AM, Steinar Vissebråten <[email protected]> wrote: > > Hi all. > > I have used TMG with great pleasure for all my work for many many years. I see that it might be a long time before I NEED to change for another software. > > But I am looking for an app to my Androide phone that can handle my big file. I have used the Heredis but now it does not work any more. > > Which software and app can handle most correctly the Gedcom file output from TMG? > And which Genealogy software can take my Gedcom from TMG and use the best way without loosing the info I have for 30000 persons? > > Much appreciate any reply. > > Regards > Steinar > > > > -- > > > Steinar Vissebråten, Liavegen 149, > N-3540 Nesbyen,NORWAY > > Phone: +47 32068733..............Mobil: +47 9069 3540 > > Internet: > http://www.vissebraaten.no/ > http://www.rukkedalen.com/ > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
I've also been pleased with GedStar Pro, which displays all the info I need on my cell phone (including exhibits). David A. Coats Coats Translation Service ATA Certified Translators: E>G, G>E Phone: 612-379-7398 Fax: 612-379-0384 email: [email protected] [email protected] [email protected] On 8/10/2019 9:24 AM, John Cordes wrote: > Another possibility is GedStar Pro, since it's an Android phone. > > Steinar - just how big is the file (how many people) do you want > to put on the phone? You mentioned 30,000 people in part of your > message. Is that also the number for the project you want to have > on the phone? > > John > > > On Sat, Aug 10, 2019 at 08:04:16AM -0600, Michael J Hannah wrote: >> Steinar, >> Don't use an app. Use SecondSite to create web pages. Then load those on your phone and view them with the included Web browser. >> Michael > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community >
John, I had copied/pasted the link you provided so I have been using http and not https. Here is the link used: < at \<a target="_blank" href="http://www.findagrave.com/memorial/[CD5]">...</a> Did I somehow get it wrong? I can no longer locate your original email with this link which I thought had been copied to a saved file. This is my second response this morning because Thunderbird appears to have lost the first one. If this is a double post I apologize; but I couldn't find the original in my Sent box. Regards, Toby
Another possibility is GedStar Pro, since it's an Android phone. Steinar - just how big is the file (how many people) do you want to put on the phone? You mentioned 30,000 people in part of your message. Is that also the number for the project you want to have on the phone? John On Sat, Aug 10, 2019 at 08:04:16AM -0600, Michael J Hannah wrote: > Steinar, > Don't use an app. Use SecondSite to create web pages. Then load those on your phone and view them with the included Web browser. > Michael
Steinar, Don't use an app. Use SecondSite to create web pages. Then load those on your phone and view them with the included Web browser. Michael
Hi all. I have used TMG with great pleasure for all my work for many many years. I see that it might be a long time before I NEED to change for another software. But I am looking for an app to my Androide phone that can handle my big file. I have used the Heredis but now it does not work any more. Which software and app can handle most correctly the Gedcom file output from TMG? And which Genealogy software can take my Gedcom from TMG and use the best way without loosing the info I have for 30000 persons? Much appreciate any reply. Regards Steinar -- Steinar Vissebråten, Liavegen 149, N-3540 Nesbyen,NORWAY Phone: +47 32068733..............Mobil: +47 9069 3540 Internet: http://www.vissebraaten.no/ http://www.rukkedalen.com/
As I mentioned in my recent message about my template, I am also able to access the FAG site using target="_blank" from a framed page. And I am using the standard current release of SecondSite. You do understand that there is an underscore in front of the word blank, all within quotes? I would also be interested to know why it does not work for you. Michael