 |
See these BTs really do eventually get done !! The problem is more requests come in than the 20 or so that can get done in 1 month. |
|
|
@Andrew-R - thanks for updating this BT which gave up the impetus to finally get it done and checked into GIT. @MatN: "Suggestion: add to Settings->Preferences-Appearance a ¨GUI language¨ setting, as a drop-down list with the supported languages, with the top entry of the list being "system language" or something like that. If the language is changed, restart cin (like currently is done if you change the theme), and store the language in the .bcast5/Cinelerra_rc file ." OK, change checked into GIT. The Locale is on the left hand side of the menu under the Layout choices of Theme and Plugins. Now in order to change the environment variable, LANGUAGE, the setting must be "sys" because that is the best way we could get it working. |
|
|
GG is considering a Preferences option/Tab to do this and actually just talked about this yesterday. Let's see if we can get this done this month. |
 |
This one _seems_ relative easy to implement, just by setting environment variable INSIDE program, like I set this DRI3_DISABLE thing long ago: --- cat dri3_disable_cin51.diff --- cinelerra/main.C.orig 2017-05-19 21:54:14.591114867 +0300 +++ cinelerra/main.C 2017-05-19 22:03:32.229841024 +0300 @@ -117,6 +117,9 @@ deamon_path[0] = 0; EDL::id_lock = new Mutex("EDL::id_lock"); + /* disable dri3, it broke hw effects on nouveau as of 19-05-2017 */ + setenv("LIBGL_DRI3_DISABLE", "1", 1); + File::init_cin_path(); const char *locale_path = File::get_locale_path(); const char *cin = File::get_cin(); --- of course this will require restart, but original request was fine with this .... |
 |
> "I personally never look at the priority or fields EXCEPT for when the icon turns red !" :-))) Nothing beats your own slip box, isn't it? |
|
|
MatN: "What happens if the system locale is e.g. sl, and the translation is not good, does Cinelerra then work with a badly translated GUI?" There are 2 philosophies here. 1) using all english instead of bad translation or 2) better to have some good translations for users who do not have much, if any, english knowledge. GG and I subscribe to the better some than none. If 90% of the translations are "good" and only 10% are "bad", at least a user stands a chance of being able to use Cin. I frequently have Google translate foreign language pages and even though the translation is not great, I can understand enough to have figured out what I need to know. If I only have that foreign language with zero translation, I got nothing. Also about side note: "issue 7 is of "category¨ feature, and as ¨severity¨ also feature. Should not the severity field indicate the desirability or importance of a feature?" Probably, but this was early on in using MantisBT and even today, I personally never look at the priority or fields EXCEPT for when the icon turns red ! |
 |
On a side note, I see that issue 7 is of ¨category¨ feature, and as ¨severity¨ also feature. Should not the severity field indicate the desirability or importance of a feature? |
|
|
What happens if the system locale is e.g. sl, and the translation is not good, does Cinelerra then work with a badly translated GUI? If so, there should be a documented way to force one of the known good translations, e.g. english . Maybe in the readme? Until such time Cinelerra allows setting the GUI language in preferences. This might be important. I can well imagine people being put off if from the beginning they see bad language. |
|
|
The po files are not good. German and Russia are the only ones that are mostly up to date but any recent additions since last June for Russia and last October for German are only in english. Not a good idea to advertise the rest. The majority were taken from a Google translate many, many months ago (maybe even over 2 years) and were put on top of translations done by personnel in the cv area. So there is some good Italian and French mixed with some bad Italian and French. |
|
|
I´d like to update the Wikipedia page with the supported languages. Are all entries in the po directory fully valid for the GUI? |
 |
It's a feature I'd like too. I write LC_ALL=C to the start string. |
|
|
Easiest way that I test using a single line: # LANGUAGE=fr {cinelerra_path}/cin This works from a english system to see French (fr), ru for Russian, de for German, etc. It would be a nice additional feature to implement your suggestion. |
- Anonymous
