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:[email protected]] On Behalf Of Chris Hill Sent: Thursday, 28 November 2019 12:07 AM To: Legacy User Group <[email protected]> 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" <[email protected]<mailto:[email protected]>> To: "Legacy User Group" <[email protected]<mailto:[email protected]>> 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 [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
