RootsWeb.com Mailing Lists
Previous Page      Next Page
Total: 40/1881
    1. [Refugees]Re: Importing TMG projects in native Mac environment
    2. Doris Wheeler
    3. My only experience with Gramps was that it was extremely simplistic -- no advanced features at all. It may have been upgraded since. On Sun, Dec 8, 2019 at 11:32 AM Michael Maggs <[email protected]> wrote: > An option that will run on a Mac, as well as other platforms, is Gramps. > > I haven’t tried it yet. Does anyone have experience of the program? > > Michael > > > On 8 Dec 2019, at 14:37, [email protected] wrote: > > > > Just to be sure, if you want to directly import TMG projects into > native Mac Catalina software, there are apparently at this moment only two > options: RootsMagic & FTB (if Mac Catalina compliant). Is this true? > > > > _______________________________________________ > > 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 > -- https://www.doriswheeler.org

    12/08/2019 11:10:12
    1. [Refugees]Re: Importing TMG projects in native Mac environment
    2. Michael Maggs
    3. An option that will run on a Mac, as well as other platforms, is Gramps. I haven’t tried it yet. Does anyone have experience of the program? Michael > On 8 Dec 2019, at 14:37, [email protected] wrote: > > Just to be sure, if you want to directly import TMG projects into native Mac Catalina software, there are apparently at this moment only two options: RootsMagic & FTB (if Mac Catalina compliant). Is this true? > > _______________________________________________ > 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

    12/08/2019 09:32:36
    1. [Refugees]Re: Importing TMG projects in native Mac environment
    2. Janis Rodriguez
    3. The current version of RM does NOT run on Mac OS Catalina which will not run 32 bit programs. RM sent out a warning to RM users NOT to upgrade to Catalina. Also, RootsMagic is NOT native Mac, YET. RM users a “wrapper” to run RM on a Mac. Kind of like Parallels but only works for RM. The next version of RM is supposed to run native on a MAC. Perhaps that is why it is taking so long to come out… Jan > On Dec 8, 2019, at 9:37 AM, [email protected] wrote: > > Just to be sure, if you want to directly import TMG projects into native Mac Catalina software, there are apparently at this moment only two options: RootsMagic & FTB (if Mac Catalina compliant). Is this true? > > _______________________________________________ > 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

    12/08/2019 08:22:58
    1. [Refugees]Importing TMG projects in native Mac environment
    2. Just to be sure, if you want to directly import TMG projects into native Mac Catalina software, there are apparently at this moment only two options: RootsMagic & FTB (if Mac Catalina compliant). Is this true?

    12/08/2019 07:37:01
    1. [Refugees]Re: GEDCOM Assessment
    2. torleif haugødegård
    3. John, What I meant was that it is important to work also with the huge MyHeritage company if the goal is to change/upgrade the GEDCOM standard. BTW, I learned today that MH FTB can read TMG's PJC project files directly, then it converts them to GEDCOM and then imports the GED in FTB. And it worked ok, it seems. 0 HEAD 1 GEDC 2 VERS 5.5 2 FORM LINEAGE-LINKED 1 SOUR MYHERITAGE-CONVERTOR (TMG) 2 VERS 1.0 2 CORP MyHeritage.com 3 ADDR 4 CITY Bnei Atarot 4 POST 60991 4 CTRY Israel 1 DEST MYHERITAGE 1 DATE 8 DEC 2019 1 CHAR ANSI 0 @[email protected] INDI ............ -----Opprinnelig melding----- Fra: John Cardinal <[email protected]> Sendt: søndag 8. desember 2019 13.13 Til: For refugees from TMG genealogy software. <[email protected]> Emne: [Refugees]Re: GEDCOM Assessment Torleif, Can you explain further? What is special about the HEAD record and subrecords of FTB? John On Sunday, December 8, 2019, torleif haugødegård <[email protected]> wrote: > I guess the most important acceptance to get is from this company; See > copy from a GEDCOM from my test site today: > > 0 HEAD > 1 GEDC > 2 VERS 5.5.1 > 2 FORM LINEAGE-LINKED > 1 CHAR UTF-8 > 1 LANG Norwegian > 1 SOUR MYHERITAGE > 2 NAME MyHeritage Family Tree Builder > 2 VERS 5.5.1 > 2 _RTLSAVE RTL > 2 CORP MyHeritage.com > 1 DEST MYHERITAGE > 1 DATE 08 DEC 2019 > .......... > > > Torleif Haugødegård > _______________________________________________ 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

    12/08/2019 05:30:46
    1. [Refugees]Re: GEDCOM Assessment
    2. John Cardinal
    3. Torleif, Can you explain further? What is special about the HEAD record and subrecords of FTB? John On Sunday, December 8, 2019, torleif haugødegård <[email protected]> wrote: > I guess the most important acceptance to get is from this company; > See copy from a GEDCOM from my test site today: > > 0 HEAD > 1 GEDC > 2 VERS 5.5.1 > 2 FORM LINEAGE-LINKED > 1 CHAR UTF-8 > 1 LANG Norwegian > 1 SOUR MYHERITAGE > 2 NAME MyHeritage Family Tree Builder > 2 VERS 5.5.1 > 2 _RTLSAVE RTL > 2 CORP MyHeritage.com > 1 DEST MYHERITAGE > 1 DATE 08 DEC 2019 > .......... > > > Torleif Haugødegård >

    12/08/2019 05:12:48
    1. [Refugees]Re: GEDCOM Assessment
    2. torleif haugødegård
    3. I guess the most important acceptance to get is from this company; See copy from a GEDCOM from my test site today: 0 HEAD 1 GEDC 2 VERS 5.5.1 2 FORM LINEAGE-LINKED 1 CHAR UTF-8 1 LANG Norwegian 1 SOUR MYHERITAGE 2 NAME MyHeritage Family Tree Builder 2 VERS 5.5.1 2 _RTLSAVE RTL 2 CORP MyHeritage.com 1 DEST MYHERITAGE 1 DATE 08 DEC 2019 .......... Torleif Haugødegård -----Opprinnelig melding----- Fra: John Cardinal <[email protected]> Sendt: fredag 6. desember 2019 15.35 Til: 'For refugees from TMG genealogy software.' <[email protected]> Emne: [Refugees]Re: GEDCOM Assessment Torleif, If GEDCOM 5.5.5 gains acceptance and is implemented by any of the popular programs, I'll consider adding support for it in assess.ged. 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

    12/08/2019 01:44:30
    1. [Refugees]Re: GEDCOM Assessment
    2. Richard Damon
    3. On 12/7/19 4:39 PM, John Cardinal wrote: > Richard, > > Tamura Jones took a different approach with 5.5.5 than I did with 5.5.2. I was trying to get software authors to agree on a modified GEDCOM 5.5.1 where most of the (relatively few) changes were limiting the spec to things that programs could already do. For example, my GEDCOM 5.5.2 was limited to UTF-8 only. That simplifies life for GEDCOM readers and writers. I also clarified the parsing rules, another attempt to make it easier to write conforming software. > > Regarding HEAD.NOTE, GEDCOM 5.5.1 allows CONT and CONC under HEAD.NOTE (pg 23-24, 2 OCT 1999 version of the draft). In my GEDCOM 5.5.2, I allowed CONT and CONC everywhere except for HEAD.CHAR and HEAD.GEDC.VERS. Those two limitations were stipulated solely to make it easier for "preview" components to verify the version and character encoding before starting up a full reader that supports CONT and CONC. > > I'll have to get over my aversion to reading PDF documents online and re-read GEDCOM 5.5.5. > > John I may have mis-read the comment from the TSC list about HEAD.NOTE and CONT (I grabbed a simple example given from a list of complaints give), it looks like that is allowed in 5.5.1 but has been explicitly forbidden in 5.5.5 due to the following section: CONC & CONT Restriction The GEDCOM specification allows CONC & CONT anywhere they are needed. GEDCOM 5.5.5 introduces a restriction, that should have been part of GEDCOM from the beginning, to keep parsing GEDCOM files simple; CONC & CONT must not be used with basic GEDCOM records, only with records defined by a GEDCOM form. It is illegal to use CONC or CONT within the Basic GEDCOM header. It is legal, but strongly discommended, to use CONC or CONT within a form-specific header extension. It is important to keep the GEDCOM header simple. The GEDCOM header is not only examined by GEDCOM readers, but also by general utilities that report file types. HEAD.DATE.COPR and HEAD.NOTE To avoid needing CONC & CONT with header subrecords of the Lineage-Linked Form, the maximum length of the HEAD.DATE.COPR and HEAD.NOTE lines values have both been set at 248 code units. The 248 code units allowed for <COPYRIGHT_GEDCOM_FILE> is significantly more than the maximum of 90 code units allowed by GEDCOM 5.4 and 5.5. The 248 code units allowed for <GEDCOM_CONTENT_DESCRIPTION> is more than the maximum 213 code units allowed by GEDCOM 5.4, and identical to the maximum of 248 code units allowed by GEDCOM 5.5. This seems to be a bit of a sample of the 'improvements' that Tamura Jones decided was needed, where practices she didn't think were good uses were just prohibited. -- Richard Damon

    12/07/2019 03:18:57
    1. [Refugees]Re: GEDCOM Assessment
    2. John Cardinal
    3. Richard, Tamura Jones took a different approach with 5.5.5 than I did with 5.5.2. I was trying to get software authors to agree on a modified GEDCOM 5.5.1 where most of the (relatively few) changes were limiting the spec to things that programs could already do. For example, my GEDCOM 5.5.2 was limited to UTF-8 only. That simplifies life for GEDCOM readers and writers. I also clarified the parsing rules, another attempt to make it easier to write conforming software. Regarding HEAD.NOTE, GEDCOM 5.5.1 allows CONT and CONC under HEAD.NOTE (pg 23-24, 2 OCT 1999 version of the draft). In my GEDCOM 5.5.2, I allowed CONT and CONC everywhere except for HEAD.CHAR and HEAD.GEDC.VERS. Those two limitations were stipulated solely to make it easier for "preview" components to verify the version and character encoding before starting up a full reader that supports CONT and CONC. I'll have to get over my aversion to reading PDF documents online and re-read GEDCOM 5.5.5. John

    12/07/2019 02:39:27
    1. [Refugees]Re: GEDCOM Assessment
    2. Richard Damon
    3. On 12/6/19 9:49 AM, John Cardinal wrote: > Richard Damon wrote: >> The GEDCOM 5.5.5 that I think you are refering to is (to my >> understanding) an unofficial release by a single person, > Richard, The document included multiple reviews, but Tamura Jones > holds the copyright, so I think you are right it was primarily the > work of one author. That's not necessarily a bad thing. Tamura Jones appears to have created a site called gedcom.org that CLAIMS to be 'This website is the official home of the GEDCOM specification.', which unless the LDS church has actually assigned such rights is an outright lie, and my understanding of the current domain name rules the LDS church could probably initiate a take-down order for the whole site (and domain name). The REAL official site for GEDCOM is https://www.familysearch.org/developers/docs/gedcom/ There are other groups/people working on successor 'standard' formats, and in general they tend to acknowledge that GEDCOM is 'owned' by the LDS, and come up with their own name,  >> without any authorization by the owners of the GEDCOM standard > The LDS has abandoned the GEDCOM standard (formally or not doesn't > matter) and its unlikely they will authorize any one else to produce > an official release. The hard part about uniting on an update to that > standard is not whether it can include "GEDCOM" in the name, though I > doubt the LDS will fight that. The hard part is getting the US/CAN/UK > players to get behind it. I produced GEDCOM 5.5.2 and worked behind > the scenes to get it adopted. I had a few comments from interested > parties, but the main players in the US/CAN/UK market ignored it. See: > https://jfcardinal.github.io/GEDCOM-5.5.2/gedcom-5.5.2.html I far > prefer my 5.5.2 proposal over GEDCOM 5.5.5. There are a lot of > similarities, but 5.5.5 has some curious and unnecessary inclusions. A > pet peeve of mine is that it is delivered in a hard-to-use PDF. This > is 2019, almost 2020. Standards should be online and in HTML. >> and currently has no industry backing. > I believe that's true and it's the key part. >> While it fixes some of the things that were problematic with the >> GEDCOM 5.5.1 document, it also breaks other things due to the person >> personal bias on what GEDCOM should be. > I read the 5.5.5 spec pretty carefully. I didn't see anything that > would be hard to implement or would "break things". I didn't agree > with several things, including a couple that I thought would put > people off. Regarding breaking things, can you give an example? From the discussion in the TSC group, it appears that due to some of the added restrictions in 5.5.5 that some data structures that have been used in 5.5.1 are specifically prohibited, and there isn't a clear path forward to implement them. One big issue is that the 'standard' insists that programs that read a 5.5.5 Gedcom must REJECT a file that doesn't fully conform to the spec, and isn't allowed to make a best effort to understand it. It prohibits the using of predefined tags in spots not specifically defined, creating a variant of a standard tag by adding a _ in front of it (tags with _ in front are specifically reserved for extensions, but can not be an existing tag with just a _ added in front, which breaks a lot of currently agreed upon extensions) and you can not create an extension tag that duplicates an existing defined tag (apparently even to use in a spot the original tag isn't allowed). One example given was that HEAD.NOTE doesn't specifically allow CONC/CONT, but it is commonly considered an acceptable extension to allow it, but by the Tamura Jones 5.5.5 a file that does that MUST be rejected, and it appears to be no easy way to define such a capability without running afoul of those rules. >> The TSC group which is working on a formal definition of an >> interchange format, that includes a GEDCOM compatibility mode has >> decided to just ignore this so called standard and not try to include >> it as part of its interoperability definition. > Does TSC have any industry backing? >From what I have read, TSC is > going much deeper than 5.5.2 or 5.5.5 attempted. My efforts, at least, > were focused on fixing some of the broken and ambiguous elements of > the GEDCOM 5.5.1 spec. I believe we have to get software authors to > agree on a GEDCOM standard before there is any hope of implementing a > better, replacement transfer standard. The TSC effort is a separate > effort, really. > John FHISO, the group that TSC works under does have some industry backing, including Ancestry.org, Rootsmagic, the FGS, and FFHS (or at least they were involved at the start, I don't follow it close enough to know how active they still are with the organization). And yes, it appears that their long term goal is something much bigger, but they are also working on a 'legacy' format that is basically GEDCOM with some cleanup and improved definition. -- Richard Damon

    12/07/2019 10:24:01
    1. [Refugees]Re: GEDCOM Assessment
    2. John Cardinal
    3. Richard Damon wrote: > The GEDCOM 5.5.5 that I think you are refering to is (to my > understanding) an unofficial release by a single person, Richard, The document included multiple reviews, but Tamura Jones holds the copyright, so I think you are right it was primarily the work of one author. That's not necessarily a bad thing. > without any authorization by the owners of the GEDCOM standard The LDS has abandoned the GEDCOM standard (formally or not doesn't matter) and its unlikely they will authorize any one else to produce an official release. The hard part about uniting on an update to that standard is not whether it can include "GEDCOM" in the name, though I doubt the LDS will fight that. The hard part is getting the US/CAN/UK players to get behind it. I produced GEDCOM 5.5.2 and worked behind the scenes to get it adopted. I had a few comments from interested parties, but the main players in the US/CAN/UK market ignored it. See: https://jfcardinal.github.io/GEDCOM-5.5.2/gedcom-5.5.2.html I far prefer my 5.5.2 proposal over GEDCOM 5.5.5. There are a lot of similarities, but 5.5.5 has some curious and unnecessary inclusions. A pet peeve of mine is that it is delivered in a hard-to-use PDF. This is 2019, almost 2020. Standards should be online and in HTML. > and currently has no industry backing. I believe that's true and it's the key part. > While it fixes some of the things that were problematic with > the GEDCOM 5.5.1 document, it also breaks other things due to > the person personal bias on what GEDCOM should be. I read the 5.5.5 spec pretty carefully. I didn't see anything that would be hard to implement or would "break things". I didn't agree with several things, including a couple that I thought would put people off. Regarding breaking things, can you give an example? > The TSC group which is working on a formal definition of an > interchange format, that includes a GEDCOM compatibility mode has > decided to just ignore this so called standard and not try to > include it as part of its interoperability definition. Does TSC have any industry backing? From what I have read, TSC is going much deeper than 5.5.2 or 5.5.5 attempted. My efforts, at least, were focused on fixing some of the broken and ambiguous elements of the GEDCOM 5.5.1 spec. I believe we have to get software authors to agree on a GEDCOM standard before there is any hope of implementing a better, replacement transfer standard. The TSC effort is a separate effort, really. John

    12/06/2019 07:49:42
    1. [Refugees]Re: GEDCOM Assessment
    2. John Cardinal
    3. Torleif, If GEDCOM 5.5.5 gains acceptance and is implemented by any of the popular programs, I'll consider adding support for it in assess.ged. John

    12/06/2019 07:35:09
    1. [Refugees]Re: GEDCOM Assessment
    2. Richard Damon
    3. On 12/6/19 5:12 AM, torleif haugødegård wrote: > How abt GEDCOM 5.5.5? > Considering to change/revise assess.ged? > > Torleif Haugødegård > TMG user in Norway since 1995 > > The GEDCOM 5.5.5 that I think you are refering to is (to my understanding) an unofficial release by a single person, without any authorization by the owners of the GEDCOM standard, and currently has no industry backing. While it fixes some of the things that were problematic with the GEDCOM 5.5.1 document, it also breaks other things due to the person personal bias on what GEDCOM should be. The TSC group which is working on a formal definition of an interchange format, that includes a GEDCOM compatibility mode has decided to just ignore this so called standard and not try to include it as part of its interoperability definition. -- Richard Damon

    12/06/2019 05:59:55
    1. [Refugees]Re: GEDCOM Assessment
    2. torleif haugødegård
    3. How abt GEDCOM 5.5.5? Considering to change/revise assess.ged? Torleif Haugødegård TMG user in Norway since 1995 -----Opprinnelig melding----- Fra: John Cardinal <[email protected]> Sendt: onsdag 4. desember 2019 22.37 Til: TMG-L <[email protected]>; [email protected] Emne: [Refugees]GEDCOM Assessment TMG and GEDCOM users, You may be interested to review a new facility, "GEDCOM Assessments". It began as structured way to evaluate how to configure TMG to GEDCOM for target applications. It grew into a separate, general-purpose facility for assessing the GEDCOM import capability of any target program or service. See: https://www.gedcomassessment.com The key component of GEDCOM Assessment is "assess.ged", a hand-crafted GEDCOM file. It's only been available a few days, and I have already heard from three software publishers who have used assess.ged to discover errors or omissions in their import methods. End users who have reason to use GEDCOM files should scan the "Assessment Review" for the application(s) they use. See: https://www.gedcomassessment.com/en/contents.htm#assessments John Cardinal Author of genealogy programs including Second Site, TMG Utility, GedSite, Gedcom Publisher, and TMG to GEDCOM _______________________________________________ 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

    12/06/2019 03:12:23
    1. [Refugees]Re: Assistance trying to "register" my TMG??? PLEASE???
    2. Jim Byram
    3. Diana, I'm assuming that you are using the account that Windows 10 created. It is an Administrator account. Administrator accounts in Windows 10 run normally as a Standard user unless the permissions are elevated. It's always best to copy the registration key from the registration information and paste it to the unlock screen. And be sure to use the information that came in the registration email that came from Wholly Genes. You need to unlock TMG two ways. 1) Running Windows 10 normally (as a Standard user). Run TMG and unlock it. Exit TMG. 2) Running TMG as administrator with elevated permissions. Right-click on the TMG shortcut and select 'Run as administrator'. Respond affirmatively to the permissions prompt and unlock TMG. Exit TMG after unlocking. Now run TMG normally when using it. You shouldn't need to unlock again. Jim

    12/04/2019 07:36:55
    1. [Refugees]Assistance trying to "register" my TMG??? PLEASE???
    2. Diana Carlson
    3. I was having trouble using TMG on Parallels on a Macintosh so I finally broke down and bought a Windows 10 pc just for TMG. It worked for awhile..but now I see it never really registered correctly, and now, most functionality is greyed out. Yes, I cannot access my data, and I’ve got about a dozen projects. I tried again today to register it, but it says registration data is invalid, even though I copied it from my previous TMG. Is there anyone who can help me get this registered again? Diana L. Carlson

    12/04/2019 05:28:20
    1. [Refugees]GEDCOM Assessment
    2. John Cardinal
    3. TMG and GEDCOM users, You may be interested to review a new facility, "GEDCOM Assessments". It began as structured way to evaluate how to configure TMG to GEDCOM for target applications. It grew into a separate, general-purpose facility for assessing the GEDCOM import capability of any target program or service. See: https://www.gedcomassessment.com The key component of GEDCOM Assessment is "assess.ged", a hand-crafted GEDCOM file. It's only been available a few days, and I have already heard from three software publishers who have used assess.ged to discover errors or omissions in their import methods. End users who have reason to use GEDCOM files should scan the "Assessment Review" for the application(s) they use. See: https://www.gedcomassessment.com/en/contents.htm#assessments John Cardinal Author of genealogy programs including Second Site, TMG Utility, GedSite, Gedcom Publisher, and TMG to GEDCOM

    12/04/2019 02:37:03
    1. [Refugees]TMG to GEDCOM Update: Version 1.03
    2. John Cardinal
    3. TMG to GEDCOM (T2G) v1.03 is now available. This is a free upgrade for existing customers that includes a few important enhancements. I recommend that all users install this version. The Newsletter for this release includes additional details and links: https://www.tmgtogedcom.com/en/tgn004.htm John Cardinal Author of genealogy programs including Second Site, TMG Utility, GedSite, Gedcom Publisher, and TMG to GEDCOM

    12/04/2019 02:28:35
    1. [Refugees]Re: TMG-REFUGEES Digest, Vol 6, Issue 59
    2. Great! Spot on. Saved me hours of research, trial and error and frustration. My heartfelt thanks! And I'll remember TMG-L for future technical questions. Andreas -----Original Message----- From: [email protected] <[email protected]> Sent: 4 December 2019 10:03 To: [email protected] Subject: TMG-REFUGEES Digest, Vol 6, Issue 59 Send TMG-REFUGEES mailing list submissions to [email protected] To subscribe via email send a message with subject subscribe and body subscribe to [email protected] To unsubscribe via email send a message with subject unsubscribe and body unsubscribe to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of TMG-REFUGEES digest..." Today's Topics: 1. TMG on Windows 10 - Norwegian letters displays wrongly (Andreas F. Halvorsen) 2. Re: TMG on Windows 10 - Norwegian letters displays wrongly (John Cardinal) ---------------------------------------------------------------------- Date: Tue, 3 Dec 2019 23:07:27 +0100 From: "Andreas F. Halvorsen" <[email protected]> Subject: [Refugees]TMG on Windows 10 - Norwegian letters displays wrongly To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" I am following the TMG-refugees mailings with interest, notably those discussing keeping TMG alive, problems with migrating the data to other platforms and recently how to make the results of years of research available to others after the researcher has stopped researching. I have maintained my TMG on a computer with Windows 7 until now. I intend keeping that computer alive as long as possible with TMG on it as a backup, but I am now in the process of migrating to a new laptop with Windows 10 for daily use. Installation of TMG 9 seemed to work just fine, but dates and Norwegian letters were displayed wrong. The dates, in formats with months represented by letters, like dd MMM yyyy, are represented with the spaces substituted with three characters: an i with two dots, an upside-down question mark and ½. In formats with months represented by numbers, the “.”, “-“ or “/” are correctly rendered. The Norwegian letters are likewise rendered as the same three characters as above. It seems that an i with two dots, an upside-down question mark and ½represents any unknown character. Has anyone encountered this problem, and found a solution for it? And if the question is outside the scope here, I would appreciate tips regarding where it would be within scope. Andreas ------------------------------ Date: Tue, 3 Dec 2019 17:31:28 -0500 From: "John Cardinal" <[email protected]> Subject: [Refugees]Re: TMG on Windows 10 - Norwegian letters displays wrongly To: "'For refugees from TMG genealogy software.'" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Andreas, Your post should probably be on TMG-L rather than TMG-Refugees. I have seen that problem before. I was helping someone else and I am not sure of all the details. If I recall correctly, there was a setting that enabled a Win10 beta feature, "Beta: Use Unicode UTF-8 for worldwide language support". If that option is checked, that causes an issue in TMG. That setting would cause trouble for any application that does not use UTF-8 as the beta feature expects. Finding that setting takes a lot of clicks! 1. Open the Win10 Settings. 2. In the "Find a setting" textbox, type "Region" and click "Region settings" when it appears. 3. Scroll down to "Additional date, time, & regional settings" and click it. 4. On "Control Panel\Clock and Region", under Region, click "Change date, time, or number formats". 5 - On the "Region" window, click the "Administrative" tab. 6 - On the Administrative tab, click the [Change system locale] button. Tired yet? 7 - On the "Region Settings" window, uncheck the "Beta: Use Unicode UTF-8 for worldwide language support" checkbox if it is checked. That should do it, but I do not have an easy way of testing whether the that property causes the behavior you described. Let me know how it goes... John ------------------------------ Subject: Digest Footer ------------------------------ End of TMG-REFUGEES Digest, Vol 6, Issue 59 *******************************************

    12/04/2019 02:28:17
    1. [Refugees]Re: TMG on Windows 10 - Norwegian letters displays wrongly
    2. John Cardinal
    3. Andreas, Your post should probably be on TMG-L rather than TMG-Refugees. I have seen that problem before. I was helping someone else and I am not sure of all the details. If I recall correctly, there was a setting that enabled a Win10 beta feature, "Beta: Use Unicode UTF-8 for worldwide language support". If that option is checked, that causes an issue in TMG. That setting would cause trouble for any application that does not use UTF-8 as the beta feature expects. Finding that setting takes a lot of clicks! 1. Open the Win10 Settings. 2. In the "Find a setting" textbox, type "Region" and click "Region settings" when it appears. 3. Scroll down to "Additional date, time, & regional settings" and click it. 4. On "Control Panel\Clock and Region", under Region, click "Change date, time, or number formats". 5 - On the "Region" window, click the "Administrative" tab. 6 - On the Administrative tab, click the [Change system locale] button. Tired yet? 7 - On the "Region Settings" window, uncheck the "Beta: Use Unicode UTF-8 for worldwide language support" checkbox if it is checked. That should do it, but I do not have an easy way of testing whether the that property causes the behavior you described. Let me know how it goes... John

    12/03/2019 03:31:28