Re: [LegacyUG] Death-burial-cremation
I have several relatives who were cremated, and then the urn buried in a cemetery plot marked with a gravestone. None of mine have been interred in memorial buildings (I don't know what they are called) with memorial crypts built into walls. Those crypts have memorial inscriptions. So, in that way, they have a cemetery and grave marker. It's your preference, but I list the site of the burial of the remains, in whatever form those remains may be. I deem the site of the cremation to be unimportant. It's going to become more confusing becauses now people are choosing organic disposal of their remains, which yields 1 cubic yard of compost. Great if you want to fertilize your or someone else's trees (there are groves devoted to that). So, perhaps your relative's burial site will be your back yard, under the large oak next to the south fence, or, in the memorial grove at..."xxx, some town, some county, some country. Everyone decides how to best handle their own information. There is no "correct" method. Providing enough information, in notes or extra events, is what is important. Cheers, CE From: LegacyUserGroup on behalf of Ian Thomas Sent: Wednesday, November 27, 2019 8:13 PM To: Legacy User Group Subject: [LegacyUG] Death-burial-cremation I have begun giving my records more accurate information against their “burial” line in Legacy. Some Melbourne, Australia cemeteries give an annotation “Interment of C.R.” which I interpret as interment /burial of the cremated remains. It may be a common practice. So I have been changing or making their record as Cremation, and also adding a General Note to indicate (ie, that there may actually be a grave or memorial of some type). For some, it may be useful to visit or to search Billion Graves. Is this the only way / best way? I.L. Thomas Victoria Park, Western Australia From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Chris Hill Sent: Thursday, 28 November 2019 12:07 AM To: Legacy User Group Subject: Re: [LegacyUG] Using special alphabet characters in Legacy Hi John I quite agree, Legacy will be stuck with ANSI until they rewrite it. Given that there is also pressure, from its users, for a Mac version, and presumably a Linux version, they have a need to develop a new program and database that is multi-OS compatible. Hopefully, with the support from MyHeritage, this will happen, but MH also owns Family Tree Builder so it might put pressure on merging with it. Regards Chris -- Original Message -- From: "John Cardinal" mailto:jfcardi...@gmail.com>> To: "Legacy User Group" mailto:legacyusergroup@legacyusers.com>> Sent: 27/11/2019 14:26:14 Subject: Re: [LegacyUG] Using special alphabet characters in Legacy Chris, During my 41-year career I've been a software developer, software architect, and CTO, including a five-year period where my team developed commercial applications in VB6. Since 1999 I've had a couple of side-project applications implemented in VB6. My focus now is .NET. As discussed on the site you mentioned and others, there are challenges to implementing Unicode-aware VB6 applications. Other sites describe how to meet those challenges. A couple techniques we used were Unicode-aware component packages and TLBs for access to wide-character functions. Perhaps the technology infrastructure Legacy uses has an ANSI-only component baked-in and switching it out would require a rewrite-level effort. If so, they'd never rewrite in VB6 now so the effective result is "we can't support Unicode until we abandon VB6". John -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
[LegacyUG] Death-burial-cremation
I have begun giving my records more accurate information against their “burial” line in Legacy. Some Melbourne, Australia cemeteries give an annotation “Interment of C.R.” which I interpret as interment /burial of the cremated remains. It may be a common practice. So I have been changing or making their record as Cremation, and also adding a General Note to indicate (ie, that there may actually be a grave or memorial of some type). For some, it may be useful to visit or to search Billion Graves. Is this the only way / best way? I.L. Thomas Victoria Park, Western Australia From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Chris Hill Sent: Thursday, 28 November 2019 12:07 AM To: Legacy User Group Subject: Re: [LegacyUG] Using special alphabet characters in Legacy Hi John I quite agree, Legacy will be stuck with ANSI until they rewrite it. Given that there is also pressure, from its users, for a Mac version, and presumably a Linux version, they have a need to develop a new program and database that is multi-OS compatible. Hopefully, with the support from MyHeritage, this will happen, but MH also owns Family Tree Builder so it might put pressure on merging with it. Regards Chris -- Original Message -- From: "John Cardinal" mailto:jfcardi...@gmail.com>> To: "Legacy User Group" mailto:legacyusergroup@legacyusers.com>> Sent: 27/11/2019 14:26:14 Subject: Re: [LegacyUG] Using special alphabet characters in Legacy Chris, During my 41-year career I've been a software developer, software architect, and CTO, including a five-year period where my team developed commercial applications in VB6. Since 1999 I've had a couple of side-project applications implemented in VB6. My focus now is .NET. As discussed on the site you mentioned and others, there are challenges to implementing Unicode-aware VB6 applications. Other sites describe how to meet those challenges. A couple techniques we used were Unicode-aware component packages and TLBs for access to wide-character functions. Perhaps the technology infrastructure Legacy uses has an ANSI-only component baked-in and switching it out would require a rewrite-level effort. If so, they'd never rewrite in VB6 now so the effective result is "we can't support Unicode until we abandon VB6". John -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Using special alphabet characters in Legacy
Hi John I quite agree, Legacy will be stuck with ANSI until they rewrite it. Given that there is also pressure, from its users, for a Mac version, and presumably a Linux version, they have a need to develop a new program and database that is multi-OS compatible. Hopefully, with the support from MyHeritage, this will happen, but MH also owns Family Tree Builder so it might put pressure on merging with it. Regards Chris -- Original Message -- From: "John Cardinal" To: "Legacy User Group" Sent: 27/11/2019 14:26:14 Subject: Re: [LegacyUG] Using special alphabet characters in Legacy Chris, During my 41-year career I've been a software developer, software architect, and CTO, including a five-year period where my team developed commercial applications in VB6. Since 1999 I've had a couple of side-project applications implemented in VB6. My focus now is .NET. As discussed on the site you mentioned and others, there are challenges to implementing Unicode-aware VB6 applications. Other sites describe how to meet those challenges. A couple techniques we used were Unicode-aware component packages and TLBs for access to wide-character functions. Perhaps the technology infrastructure Legacy uses has an ANSI-only component baked-in and switching it out would require a rewrite-level effort. If so, they'd never rewrite in VB6 now so the effective result is "we can't support Unicode until we abandon VB6". John -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Using special alphabet characters in Legacy
Chris, During my 41-year career I've been a software developer, software architect, and CTO, including a five-year period where my team developed commercial applications in VB6. Since 1999 I've had a couple of side-project applications implemented in VB6. My focus now is .NET. As discussed on the site you mentioned and others, there are challenges to implementing Unicode-aware VB6 applications. Other sites describe how to meet those challenges. A couple techniques we used were Unicode-aware component packages and TLBs for access to wide-character functions. Perhaps the technology infrastructure Legacy uses has an ANSI-only component baked-in and switching it out would require a rewrite-level effort. If so, they'd never rewrite in VB6 now so the effective result is "we can't support Unicode until we abandon VB6". John -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Using special alphabet characters in Legacy
Hi John I will accept that in my 50 years experience as a developer, IT Manager and consultant I never had the need to use VB6. Therefore I was equally puzzled by the limitations that the Legacy developers seem to have applied, given that by the late 1990s Unicode support was becoming common. So I did a web search for 'VB 6 Unicode' and found this website at VBForums: http://www.vbforums.com/showthread.php?365738-Classic-VB-Does-Visual-Basic-6-support-Unicode Note that the initial entry, in 17 Jun 2008, explicitly refers to the conversion of 16-bit characters (aka Unicode) to ANSI in API interfaces and file saves. It then extends to discuss the development of Unicode based API extensions and the use of code sets. There are then a number of later posts regarding methods to implement Unicode in VB6. If we believe this, and I have no reason not to, it would appear that the Legacy developers were limited to the ANSI character set, unless they were prepared to develop or acquire Unicode based APIs and interfaces. This has been an issue with Legacy for many years and even the Legacy support staff agree that they are limited to ANSI. ___ Hi Otto I am running the latest version of Legacy, 9.0.0.332, on a 64-bit Win 10 system using the English (United Kingdom) display language - which version are you running with. If I create a new person and enter into his name fields via the Alt+ sequence in the range Alt+0032 to Alt+0255 then Legacy will accept then into the field on the display, excluding later checks that Legacy might want to apply if I Save the record. However, if I continue with Alt+0256, Alt+0257 onwards, then the additional characters are not included in the fields, and usually respond with a beep. Hence, those fields are limited to the ANSI character set. Equally, if I create a new event and then type into the Notes field, then I can happily ENTER additional characters, thus I can ENTER and have DISPLAYED the following, Alt-0250 to Alt-0255 : úûüýþÿ - this is the Unicode set for u with Acute, Circumfles and Diaeresis, y with Acute, lower case Thorn and y with Diaeresis Alt-0256 onwards, using Copy from Character map : ĀāĂ㥹ĆćĈĉĊċČč - some of these do not work using the Alt- format, these are the upper and lower case pairs of A with Macron, Breve and Ogonek, and C with Acute, Circumflex, Dot Above and Caron. So, text fields will accept, as input, characters past the ANSI set, while control fields will not, or will convert them to ?. That is good UNTIL you want to save the data. Do that and then open the event - ALL of the characters after Alt-0255 are missing, so it will ONLY save within the ANSI set. Also, if you refer to the Special Character set, click on the solid square at the top of the bar to the left of the Notes field in the Event, and you will see a list of the characters that Legacy will accept - this should be a match to the Alt-0032 to Alt-0256 set from the Windows Character Map. As far as I can tell it does, but my version of Char Map misses U+007F through U+009F if set to Unicode, and does show them if set to Windows:Western with exceptions. This points us to the question of code sets, which were designed in the 1980s to enable different glyphs to be used for characters in the Alt-0128 to Alt-0255 range to be used to cover multiple alphabets using the same character code to represent different glyphs. Good, so long as you only work within a single code set, and difficult if not unless you can deal with changing the code set on the fly. Of course, Unicode was the solution for that, enabling the extension of the character set from 8-bits to 16- and 32-bits, so long as the programmer KNEW which version was in use - there were multiple versions in the early days. Now, Otto, I see from your response below that you seem to be based in Finland. If I convert my Character Map to show the Windows:Central Europe set I can see that the character set for the range from Alt-0128 onwards is different, and includes the C with Acute, Cedilla and Caron marks. Within the Western set only the version with Cedilla is present - C with Acute becomes the Æ glyph ( a combined AE glyph) and the C with Caron becomes the È glyph (E with Grave). In Unicode all of the C with Acute, Circumflex, Dot Above and Caron glyphs are in the range U+0106 to U+010D and outside of the ANSI set within a Western code set. ___ All of this indicates that Legacy was developed in the 1990s, within America, with the traditional mindset of ANSI and the Western Europe code set, and perhaps supports different code sets if you change the default language set, and has never been extended to support Unicode. Regards Chris -- Original Message -- From: "Otso Havu" To: "Legacy User Group" Sent: 27/11/2019 01:00:15 Subject: Re: [LegacyUG] Using special alphabet characters in Legacy Legacy accepts Unicode from Win CharMap eg. in the
