Issue 26: extended ascii char. from keyboard are ignored

[atao60]

When playing notes with computer keyboard, neither extended ASCII key nor dead key can be used for mapping.
Then, e.g. with a french AZERTY keyboard, only the bottom set of keys is useful.

There are in fact two different issues:

• the extended ASCII keys : only one line of code has to be changed!
  In brightonControllers.c, inside brightonMapKeyboard method, the "from" variable must be declared "unsigned char" in place of "int".
  That's it! Well almost: the profile file must be coded in some kind of iso 8859 to get extended ascii characters on one byte.

To use UTF 8 coding (or any other multi bytes coding), (unsigned) int or char declarations would have to be replaced by wchar_t. That's an other story.

• the dead keys (e.g. on a french AZERTY keyboard, the key "^" between "p" and "$" is one of them...). Here a list of substitutions is needed. Can be done by adding a dynamic array to brightonWindow. It's not very clean but it avoids any other change of existing struct definitions. To fill this array, add a optional fourth field to "KM" records in the profile file.

See #93 extended ascii char. from keyboard are ignored