2009-03-05, 15:05
Hello folks,
I finally got my display working, and apart from some latency it works great with LCDproc and XBMC. The only issue I have is that the progress bar when playing a movie shows up something like this:Now I had a look at LCD.cpp and found out that there are basically two char mappings, one for the KS0073 controller and one for the rest of them. The other one is actually the mapping for the very popular HD44780 display.
I myself have a graphical display at 256x64 pixels and the text on it is rendered by LCDproc using the Freetype library and the Andale Mono truetype font. So what happens, XBMC sends the "block" character for the progress bar (0xAB), which gets remapped by the HD44780 mapping to 0xFF, which corresponds to the "ÿ" character in a normal ASCII charset and gets rendered as such on the display.
To resolve this issue, I could simply patch LCDproc and introduce another mapping that maps this char back to the correct value. However there are some things I don't understand yet:
This issue should concern everyone with a non-alphanumeric but graphical display where font rendering from standard character maps is incorporated. Any thoughts?
I finally got my display working, and apart from some latency it works great with LCDproc and XBMC. The only issue I have is that the progress bar when playing a movie shows up something like this:
Code:
[ÿÿÿÿÿ ]I myself have a graphical display at 256x64 pixels and the text on it is rendered by LCDproc using the Freetype library and the Andale Mono truetype font. So what happens, XBMC sends the "block" character for the progress bar (0xAB), which gets remapped by the HD44780 mapping to 0xFF, which corresponds to the "ÿ" character in a normal ASCII charset and gets rendered as such on the display.
To resolve this issue, I could simply patch LCDproc and introduce another mapping that maps this char back to the correct value. However there are some things I don't understand yet:
- Why does XBMC have to do any remapping anyway? Isn't LCDproc supposed to know which display controller is used and apply the correct mapping?
- What about Unicode characters? In the font used for the rendering, all graphical gimmick symbols are >0xFF, so if XBMC's char mappings should be extended in order to solve the issue, it would have to support Unicode characters.
This issue should concern everyone with a non-alphanumeric but graphical display where font rendering from standard character maps is incorporated. Any thoughts?
