On Thu, Apr 07, 2016 at 01:06:10AM +0300, Anton Zinoviev wrote: > > Unfortunately, at the moment I have no idea what might have caused this > strange behaviour.
Ah, it just occured to me that maybe you have observed the following: 1. fsck displays its messages with correct non-break space. 2. A second later console-setup changes the font and only then the non-break space is replaced with "strange" symbol. Am I right? If so, then I think I understand the cause of the problem and the possible fixes. Anton Zinoviev