FMSLogo Code

Translate the documentation for the LISTBOX* procedures into Spanish.
This translation was based on Rosario Ruiz's translation of the MSWLogo manual.

Undo the previous fix for Bug #518.

Bug #518 was that NUL glyphs would appear when typing Greek or Russian.
The underlying bug (Bug #522) was that wxWidgets was giving FMSLogo a NUL
character in the WM_CHAR handler. This was fixed, along with Bug #525,
which made FMSLogo suggest the wrong script for the fonts. With these
other two bugs fixed, the editors should work as expected for Greek and
Russian computers without using the stripped-down one used by the
Traditional Chinese version of FMSLogo.

Combine the ANSI Chinese/Greek/Russian tests into a single file.
Since files are read as a series of code points, there's no need to separate them into separate files.
The parts for the other languages look like gibberish in the source code, but won't be executed.

Fix Bug #523

The two-input form of KEYBOARDON once again outputs the correct code from KEYBOARDVALUE for non-Latin characters when called from the "keyup" instruction list. This was accomplished by refactoring the logic which gets the keycode to be called from both WM_KEYUP and WM_KEYDOWN.

Fix Bug #525; FMSLogo now suggests the system language as the default script for a font.

This fixes a problem where non-Latin users would have to configure their fonts specially to be able to type non-Latin characters (assuming they could figure out why they were typing gibberish). It also fixes a problem where LABEL would draw gibberish on the screen until SETLABELFONT was called appropriately (again, assuming someone knew the magic number to pass SETLABELFONT).

This change also replaces a few magic numbers with their symbolic names for a font's default.

Fix Bug #522; Patch wxWidgets to use the ANSI keycode as-is when handling WM_CHAR events

Note that this is a change to the wxWidgets library, not to FMSLogo.

The problem was that it was trying to take an ANSI character code, thinking it was Unicode, and then converting it to ANSI. When this invitably failed for non-Latin characters, wxWidgets would default to 0, which manifested itself as [NUL] when typing into the editor. Since the key code is already ANSI, there's no reason try to convert it to ANSI.

This revision also updates the change I had made to ScintillaWX.cpp to instead match the change which the wxWidgets developers made when I reported the problem to them. Now that the characters can't ever be over 255, it's safe to use the mainline change.

Fix the label for the "key up" handler

Clarify that the name input must be unique across all widget types

Fix a typo: "alturza" -> "altura"

Translate the documentation for the DIALOG commands into Spanish.
This translation was based on Rosario Ruiz's translation of the MSWLogo manual.