I assume that the implied information in this thread’s title is that not only the parser is the same, but also the dictionary, word list, spelling conventions etc. Them NOT being the same was the price we all paid for leaving the old SIL Scripture Editor behind, but that’s water over the dam. OK developers, here’s a shot in the dark from an out-of-practice programmer in his former life (think punched cards). Can you read the Flex data base, and pull all the bits and pieces of lexical data from Flex that it would take to create an exact imitation of the data structures which ParaText uses natively? If so, could you build such a routine into Paratext and then let users choose whether to a) use the native Paratext data structures, or b) read them from Flex and use the imitation structures? This would allow the rest of Paratext’s source code to be remain unchanged, and people with no interest in Flex (which is probably most translators) would never be any the wiser.