Yes. The tem will get UTF-8 byte stream which we assemble to unicode wide char (8859-1 right now) and which is passed down for rendering either on bitmap or vga text console. The current fonts in kernel are indeed only 8859-1 fonts and what we want to happen is to get our rendering part to be set up to be prepared to receive the wide chars. This update does address the bitmap part, the VGA text must wait still, till we have gfx_private... 
Eventually we will switch font rendering to use usr/src/common/font/font.c which is already waiting. Also the loader FB implementation is using the same concept, implementing both bitmap and vga text components.
Of course in final font.c we do not operate on array directly, since the glyph space is not contiguous, but if the glyph is not found, we will use special "default" char.