#32 (????) characters are not supportet

[CyberVillain]

The character mapper in smartie does not convert the
ĹÄÖĺäö characters to the character set of the display,
so they look all wrong on the display.

Clansley asked me to add this to the bugtracker so that
its not overlooked for the next release...

Keep up the good work guys and keep the low CPU and
memory usage down to a minimum (thats the reason
why i use LCD smartie)...

[Chris Lansley]

Logged In: YES
user_id=1114156

Research findings:
Crystalfontz v1 CGROM has:
Crystalfontz v2 CGROM has: [and a lot of others, but
could find unless a 'A' and 'a' with a single dot above
is the same.]
Matrix Orbital: same as CF v1.
HD44780... They are all different, I've send one that
support all of the requested characters - but I've also seen
some that support none of them.

[It's possible to support the missing characters by using
custom characters - but this will impact any graph on the
screen (really the custom character code needs a rethink).]

[BasieP]

Logged In: YES
user_id=1184293

solution can be that someone writes a plugin that does the
following:

- defines the chars () as custom chars
- converts those chars to the defined custom chars

problem could be that this plugin messes up other custom
chars smartie (or it's plugins) use

[Carlo DrSurfer]

Unreadable chars... I've edited the summary to fix SourceForge tracker... atleast on Firefox 4 they are unreadable.