On Tue, May 03, 2016 at 09:17:03AM +0100, Klaus Ethgen wrote:
>
> > I suppose now
> >
> > printf '\033%%G'
> >
> > is the default in the kernel, that is UTF-8,
>
> Well, that is not true. I have that bug as well on systems that uses
> standard debian kernel as also on systems where I have a cu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Di den 3. Mai 2016 um 8:47 schrieb Anton Zinoviev:
> On Mon, May 02, 2016 at 10:39:49PM +0100, Klaus Ethgen wrote:
> > >
> > > printf '\033%%@'
> > >
> > > Does this reconfigure the console to use ISO-8859-1?
> >
> > I already tried that
On Mon, May 02, 2016 at 10:39:49PM +0100, Klaus Ethgen wrote:
> >
> > printf '\033%%@'
> >
> > Does this reconfigure the console to use ISO-8859-1?
>
> I already tried that and yes, it works. (or print '\033%@') So when I
> read that correct (The information about % is very rar) that sets
> the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Mo den 2. Mai 2016 um 20:22 schrieb Anton Zinoviev:
> > When logging in as root and do dpkg-reconfigure console-setup with all
> > settings as before (or running cached_setup_font.sh),
>
> Just to be sure that the only problem is with the encodi
On Fri, Apr 29, 2016 at 10:15:26AM +0100, Klaus Ethgen wrote:
>
> When using console-setup to setup proper console char set (latin1), it
> does not preserve it over logout/login or reboot. After logout, the
> console is again set to UTF-8.
Console-setup supports non-UTF-8 encodings, which means w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: console-setup
Version: 1.142
Severity: important
When using console-setup to setup proper console char set (latin1), it
does not preserve it over logout/login or reboot. After logout, the
console is again set to UTF-8 what makes it difficul
6 matches
Mail list logo
