On 9/1/19 10:17 PM, Bruce W Fairhall wrote: > So, while I follow to to and fro of this discussion, how should we > record Southern Hemisphere latitudes in TMG 9.05 so that TMG Reports > and SS both interpret them correctly? begin with \- so the - isn't first, so doesn't act as the exclusion character. -- Richard Damon

So, while I follow to to and fro of this discussion, how should we record Southern Hemisphere latitudes in TMG 9.05 so that TMG Reports and SS both interpret them correctly? *Bruce Fairhall* On 01-Sep.-19 3:09 am, Michael J. Hannah wrote: > John Cardinal wrote: >> ... I was presuming, but I left out something important: I was deeply >> involved in the specification process when TMG switched from >> using a degrees-minutes-seconds format to decimal degrees. > > I bow to and acknowledge your much more intimate knowledge of the > development of TMG and its inner workings.  Apologies if I seemed to > imply otherwise. > >> 1 - That TMG should use a single "escape" character, '\' (backslash) >> 2 - The escape character should always defeat the special meaning of the >> subsequent character (if any) > > And I could even agree that this is how TMG *should* work.  But in my > opinion how TMG "should" work became academic five years ago with Bob > Velke's announcement terminating TMG development. > > My book and my list of Bugs is now trying to focus on how this final > TMG version DOES work, whether is "should" be that way or not.  Thus I > try to find some kind of "reason" why a particular TMG feature works > the way that it does in an attempt to help remember and understand > that feature, even if that is a rationalization and never intended by > the developers. > >> ... we explicitly discussed the issue of negative latitude values and >> the requirement that the user would have to enter the escape character >> to defeat the special meaning of the leading hyphen. > > So since "-12.123456,123.123456" does not escape the leading hyphen as > would be required for a negative latitude, TMG is correct to treat it > as a single excluded value with a positive latitude.  TMG's addition > of the escape character after the hypen does not change the treatment > of that entry, it just changes the display in the LatLong field on > screen.  And since escape characters are removed on output, if the > value is output it will appear as a positive latitude as it should > be.  Thus the value is treated correctly by TMG, so where's the bug? > > We could even agree that TMG "shouldn't" insert this escape character > in the display, but it DOES and that won't change. Since the value is > being treated as is should be, I am therefore personally focused on > "creating" a potentially helpful "reason" for the automatically > changed display so that users might be less confused about this action > and appearance which DOES take place and thus help understand it. > > Michael > > P.S. Thanks to Robin for his post on HRE's exclusion character, as > that is a forum where discussions of how software "should" work are > useful. > > _______________________________________________ > 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 >

Lee Hoffman replied concerning: >> Recent additions are: > ===clipped=== >> [Added 30 Jul 2019] A single vertical bar character in conditional >> memo text is treated as the Two Principals separator > > This has been the way TMG worked since the very early versions. > A bug? Based of the majority of users, possibly. Yes, Lee, as my "List of Bugs" page starts: > What kind of program behavior constitutes a “Bug” is a matter > of user perception. Some may consider a particular program behavior > as intended design, an overlooked feature, or unavoidable > consequences of improper user actions. Others may consider the > program behavior an error, or even extremely unexpected, > and thus label it a “bug”. The designation of “bug” for the > following behaviors is strictly *my* perception. While whether any particular program behaviour should be labeled a "bug" is in the "eye of the beholder", I choose to include it in my list because some users found it at least unexpected. Whether the behaviour is intended or not, it is how the program works. If some users find it confusing I want try to help them by describing it as accurately as possible in a way that it might be (somewhat) understandable, and also describe how it "might" be useful to them or describe "workarounds" to avoid it. Hopefully I have been somewhat successful. Michael

At 8/31/2019 19:18, Michael J. Hannah wrote >I have had some time this week to review old notes of reported bugs >in TMG and add new descriptions and workarounds to my on-line list >of outstanding bugs in the final TMG version. The full list is at: > >https://www.mjh-nm.net/BUGS.HTML > >Recent additions are: ===clipped=== >[Added 30 Jul 2019] A single vertical bar character in conditional >memo text is treated as the Two Principals separator >https://www.mjh-nm.net/BUGS.HTML#B106 This has been the way TMG worked since the very early versions. It was definitely in use before Roles were introduced (probably v1, v2, v3 , and possibly up to v3.5). (We always had Roles, but they were limited to a few, -- such as: Principal, Second Principal, Witness and a couple others). It was also in versions before split fields were introduced. I recall discussion as to whether to include the "or" separator in the Memo field. It was thought by some to be advantageous especially since a different Memo text might be desired depending on whether one or two principals were entered. I cannot recall the examples given except perhaps one involving land transactions where the first Principal sold the land and the Second Principal bought it as compared to the first buying the land and a Witness selling it. In any case, I think there was very little use of the separator by users. Then, over time and many versions later, it was more or less forgotten. A bug? Based of the majority of users, possibly. If still under development, there might be some considersation for its removal from the Memo fields. Personally, I don't recall a problem with its inadvertant use although I also don't recall ever needing to use the vertical bar in a Memo. Lee

I have had some time this week to review old notes of reported bugs in TMG and add new descriptions and workarounds to my on-line list of outstanding bugs in the final TMG version. The full list is at: https://www.mjh-nm.net/BUGS.HTML Recent additions are: [Added 7 Jul 2019] Some irregular forms of date input are interpreted as regular “between” dates https://www.mjh-nm.net/BUGS.HTML#B105 [Added 30 Jul 2019] A single vertical bar character in conditional memo text is treated as the Two Principals separator https://www.mjh-nm.net/BUGS.HTML#B106 [Added 30 Aug 2019] A Negative Latitude entered in the LatLong Place field requires a leading Escape character https://www.mjh-nm.net/BUGS.HTML#B107 [Added 31 Aug 2019] “Name-Variation // Surname” filter does not work with some operators https://www.mjh-nm.net/BUGS.HTML#B108 [Added 31 Aug 2019] LIND codes around a Memo variable can produce FONTM errors depending upon periods https://www.mjh-nm.net/BUGS.HTML#B109 I hope these descriptions and workarounds help those users unfortunate enough to encounter these bugs. Michael

At 02:02 PM 8/30/2019 -0400, Trudie davis-long wrote: >Dennis, >Lee was right. Somehow it was minimized, but I am only able to restore >the >screen right-clicking on the thumbnail and choosing the maximize >function. >I have no idea, why it has changed. It never used to be this way. It is >either completely minimized or full screen. I'd still suggest running as administrator to see if it is a global or user matter. As a test, I just opened TMG9, changed to full-screen mode using the [] -> []] icon, exited saving a new layout. I then compared the new layout file to the original one. From the full-screen: [MainWindow] State=2 Top=76 Left=0 Height=1124 Width=1920 Flag=1 vs my normal window [MainWindow] State=0 Top=189 Left=174 Height=869 Width=1455 Flag=1 I suspect the crucial item is "State" -- 2 being maximized, 0 being regular (changeable) [hypothesis: 1 is minimized] You might want to check the .lo files in your application data directory (mine is C:\Users\Wulfraed\AppData\Roaming\The Master Genealogist v9 ), using a plain text editor; if you find any layouts where [MainWindow] State is not 0, change it to a zero and save. THEN try reopening TMG. Also, check the app.ini file for [advanced] lastlayout=xxxxx and try any other layout file you have except the one listed there. -- [email protected] Dennis Lee Bieber http://genealogy.microdiversity.freeddns.org/

Works OK for me on Windows 7. On Sat, Aug 31, 2019 at 12:22 PM Scott Schaffer <[email protected]> wrote: > John, I am also having the same issue after the upgrade. There is no error > message on the screen and the program is no longer visible in the task > manager. > I am running windows 10.0.1832.295 > > Thanks, Scott > > > -----Original Message----- > From: James Holcombe [mailto:[email protected]] > Sent: Saturday, August 31, 2019 7:51 AM > To: John Cardinal > Cc: Second Site News; [email protected]; TMG-L > Subject: [TMG] Re: [ssn] Second Site v7.04 Is Available > > When I click on Publish, the program immediately closes. I reinstalled and > the same thing happens > > On Fri, Aug 30, 2019 at 11:42 AM John Cardinal <[email protected]> > wrote: > > > *Second Site Version 7.04 is now available.* This is a maintenance > > release with a couple of minor changes. I encourage all users to install > > the latest version. > > > > The newsletter link is here: > > > > https://www.secondsite7.com/ssn086.htm > > > > Users with a Second Site 7 license can download the installer here: > > > > https://www.secondsite7.com/downloads.htm?v=7.04 > > > > *This is a free upgrade for registered users of Second Site 7*. If you > > are using Second Site 6 or a previous version, you must purchase a > license > > to use Second Site 7: > > > > https://www.secondsite7.com/purchases.htm?v=7.04 > > > > In November of 2016, I began using new web store software for software > > license sales. I did not migrate the customer records from the old store > to > > the new store. If your last purchase was prior to November 2016, you will > > *not* have an existing customer record in the new store and you'll have > > to create a new one. If so, when given the choice to either Logon or > > Register, choose Register. > > > > *Getting Online* > > > > If you'd like to publish your site online, please choose *Family History > > Hosting <https://www.familyhistoryhosting.com/>*. We'll help you > > understand and navigate the process of acquiring a domain name and > > publishing your site. The Publish command in Second Site makes publishing > > easy, it works exclusively with FHH! Family History Hosting includes > *long-term > > hosting plans*. Check it out! > > > > https://www.FamilyHistoryHosting.com/archiveplans.htm > > > > *Other Notes* > > > > You do *not* have to use the right-click, "Run as Administrator" method > > to start the installer for v7.04. You may be warned that the installer is > > not from a trusted source. You can ignore that warning. If you have any > > trouble installing, please contact me. > > > > > > > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Second Site News" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected] > > To view this discussion on the web visit > > > > https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30%2 > 48febce90%24%40gmail.com > <https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30%248febce90%24%40gmail.com> > > > < > https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30% > 248febce90%24%40gmail.com?utm_medium=email&utm_source=footer > <https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30%248febce90%24%40gmail.com?utm_medium=email&utm_source=footer> > > > > . > > > > _______________________________________________ > 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 Cardinal wrote: > ... I was presuming, but I left out something important: I was deeply > involved in the specification process when TMG switched from > using a degrees-minutes-seconds format to decimal degrees. I bow to and acknowledge your much more intimate knowledge of the development of TMG and its inner workings. Apologies if I seemed to imply otherwise. > 1 - That TMG should use a single "escape" character, '\' (backslash) > 2 - The escape character should always defeat the special meaning of the > subsequent character (if any) And I could even agree that this is how TMG *should* work. But in my opinion how TMG "should" work became academic five years ago with Bob Velke's announcement terminating TMG development. My book and my list of Bugs is now trying to focus on how this final TMG version DOES work, whether is "should" be that way or not. Thus I try to find some kind of "reason" why a particular TMG feature works the way that it does in an attempt to help remember and understand that feature, even if that is a rationalization and never intended by the developers. > ... we explicitly discussed the issue of negative latitude values and > the requirement that the user would have to enter the escape character > to defeat the special meaning of the leading hyphen. So since "-12.123456,123.123456" does not escape the leading hyphen as would be required for a negative latitude, TMG is correct to treat it as a single excluded value with a positive latitude. TMG's addition of the escape character after the hypen does not change the treatment of that entry, it just changes the display in the LatLong field on screen. And since escape characters are removed on output, if the value is output it will appear as a positive latitude as it should be. Thus the value is treated correctly by TMG, so where's the bug? We could even agree that TMG "shouldn't" insert this escape character in the display, but it DOES and that won't change. Since the value is being treated as is should be, I am therefore personally focused on "creating" a potentially helpful "reason" for the automatically changed display so that users might be less confused about this action and appearance which DOES take place and thus help understand it. Michael P.S. Thanks to Robin for his post on HRE's exclusion character, as that is a forum where discussions of how software "should" work are useful.

John, I am also having the same issue after the upgrade. There is no error message on the screen and the program is no longer visible in the task manager. I am running windows 10.0.1832.295 Thanks, Scott -----Original Message----- From: James Holcombe [mailto:[email protected]] Sent: Saturday, August 31, 2019 7:51 AM To: John Cardinal Cc: Second Site News; [email protected]; TMG-L Subject: [TMG] Re: [ssn] Second Site v7.04 Is Available When I click on Publish, the program immediately closes. I reinstalled and the same thing happens On Fri, Aug 30, 2019 at 11:42 AM John Cardinal <[email protected]> wrote: > *Second Site Version 7.04 is now available.* This is a maintenance > release with a couple of minor changes. I encourage all users to install > the latest version. > > The newsletter link is here: > > https://www.secondsite7.com/ssn086.htm > > Users with a Second Site 7 license can download the installer here: > > https://www.secondsite7.com/downloads.htm?v=7.04 > > *This is a free upgrade for registered users of Second Site 7*. If you > are using Second Site 6 or a previous version, you must purchase a license > to use Second Site 7: > > https://www.secondsite7.com/purchases.htm?v=7.04 > > In November of 2016, I began using new web store software for software > license sales. I did not migrate the customer records from the old store to > the new store. If your last purchase was prior to November 2016, you will > *not* have an existing customer record in the new store and you'll have > to create a new one. If so, when given the choice to either Logon or > Register, choose Register. > > *Getting Online* > > If you'd like to publish your site online, please choose *Family History > Hosting <https://www.familyhistoryhosting.com/>*. We'll help you > understand and navigate the process of acquiring a domain name and > publishing your site. The Publish command in Second Site makes publishing > easy, it works exclusively with FHH! Family History Hosting includes *long-term > hosting plans*. Check it out! > > https://www.FamilyHistoryHosting.com/archiveplans.htm > > *Other Notes* > > You do *not* have to use the right-click, "Run as Administrator" method > to start the installer for v7.04. You may be warned that the installer is > not from a trusted source. You can ignore that warning. If you have any > trouble installing, please contact me. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Second Site News" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > To view this discussion on the web visit > https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30%2 48febce90%24%40gmail.com > <https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30% 248febce90%24%40gmail.com?utm_medium=email&utm_source=footer> > . > _______________________________________________ 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

When I click on Publish, the program immediately closes. I reinstalled and the same thing happens On Fri, Aug 30, 2019 at 11:42 AM John Cardinal <[email protected]> wrote: > *Second Site Version 7.04 is now available.* This is a maintenance > release with a couple of minor changes. I encourage all users to install > the latest version. > > The newsletter link is here: > > https://www.secondsite7.com/ssn086.htm > > Users with a Second Site 7 license can download the installer here: > > https://www.secondsite7.com/downloads.htm?v=7.04 > > *This is a free upgrade for registered users of Second Site 7*. If you > are using Second Site 6 or a previous version, you must purchase a license > to use Second Site 7: > > https://www.secondsite7.com/purchases.htm?v=7.04 > > In November of 2016, I began using new web store software for software > license sales. I did not migrate the customer records from the old store to > the new store. If your last purchase was prior to November 2016, you will > *not* have an existing customer record in the new store and you'll have > to create a new one. If so, when given the choice to either Logon or > Register, choose Register. > > *Getting Online* > > If you'd like to publish your site online, please choose *Family History > Hosting <https://www.familyhistoryhosting.com/>*. We'll help you > understand and navigate the process of acquiring a domain name and > publishing your site. The Publish command in Second Site makes publishing > easy, it works exclusively with FHH! Family History Hosting includes *long-term > hosting plans*. Check it out! > > https://www.FamilyHistoryHosting.com/archiveplans.htm > > *Other Notes* > > You do *not* have to use the right-click, "Run as Administrator" method > to start the installer for v7.04. You may be warned that the installer is > not from a trusted source. You can ignore that warning. If you have any > trouble installing, please contact me. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Second Site News" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > To view this discussion on the web visit > https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30%248febce90%24%40gmail.com > <https://groups.google.com/d/msgid/second-site-news/002b01d55f49%24854e9a30%248febce90%24%40gmail.com?utm_medium=email&utm_source=footer> > . >

After our discussions and fixing issues yesterday, when I went to layouts to overwrite a 'changed' resized page, the page again disappeared off the screen and I had to do the same thing over. The page opened maximized and I then I again created a resized page to work with. Steps followed for the above: View Layout Manage layouts overwrite screen page disappeared. I decided to work on it another time. Today I was back to TMG and it only opened as a maximized page. I then changed the page size. Went to layouts Added current image as a NEW layout and it worked fine. Why would there be a hiccup with overwriting a layout? Does any of this make sense? Hopefully, this is the end of the problem.

I am _always_ recommending CutePDF so perhaps it was me. I even use it at work all the time. Constance On Sat, Aug 31, 2019 at 8:40 AM Judy Madnick <[email protected]> wrote: > CutePDF is actually my PDF creator of choice. When I ran into this new > problem, I went back and forth between CutePDF and MS Print to PDF just in > case there was a problem with one of them. Perhaps you were the person who > reminded me a number of months ago that CutePDF could be used with TMG? > > On Sat, Aug 31, 2019, 8:31 AM Constance Chappell Horne < > [email protected]> wrote: > > > I would also suggest that if you truly want PDFs, that you install > CutePDF. > > It installs as a printer. I have it as my default printer and print > > everything that way usually. It is free and works great. I highly > recommend > > it. > > > > Constance > > > > On Sat, Aug 31, 2019 at 6:50 AM Judy Madnick <[email protected]> wrote: > > > > > Note my previous message. I don't have Word and had to change the > > > association of .rtf files to Libre Office/Write. Apparently I just had > to > > > have them associated with some program on my computer, and Windows > > > associated them to Word by default. Thanks for your input! > > > > > > On Fri, Aug 30, 2019, 11:04 PM campbell <[email protected]> wrote: > > > > > > > Hi Judy > > > > I had this same problem not so long ago after some windows or word > > > update. > > > > I solved the matter by checking (in Win10) Settings/Apps/Default > > > > apps/Choose > > > > default applications by file type. > > > > Make sure ".doc" and similar file extensions select "Word" > > > > Make sure ".rtf" selects "Word". > > > > > > > > Hope this helps > > > > > > > > Campbell Stanford > > > > Auckland > > > > New Zealand > > > > > > > > > > > > -----Original Message----- > > > > From: Judy Madnick <[email protected]> > > > > Sent: Saturday, 31 August 2019 7:01 AM > > > > To: The Master Genealogist Rootsweb Email List <[email protected]> > > > > Subject: [TMG] .pdf printing problem in 9.05 in Windows 10 > > > > > > > > New computer, TMG installed, and most everything seems to be > okay...so > > > far. > > > > I've chosen Microsoft Print to PDF, but my reports are being saved > to a > > > > temp > > > > file AND they have an .rtf extension. I'm not finding an option as > to > > > > where > > > > I would like to report to go. On my old computer (also Windows 10), > it > > > > would > > > > show up in my task bar, but not so on my new computer. I don't ever > > > > remember > > > > having to choose a place for the report to be sent, and it was so > > simple > > > to > > > > just open the file from the task bar. I tried this with CutePDF also > > with > > > > the same problem resulting. > > > > > > > > I'm having the same issue with Screen Preview, which used to "pop" > > right > > > > open. > > > > > > > > Judy Madnick > > > > Albany, NY > > > > > > > > _______________________________________________ > > > > 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 > > > > > > > > > > _______________________________________________ > > > 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 > > > > _______________________________________________ > 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 >

CutePDF is actually my PDF creator of choice. When I ran into this new problem, I went back and forth between CutePDF and MS Print to PDF just in case there was a problem with one of them. Perhaps you were the person who reminded me a number of months ago that CutePDF could be used with TMG? On Sat, Aug 31, 2019, 8:31 AM Constance Chappell Horne < [email protected]> wrote: > I would also suggest that if you truly want PDFs, that you install CutePDF. > It installs as a printer. I have it as my default printer and print > everything that way usually. It is free and works great. I highly recommend > it. > > Constance > > On Sat, Aug 31, 2019 at 6:50 AM Judy Madnick <[email protected]> wrote: > > > Note my previous message. I don't have Word and had to change the > > association of .rtf files to Libre Office/Write. Apparently I just had to > > have them associated with some program on my computer, and Windows > > associated them to Word by default. Thanks for your input! > > > > On Fri, Aug 30, 2019, 11:04 PM campbell <[email protected]> wrote: > > > > > Hi Judy > > > I had this same problem not so long ago after some windows or word > > update. > > > I solved the matter by checking (in Win10) Settings/Apps/Default > > > apps/Choose > > > default applications by file type. > > > Make sure ".doc" and similar file extensions select "Word" > > > Make sure ".rtf" selects "Word". > > > > > > Hope this helps > > > > > > Campbell Stanford > > > Auckland > > > New Zealand > > > > > > > > > -----Original Message----- > > > From: Judy Madnick <[email protected]> > > > Sent: Saturday, 31 August 2019 7:01 AM > > > To: The Master Genealogist Rootsweb Email List <[email protected]> > > > Subject: [TMG] .pdf printing problem in 9.05 in Windows 10 > > > > > > New computer, TMG installed, and most everything seems to be okay...so > > far. > > > I've chosen Microsoft Print to PDF, but my reports are being saved to a > > > temp > > > file AND they have an .rtf extension. I'm not finding an option as to > > > where > > > I would like to report to go. On my old computer (also Windows 10), it > > > would > > > show up in my task bar, but not so on my new computer. I don't ever > > > remember > > > having to choose a place for the report to be sent, and it was so > simple > > to > > > just open the file from the task bar. I tried this with CutePDF also > with > > > the same problem resulting. > > > > > > I'm having the same issue with Screen Preview, which used to "pop" > right > > > open. > > > > > > Judy Madnick > > > Albany, NY > > > > > > _______________________________________________ > > > 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 > > > > > > > _______________________________________________ > > 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 >

I would also suggest that if you truly want PDFs, that you install CutePDF. It installs as a printer. I have it as my default printer and print everything that way usually. It is free and works great. I highly recommend it. Constance On Sat, Aug 31, 2019 at 6:50 AM Judy Madnick <[email protected]> wrote: > Note my previous message. I don't have Word and had to change the > association of .rtf files to Libre Office/Write. Apparently I just had to > have them associated with some program on my computer, and Windows > associated them to Word by default. Thanks for your input! > > On Fri, Aug 30, 2019, 11:04 PM campbell <[email protected]> wrote: > > > Hi Judy > > I had this same problem not so long ago after some windows or word > update. > > I solved the matter by checking (in Win10) Settings/Apps/Default > > apps/Choose > > default applications by file type. > > Make sure ".doc" and similar file extensions select "Word" > > Make sure ".rtf" selects "Word". > > > > Hope this helps > > > > Campbell Stanford > > Auckland > > New Zealand > > > > > > -----Original Message----- > > From: Judy Madnick <[email protected]> > > Sent: Saturday, 31 August 2019 7:01 AM > > To: The Master Genealogist Rootsweb Email List <[email protected]> > > Subject: [TMG] .pdf printing problem in 9.05 in Windows 10 > > > > New computer, TMG installed, and most everything seems to be okay...so > far. > > I've chosen Microsoft Print to PDF, but my reports are being saved to a > > temp > > file AND they have an .rtf extension. I'm not finding an option as to > > where > > I would like to report to go. On my old computer (also Windows 10), it > > would > > show up in my task bar, but not so on my new computer. I don't ever > > remember > > having to choose a place for the report to be sent, and it was so simple > to > > just open the file from the task bar. I tried this with CutePDF also with > > the same problem resulting. > > > > I'm having the same issue with Screen Preview, which used to "pop" right > > open. > > > > Judy Madnick > > Albany, NY > > > > _______________________________________________ > > 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 > > > > _______________________________________________ > 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 >

Note my previous message. I don't have Word and had to change the association of .rtf files to Libre Office/Write. Apparently I just had to have them associated with some program on my computer, and Windows associated them to Word by default. Thanks for your input! On Fri, Aug 30, 2019, 11:04 PM campbell <[email protected]> wrote: > Hi Judy > I had this same problem not so long ago after some windows or word update. > I solved the matter by checking (in Win10) Settings/Apps/Default > apps/Choose > default applications by file type. > Make sure ".doc" and similar file extensions select "Word" > Make sure ".rtf" selects "Word". > > Hope this helps > > Campbell Stanford > Auckland > New Zealand > > > -----Original Message----- > From: Judy Madnick <[email protected]> > Sent: Saturday, 31 August 2019 7:01 AM > To: The Master Genealogist Rootsweb Email List <[email protected]> > Subject: [TMG] .pdf printing problem in 9.05 in Windows 10 > > New computer, TMG installed, and most everything seems to be okay...so far. > I've chosen Microsoft Print to PDF, but my reports are being saved to a > temp > file AND they have an .rtf extension. I'm not finding an option as to > where > I would like to report to go. On my old computer (also Windows 10), it > would > show up in my task bar, but not so on my new computer. I don't ever > remember > having to choose a place for the report to be sent, and it was so simple to > just open the file from the task bar. I tried this with CutePDF also with > the same problem resulting. > > I'm having the same issue with Screen Preview, which used to "pop" right > open. > > Judy Madnick > Albany, NY > > _______________________________________________ > 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 >

Hi Judy I had this same problem not so long ago after some windows or word update. I solved the matter by checking (in Win10) Settings/Apps/Default apps/Choose default applications by file type. Make sure ".doc" and similar file extensions select "Word" Make sure ".rtf" selects "Word". Hope this helps Campbell Stanford Auckland New Zealand -----Original Message----- From: Judy Madnick <[email protected]> Sent: Saturday, 31 August 2019 7:01 AM To: The Master Genealogist Rootsweb Email List <[email protected]> Subject: [TMG] .pdf printing problem in 9.05 in Windows 10 New computer, TMG installed, and most everything seems to be okay...so far. I've chosen Microsoft Print to PDF, but my reports are being saved to a temp file AND they have an .rtf extension. I'm not finding an option as to where I would like to report to go. On my old computer (also Windows 10), it would show up in my task bar, but not so on my new computer. I don't ever remember having to choose a place for the report to be sent, and it was so simple to just open the file from the task bar. I tried this with CutePDF also with the same problem resulting. I'm having the same issue with Screen Preview, which used to "pop" right open. Judy Madnick Albany, NY _______________________________________________ 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

Michael, I wrote: > The "1" (or whatever digit is first) does NOT need to be escaped. You wrote: > No, but precisely to avoid confusion about the purpose of the > minus sign it needs to be separated from the latitude value, > which escape does. ... And I also wrote that I was presuming to know what TMG was attempting. That was accurate, I was presuming, but I left out something important: I was deeply involved in the specification process when TMG switched from using a degrees-minutes-seconds format to decimal degrees. I wrote the initial request to change to decimal degrees, I reviewed the instructions given to the implementer, and I discussed edge cases and other issues with the implementer. We never discussed using the escape character as a visual signal to the user and I would have vehemently opposed that usage. From early in the 2000s, I argued for a simple, one-size-fits-all approach to escape character processing and even quoted that during discussions of the decimal degrees implementation: 1 - That TMG should use a single "escape" character, '\' (backslash) 2 - The escape character should always defeat the special meaning of the subsequent character (if any) No more, no less. No additional rules, no additional purposes. The rule is simple, and while it may not be intuitive to all TMG users, it's easy to remember once learned. The rule has the benefit of being very similar, if not exactly the same, as backslash used as an escape in dozens of other systems. So, I would have been on high-alert for someone proposing to use '\' as a signal that the hyphen was not part of the decimal latitude value. Furthermore, I just reviewed some email messages from 2010 when the change was made, and we explicitly discussed the issue of negative latitude values and the requirement that the user would have to enter the escape character to defeat the special meaning of the leading hyphen. We did not discuss using the backslash as a signal to the user. We did not discuss any special data entry rules, at least via email, but there were other discussion tools and I suspect further discussions took place there. John

Problem solved. I had .rtf files associated with Word (by default), and I don't have Word! So I downloaded Libre Office, associated .rtf files with that, and...BINGO! Whew! On Fri, Aug 30, 2019 at 3:01 PM Judy Madnick <[email protected]> wrote: > > New computer, TMG installed, and most everything seems to be okay...so > far. I've chosen Microsoft Print to PDF, but my reports are being > saved to a temp file AND they have an .rtf extension. I'm not finding > an option as to where I would like to report to go. On my old computer > (also Windows 10), it would show up in my task bar, but not so on my > new computer. I don't ever remember having to choose a place for the > report to be sent, and it was so simple to just open the file from the > task bar. I tried this with CutePDF also with the same problem > resulting. > > I'm having the same issue with Screen Preview, which used to "pop" right open. > > Judy Madnick > Albany, NY

The use of a leading "-" as an exclusion marker in TMG has proved to been problematic. HRE will use a leading "}" to show that the whole field is excluded this avoiding this problem. RobinL On 31/08/2019 9:34 am, Michael J. Hannah wrote: > John Cardinal wrote: >> The user enters "-12.123456,123.123456". >> >> TMG replaces the leading "-12" with "-\12". >> >> There is no reason to make that change. > > We can agree to disagree.  I think there IS a reason, and I think it > is a good one.  I think the change "emphasizes" that TMG is > interpreting the entire LatLong value as single excluded.  Using the > escape character to "separate" the exclusion character from the > LatLong value I think is very helpful.  Now visually the minus sign > CLEARLY is not part of the latitude value. > >> The "1" (or whatever digit is first) does NOT need to be escaped. > > No, but precisely to avoid confusion about the purpose of the minus > sign it needs to be separated from the latitude value, which escape does. > >> I admit that I am only presuming what TMG probably intended to do > > Obviously I am also only presuming.  <smile> > >> but using an escape character is a BIG clue: > > I disagree.  It is the only character which could be added to a valid > Lat/Long value to make it clear that the exclusion minus sign is not > part of the latitude value, especially as TMG does not allow spaces in > this value except to separate latitude from longitude. > >> the only reason to add an escape is to avoid interpreting >> the leading hyphen as an exclusion marker. > > No, adding the escape where it does makes it clear TMG *IS* > interpreting the leading minus as an exclusion marker.  To avoid > interpreting the minus as an exclusion marker requires the USER to > escape the minus sign.  I believe the error is the user's.  If there > is no escape entered by the user then I think TMG MUST interpret it as > exclusion, and separating the minus from the latitude value makes that > interpretation even clearer. > >> If I am wrong, then the TMG behavior is still a bug, > > No, I do not think it is a bug, I think the problem is erroneous data > entry by the user.  How else is TMG to differentiate an excluded > LatLong value from a negative latitude?  If the user fails to escape > the minus, then the value must be viewed by TMG as intended to be > exclusion. > >> ...the result is a completely useless change that will confuse users. > > And I believe the result "clears up" any possible confusion of whether > the LatLong value is: > > A) an excluded value with a positive latitude: -\12.123456,123.123456 > versus > B) a non-excluded value with a negative latitude: \-12.123456,123.123456 > > I think these are clearly different, with no confusion between them. > > The only confusing value is: -12.123456,123.123456   Which is this? > > But again obviously these are just our differing opinions based on our > differing presumptions of what TMG intended with this action when this > code was written well over five years ago. > > Not the first time we have assumed different things about TMG <grin> > > Michael > > P.S. The reason that "Preferences / Program Options / Prompts / > Validate LAT/LONG values" triggers this automatic escape character is > that if this Preference is disabled, any value entered in this place > field is treated as text by TMG and not as a Latitude/Longitude > value.  So IMHO TMG is validating the Lat/Long value and "clearing up" > any confusion. > > _______________________________________________ > 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 > -- Robin Lamacraft, Adelaide, Australia --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

John Cardinal wrote: > The user enters "-12.123456,123.123456". > > TMG replaces the leading "-12" with "-\12". > > There is no reason to make that change. We can agree to disagree. I think there IS a reason, and I think it is a good one. I think the change "emphasizes" that TMG is interpreting the entire LatLong value as single excluded. Using the escape character to "separate" the exclusion character from the LatLong value I think is very helpful. Now visually the minus sign CLEARLY is not part of the latitude value. > The "1" (or whatever digit is first) does NOT need to be escaped. No, but precisely to avoid confusion about the purpose of the minus sign it needs to be separated from the latitude value, which escape does. > I admit that I am only presuming what TMG probably intended to do Obviously I am also only presuming. <smile> > but using an escape character is a BIG clue: I disagree. It is the only character which could be added to a valid Lat/Long value to make it clear that the exclusion minus sign is not part of the latitude value, especially as TMG does not allow spaces in this value except to separate latitude from longitude. > the only reason to add an escape is to avoid interpreting > the leading hyphen as an exclusion marker. No, adding the escape where it does makes it clear TMG *IS* interpreting the leading minus as an exclusion marker. To avoid interpreting the minus as an exclusion marker requires the USER to escape the minus sign. I believe the error is the user's. If there is no escape entered by the user then I think TMG MUST interpret it as exclusion, and separating the minus from the latitude value makes that interpretation even clearer. > If I am wrong, then the TMG behavior is still a bug, No, I do not think it is a bug, I think the problem is erroneous data entry by the user. How else is TMG to differentiate an excluded LatLong value from a negative latitude? If the user fails to escape the minus, then the value must be viewed by TMG as intended to be exclusion. > ...the result is a completely useless change that will confuse users. And I believe the result "clears up" any possible confusion of whether the LatLong value is: A) an excluded value with a positive latitude: -\12.123456,123.123456 versus B) a non-excluded value with a negative latitude: \-12.123456,123.123456 I think these are clearly different, with no confusion between them. The only confusing value is: -12.123456,123.123456 Which is this? But again obviously these are just our differing opinions based on our differing presumptions of what TMG intended with this action when this code was written well over five years ago. Not the first time we have assumed different things about TMG <grin> Michael P.S. The reason that "Preferences / Program Options / Prompts / Validate LAT/LONG values" triggers this automatic escape character is that if this Preference is disabled, any value entered in this place field is treated as text by TMG and not as a Latitude/Longitude value. So IMHO TMG is validating the Lat/Long value and "clearing up" any confusion.