Forward / Backward compatability
Cambell Prince
Recently WeSay has upgraded to implementing lift 0.13. This is
available now in the latest WeSay 0.5.x series. However, Flex has not
yet done this in a publicly available version. The result is that Flex
cannot import WeSay lexicons. Flex simply says 0.13 is too new, go away.
What's the thinking on playing in the Bazaar, with multiple tools
operating on the same data format, when the data format goes through
change from time to time?
Regards,
Cambell
--
Cambell Prince
Payap Language Software and SIL MSEAG
Skype: cambell.prince | Mobile: +66 87 190 5871 | Fax: +64 6 759 6152
www.palaso.org and www.sil.org
John Hatton
Microsoft pushes, for example, Office 2007-opening ability back out to all the existing Office 2003 users via Office update. Could this be done for FLEx in a low-tech way? At this moment I'm writing an add-in for FLEx to clean up some data, and it has at least two other "extension point" (exporters being one). So one answer might be to ask the FLEx team to implement the ability to supply importers as add-ins, and to create them for new LIFT versions. Then on the WeSay side we could delay supporting a new LIFT version until FLEx has published the supporting add-in.
Then the error message you saw could say "Go to http://...../FlexLiftImportAddins" to download the ability to open that Lift 0.13 file.
In the meantime, I guess one of us should writing a converter from 0.13-->0.12(FLEx).
JH