FMSLogo Code

Remove the translation of "HALT" to "ALTO".
Because STOP is also translated as ALTO and appears later in init.cpp, it replaced the translation of HALT to ALTO (you can't have ALTO mean two things, after all).

This removes confusion in the code and also in the manual's translation tables which falsely claimed that ALTO means both STOP and HALT.

Translate the introductory text for the Control Structures section into Spanish.

Translate the documentation for the debugging procedures into Spanish.
This translation is based on Rosario Ruiz's translation of the MSWLogo manual.

Translate the documentation for the Workspace Control procedures to Spanish.
This translation is based on Rosario Ruiz's translation of the MSWLogo manual.

Remove a repeated definition of BNOMBRES.
From the copydef comment, it looks like this was supposed to be named BOVARS.
This would have made more sense given the names BOVAR and LVARS.

Since BNOMBRES exist and BOVARS hasn't existed for a decade without complaint,
I don't think adding a BOVARS would improve FMSLogo, I'm simply deleting the
redundant definition and the errant copydef.

The impact on FMSLogo should only be the removal of a bogus entry
in the Spanish manual's translation tables.

Translate the documentation for the workspace inspection procedures into Spanish.
This is based on Rosario Ruiz's translation of the MSWLogo manual.

Translate the documentation for the Workspace Questions procedures into Spanish.
This translation is based on Rosario Ruiz's translation of MSWLogo.

Correct the case in the output of CONTENTS in the example

Standardize on "argumento" (argument) instead of "entrada" (input) for procedure inputs for the Spanish manual.
The main reason is that the procedure OUTPUT was translated as DEVULEVE (return) long ago
and it's too late to change it. Because of this, there is no natural symmetry of input/output,
like there is in English. Most people familiar with other languages use the term "argument"
for this notion, so "input" feels out-of-place even in English. Without the pairing of input/output
(entrada/salida) to justify the term "input", using "argumento" feels preferable.

The English manual will continue to use "input".

Translate the documentation for the workspace predicates to Spanish.
This translation is based on Rosario Ruiz's translation of the MSWLogo manual.