Samuel Thibault, le mer. 06 juin 2018 15:19:07 +0200, a ecrit:
> Samuel Thibault, le ven. 01 juin 2018 16:28:23 +0200, a ecrit:
> > Anton Zinoviev, le ven. 01 juin 2018 17:22:06 +0300, a ecrit:
> > > On Fri, Jun 01, 2018 at 04:10:36PM +0200, Samuel Thibault wrote:
> > > > U+015A would be what
Samuel Thibault, le ven. 01 juin 2018 16:28:23 +0200, a ecrit:
> Anton Zinoviev, le ven. 01 juin 2018 17:22:06 +0300, a ecrit:
> > On Fri, Jun 01, 2018 at 04:10:36PM +0200, Samuel Thibault wrote:
> > > U+015A would be what you'd expect for a latin1 language (^ + S), and I
> > > guess due to rule
On Fri, Jun 01, 2018 at 04:28:23PM +0200, Samuel Thibault wrote:
>
> Maybe we should just go and define all X11 deadkeys in Linux (there
> are like 55 of them, that will fit), to be done with the issue.
Either this, or console-setup can have a hardcoded list of "Latin2"
layouts.
Anton
Anton Zinoviev, le ven. 01 juin 2018 17:22:06 +0300, a ecrit:
> On Fri, Jun 01, 2018 at 04:10:36PM +0200, Samuel Thibault wrote:
> > U+015A would be what you'd expect for a latin1 language (^ + S), and I
> > guess due to rule ordering, the existing rule doesn't get overrident by
> > the rule you
On Fri, Jun 01, 2018 at 04:10:36PM +0200, Samuel Thibault wrote:
>
> U+015A would be what you'd expect for a latin1 language (^ + S), and I
> guess due to rule ordering, the existing rule doesn't get overrident by
> the rule you introduced, so we need to explicitly remove the existing
> rule.
And
Jan Rafaj, le ven. 01 juin 2018 16:06:34 +0200, a ecrit:
> the following ones still do not produce the
> corresponding caron-ified characters as they should - I have no idea why:
>
> compose '^' 'S' to U+0160 # instead produces U+015A (0xC59A)
U+015A would be what you'd expect for a
On Thu, 31 May 2018, Samuel Thibault wrote:
Anton Zinoviev, le ven. 01 juin 2018 00:48:18 +0300, a ecrit:
If a bug makes a package totally unusable, but otherwise harmless,
then this bug is (usually) not going to be fixed in the stable
release.
Mmm, I believe that sentence enters the
Anton Zinoviev, le ven. 01 juin 2018 00:48:18 +0300, a ecrit:
> If a bug makes a package totally unusable, but otherwise harmless,
> then this bug is (usually) not going to be fixed in the stable
> release.
Mmm, I believe that sentence enters the "important" area, or even more:
4 important
Hello guys,
Thanks for your valuable input, and for shedding more light on the inners
of the current localisation approach.
The layouts from the 'kbd' package do not work with UTF-8 input. I've
used them in the past with 1-byte input forced in the kernel by adding
the 'vt.default_utf8=0' boot
On Thu, May 31, 2018 at 11:12:43PM +0300, Anton Zinoviev wrote:
>
> only important bugs are fixed
I realised the word 'important' was very inapropriate in this context.
What is unimportant for one user can be very important for another. So
by 'important' bugs I meant things about
On Mon, May 28, 2018 at 12:25:04PM +0200, Jan Rafaj wrote:
>
> Anton, thanks for suggesting the workaround. However, adding the kmap
> "snapped" with ckbcomp and hand-modified afterwards as a value to 'KMAP=' in
> the /etc/default/keyboard is not really a workaround, since
> this overrides
On Mon, 28 May 2018, Jan Rafaj wrote:
attached file. If you could append this to the
/etc/console-setup/compose.ISO-8859-2.inc file. This will add all the missing
definitions, enabling the user to input all the czech letters on a cz
keyboard layout, provided that (s)he has defined either
Hello guys,
Thanks for your valuable input, and for shedding more light on the inners
of the current localisation approach.
The layouts from the 'kbd' package do not work with UTF-8 input. I've
used them in the past with 1-byte input forced in the kernel by adding
the 'vt.default_utf8=0' boot
Anton Zinoviev, le dim. 27 mai 2018 20:05:30 +0300, a ecrit:
> Ah, I didn't know that the compose sequences are used for the dead keys.
Dead keys simply produce compose + '`' or '\'' or '^' or '~' or '"' or
',' yes.
> Compose sequences in console-setup are encoding-based. See for example
>
On Sat, May 26, 2018 at 01:17:03PM +0200, Samuel Thibault wrote:
>
> Keymaps do have e.g.
>
> ./keymaps/i386/qwerty/et.kmap:compose '^' 'S' to Scaron
>
> I don't remember whether console-setup generates compose sequences, but
> it should be feasible.
Ah, I didn't know that the compose
Hello,
Anton Zinoviev, le sam. 26 mai 2018 12:20:59 +0300, a ecrit:
> I have some doubts that the dead keys are
> usable with non-Latin1 symbols on the console.
Keymaps do have e.g.
./keymaps/i386/qwerty/et.kmap:compose '^' 'S' to Scaron
I don't remember whether console-setup generates
On Thu, May 24, 2018 at 10:46:36AM +0200, Jan Rafaj wrote:
>
> I have confirmed that the problem described exists for the "bksl",
> "qwerty" and "qwerty_bksl" keyboard variants, as well as XKBVARIANT ""
> (in the /etc/default/keyboard).
>
> The problem described above appeared since the switch
Package: keyboard-configuration
Version: 1.164
Severity: important
Tags: l10n
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
18 matches
Mail list logo
