Re: [Scilab-users] Behavior of gettext

2019-03-12 Thread Federico Miyara
Thank you Samuel, this one does work! I understand the verbosity issue (it's the age of SMS's and WhatsApp's). However, the "orthogonality", in spite of being a good idea to avoid many instances of similar messages, would be really useful if some way to combine short messages did exist. But I

Re: [Scilab-users] Behavior of gettext

2019-03-12 Thread Samuel Gougeon
Le 12/03/2019 à 21:31, Federico Miyara a écrit : Dear All, I try to get this error message translated: msprintf(gettext("%s: Argument #%d: Vector expected.\n"), "bandfilter", 1) Any idea of what's wrong? The long historical form is gettext("%s: Wrong size for argument #%d: Vector expected.\

Re: [Scilab-users] Behavior of gettext

2019-03-12 Thread Samuel Gougeon
Hello, Le 12/03/2019 à 21:31, Federico Miyara a écrit : Dear All, I try to get this error message translated: msprintf(gettext("%s: Argument #%d: Vector expected.\n"), "bandfilter", 1) It may be a very recent one, not yet translated. Samuel ___

Re: [Scilab-users] Behavior of gettext

2019-03-12 Thread Federico Miyara
Dear All, I try to get this error message translated: msprintf(gettext("%s: Argument #%d: Vector expected.\n"), "bandfilter", 1) Any idea of what's wrong? This one works fine: msprintf(gettext("%s: Wrong number of input arguments: %d to %d expected.\n"), "bandfilter", 2, 4) Both messages

Re: [Scilab-users] Check code on SCILAB``

2019-03-12 Thread farimani
I was wondering if there is any way to force the interpreter check all the syntax, including the ones inside the functions, while/for loops, if statement ...? -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html