Messages in this thread | | | Date | Sun, 19 Feb 2006 13:45:26 +0100 | From | Adam Tla/lka <> | Subject | Re: [PATCH]console:UTF-8 mode compatibility fixes |
| |
On Sun, Feb 19, 2006 at 09:24:26AM +0500, Alexander E. Patrakov wrote: > Adam TlaĹka wrote: > > >Maybe I should remember all bytes of the UTF-sequence to use their > >values as a last resort char in case of malformed sequence and 0xfffd > >not defined? > > Please don't do that. Display question marks instead in the case when > 0xfffd is not defined.
But this is the normal console behaviour in case of non existing replacement glyph for some char. I just not changed it. Anyway if you have no '?' glyph at '?' char code position you get some different char on the screen. Replacement glyph should always be defined as I said before, so this part of code could be easilly removed but I do not really know if this assumption is true now.
Regards -- Adam Tlałka mailto:atlka@pg.gda.pl ^v^ ^v^ ^v^ System & Network Administration Group ~~~~~~ Computer Center, Gdańsk University of Technology, Poland PGP public key: finger atlka@sunrise.pg.gda.pl - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |