This need to be check but I don't think that the strings for the DEPS and SCO evolutionary algorithms and their settings have been extracted and made available for the localization.
I suspect that those strings came directly from the algorithm extensions... Let me check on that.
FYI I'm on vacation right now so I will be slow in responding etc.
As I suspected, those strings come directly from the extensions which are (unfortunately) written in Java. The built-in linear solver is also written as an extension, but it's written in C++ and it uses LO's internal string resource manager, which means they have taken a shortcut. ;-)
As for the other two Java extensions, localizing that would not be an easy task, and the localized strings will have to be given directly inside the extensions, which means no way to extract them into the rest of the LO strings for smooth translations... :-(
Ok. I just finished inspecting the source code of the NLP solver engine, and found out that those solver engine names are in fact hard-coded to be English in all locales. The extension has some localization mechanism in place, but the name is not localized.
For those who are interested, I've cloned the source code from the original Oracle extension CVS repo to my personal git. To check out the sources run
git clone git://people.freedesktop.org/~kohei/nlpsolver
Created attachment 41247 [details]
enabled localization of .properties files
Could you please review my patch for libreoffice-3-3? Many translations are ready to commit, more are in progress. This patch lightweight, does not require re-downloading or re-configuring anything. Thanks!
The patch looks good. Please commit to the libreoffice-3-3 branch. Thanks!
Verified in 3.3 so closing - Sophie