Brian
My thoughts exactly. I have "bitten my tongue" about these issues for the last
6+ months. Even with the no-longer-supported VB6, Unicode can be supported -
but that is not the sensible way to have proceeded. It would have required a
complete rewrite, with old and clunky technology. { VB6 was released in 1998,
and declared "legacy" by Microsoft in 2008.]
With the "refactored" .NET Core* which Microsoft has produced, a complete
rewrite would cater for Windows, MacOS, and Linux/Unix (if anyone was
interested) with
essentially the same codeset.
* http://www.microsoft.com/net/core
Ian Thomas
Albert Park, Victoria 3206 Australia
-----Original Message-----
From: LegacyUserGroup [mailto:[email protected]] On
Behalf Of Brian Kelly
Sent: Friday, 4 August 2017 11:50 PM
To: Legacy Test <[email protected]>; Legacy User Group
<[email protected]>
Subject: [LegacyUG] Millennia Sale to MyHeritage
Well it looks like there will be interesting times ahead for Millennia and the
software with the merger/acquisition of Millennia by MyHeritage.
Too bad that one of the answers about Legacy 10 is that it will not support
Unicode. I guess that means that it will still be a Visual Basic application.
I am beginning to think it will never be migrated to the .net framework and
Unicode.
Brian Kelly
---
This email has been checked for viruses by AVG.
http://www.avg.com
--
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]/
--
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]/
