We have some strong interest for Slicer and slicermorph from the spanish speaking countries, particular in SA. One of the ideas that was bounced during the workshop was converting menus into Spanish (or at least for some selected subset of extensions or modules).
Forum threads show there was at least one discussion of Spanish version of Slicer from couple years back. Did that ever reach into a usable state?
And more importantly, how does the language changes happen? Does that mean maintaining a completely separate build for that language in all three platforms (which I dont think we will be very appealing to the people who wants to help with the process)
Qt has very good translation infrastructure and tools for maintaining translations, so all Qt resources and strings in Qt classes in Slicer can be translated relatively easily. However, we need to figure out how to make strings in VTK classes, CLI modules, and Python scripted modules translatable (preferably using the same Qt translation tools).
We have been considering about applying for CZI essential software project for developing localization of Slicer and create French (and maybe Spanish) translation and documentation. Once the infrastructure is in place, anyone can create translations for any language. All languages will be built into the Slicer package and you can change the language any time in application settings.
There have been efforts to internationalize at least parts of Slicer primarily to Spanish, French, and Arabic in terms of the MacBiolDi project, but I’m not sure how far it has gotten.
Thanks for the tips, these are all very relevant, because we are in a very similar situation as napari - having lots of plugins implemented in Python by various groups and we would need a way to provide translations for them.