Bug#626159: ITP: scilab-jims -- Binding the worlds of Scilab and Java

[Justin B Rye <jbr@edlug.org.uk>]

Christian PERRIER wrote:
> Quoting Sylvestre Ledru (sylvestre@debian.org):
>> Description: Binds Java from the Scilab engine
> 
> That's still a verb sentence and still has a leading capital..:)
> 
> How about "Scilab Java bindings"
> 
> (here, the leading capital is OK as this is the official spelling of Scilab

Or (mostly just to keep it from looking too much like a repeat of the
package name):

   Description: Java bindings for the Scilab engine
 
>>  JIMS is an effort to allow Scilab programs full access to Java class
>>  libraries. This is achieved by interfacing at the native level in both
>> Virtual Machines.

"Effort to" and "achieved" don't really go together - if its aims are
really achieved, it's more than just an effort.  I don't know what
interfacing at the native level is exactly, but having looked up what
JIMS stands for it sounds as if you could say something like:

    The Java Interaction Mechanism in Scilab (JIMS) provides a native-level
    interface between the two Virtual Machines, giving Scilab programs full
    access to Java class libraries.

>>  .
>>  From Scilab, JIMS allows the capability to load and manage Java objects
>>  from the Scilab interpreter.
> 
> "allows the capibility" is too french for being honest..:-). See
> http://wiki.debian.org/I18n/SmithDebconfReviewGuidelines for what is
> allowed after "allow"....

And now that I've expanded JIMS the repeats of "Java" and "Scilab" are
getting a bit excessive (especially here where it seems to repeat the
"from Scilab" part).

                                         [...], giving Scilab programs full
    access to Java class libraries and allowing them to load and manage Java
    objects.
 
>>  .
>>  Thanks to this module, Scilab can access to complex and advanced Java objects
>>  with Scilab classical data types.
> 
> I suspect that "thanks to this module" can be improved.

"Access" doesn't need "to".  But is this "can access objects with
(=that have) Scilab classical data types" or "can access objects with
(=by using) Scilab classical data types"?  I'd guess the latter, but
that means it looks like just another item to merge into that list of
things it allows Scilab to do.  Something like:

 Description: Java bindings for the Scilab engine
  The Java Interaction Mechanism in Scilab (JIMS) provides a native-level
  interface between the two Virtual Machines. It gives Scilab programs
  full access to Java class libraries, allowing them to load and manage
  complex and advanced Java objects using Scilab's classical data types.

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package