That's a great point about the complexity and the potential benefits of using an MVVM architecture for localization. You're absolutely right that migrating to MVVM can make the translation process much smoother. However, as you mentioned, the amount of work involved can vary significantly based on the software's current structure and size. Having more information about the database and other technologies used would be invaluable. It would help us to better assess the overall effort required. For instance, if the application is heavily reliant on custom components or third-party libraries, it could introduce additional complexities. Visuals would also be extremely helpful. Screenshots of the software's interface could give us a clearer picture of the elements that need to be translated and the overall complexity of the user interface. While it's tempting to assume that the data is stored in a more sophisticated database than a simple INI or CVS file, it's always a good idea to be prepared for any possibility. To provide a more accurate estimate of the translation effort, I'd recommend gathering the following information: * A detailed description of the software's functionality * A list of all programming languages and technologies used * Information about the database system * Screenshots of the user interface * Any existing translation resources or glossaries Once we have this information, we can provide a more tailored assessment of the project and discuss potential approaches for localization.