Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #224422 > unrolled thread
| Started by | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| First post | 2020-07-06 07:40 +0200 |
| Last post | 2020-07-10 05:00 +0200 |
| Articles | 20 on this page of 87 — 14 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-06 07:40 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-06 14:30 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-06 14:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-06 21:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-06 22:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-07 17:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-07 08:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-07 17:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-09 23:50 +0200
Re: Using .XCompose [resend of xev_output_annotated.txt] davidson <davidson@freevolt.org> - 2020-07-10 03:40 +0200
Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-10 10:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 10:40 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 12:30 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-12 17:00 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-13 06:00 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-13 14:00 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-13 20:30 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-13 20:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-13 20:50 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-13 21:50 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-14 05:40 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-15 16:50 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-15 17:10 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-15 17:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 01:30 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 02:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-16 20:40 +0200
how u mine 4 utf8 [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-18 03:20 +0200
UTF-8 Everywhere -- Re: how u mine 4 utf8 [was Re: Using .XCompose] Zenaan Harkness <zenaan@freedbms.net> - 2020-07-18 07:40 +0200
Re: how u mine 4 utf8 [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-18 09:20 +0200
Re: how u mine 4 utf8 [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 13:00 +0200
Fw: how u mine 4 utf8 [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 12:50 +0200
Re: Fw: how u mine 4 utf8 [was Re: Using .XCompose] Tom Browder <tom.browder@gmail.com> - 2020-07-19 13:10 +0200
Re: how u mine 4 utf8 [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 13:50 +0200
sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-18 12:10 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Zenaan Harkness <zenaan@freedbms.net> - 2020-07-18 12:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] William Michels <wjm1@caa.columbia.edu> - 2020-07-18 22:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-18 13:20 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] songbird <songbird@anthive.com> - 2020-07-18 21:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] <tomas@tuxteam.de> - 2020-07-18 16:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] mick crane <mick.crane@gmail.com> - 2020-07-18 22:40 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] <tomas@tuxteam.de> - 2020-07-18 23:10 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] mick crane <mick.crane@gmail.com> - 2020-07-18 23:30 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] <tomas@tuxteam.de> - 2020-07-19 10:40 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] mick crane <mick.crane@gmail.com> - 2020-07-20 13:20 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] David Christensen <dpchrist@holgerdanske.com> - 2020-07-19 01:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 12:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] David Christensen <dpchrist@holgerdanske.com> - 2020-07-19 23:30 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 13:40 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] William Michels <wjm1@caa.columbia.edu> - 2020-07-19 21:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] David Wright <deblis@lionunicorn.co.uk> - 2020-07-23 04:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] songbird <songbird@anthive.com> - 2020-07-23 12:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 02:00 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-16 20:40 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-11 17:00 +0200
Tex characters Teemu Likonen <tlikonen@iki.fi> - 2020-07-11 18:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 22:40 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-13 14:00 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 07:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 18:10 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 15:30 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-20 15:30 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 18:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-10 12:50 +0200
Re: [offlist] posting style [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 05:00 +0200
Re: [offlist] posting style [was Re: Using .XCompose] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-08 07:00 +0200
Re: [not-so-offlist] posting style [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-08 07:10 +0200
Re: [offlist] Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 05:00 +0200
Re: [offlist] Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-08 05:20 +0200
Re: [offlist] Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-08 05:40 +0200
Re: [offlist] Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-08 08:00 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-07 00:40 +0200
tangent on man page locations [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-07 01:10 +0200
Re: tangent on man page locations [was Re: Using .XCompose] David Wright <deblis@lionunicorn.co.uk> - 2020-07-07 03:50 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-07 11:50 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-07 13:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 16:30 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-09 02:20 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-09 04:20 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-08 01:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-08 02:30 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 05:10 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 18:40 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-09 04:00 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-10 02:40 +0200
Re: Using .XCompose The Wanderer <wanderer@fastmail.fm> - 2020-07-10 02:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-10 05:00 +0200
Page 1 of 5 [1] 2 3 4 5 Next page →
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-06 07:40 +0200 |
| Subject | Using .XCompose |
| Message-ID | <Aps1b-c3-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi,
I am new to Linux and Debian.I am trying to build a custom layout for my mother tongue Malayalam (India, Kerala).
The problem I am trying to tackle:
One of the Malayalam letters, ങ (U+0D19), is used much more commonly in its geminate form which is composed of three unicode charcters ങ ് ങ (U+0D19 U+0D4D U+0D19) which will yield the geminate form ങ്ങ So, when I type, I want the ങ to be replaced with ങ്ങ.The keyboard layout is working fine as far as I can see. It does yield the correct letters. What doesn't seem to work is the .XCompose mechanism. Please tell me what I am missing.
Relevant part of my layout file /usr/share/X11/xkb/symbols/in
-----------------------
partial alphanumeric_keys
xkb_symbols "mal_puthuniraA" {
name[Group1] = "Malayalam (Puthu Nira Aarambham)";
key.type="FOUR_LEVEL";
key <AC09> { [ U0D41, U0D19, U0D4E, U0D71] }; // ു MALAYALAM VOWEL SIGN U, ങ്ങ MALAYALAM LETTER NGA geminate form, ൎMALAYALAM LETTER DOT REPH, ൱ MALAYALAM NUMBER ONE HUNDRED include "level3(ralt_switch)"
};----------------------
My .XCompose file in my home directory is---------------------include "%L"
<XK_Shift_L> <U0D19> : "ങ്ങ"
<U0D19> : "ങ്ങ"
ങ : "ങ്ങ"---------------------
I found the name XK_Shift_L in keysymdef.h file. I tried the unicode character and its code as well to identify the keypress. I tried with only one of the lines as well. XCompose(3) — libx11-doc — Debian buster — Debian Manpages was consulted. I have tried restarting after making changes which didn't help.
Am I referring to the keypress correctly? What am I missing?
Thanks for your help,ajith
|
|
|
| | |
|
|
|
| |
XCompose(3) — libx11-doc — Debian buster — Debian Manpages
|
|
|
[toc] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-07-06 14:30 +0200 |
| Message-ID | <ApypX-4bi-1@gated-at.bofh.it> |
| In reply to | #224422 |
On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote: > I am new to Linux and Debian.I am trying to build a custom layout for my mother tongue Malayalam (India, Kerala). Sadly, I know almost nothing about Asian languages. Does <https://wiki.debian.org/XCompose> help you? If it's just a handful of characters that are giving you trouble, this might be an adequate solution.
[toc] | [prev] | [next] | [standalone]
| From | Zenaan Harkness <zenaan@freedbms.net> |
|---|---|
| Date | 2020-07-06 14:50 +0200 |
| Message-ID | <ApyJk-4hK-9@gated-at.bofh.it> |
| In reply to | #224422 |
On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote: > Hi, > I am new to Linux and Debian.I am trying to build a custom layout for my mother tongue Malayalam (India, Kerala). > The problem I am trying to tackle: > One of the Malayalam letters, ങ (U+0D19), is used much more commonly in its geminate form which is composed of three unicode charcters ങ ് ങ (U+0D19 U+0D4D U+0D19) which will yield the geminate form ങ്ങ So, when I type, I want the ങ to be replaced with ങ്ങ.The keyboard layout is working fine as far as I can see. It does yield the correct letters. What doesn't seem to work is the .XCompose mechanism. Please tell me what I am missing. I have a little experience only with X layout files and not the compose mechanism. When you solve this, please post your solution here :)
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-06 21:20 +0200 |
| Message-ID | <ApEOJ-839-3@gated-at.bofh.it> |
| In reply to | #224422 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote:
> Hi,
> I am new to Linux and Debian.
That is good news. Welcome.
> I am trying to build a custom layout for my mother tongue Malayalam
> (India, Kerala).
That sounds like an interesting challenge.
Your original message appears to be in html format. The subscribers to
this mailing list use a great variety of clients to read the messages
here. Many of these clients display only plain text, and some of them
(such as my own) will tend to mangle html messages beyond recognition,
in a heroic effort to transform html into plain text.
It is therefore the convention on this list to send plain text
messages only. If you are able to conform to this convention, your
messages will reach a wider audience, and you may get more --and
better-- responses as a result.
The rest of my reply is merely the remainder of your original message,
--quoted, but converted to plain text (using the lynx text browser)--
for the benefit of subscribers who, like me, use mail clients (eg,
alpine) which badly mangled the original.
(NB: Setting up an environment that displays Malayalam glyphs as
intended is a separate matter, outside my scope here.)
Good luck with your project.
> The problem I am trying to tackle:
>
> One of the Malayalam letters, ങ (U+0D19), is used much more commonly
> in its geminate form which is composed of three unicode charcters
>
> ങ ് ങ (U+0D19 U+0D4D U+0D19)
>
> which will yield the geminate form
>
> ങ്ങ
>
> So, when I type, I want the ങ to be replaced with ങ്ങ.
>
> The keyboard layout is working fine as far as I can see. It does
> yield the correct letters. What doesn't seem to work is the
> .XCompose mechanism. Please tell me what I am missing.
>
> Relevant part of my layout file /usr/share/X11/xkb/symbols/in
> -----------------------
> partial alphanumeric_keys
> xkb_symbols "mal_puthuniraA" {
> name[Group1] = "Malayalam (Puthu Nira Aarambham)";
> key.type="FOUR_LEVEL";
> key <AC09> { [ U0D41, U0D19, U0D4E, U0D71] }; // ു MALAYALAM VOWEL SIGN U, ങ്ങ MALAYALAM LETTER
> NGA geminate form, ൎMALAYALAM LETTER DOT REPH, ൱ MALAYALAM NUMBER ONE HUNDRED
> include "level3(ralt_switch)"
> };
> ----------------------
> My .XCompose file in my home directory is
> ---------------------
> include "%L"
> <XK_Shift_L> <U0D19> : "ങ്ങ"
> <U0D19> : "ങ്ങ"
> ങ : "ങ്ങ"
> ---------------------
> I found the name XK_Shift_L in keysymdef.h file. I tried the unicode character and its code as well to
> identify the keypress. I tried with only one of the lines as well.
> XCompose(3) — libx11-doc — Debian buster — Debian Manpages was consulted. I have tried restarting after
> making changes which didn't help.
> Am I referring to the keypress correctly? What am I missing?
> Thanks for your help,
> ajith
>
> XCompose(3) — libx11-doc — Debian buster — Debian Manpages
--
What do you want to take off? [hrzF or ?*] F
You were wearing a +0 robe. The frost giant turns to flee.
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-06 22:40 +0200 |
| Message-ID | <ApG49-gN-1@gated-at.bofh.it> |
| In reply to | #224455 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, 6 Jul 2020 davidson wrote:
> On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote:
[snip]
>> I am trying to build a custom layout for my mother tongue Malayalam
>> (India, Kerala).
[snip]
>> The problem I am trying to tackle:
>>
>> One of the Malayalam letters, ങ (U+0D19), is used much more commonly
>> in its geminate form which is composed of three unicode charcters
>>
>> ങ ്ങ (U+0D19 U+0D4D U+0D19)
>>
>> which will yield the geminate form
>>
>> ങ്ങ
>>
>> So, when I type, I want the ങ to be replaced with ങ്ങ.
^^^^ ^ ^^^^
>From the above, it sounds to me that you are saying you would like a
*single* keypress to result in entry of the above geminate form. Do I
understand you correctly?
And if so, are you setting aside the question of how to enter the
simple glyph
ങ (U+0D19)
as an exercise for later?
I am still working towards interpreting (1) what you've done so far,
(2) what exactly you want to achieve, and (3) figuring out how I'd
solve some similar problem.
I lack expertise, but am interested.
>> The keyboard layout is working fine as far as I can see. It does
>> yield the correct letters. What doesn't seem to work is the
>> .XCompose mechanism. Please tell me what I am missing.
Not sure yet. In the meantime, I have one trivial observation to make,
below.
>> Relevant part of my layout file /usr/share/X11/xkb/symbols/in
>> -----------------------
>> partial alphanumeric_keys
>> xkb_symbols "mal_puthuniraA" {
>> name[Group1] = "Malayalam (Puthu Nira Aarambham)";
>> key.type="FOUR_LEVEL";
>> key <AC09> { [ U0D41, U0D19, U0D4E, U0D71] }; // ുMALAYALAM VOWEL
>> SIGN U, ങ്ങ MALAYALAM LETTER NGA geminate form, ൎMALAYALAM LETTER DOT REPH,
>> ൱ MALAYALAM NUMBER ONE HUNDRED
>> include "level3(ralt_switch)"
>> };
>> ----------------------
>> My .XCompose file in my home directory is
>> ---------------------
>> include "%L"
>> <XK_Shift_L> <U0D19> : "ങ്ങ"
In XCompose(3), under FILE FORMAT, I read:
"Keysyms are specified without the XK_ prefix."
So one change you could try, would be to replace
<XK_Shift_L>
with
<Shift_L>
in the line above.
>> <U0D19> : "ങ്ങ"
>> ങ : "ങ്ങ"
>> ---------------------
>> I found the name XK_Shift_L in keysymdef.h file. I tried the unicode
>> character and its code as well to
>> identify the keypress. I tried with only one of the lines as well.
>> XCompose(3) — libx11-doc — Debian buster — Debian Manpages was consulted. I
>> have tried restarting after
>> making changes which didn't help.
>> Am I referring to the keypress correctly? What am I missing?
>> Thanks for your help,
>> ajith
>>
>> XCompose(3) — libx11-doc — Debian buster — Debian
>> Manpages
--
What do you want to take off? [hrzF or ?*] F
You were wearing a +0 robe. The frost giant turns to flee.
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-07 17:20 +0200 |
| Message-ID | <ApXy1-2Jo-3@gated-at.bofh.it> |
| In reply to | #224457 |
[Multipart message — attachments visible in raw view] — view raw
Hi,
>>>>From the above, it sounds to me that you are saying you would like a
*single* keypress to result in entry of the above geminate form. Do I
understand you correctly?>>>>Yes, perfectly.
>>>>And if so, are you setting aside the question of how to enter the
simple glyph
ങ (U+0D19)
as an exercise for later?>>>>
No. I have achieved that already. I have defined a custom layout which seems to work ok. Among other lines, this line in the layout file is relevant to the character I am talking
key <AC09> { [ U0D41, U0D19, U0D4E, U0D71] };
>>>>I lack expertise, but am interested.>>>>Your help is very much appreciated
>>>>So one change you could try, would be to replace
<XK_Shift_L>
with
<Shift_L>
in the line above.>>>>
After reading your reply in another mail, I tried that; didn't work. I tried a composing example from the files in the link you provided but couldn't get composing to work (I have given the details in another mail). I suspect that I am missing something basic (I have named the file .XCompose and it is in my home folder). Should it have a particular start or end? To test composing, my .XCompose is just include "%L"
<Multi_key> <s> <x> : "✄" U2704 # WHITE SCISSORS
Thanks,ajith
On Tuesday, 7 July, 2020, 2:07:52 am IST, davidson <davidson@freevolt.org> wrote:
On Mon, 6 Jul 2020 davidson wrote:
> On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote:
[snip]
>> I am trying to build a custom layout for my mother tongue Malayalam
>> (India, Kerala).
[snip]
>> The problem I am trying to tackle:
>>
>> One of the Malayalam letters, ങ (U+0D19), is used much more commonly
>> in its geminate form which is composed of three unicode charcters
>>
>> ങ ്ങ (U+0D19 U+0D4D U+0D19)
>>
>> which will yield the geminate form
>>
>> ങ്ങ
>>
>> So, when I type, I want the ങ to be replaced with ങ്ങ.
^^^^ ^ ^^^^
>From the above, it sounds to me that you are saying you would like a
*single* keypress to result in entry of the above geminate form. Do I
understand you correctly?
And if so, are you setting aside the question of how to enter the
simple glyph
ങ (U+0D19)
as an exercise for later?
I am still working towards interpreting (1) what you've done so far,
(2) what exactly you want to achieve, and (3) figuring out how I'd
solve some similar problem.
I lack expertise, but am interested.
>> The keyboard layout is working fine as far as I can see. It does
>> yield the correct letters. What doesn't seem to work is the
>> .XCompose mechanism. Please tell me what I am missing.
Not sure yet. In the meantime, I have one trivial observation to make,
below.
>> Relevant part of my layout file /usr/share/X11/xkb/symbols/in
>> -----------------------
>> partial alphanumeric_keys
>> xkb_symbols "mal_puthuniraA" {
>> name[Group1] = "Malayalam (Puthu Nira Aarambham)";
>> key.type="FOUR_LEVEL";
>> key <AC09> { [ U0D41, U0D19, U0D4E, U0D71] }; // ുMALAYALAM VOWEL
>> SIGN U, ങ്ങ MALAYALAM LETTER NGA geminate form, ൎMALAYALAM LETTER DOT REPH,
>> ൱ MALAYALAM NUMBER ONE HUNDRED
>> include "level3(ralt_switch)"
>> };
>> ----------------------
>> My .XCompose file in my home directory is
>> ---------------------
>> include "%L"
>> <XK_Shift_L> <U0D19> : "ങ്ങ"
In XCompose(3), under FILE FORMAT, I read:
"Keysyms are specified without the XK_ prefix."
So one change you could try, would be to replace
<XK_Shift_L>
with
<Shift_L>
in the line above.
>> <U0D19> : "ങ്ങ"
>> ങ : "ങ്ങ"
>> ---------------------
>> I found the name XK_Shift_L in keysymdef.h file. I tried the unicode
>> character and its code as well to
>> identify the keypress. I tried with only one of the lines as well.
>> XCompose(3) — libx11-doc — Debian buster — Debian Manpages was consulted. I
>> have tried restarting after
>> making changes which didn't help.
>> Am I referring to the keypress correctly? What am I missing?
>> Thanks for your help,
>> ajith
>>
>> XCompose(3) — libx11-doc — Debian buster — Debian
>> Manpages
--
What do you want to take off? [hrzF or ?*] F
You were wearing a +0 robe. The frost giant turns to flee.
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-07 08:40 +0200 |
| Message-ID | <ApPqO-686-19@gated-at.bofh.it> |
| In reply to | #224455 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, 6 Jul 2020 davidson wrote: > On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote: [snip] >> The problem I am trying to tackle: >> >> One of the Malayalam letters, ങ (U+0D19), is used much more commonly >> in its geminate form which is composed of three unicode charcters >> >> ങ ്ങ (U+0D19 U+0D4D U+0D19) >> >> which will yield the geminate form >> >> ങ്ങ >> >> So, when I type, I want the ങ to be replaced with ങ്ങ. >> >> The keyboard layout is working fine as far as I can see. It does >> yield the correct letters. What doesn't seem to work is the >> .XCompose mechanism. One thing that would be helpful for us to know: How are you *testing* whether the .XCompose mechanism "works"? That is, after making changes to the ~/.XCompose file, what applications do you use for testing? Do you use xterm? Some other terminal emulator? Firefox? Several applications? Which ones? Do they all yield the same results? >> Please tell me what I am missing. [snip] -- What do you want to take off? [hrzF or ?*] F You were wearing a +0 robe. The frost giant turns to flee.
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-07 17:20 +0200 |
| Message-ID | <ApXy1-2Jo-7@gated-at.bofh.it> |
| In reply to | #224477 |
[Multipart message — attachments visible in raw view] — view raw
Hi,
I test it by typing the letter from the keyboard (using shift / without it based on the layout specification) from the same terminal (Konsole) that i use setxkbmap to change to my layout. Then I run another terminal using the desktop link and try tying it. Then I try in Kate. And finally I reboot and try in Kate again.ajith
On Tuesday, 7 July, 2020, 12:04:46 pm IST, davidson <davidson@freevolt.org> wrote:
On Mon, 6 Jul 2020 davidson wrote:
> On Mon, Jul 06, 2020 at 05:34:59AM +0000, Ajith R wrote:
[snip]
>> The problem I am trying to tackle:
>>
>> One of the Malayalam letters, ങ (U+0D19), is used much more commonly
>> in its geminate form which is composed of three unicode charcters
>>
>> ങ ്ങ (U+0D19 U+0D4D U+0D19)
>>
>> which will yield the geminate form
>>
>> ങ്ങ
>>
>> So, when I type, I want the ങ to be replaced with ങ്ങ.
>>
>> The keyboard layout is working fine as far as I can see. It does
>> yield the correct letters. What doesn't seem to work is the
>> .XCompose mechanism.
One thing that would be helpful for us to know: How are you *testing*
whether the .XCompose mechanism "works"?
That is, after making changes to the ~/.XCompose file, what
applications do you use for testing? Do you use xterm? Some other
terminal emulator? Firefox? Several applications? Which ones? Do
they all yield the same results?
>> Please tell me what I am missing.
[snip]
--
What do you want to take off? [hrzF or ?*] F
You were wearing a +0 robe. The frost giant turns to flee.
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-09 23:50 +0200 |
| Message-ID | <AqMAx-8gV-3@gated-at.bofh.it> |
| In reply to | #224506 |
[Multipart message — attachments visible in raw view] — view raw
I have conducted an experiment with the following ~/.XCompose file,
and tried to document it relatively thoroughly below.
It is my hope that OP and/or others may find some of this
(unfortunately rather voluminous) information helpful or at least
somewhat interesting, though it is difficult for me to know precisely
whether or how they will be able to use it.
Of course, to interpret any meaning from the results presented here,
the context/environment in which the test was conducted matters
greatly. Details about my system are attached, in the file
"system_synposis_bbhuit.txt". (In case that attachment gets lost
somehow, I will simply post the same information in a follow-up
message.)
%% THREE XCOMPOSE RULES to test
$ cat ~/.XCompose
include "%L"
<U0D19> : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19)
<Multi_key> <s> <x> : "✄" # (U2704) white scissors, h/t David Wright
<Z> : "ARGA WARGA IN THE DARGA instead of Z"
I started an X Window session, and then in a few applications I tested
whether the three custom rules above were effective.
For the tests, I used a couple of terminal emulators for X (xterm and
mlterm) and a couple of graphical web browsers (firefox-esr and
qutebrowser):
davidson@bbhuit:0 ~$ dpkg-query -l --no-pager xterm mlterm firefox-esr qutebrowser
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-====================-============-============================================================
ii firefox-esr 68.10.0esr-1~deb10u1 amd64 Mozilla Firefox web browser - Extended Support Release (ESR)
ii mlterm 3.8.6-2 amd64 MultiLingual TERMinal
ii qutebrowser 1.6.1-2 all Keyboard-driven, vim-like browser based on PyQt5
ii xterm 344-1 amd64 X terminal emulator
%% ARGA WARGA
The third rule ('Z' => "ARGA WARGA...Z") was easiest to test:
1. Open the application. (If necessary, navigate to a text entry field.)
2. (While under "us" keyboard layout) strike the key labeled "Z" on my
standard US laptop keyboard
3. Observe whether
ARGA WARGA IN THE DARGA instead of Z
is printed.
The two terminal emulators passed this test. The graphical web browsers failed
in an interesting way. Instead of displaying
ARGA WARGA IN THE DARGA instead of Z
in the text entry field, they displayed just
A
Also, upon starting up (but only on the first start-up since
installation of the three rules in ~/.XCompose) , firefox-esr issued
the following errors, which appear to be explanatory:
(firefox-esr:11619): Gtk-WARNING **: 16:27:05.630: GTK+ supports to output one char only:
"ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19):
<U0D19> : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19)
(firefox-esr:11619): Gtk-WARNING **: 16:27:05.630: GTK+ supports to output one char only:
"ARGA WARGA IN THE DARGA instead of Z":
<Z> : "ARGA WARGA IN THE DARGA instead of Z"
(I have split each error into three separate lines above to improve legibility.)
Although both web browsers performed identically, failing in the same
way, only firefox-esr issued this explanatory error message.
Unlike firefox-esr, qutebrowser does not use libgtk (do "apt-cache
depends qutebrowser" to see its dependencies), but both graphical web
browsers failed this test identically.
%% WHITE SCISSORS
The second rule (David Wright's white scissors rule) was tested as
follows:
1. Open the application. (If necessary, navigate to a text entry field.)
2. Under "us" keyboard layout, hold down the compose key. Strike the
key labeled "S" on my standard US laptop keyboard. Release the
compose key. Strike the key labeled "X".
3. Observe whether
✄
is printed.
All four applications passed this test. (I should mention that I have
noticed that sometimes when I use the compose key, it seems to get
ignored on the first try. It happens frequently enough that it has
become second nature to me to simply backspace and try again, when
this happens. Whether this is human error, or something else, is not
something I have spent time investigating. Whatever the cause, it does
not trouble me more than other commonly self-inflicted typos do.)
NB: If, like me, you occasionally confuse the Ctrl key with the
compose key, then keep in mind that when testing this rule in a
terminal emulator, that typing Ctrl-s (presumably by accident) may
well stop the terminal from echoing entered characters to the display
until you enter Ctrl-q to resume normal terminal operation. (That is
to say, Ctrl-s doesn't "break your keyboard", it only pauses your
terminal's printout to the display until you resume it with Ctrl-q.)
%% AUTO-GEMINATION
Finally. The first rule in the ~/.XCompose file above
<U0D19> : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19)
I tested as follows (after installing the "Lohit TrueType font for
Malayalam Language" package, fonts-lohit-mlym):
1. I opened an xterm (uxterm, actually) and issued the following
command to alter the X Window display keymap:
$ setxkbmap -display $DISPLAY -layout us,in -variant ,mal
This configures --as my alternate keyboard layout in the current X
display-- the variant "mal" (malayalam) of the "in" (indian)
keyboard layout, so that switching to the alternate layout will
permit me to enter malayalam characters.
On my system, the longer command below is equivalent to the
command above, because the setting for XKBOPTIONS that the longer
command specifies (with the -option flag), is already set as a
default in my /etc/default/keyboard (see attached system synopsis
for details of this):
$ setxkbmap -display $DISPLAY -layout us,in -variant ,mal -option grp:caps_toggle
I mention this equivalence because the longer command makes
explicit whick key permits me to switch from my main "us" keyboard
layout to the alternate layout "in.mal" (and back again).
NB: In these commands, make note of the commas. In particular the
comma in ",mal" is not a typo.
NBB: I believe at least one other poster here correctly urged
caution when experimenting with setxkbmap. You can render your
keyboard non-functional in the X session. Have a plan for shutting
down the X session without the use of your keyboard.
2. To test applications besides xterm itself, I launched the
application from the xterm just opened. (When testing xterm, I
skipped this step.)
$ mlterm # or firefox-esr or qutebrowser
3. If necessary, navigate to a text entry field.
4. Strike the capslock key to switch to the alternate keyboard
layout configured in step 1.
5. Hold down the shift key. Strike the key labeled "U" on my standard
US laptop keyboard.
6. Observe whether
ങ്ങ
is printed, according to the custom auto-geminate rule in ~/.XCompose.
The terminal emulators passed this test. The graphical web browsers
failed, instead printing only
ങ
The error message from firefox-esr above seems to suggest why that is.
Another thing I think is interesting is that while the terminal
emulators did pass this test and the browsers failed, it is only the
graphical web browsers which seem to transform/meld a typed sequence
of
"ങ" followed by "്" followed by "ങ"
into what appears (to my utterly ignorant eye) to be a "freshly
synthetic" glyph. (That three-character sequence is typed, on my
standard US laptop keyboard under the "in.mal" keyboard layout, by
striking the "U" key while holding down shift, then striking the "D"
key (unshifted), and then again striking the "U" key while holding
down shift.)
Finally, in case it is of interest to anyone, in the attached file
"xev_output_annotated.txt" is some xev(1) output with commentary that
gives a detailed close-up of performing steps 4 through 6 in an
xterm. (As with the system synopsis, if it happens to "get lost" I'll
just post it the message body of a follow-up.)
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-10 03:40 +0200 |
| Subject | Re: Using .XCompose [resend of xev_output_annotated.txt] |
| Message-ID | <AqQb7-20t-1@gated-at.bofh.it> |
| In reply to | #224662 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 9 Jul 2020 davidson wrote:
[snip]
> Finally, in case it is of interest to anyone, in the attached file
> "xev_output_annotated.txt" is some xev(1) output with commentary
> that gives a detailed close-up of performing steps 4 through 6 in an
> xterm. (As with the system synopsis, if it happens to "get lost"
> I'll just post it the message body of a follow-up.)
It appears that the process of attaching that file to my previous
message caused alteration of those bytes encoding the malayalam
characters. This affected all lines beginning with either
XLookupString gives N bytes:
or
XmbLookupString gives N bytes:
for N greater than 0.
The remainder of this message is (hopefully) a more faithful
representation of the file (previously attached as
"xev_output_annotated.txt").
____________________________________________________________________
$ man xev
[...]
DESCRIPTION
Xev creates a window and then asks the X server to send it events
whenever anything happens to the window (such as it being moved,
resized, typed in, clicked in, etc.). You can also attach it to an
existing window. It is useful for seeing what causes events to
occur and to display the information that they contain; it is
essentially a debugging and development tool, and should not be
needed in normal usage.
This is the command I issued from within an xterm (uxterm, really) to
launch xev and attach it to that terminal's window.
$ xev -id $WINDOWID -event keyboard # I press enter, of course
# And here is the release of the enter key:
KeyRelease event, serial 18, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76502401, (1362,764), root:(1364,766),
state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
XLookupString gives 1 bytes: (0d) ""
XFilterEvent returns: False
# Next, I strike the capslock key to enter the Malayalam keymap, "ml".
# The capslock key's keycode happens to be 66. This is a relatively
# low-level identifier, mechanical, relatively meaningless in itself,
# fixed by factual accident.
#
# Its keysym, under my configuration, is apparently <ISO_Next_Group>.
#
# A keysym is an identifier of somewhat higher abstraction than a
# keycode, and is meant to *mean* something. (I mean, just compare the
# two names to see this!)
#
# The following *three* records correspond to striking this key.
#
# NB: For some reason, each key struck seems to correspond to *three*
# records in the xev output:
#
# 1. a KeyRelease event (kind of weird, but that's how it is).
# 2. a KeyPress event.
# 3. a KeyRelease event.
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76506392, (1362,764), root:(1364,766),
state 0x0, keycode 66 (keysym 0xfe08, ISO_Next_Group), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76506392, (1362,764), root:(1364,766),
state 0x0, keycode 66 (keysym 0xfe08, ISO_Next_Group), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76506480, (1362,764), root:(1364,766),
state 0x2000, keycode 66 (keysym 0xfe08, ISO_Next_Group), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
# Next, I hold down a shift key (left shift, as it happens).
#
# NB: The following *two* records correspond to this. First a
# KeyRelease, then a KeyPress.
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76509510, (1362,764), root:(1364,766),
state 0x2000, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76509510, (1362,764), root:(1364,766),
state 0x2000, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
# Then, still holding down the shift key, I strike the key labeled "U"
# on my standard US laptop keyboard.
#
# NB: The next *four* records correspond to this action.
#
# * The first two events are due to holding down the key labeled
# "U" (KeyRelease event followed by KeyPress),
#
# * followed by a third, MAGICALLY INTERPOLATED, KeyPress event
# (presumably due to the relevant entry in ~/.XCompose),
#
# * and wrapped up with the KeyRelease event corresponding to
# releasing that "U" labeled key.
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76509907, (1362,764), root:(1364,766),
state 0x2001, keycode 30 (keysym 0x1000d19, U0D19), same_screen YES,
XLookupString gives 3 bytes: (e0 b4 99) "ങ"
XFilterEvent returns: False
KeyPress event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76509907, (1362,764), root:(1364,766),
state 0x2001, keycode 30 (keysym 0x1000d19, U0D19), same_screen YES,
XLookupString gives 3 bytes: (e0 b4 99) "ങ"
XmbLookupString gives 3 bytes: (e0 b4 99) "ങ"
XFilterEvent returns: True
# This one is THE MAGIC!
KeyPress event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76509907, (1362,764), root:(1364,766),
state 0x2001, keycode 0 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 9 bytes: (e0 b4 99 e0 b5 8d e0 b4 99) "ങ്ങ"
XFilterEvent returns: False
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76509998, (1362,764), root:(1364,766),
state 0x2001, keycode 30 (keysym 0x1000d19, U0D19), same_screen YES,
XLookupString gives 3 bytes: (e0 b4 99) "ങ"
XFilterEvent returns: False
# And now I release the shift key.
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76510083, (1362,764), root:(1364,766),
state 0x2001, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
# Having wrapped up my experiment (and happily observing the desired
# character echoed to the terminal), I strike the capslock key to
# return to a more familiar-to-me keymap. Three records, as per usual,
# correspond to this action: Release, Press, Release.
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76514882, (1362,764), root:(1364,766),
state 0x2000, keycode 66 (keysym 0xfe08, ISO_Next_Group), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76514882, (1362,764), root:(1364,766),
state 0x2000, keycode 66 (keysym 0xfe08, ISO_Next_Group), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76514968, (1362,764), root:(1364,766),
state 0x0, keycode 66 (keysym 0xfe08, ISO_Next_Group), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
# Here I hold down the control key, as a preliminary step to entering
# Ctrl-c, to kill xev. Two events (Release followed by Press),
# correspond to this preliminary action. The victim of the killing
# strike --'c'-- has obviously failed to record its own assassination.
KeyRelease event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76517083, (1362,764), root:(1364,766),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 21, synthetic NO, window 0x60000f,
root 0x102, subw 0x0, time 76517083, (1362,764), root:(1364,766),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
--
The day will come | Last words, August Spies (1855--1887).
When our silence will be | Hanged, by the state of Illinois,
More powerful than | alongside fellow journalists
The voices you strangle today | Adolf Fischer and Albert Parsons.
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-10 10:50 +0200 |
| Message-ID | <AqWTf-6aG-1@gated-at.bofh.it> |
| In reply to | #224662 |
Hi, Thanks for your experiment. The fact that it works atleast in some applications gives hope. I copied your exact sentences to my compose file. In Konsole the command cat ~/.XCompose gives the result: include "%L" <U0D19> : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19) <Multi_key> <s> <x> : "✄" # (U2704) white scissors, h/t David Wright <Z> : "ARGA WARGA IN THE DARGA instead of Z" Next, I issued setxkbmap -layout us, just to make sure that the layout is us. I used konsole and UXterm to test Z. The test failed with Z remaining unchanged. So, as Zeenan says, there is something fundamentally wrong in my system. I have to find that and correct it or reinstall everything. I tried in another computer with Debian and KDE. The Z gets replaced by the first letter in replacement string, while nothing happens in Xterm. Is KDE the problem? I checked IceWM and got the same result. > into what appears (to my utterly ignorant eye) to be a "freshly > synthetic" glyph That "freshly synthetic" glyph would be the geminate form. > firefox-esr issued the following errors, which appear to be explanatory: > (firefox-esr:11619): Gtk-WARNING **: 16:27:05.630: GTK+ supports to output one char only: This means that all softwares that use Gtk will behave similarly? > NB: If, like me, you occasionally confuse the Ctrl key with the > compose key, then keep in mind that when testing this rule in a > terminal emulator, that typing Ctrl-s (presumably by accident) may > well stop the terminal from echoing entered characters to the display > until you enter Ctrl-q to resume normal terminal operation. (That is > to say, Ctrl-s doesn't "break your keyboard", it only pauses your > terminal's printout to the display until you resume it with Ctrl-q.) Thanks for pointing this out. I don't think I have done so because Konsole flashes the message that I have suspended display when I press Ctrl S. I would have noticed it. Thanks a lot for your detailed explanations, ajith
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-11 10:40 +0200 |
| Message-ID | <Arjd7-4cJ-9@gated-at.bofh.it> |
| In reply to | #224676 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, 10 Jul 2020 Ajith R wrote:
> Hi,
>
> Thanks for your experiment. The fact that it works atleast in some
> applications gives hope.
There remains the strange fact that in no application (yet) have we
seen *both* properties:
1. application produces multiple characters in accordance with
XCompose rule that specifies this
2. application displays the sequence of the three unicode characters
U+0D19 U+0D4D U+0D19 as the appropriate geminate glyph
I found xterm and mlterm to have property (1), and some graphical
browsers (firefox-esr and qutebrowser) to have property (2). We have
not yet seen anything do both.
(Actually, I have just learned how to make firefox-esr do both. See
GTK_IM_MODULE below.)
Curious parties (like myself) wishing to understand the orthographic
peculiarities at issue here, might find the following section of the
Wikipedia entry on Malayalam script provides brief, helpful
background:
https://en.wikipedia.org/wiki/Malayalam_script#Ligatures
The "appropriate geminate glyph" refered to in property (2) above is
illustrated in this table, in the "ligated" row under the column
headed "ṅṅa".
https://en.wikipedia.org/wiki/Malayalam_script#Common_consonant_ligatures
> I copied your exact sentences to my compose file.
>
> In Konsole the command cat ~/.XCompose gives the result:
>
> include "%L"
> <U0D19> : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19)
> <Multi_key> <s> <x> : "✄" # (U2704) white scissors, h/t David Wright
> <Z> : "ARGA WARGA IN THE DARGA instead of Z"
Do you know what I see in four lines above, representing the content
of your ~/.XCompose file? I see "non-breaking space" characters
(two-byte sequences 0xc2a0). I see 8 of them in the last line alone
(the <Z> rule). Do you know what non-breaking space characters are?
I'm not quite sure how best to describe them, myself.
But I will tell you what they *aren't*. They aren't spaces. They
aren't tabs. And the only thing their presence is going to do --in
your code and in your configuration files-- is wreak havoc.
Their name is very ironic. For our purposes,
1. they aren't spaces, and
2. they break EVERYTHING.
Whatever it is you are doing that puts them there, STOP DOING IT.
You can print all lines of sometextfile which contain them by doing
this:
$ grep $'\xc2\xa0' sometextfile
> Next, I issued setxkbmap -layout us, just to make sure that the layout is us.
>
> I used konsole and UXterm to test Z. The test failed with Z remaining unchanged.
The non-breaking spaces alone explain this much.
> So, as Zeenan says, there is something fundamentally wrong in my
> system. I have to find that and correct it or reinstall everything.
Is the situation still as you describe here?
8 July 2020 Ajith R to debian-user
https://lists.debian.org/msgid-search/620563117.3978825.1594226239402@mail.yahoo.com
Now, things are even more strange. When I press the Caps Lock, a
strange character appears. (I copy pasted it, searched the net and
found it to be unicode compose character.) Then when I type s, the
Caps Lock light gets switched on and the character S (caps) appears
on screen. Then when I type X, the compose character and S become
invisible and x/X doesn't appear. When I change focus to another
window, the terminal in which I was typing shows the compose
character and S.
This behaviour has not changed after I unchecked the settings
through KDE settings menu, after restarting computer, re-issuing
xmodmap command or changing the layout to us. The same sequence is
seen with typing in Kate as well. Even when I use Scroll Lock as the
compose key, the situation is only different in that the s is not
capitalised.
If this is still so, we ought to figure out what's going on. To this
end, I previously asked for the output of
$ xmodmap
and
$ xmodmap -pk
> I tried in another computer with Debian and KDE. The Z gets replaced
> by the first letter in replacement string, while nothing happens in
> Xterm.
Try again, for firefox-esr (and with a ~/.XCompose file that is not
befouled with nonbreaking spaces).
But make one change to the procedure. When you launch firefox-esr, do
so like this:
$ env GTK_IM_MODULE=xim firefox-esr
Let us know how that goes.
> Is KDE the problem? I checked IceWM and got the same result.
>
>> into what appears (to my utterly ignorant eye) to be a "freshly
>> synthetic" glyph
>
> That "freshly synthetic" glyph would be the geminate form.
I must say that the more I learn about the project you outlined in
your original post, the more interesting it becomes.
May I ask how you happened to find the post about providing linux
support for the Breton keyboard
https://dominiko.livejournal.com/20206.html
which you mentioned in this 7 July reply to David Wright?
https://lists.debian.org/msgid-search/563409927.3312315.1594115078623@mail.yahoo.com
However it is that you came across it, that is a very interesting case
as well.
>> firefox-esr issued the following errors, which appear to be explanatory:
>> (firefox-esr:11619): Gtk-WARNING **: 16:27:05.630: GTK+ supports to output one char only:
>
> This means that all softwares that use Gtk will behave similarly?
I would not hastily draw broad conclusions. I don't know about you,
but for my part --conceptually speaking-- I am still stumbling around
in a dark room trying to acquire some semblance of object permanence
without knocking over the coffee table.
>> NB: If, like me, you occasionally confuse the Ctrl key with the
>> compose key, then keep in mind that when testing this rule in a
>> terminal emulator, that typing Ctrl-s (presumably by accident) may
>> well stop the terminal from echoing entered characters to the display
>> until you enter Ctrl-q to resume normal terminal operation. (That is
>> to say, Ctrl-s doesn't "break your keyboard", it only pauses your
>> terminal's printout to the display until you resume it with Ctrl-q.)
>
> Thanks for pointing this out. I don't think I have done so because
> Konsole flashes the message that I have suspended display when I
> press Ctrl S. I would have noticed it.
That is very friendly of konsole to do. I did not know this.
> Thanks a lot for your detailed explanations,
Well, they are detailed. As to whether I have managed to explain
anything, I think that is open to interpretation. But it is kind of
you to say.
--
You won't feel the collar if you don't go anywhere.
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-11 12:30 +0200 |
| Message-ID | <ArkVz-5gw-1@gated-at.bofh.it> |
| In reply to | #224698 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 11 Jul 2020 davidson wrote: > On Fri, 10 Jul 2020 Ajith R wrote: >> Hi, >> >> Thanks for your experiment. The fact that it works atleast in some >> applications gives hope. > > There remains the strange fact that in no application (yet) have we > seen *both* properties: > > 1. application produces multiple characters in accordance with > XCompose rule that specifies this > > 2. application displays the sequence of the three unicode characters > U+0D19 U+0D4D U+0D19 as the appropriate geminate glyph [snip] > The "appropriate geminate glyph" refered to in property (2) above is > illustrated in this table, [WHEN *cough* ...viewed with an application possessing property (2)] > in the "ligated" row under the column headed "ṅṅa". > > https://en.wikipedia.org/wiki/Malayalam_script#Common_consonant_ligatures
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-12 17:00 +0200 |
| Message-ID | <ArLCp-4oG-3@gated-at.bofh.it> |
| In reply to | #224700 |
[Multipart message — attachments visible in raw view] — view raw
Hi All,
I will start with what I did in sequence
Using Konsole from my home directory
1)executed setxkbmap -layout us
2)executed xmodmap which gave the following output
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x69)
mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
3)executed xmodmap -pk > xmm
The file named xmm is attached
4) executed setxkbmap -print which gave the following
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc104)" };
};
5) execute grep $'\x00A0' .XCompose. All lines from the .XCompose file were listed.
So, I replaced the .XCompose file and retyped the three lines (with only space typed using the space bar of the kyboardbetween the letters) and executed the grep command. Again it returned all lines. So, I replaced .XCompose file with just the W line. Again that line was reported by grep. So, I abandoned Kate and built one using cat > .XCompose followed by the line <W> : "This replaces W", followed by Enter and Ctrl+D. The grep command returned the line.
I noticed that there is $ sign before the search string, which I couldn't understand. I removed it and re-executed the new grep command grep '\x00A0' .XCompose. Now it doesn't return the line
6) The command grep "W" .XCompose | tr $'\xc2\xa0' \! returns
grep "W" .XCompose | tr $'\xc2\xa0' \!
7) I typed W (holding down shift and pressing w). The Konsole (the instance from which I issued the command as well as a new instance) did nothing except displaying the W. I typed W in Kate with the same result.
Is it safe to say that the .XCompose file doesn't have the nonbreaking spaces?
> You can print all lines of sometextfile which contain them by doing
> this:
> $ grep $'\xc2\xa0' sometextfile
Is the $ just before the search string in single quotes in the grep command intentional? If so, what is its significance?
> '!' marks the spot of nonbreaking spaces that made it into OP's first
> report of odd behavior, upon testing the white scissors XCompose rule:
Could you please see if any of the lines in this message too behaves similarly? If so, isn't possible that the mail system adds them?
BTW, I understand that OP refers to me; but, what exactly does it stand for? Original Petitioner?
> So those examples, fi and ½, illustrate the difference between
> modification on output and input in English. I can't judge how the OP
> views this, nor whether they are contravening some conventions in
> their own computer culture by trying to make their changes. This
> doesn't even address how a computer responds to a command line
> written in non-latin script.
I am concerned with the internal representation only. That is, I want <U0D19> to be replaced with <U0D19> < U0D4D> <U0D19>. The display of this sequence as a ligated conjunct or as three different symbols is dependant on the font the user has. Whether this sequence is displayed as the ligated conjunct or as three different charcters, it would be read the same. So, there isn't breaking of any langauge semantics or conventions. All this would bring is some ease of typing a commonly used conjunct.
> I know knothing about DE menus.
> It would appear from others' posts that DEs can change anything
> and everything.
What does DE stand for?
> May I ask how you happened to find the post about providing linux
> support for the Breton keyboard
> https://dominiko.livejournal.com/20206.html
I found it by searching the net
> Try again, for firefox-esr (and with a ~/.XCompose file that is not
> befouled with nonbreaking spaces).
> But make one change to the procedure. When you launch firefox-esr, do
> so like this:
> $ env GTK_IM_MODULE=xim firefox-esr
> Let us know how that goes.
Yet to do this. Will inform
Thanks everyone for all your help,
ajith
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-07-13 06:00 +0200 |
| Message-ID | <ArXNf-3hr-1@gated-at.bofh.it> |
| In reply to | #224709 |
I have cat /etc/default/keyboard
XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS="lv3:ralt_switch,compose:caps,terminate:ctrl_alt_bksp"
BACKSPACE="guess"
On Sun 12 Jul 2020 at 14:51:33 (+0000), Ajith R wrote:
> Using Konsole from my home directory
>
> 1)executed setxkbmap -layout us
> 2)executed xmodmap which gave the following output
>
> xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
>
> shift Shift_L (0x32), Shift_R (0x3e)
> lock Caps_Lock (0x42)
> control Control_L (0x25), Control_R (0x69)
> mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
> mod2 Num_Lock (0x4d)
> mod3
> mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
> mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
As expected from /e/d/k at the top, mine has slight differences:
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock
control Control_L (0x25), Control_R (0x69)
mod1 Alt_L (0x40), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
but note that all my whitespace is spaces, whereas yours has a
0xc2 0xa0 sequence preceding each space.
> 3)executed xmodmap -pk > xmm
>
> The file named xmm is attached
Again, very similar to mine. The only different lines are:
- 22 0xff08 (BackSpace) 0xff08 (BackSpace) 0xff08 (BackSpace) 0xff08 (BackSpace) 0x0000 (NoSymbol) 0x0000 (NoSymbol) 0xfed5 (Terminate_Server)
+ 22 0xff08 (BackSpace) 0xff08 (BackSpace) 0xff08 (BackSpace) 0xff08 (BackSpace)
- 66 0xff20 (Multi_key) 0xff20 (Multi_key) 0xff20 (Multi_key) 0xff20 (Multi_key)
+ 66 0xffe5 (Caps_Lock) 0x0000 (NoSymbol) 0xffe5 (Caps_Lock)
- 108 0xfe03 (ISO_Level3_Shift) 0x0000 (NoSymbol) 0xfe03 (ISO_Level3_Shift)
+ 108 0xffea (Alt_R) 0xffe8 (Meta_R) 0xffea (Alt_R) 0xffe8 (Meta_R)
My (-) lines show the results of the three XKBOPTIONS in /e/d/k.
(I have compressed the whitespace here.)
Note that the whitespace in your *attached* file (mixed tabs and
saces) matched my own, whereas the file here in your post does not.
That suggests that the 0xc2 0xa0 sequences may be a result of your
copy/paste operation.
> 4) executed setxkbmap -print which gave the following
>
> xkb_keymap {
> xkb_keycodes { include "evdev+aliases(qwerty)" };
> xkb_types { include "complete" };
> xkb_compat { include "complete" };
> xkb_symbols { include "pc+us+inet(evdev)" };
> xkb_geometry { include "pc(pc104)" };
> };
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)+level3(ralt_switch)+compose(caps)+terminate(ctrl_alt_bksp)" };
xkb_geometry { include "pc(pc105)" };
};
again just reflects the additions in my /e/d/k.
> 5) execute grep $'\x00A0' .XCompose.
That's not going to work, on two counts. Firstly, $'\x00' is NUL,
which terminates the string, so grep $'\x00efghijkl' will give
the same result as grep $'\x00'. Secondly, \x should be followed
by only two characters, so grep $'\xc2\xa0' will reveal those
lines with odd whitescape. However, grep $'\xa0' will find them too.
BTW, C2A0 is UTF-8 for the Unicode codepoint \xa0, the unbreakable space.
So if you want to show the contents of a file, it might be better to
do it by incluing the file with your email editor. The output of
commands can be inserted by redirecting the output to a temporary
file and the included likewise.
> I noticed that there is $ sign before the search string, which I couldn't understand. I removed it and re-executed the new grep command grep '\x00A0' .XCompose. Now it doesn't return the line
… because it doesn't contain any lines with \x00A0 in them.
$ man bash
[ snip to line 516 ]
Words of the form $'string' are treated specially. The word expands
to string, with backslash-escaped characters replaced as specified
by the ANSI C standard. Backslash escape sequences, if present, are
decoded as follows:
[…]
\xHH the eight-bit character whose value is the hexadecimal value
HH (one or two hex digits)
\uHHHH the Unicode (ISO/IEC 10646) character whose value is the
hexadecimal value HHHH (one to four hex digits)
So you were mixing up those two constructions, perhaps.
> Is it safe to say that the .XCompose file doesn't have the nonbreaking spaces?
If you haven't got it, install the package bsdmainutils which contains
the hexdump command. hexdump -C filename will reveal exactly what's
in a file, hex to the left, and corresponding characters to the right.
(I alias "hex" to hexdump -C.)
> BTW, I understand that OP refers to me; but, what exactly does it stand for? Original Petitioner?
Original Post(er). Both post and person: which one is usually
obvious from the context.
> > So those examples, fi and ½, illustrate the difference between
> > modification on output and input in English. I can't judge how the OP
> > views this, nor whether they are contravening some conventions in
> > their own computer culture by trying to make their changes. This
> > doesn't even address how a computer responds to a command line
> > written in non-latin script.
>
> I am concerned with the internal representation only. That is, I want <U0D19> to be replaced with <U0D19> < U0D4D> <U0D19>. The display of this sequence as a ligated conjunct or as three different symbols is dependant on the font the user has. Whether this sequence is displayed as the ligated conjunct or as three different charcters, it would be read the same. So, there isn't breaking of any langauge semantics or conventions. All this would bring is some ease of typing a commonly used conjunct.
OK. I wonder whether the problem you're having with using XCompose
is that although those three characters <U0D19> <U0D4D> <U0D19>
look independent of each other in the file, the keystrokes that
generate them might not be. Not having your layout, I don't think
I can test whether you get the behaviour I think you do, that
when you put the cursor at the beginning of a *typed* line that
looks like the next one and press Delete once:
ങ്ങ
you get
ങ
whereas I get
്ങ
Is that right?¹ If so, there must be some extra logic built into the
keyboard mapping to achieve that effect. Perhaps this is interfering
with XCompose. Or possibly, because of the standard way in which the
keyboard is set up for all Indic scripts, XCompose just isn't
supported with that layout, as you have no need to compose characters
in the way that's needed for Latin scripts.
> > I know knothing about DE menus.
> > It would appear from others' posts that DEs can change anything
> > and everything.
>
> What does DE stand for?
Desktop Environment. They seem to change the way most things are configured.
¹ This might only happen when you're typing input, not editing a file.
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-07-13 14:00 +0200 |
| Message-ID | <As5hL-7Q0-13@gated-at.bofh.it> |
| In reply to | #224709 |
On Sun, Jul 12, 2020 at 02:51:33PM +0000, Ajith R wrote: > 5) execute grep $'\x00A0' .XCompose. All lines from the .XCompose file were listed. Bash's $'...' quoting allows several different forms, and you've used the wrong one. The \x is followed by *two* hex digits, to give a single byte. You've got $'\x00' which is a NUL byte. Passing a NUL byte as an argument to a command is equivalent to passing the empty string. So, basically you have run grep '' .XCompose which, as you observed, gives you every line of the file. I would imagine you were trying to pass a Unicode character. If that's the case, you need the \u or \U form instead. grep $'\u00A0' .XCompose Unicode character 00A0 is a non-breaking space. It's not clear whether that was your intention or not. > I noticed that there is $ sign before the search string, which I couldn't understand. I removed it and re-executed the new grep command grep '\x00A0' .XCompose. Now it doesn't return the line Uh... you mean you *weren't* trying to grep for non-breaking spaces in your file using bash's $'...' quoting syntax? You're just typing something you found at random on the Internet without understanding it? That's pretty dangerous. <https://mywiki.wooledge.org/Quotes> might be good reading for you at this point. > 6) The command grep "W" .XCompose | tr $'\xc2\xa0' \! returns > grep "W" .XCompose | tr $'\xc2\xa0' \! The two hex bytes c2 a0 are the UTF-8 encoding of a non-breaking space, so it *does* seem like you're chasing after non-breaking spaces for some reason.... If that's truly your goal, you might also want to pursue configuring your text editor to show them to you. There are various ways to do that, depending on which text editor you use. (I don't even know whether you're in a UTF-8 encoding, though, so who knows whether those are even the correct bytes for an NBSP in your locale. You're better off using \u00A0 instead.)
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-13 20:30 +0200 |
| Message-ID | <Asbnc-3gd-5@gated-at.bofh.it> |
| In reply to | #224738 |
Hi Greg, > I would imagine you were trying to pass a Unicode character. If that's > the case, you need the \u or \U form instead. > > grep $'\u00A0' .XCompose > > Unicode character 00A0 is a non-breaking space. It's not clear whether > that was your intention or not. Yes, that was my intention > > I noticed that there is $ sign before the search string, which I couldn't understand. I removed it and re-executed the new grep command grep '\x00A0' .XCompose. Now it doesn't return the line > > Uh... you mean you *weren't* trying to grep for non-breaking spaces > in your file using bash's $'...' quoting syntax? You're just typing > something you found at random on the Internet without understanding > it? That's pretty dangerous. Yes, I was trying something that I didn't understand. However, it was not from the internet but given a pretty helpful person in this group. > <https://mywiki.wooledge.org/Quotes> might be good reading for you at > this point. Thanks, will check it out. > 6) The command grep "W" .XCompose | tr $'\xc2\xa0' \! returns > grep "W" .XCompose | tr $'\xc2\xa0' \! > The two hex bytes c2 a0 are the UTF-8 encoding of a non-breaking space, > so it *does* seem like you're chasing after non-breaking spaces for > some reason.... I was trying to find if NBSP are getting added in my .XCompose file > If that's truly your goal, you might also want to pursue configuring > your text editor to show them to you. There are various ways to do > that, depending on which text editor you use. I am using Kate. How can I accomplish that in Kate? > (I don't even know whether you're in a UTF-8 encoding, though, so > who knows whether those are even the correct bytes for an NBSP in> > your locale. You're better off using \u00A0 instead.) No, I don't want to use them. Just wanted to know if they were creeping into my file. Thanks, ajith
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-07-13 20:40 +0200 |
| Message-ID | <AsbwS-3j7-3@gated-at.bofh.it> |
| In reply to | #224757 |
On Mon, Jul 13, 2020 at 06:24:58PM +0000, Ajith R wrote: > I was trying to find if NBSP are getting added in my .XCompose file > > I am using Kate. How can I accomplish that in Kate? I googled <show non-breaking spaces in kate editor>. The first result didn't talk about them at all. The second result was to a PDF which is apparently their official documentation. <https://docs.kde.org/trunk5/en/applications/katepart/katepart.pdf>. In it, there is a brief mention of some option you can toggle called "Show Non-Printable Spaces", whose description is "Show/hide bounding box around non-printable spaces." I have no idea what they consider to be a "non-printable space". You could try it. > > (I don't even know whether you're in a UTF-8 encoding, though, so > > who knows whether those are even the correct bytes for an NBSP in> > > your locale. You're better off using \u00A0 instead.) > > No, I don't want to use them. Just wanted to know if they were creeping into my file. I meant use in your bash + grep command. The earlier attempts to use $'\x00A0' or $'\x00\xA0' were not correct.
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-13 20:50 +0200 |
| Message-ID | <AsbGx-3mx-1@gated-at.bofh.it> |
| In reply to | #224759 |
Hi Greg, > In it, there is a brief mention of some option you can toggle called > "Show Non-Printable Spaces", whose description is "Show/hide bounding > box around non-printable spaces." Yes, though not very obvious, Kate does show the non breaking sapces with an open box after selecting the option. Thanks, ajith
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-07-13 21:50 +0200 |
| Message-ID | <AscCB-3Vx-9@gated-at.bofh.it> |
| In reply to | #224760 |
On Mon 13 Jul 2020 at 18:45:45 (+0000), Ajith R wrote: > Hi Greg, > > > In it, there is a brief mention of some option you can toggle called > > "Show Non-Printable Spaces", whose description is "Show/hide bounding > > box around non-printable spaces." > > Yes, though not very obvious, Kate does show the non breaking sapces with an open box after selecting the option. And I assume they're not in the files that you wrote from scratch, like .XCompose. Would that be right? Kate appears to be a normal text editor. The third sentence of its official description (https://kate-editor.org/) says "Choose it for […], editing configuration files". It doesn't seem to me to be like writing text files in, say, Word (a word processor). It would be nice not to get sidetracked by this, and to find out whether the way that the Indic Script input system (InScript) works is compatible with the composition of characters, which is the purpose of .XCompose. (I'm assuming that linux tries to give the >1billion people concerned an InScript system that's compatible with other platforms). Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 1 of 5 [1] 2 3 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web