11 Feb
2022
11 Feb
'22
12:40 a.m.
Greetings!
I may have fumbled and hit two keys or something but now I don´t have
a regular apostrophe (I get ´ instead) or regular double quotes (I get
¨ instead).
I´m on TDE on Q4OS Buster. I´m sure someone has a quick fix at
hand....
Thanks in advance!
--
Felmon
Verbum sat sapienti.
11 Feb
11 Feb
1:51 a.m.
On Thursday 10 February 2022 06:40:23 pm Felmon Davis wrote:
Greetings!
I may have fumbled and hit two keys or something but now I don´t have
a regular apostrophe (I get ´ instead) or regular double quotes (I get
¨ instead).
I´m on TDE on Q4OS Buster. I´m sure someone has a quick fix at
hand....
Check your alt switch(s) or function lock buttons... You might have
to "Google it on Bing" your keyboard if it's a hidden switch though...
8:41 p.m.
On Thu, 10 Feb 2022, Michael wrote:
On Thursday 10 February 2022 06:40:23 pm Felmon Davis
wrote:
I will check this out but I now have several other issues, not sure of
the relation. I´ve lost umlauts though I get accented vowels such as
á.
so far playing with dpkg -reconfigure keyboard-configuration and dpkg
--reconfigure console-setup doesn´t help, nor anything in ´Regional
and Accessibility´.
I thought I had those values set to the state they have always been in
but I can´t get umlauts and get right shift as compose key. (I´m happy
to have some other key set as compose key.)
I am using an American keyboard set to ´Generic 105-key PC (intl)´.
Layout is ´English (US) us, intl, thus:
setxkbmap -model pc105 -layout us -variant intl
Compose key is now set to ´Menu´ but it´s ignored; right Alt generates
ß and the á, ó letters.
before whatever it is that happened I could effortlessly generate
Umlauts (right shift + double-quote + vowel).
I probably have set something wrong, some configuration issue, but no
luck or insight yet.
it´s an ASUS laptop, pretty old: UX330U.
I kinda need Umlauts.
I´ll check if something got locked at hardware level, googling on bing
as you say.
f.
--
Felmon Davis
Verbum sat sapienti.
Greetings!
I may have fumbled and hit two keys or something but now I don´t have
a regular apostrophe (I get ´ instead) or regular double quotes (I get
¨ instead).
I´m on TDE on Q4OS Buster. I´m sure someone has a quick fix at
hand....
Check your alt switch(s) or function lock buttons... You might have
to "Google it on Bing" your keyboard if it's a hidden switch though...
9:17 p.m.
On Friday 11 February 2022 12:41:12 Felmon Davis wrote:
On Thu, 10 Feb 2022, Michael wrote:
You could use a diaresis instead. (Just kidding ...)
On Thursday 10 February 2022 06:40:23 pm Felmon
Davis wrote:
I will check this out but I now have several other issues, not sure of
the relation. I´ve lost umlauts though I get accented vowels such as
á.
so far playing with dpkg -reconfigure keyboard-configuration and dpkg
--reconfigure console-setup doesn´t help, nor anything in ´Regional
and Accessibility´.
I thought I had those values set to the state they have always been in
but I can´t get umlauts and get right shift as compose key. (I´m happy
to have some other key set as compose key.)
I am using an American keyboard set to ´Generic 105-key PC (intl)´.
Layout is ´English (US) us, intl, thus:
setxkbmap -model pc105 -layout us -variant intl
Compose key is now set to ´Menu´ but it´s ignored; right Alt generates
ß and the á, ó letters.
before whatever it is that happened I could effortlessly generate
Umlauts (right shift + double-quote + vowel).
I probably have set something wrong, some configuration issue, but no
luck or insight yet.
it´s an ASUS laptop, pretty old: UX330U.
I kinda need Umlauts. Greetings!
I may have fumbled and hit two keys or something but now I don´t have
a regular apostrophe (I get ´ instead) or regular double quotes (I get
¨ instead).
I´m on TDE on Q4OS Buster. I´m sure someone has a quick fix at
hand....
Check your alt switch(s) or function lock buttons... You might have
to "Google it on Bing" your keyboard if it's a hidden switch though...
I´ll check if something got locked at hardware level, googling on bing
as you say.
f.
I expect that you have already explored the keyboard mapping options in
Trinity Control Center: TCC / Regional & Accessibility / Keyboard Layout /
Xkb Options.
Somewhere buried in your system, there must be a configuration file, a text
file, probably ending in -rc, and if so, there is probably also a recent
backup of that file, from before mistakes were made, and whoever or whatever
messed it up.
Maybe it is kept in /opt/trinity/, maybe it is somewhere in /usr/X, maybe it
is in /home/~/.trinity, but there ought to be a record of your previous
settings.
Bill
9:59 p.m.
On Fri, 11 Feb 2022, William Morder via tde-users wrote:
yes, still am.
I am using an American keyboard set to ´Generic
105-key PC (intl)´.
Layout is ´English (US) us, intl, thus:
setxkbmap -model pc105 -layout us -variant intl
Compose key is now set to ´Menu´ but it´s ignored; right Alt generates
ß and the á, ó letters.
before whatever it is that happened I could effortlessly generate
Umlauts (right shift + double-quote + vowel).
I probably have set something wrong, some configuration issue, but no
luck or insight yet.
it´s an ASUS laptop, pretty old: UX330U.
I kinda need Umlauts.
I expect that you have already explored the keyboard mapping options in
Trinity Control Center: TCC / Regional & Accessibility / Keyboard Layout /
Xkb Options. Somewhere buried in your system, there must be a
configuration file, a text
file, probably ending in -rc, and if so, there is probably also a recent
backup of that file, from before mistakes were made, and whoever or whatever
messed it up.
hard to search with double quotes and single quotes. even if I
ctrl+alt+fn1 out to a full screen terminal, I can´t get proper
quote-marks, thus cannot write proper command lines.
Maybe it is kept in /opt/trinity/, maybe it is
somewhere in /usr/X, maybe it
is in /home/~/.trinity, but there ought to be a record of your previous
settings.
will search for the proper config files. got another laptop here, may
have to switch to it as I´m on the road and lack time also for
tinkering.
diaeresis or Umlaut - my kingdom for a glyph!
f.
--
Felmon Davis
Verbum sat sapienti.
10:11 p.m.
On 2/11/22 1:59 PM, Felmon Davis wrote:
hard to search with double quotes and single quotes.
even if I
ctrl+alt+fn1 out to a full screen terminal, I can´t get proper
quote-marks, thus cannot write proper command lines.
Find whatever symbol/character you need somewhere else -- KCharSelect, web
page, email, text file, etc. Then copy/paste where you need it. A bit
cumbersome, but gets the job done in a pinch.
--
PGP key: http://homestead-products.com/pubkey.htm
12 Feb
12 Feb
12:32 a.m.
On Fri, 11 Feb 2022, Dan Youngquist wrote:
On 2/11/22 1:59 PM, Felmon Davis wrote:
indeed. umlauts, ok, you use double vowels so umlaut ´a´ becomes ´ae´.
got that stoopid single quote for writing prose. alright, copy and
paste double-quotes. life, and writing, goes on.
I would hate to reinstall though I should upgrade to Bullseye. want
something more targeted.
you have a problem with keyboard layout and chars from a couple of
languages but you don´t want to reinstall the whole chimichanga - what
subsystem(s) would you reinstall?
a couple of deft ´apt installs´ would get me back in shape.
maybe best to upgrade now. maybe that´ s what the daemons of the
binary world are telling me. has to wait a bit though.
I wish I knew what happened. haven´t done my keyboard lock research
yet as advised by Michael. I´ll copy and paste to search on the
commandline for files ending in ´.rc´. distracted by other things at
the moment.
f.
--
Felmon Davis
Verbum sat sapienti.
hard to search with double quotes and single
quotes. even if I
ctrl+alt+fn1 out to a full screen terminal, I can´t get proper
quote-marks, thus cannot write proper command lines.
Find whatever symbol/character you need somewhere else -- KCharSelect, web
page, email, text file, etc. Then copy/paste where you need it. A bit
cumbersome, but gets the job done in a pinch. 
11 Feb
11 Feb
10:17 p.m.
On Fri February 11 2022 13:59:47 Felmon Davis wrote:
hard to search with double quotes and single quotes.
even if I
ctrl+alt+fn1 out to a full screen terminal, I can´t get proper
quote-marks, thus cannot write proper command lines.
Here are some quotes you can copy/paste: " ' `
You could possibly also get any characters you need to fix this
from T-Menu / Utilities / Character Selector.
--Mike
12 Feb
12 Feb
2:31 a.m.
I kinda need Umlauts.
I expect that you have already explored the keyboard mapping options in
Trinity Control Center: TCC / Regional & Accessibility / Keyboard Layout
/ Xkb Options. > Maybe it is kept in }...] /home/~/.trinity, but
there ought to be a record
> of your previous settings.
It's probably in your home folder, in that .trinity folder, because the other
places ought to get changed on a new installation.
I did a little searching myself, but I don't have the same need for umlauts in
writing mostly English here, so I don't have the same configuration, which
makes it hard for me to search for what doesn't exist in my own system.
Looking in this folder:
/home/~/.trinity/share/config/
most likely candidates seem to be:
kxkbrc
kkbswitchrc
khotkeysrc
kglobalshortcutsrc
kdeglobals
Some of these, on my system, have no backup versions; others have several
backups from when things got changed.
will search for the proper config files. got another laptop here, may
have to switch to it as I´m on the road and lack time also for
tinkering.
If you have Trinity installed on the laptop, then a brute force option would
be just to copy your configuration files to the other system. But that seems
too much like using a hammer to make minor fine-tuning adjustments; you might
only mess things up more.
However, if indeed you have Trinity installed on both machines, and assuming
that your umlauts work just fine on the other machine -- well, now you have
something for comparison. You might be able to find it by comparing likely
config files.
diaeresis or Umlaut - my kingdom for a glyph!
Yes, I see that I made a typo, too, as my old eyes seem to miss little things
like letters. I don't know why I make more mistakes with email than I do with
other kinds of text. Oh well.
That email was already sent when I noticed my mistake, so there was no
correcting it. Nothing worse than a pedant who gets it wrong!
f.
We ought to have asked this question at the start, but better late than never:
Do you experience this problem system-wide, or only with certain programs?
e.g., your usual keystrokes work okay to create umlauts in text files, etc.,
but not in your Office program? What comes through in your email is messy,
but that could be on my end. (I get a lot of � characters in your emails;
and just by pasting that in, my keyboard behaves now like I am typing in
Hebrew, right to left.)
Happy hunting!
Bill
11:42 a.m.
On Fri, 11 Feb 2022, William Morder via tde-users wrote:
yes, still am.
> Somewhere buried in your system, there must be a configuration file, a
> text file, probably ending in -rc, and if so, there is probably also a
> recent backup of that file, from before mistakes were made, and whoever
> or whatever messed it up.
thank you for doing my research for me! this is very helpful as also
the tips below:
I kinda need Umlauts.
I expect that you have already explored the keyboard mapping options in
Trinity Control Center: TCC / Regional & Accessibility / Keyboard Layout
/ Xkb Options. > Maybe it is kept in }...] /home/~/.trinity,
but there ought to be a record
> of your previous settings.
It's probably in your home folder, in that .trinity folder, because the other
places ought to get changed on a new installation.
I did a little searching myself, but I don't have the same need for umlauts in
writing mostly English here, so I don't have the same configuration, which
makes it hard for me to search for what doesn't exist in my own system.
Looking in this folder:
/home/~/.trinity/share/config/
most likely candidates seem to be:
kxkbrc
kkbswitchrc
khotkeysrc
kglobalshortcutsrc
kdeglobals
Some of these, on my system, have no backup versions; others have several
backups from when things got changed.
I think I might tinker and pull over just those config files. the
other laptop is running TDE.
will search for the proper config files. got another laptop here, may
have to switch to it as I´m on the road and lack time also for
tinkering.
If you have Trinity installed on the laptop, then a brute force option would
be just to copy your configuration files to the other system. But that seems
too much like using a hammer to make minor fine-tuning adjustments; you might
only mess things up more. We ought to have asked this question at the start, but
better late than never:
Do you experience this problem system-wide, or only with certain programs?
e.g., your usual keystrokes work okay to create umlauts in text files, etc.,
but not in your Office program? What comes through in your email is messy,
but that could be on my end. (I get a lot of ? characters in your emails;
and just by pasting that in, my keyboard behaves now like I am typing in
Hebrew, right to left.)
I thought I had checked this out but realize I had only FN-ed to a
full-screen terminal window. there the problem is present too.
but now in OpenOffice I see I have the double quotes. when I do a
single quote it first quickly produces ´ but then becomes a regular
single quote. the ´compose key´ produces á, ú, etc, no Umlauts.
there is clearly something going on in the terminals. I use Console
also for these mails (using Alpine); the accented vowels show up in
Gmail (under Brave Browser). I am not sure what the full-screen
terminal is called.
Happy hunting!
soon. gotta do some work right now though!
this has been a help though as it helps localized problems.
but I think I´ll just pull over the configs from the other laptop -
two laptops are on my desk, an Asus (problem child) and an Acer which
I will use as source of configs.
f.
--
Felmon Davis
Verbum sat sapienti.
11:53 a.m.
On Saturday 12 February 2022 03:42:45 Felmon Davis wrote:
Make sure that you back up whatever are your current config files!
Elementary, of course, but that is what we always forget ... especially if we
are in haste to get back to our more important work. These computer things
are a nuisance. I am gradually returning to writing out longhand for most
stuff, and only then transferring to digital files.
Bill
On Fri, 11 Feb 2022, William Morder via tde-users
wrote:
>>>> I kinda need Umlauts.
Looking in
this folder:
/home/~/.trinity/share/config/
most likely candidates seem to be:
kxkbrc
kkbswitchrc
khotkeysrc
kglobalshortcutsrc
kdeglobals
thank you for doing my research for me! this is very helpful as also
the tips below:
Some of these, on my system, have no backup
versions; others have several
backups from when things got changed.
I think I might tinker and pull over just those config files. the
other laptop is running TDE.
will search for the proper config files. got
another laptop here, may
have to switch to it as I´m on the road and lack time also for
tinkering.
If you have Trinity installed on the laptop, then a brute force option
would be just to copy your configuration files to the other system. But
that seems too much like using a hammer to make minor fine-tuning
adjustments; you might only mess things up more. We ought to have asked this question at the
start, but better late than
never: Do you experience this problem system-wide, or only with certain
programs? e.g., your usual keystrokes work okay to create umlauts in text
files, etc., but not in your Office program? What comes through in your
email is messy, but that could be on my end. (I get a lot of ? characters
in your emails; and just by pasting that in, my keyboard behaves now
like I am typing in Hebrew, right to left.)
I thought I had checked this out but realize I had only FN-ed to a
full-screen terminal window. there the problem is present too.
but now in OpenOffice I see I have the double quotes. when I do a
single quote it first quickly produces ´ but then becomes a regular
single quote. the ´compose key´ produces á, ú, etc, no Umlauts.
there is clearly something going on in the terminals. I use Console
also for these mails (using Alpine); the accented vowels show up in
Gmail (under Brave Browser). I am not sure what the full-screen
terminal is called.
Happy hunting!
soon. gotta do some work right now though!
this has been a help though as it helps localized problems.
but I think I´ll just pull over the configs from the other laptop -
two laptops are on my desk, an Asus (problem child) and an Acer which
I will use as source of configs.
f.
10 Apr
10 Apr
10:17 p.m.
New subject: Umlauts fixed! Was: lost double quote mark
On Sat, Feb 12, 2022 at 12:54 PM William Morder via tde-users <
users(a)trinitydesktop.org> wrote:
On Saturday 12 February 2022 03:42:45 Felmon Davis wrote:
I wrote the above in February and got some tips about restoring Umlauts (or
as I am proud to say now Umläute) but to no avail. (But thanks, Bill, and
others!)
I tried through the Trinity Control Center -- after all, things had worked
that way from the first installation -- but no joy (using a Q4os blend of
TDE).
Frustrating. Plus I had problems with double quotes and single quotes but
solved them, not sure how, mainly restoring a setting that worked before.
But months of 'ae' and 'ue' and 'oe'! dispiriting.
Decided to dive under the gui. edited /usr/share/X11/xkb/symbols/us and
dumped some key codes (diaeresis markers added to a, u and o), restarted
the session and after a couple of mistrials and adjustments the Umläute are
back!
I would like to change the compose key but haven't found the incantation
yet.
Anyway, the trick was to dump the following into
/usr/share/X11/xkb/symbols/us:
key <AD07> { [ u, U, udiaeresis, Udiaeresis ] };
key <AD09> { [ o, O, odiaeresis, Odiaeresis ] };
key <AC01> { [ a, A, adiaeresis, Adiaeresis ] };
key <AC02> { [ s, S, U00DF, NoSymbol ] };
how does the 'us' file determine the compose key, or is that set through
the Control Center? it must be possible to set it here instead.
in my case the 'us' file set for:
xkb_symbols "basic" {
name[Group1] = "English (US)";
....
I have not played with .xmodmap.
Felmon
On Fri, 11 Feb 2022, William Morder via tde-users
wrote:
>>>> I kinda need Umlauts.
> > Looking in this folder:
> > /home/~/.trinity/share/config/
> > most likely candidates seem to be:
> >
> > kxkbrc
> > kkbswitchrc
> > khotkeysrc
> > kglobalshortcutsrc
> > kdeglobals
>
> thank you for doing my research for me! this is very helpful as also
> [...]
11 Apr
11 Apr
4:09 a.m.
New subject: Umlauts fixed! Was: lost double quote mark
On Sunday 10 April 2022 15:17:49 nemo wrote:
users(a)trinitydesktop.org> wrote:
So, let me get this straight ...
What started as a joke (i.e., use a diaeresis instead of an umlaut) actually
turned out to be correct? How weird is that?!
On Saturday 12 February 2022 03:42:45 Felmon
Davis wrote:
> >>>> I kinda need Umlauts.
I wrote the above in February and got some tips about restoring Umlauts (or
as I am proud to say now Umläute) but to no avail. (But thanks, Bill, and
others!)
I tried through the Trinity Control Center -- after all, things had worked
that way from the first installation -- but no joy (using a Q4os blend of
TDE).
Frustrating. Plus I had problems with double quotes and single quotes but
solved them, not sure how, mainly restoring a setting that worked before.
But months of 'ae' and 'ue' and 'oe'! dispiriting.
Decided to dive under the gui. edited /usr/share/X11/xkb/symbols/us and
dumped some key codes (diaeresis markers added to a, u and o), restarted
the session and after a couple of mistrials and adjustments the Umläute are
back!
I would like to change the compose key but haven't found the incantation
yet.
Anyway, the trick was to dump the following into
/usr/share/X11/xkb/symbols/us:
key <AD07> { [ u, U, udiaeresis, Udiaeresis ] };
key <AD09> { [ o, O, odiaeresis, Odiaeresis ] };
key <AC01> { [ a, A, adiaeresis, Adiaeresis ] };
key <AC02> { [ s, S, U00DF, NoSymbol ] };
how does the 'us' file determine the compose
key, or is that set through
the Control Center? it must be possible to set it here instead.
us, meaning US for locale?
in my case the 'us' file set for:
xkb_symbols "basic" {
name[Group1] = "English (US)";
....
I have not played with .xmodmap.
Felmon
Didn't think of xkb, but that makes sense.
The problem with single and double quotes has me stumped, but I don't use your
keyboard setup.
I doubt that this could be an issue; however, I did have some problems getting
Q4OS to work as I wanted. In particular, as I recall, I could not set my
password using "special characters" -- although I imagine it was possible to
change that later, if I had got more into it. It is one of those kinds of
snags that happen more often with preconfigured stuff, such as Q4OS. I didn't
stay long with Q4OS, but went straight for Debian and then Devuan.
Just throwing it out there for consideration.
Bill
1:02 p.m.
New subject: Umlauts fixed! Was: lost double quote mark
On Sun, 10 Apr 2022, William Morder via tde-users wrote:
the filename is not capitalized
/usr/share/X11/xkb/symbols/us
I fixed that.
On Sunday 10 April 2022 15:17:49 nemo wrote:
even you can't believe how praeternaturally insightful you are!
Anyway, the trick was to dump the following into
/usr/share/X11/xkb/symbols/us:
key <AD07> { [ u, U, udiaeresis, Udiaeresis ] };
key <AD09> { [ o, O, odiaeresis, Odiaeresis ] };
key <AC01> { [ a, A, adiaeresis, Adiaeresis ] };
key <AC02> { [ s, S, U00DF, NoSymbol ] };
So, let me get this straight ...
What started as a joke (i.e., use a diaeresis instead of an umlaut) actually
turned out to be correct? How weird is that?! how does the
'us' file determine the compose key, or is that set through
the Control Center? it must be possible to set it here instead.
us, meaning US for locale?
in my case the 'us' file set for:
xkb_symbols "basic" {
name[Group1] = "English (US)";
....
I have not played with .xmodmap.
Felmon
Didn't think of xkb, but that makes sense.
The problem with single and double quotes has me stumped, but I don't use your
keyboard setup. I doubt that this could be an issue; however, I did
have some problems getting
Q4OS to work as I wanted. In particular, as I recall, I could not set my
password using "special characters" -- although I imagine it was possible to
change that later, if I had got more into it. It is one of those kinds of
snags that happen more often with preconfigured stuff, such as Q4OS. I didn't
stay long with Q4OS, but went straight for Debian and then Devuan.
Just throwing it out there for consideration.
spent yrs with Devuan, no problem. I think I threw Q4OS on for no
particular reason and never bothered to change it nor do any ambitious
configuration - no incentive given my usage.
guess the main problems of configuration I've had are with printing
and with, well, printing. works now. then suddenly a month or so ago,
the Umlaut issue. also tricking my way past a hotel portal.
I have MX on another machine. too 'busy' for me though configures
itself quite handily.
thank you for the help and encouragement!
f.
--
Davis
Verbum sat sapienti.
4:13 p.m.
New subject: Umlauts fixed! Was: lost double quote mark
On Monday 11 April 2022 06:02:22 Felmon Davis wrote:
It's time I take responsibility. I realize that I must be the one of whom the
prophets spoke.
Bill
So, let me get this straight ...
What started as a joke (i.e., use a diaeresis instead of an umlaut)
actually turned out to be correct? How weird is that?!
even you can't believe how praeternaturally insightful you are!
5:07 a.m.
New subject: Umlauts fixed! Was: lost double quote mark
Hi Felmon,
Sorry, I haven't followed the entire thread. This is how I solved the
problem with Umlaute. For the current running session just type in a
terminal:
setxkbmap -option compose:lwin
This maps the left winkey to "compose". If you want the right control key
to be compose, then you can set:
setxkbmap -option compose:rctrl
or the menu key:
setxkbmap -option compose:menu
You can also combine them:
setxkbmap -option compose:lwin -option compose:menu
You can set this globally by adding the commands above to the login
profiles /etc/csh.login.local and/or /etc/profile.local.
More information is here:
https://wiki.archlinux.org/title/Xorg/Keyboard_configuration
I am also not entirely sure that the plural of Umlaut is Umläute.
According to the Duden I have, the plural of "Laut" is "Laute"
(without
Umlaut). But I may be mistaken.
Gianluca
On Mon, 11 Apr 2022, nemo wrote:
On Sat, Feb 12, 2022 at 12:54 PM William Morder via
tde-users <users(a)trinitydesktop.org>
wrote:
On Saturday 12 February 2022 03:42:45 Felmon Davis wrote:
-----------------------------------------------------
Gianluca Interlandi, PhD gianluca(a)u.washington.edu
+1 (206) 685 4435
http://gianluca.today/
Department of Bioengineering
University of Washington, Seattle WA U.S.A.
-----------------------------------------------------
On Fri, 11 Feb 2022, William Morder via tde-users
wrote:
>>>> I kinda need Umlauts.
I wrote the above in February and got some tips about restoring Umlauts (or as I am
proud
to say now Umläute) but to no avail. (But thanks, Bill, and others!)
I tried through the Trinity Control Center -- after all, things had worked that way from
the first installation -- but no joy (using a Q4os blend of TDE).
Frustrating. Plus I had problems with double quotes and single quotes but solved them,
not
sure how, mainly restoring a setting that worked before.
But months of 'ae' and 'ue' and 'oe'! dispiriting.
Decided to dive under the gui. edited /usr/share/X11/xkb/symbols/us and dumped some key
codes (diaeresis markers added to a, u and o), restarted the session and after a couple
of
mistrials and adjustments the Umläute are back!
I would like to change the compose key but haven't found the incantation yet.
Anyway, the trick was to dump the following into /usr/share/X11/xkb/symbols/us:
key <AD07> { [ u, U, udiaeresis, Udiaeresis ] };
key <AD09> { [ o, O, odiaeresis, Odiaeresis ] };
key <AC01> { [ a, A, adiaeresis, Adiaeresis ] };
key <AC02> { [ s, S, U00DF, NoSymbol ] };
how does the 'us' file determine the compose key, or is that set through the
Control
Center? it must be possible to set it here instead.
in my case the 'us' file set for:
xkb_symbols "basic" {
name[Group1] = "English (US)";
....
I have not played with .xmodmap.
Felmon
Looking
in this folder:
/home/~/.trinity/share/config/
most likely candidates seem to be:
kxkbrc
kkbswitchrc
khotkeysrc
kglobalshortcutsrc
kdeglobals
thank you for doing my research for me! this is very helpful as also
[...]
11:40 a.m.
New subject: Umlauts fixed! Was: lost double quote mark
On Sun, 10 Apr 2022, Gianluca Interlandi wrote:
You can also combine them:
setxkbmap -option compose:lwin -option compose:menu
You can set this globally by adding the commands above to the login profiles
/etc/csh.login.local and/or /etc/profile.local.
I'll try these the next time. good information - the information is on
the webs but often hard to work out from the context.
before the catastrophe, I used a combination 'shift key' + 'double
quote' as dead-key. not sure how that got encoded, I must have set it
up.
More information is here:
https://wiki.archlinux.org/title/Xorg/Keyboard_configuration
I am also not entirely sure that the plural of Umlaut is Umläute. According
to the Duden I have, the plural of "Laut" is "Laute" (without
Umlaut). But I
may be mistaken.
No, I think you are right!
fjd
On Mon, 11 Apr 2022, nemo wrote:
--
Davis
Verbum sat sapienti.
On Sat, Feb 12, 2022 at 12:54 PM William Morder
via tde-users
<users(a)trinitydesktop.org>
wrote:
On Saturday 12 February 2022 03:42:45 Felmon Davis wrote:
also
-----------------------------------------------------
Gianluca Interlandi, PhD gianluca(a)u.washington.edu
+1 (206) 685 4435
http://gianluca.today/
Department of Bioengineering
University of Washington, Seattle WA U.S.A.
----------------------------------------------------- On Fri, 11 Feb 2022, William Morder via tde-users
wrote:
>>>> I kinda need Umlauts.
I wrote the above in February and got some tips about restoring Umlauts (or
as I am proud
to say now Umläute) but to no avail. (But thanks, Bill, and others!)
I tried through the Trinity Control Center -- after all, things had worked
that way from
the first installation -- but no joy (using a Q4os blend of TDE).
Frustrating. Plus I had problems with double quotes and single quotes but
solved them, not
sure how, mainly restoring a setting that worked before.
But months of 'ae' and 'ue' and 'oe'! dispiriting.
Decided to dive under the gui. edited /usr/share/X11/xkb/symbols/us and
dumped some key
codes (diaeresis markers added to a, u and o), restarted the session and
after a couple of
mistrials and adjustments the Umläute are back!
I would like to change the compose key but haven't found the incantation
yet.
Anyway, the trick was to dump the following into
/usr/share/X11/xkb/symbols/us:
key <AD07> { [ u, U, udiaeresis, Udiaeresis ] };
key <AD09> { [ o, O, odiaeresis, Odiaeresis ] };
key <AC01> { [ a, A, adiaeresis, Adiaeresis ] };
key <AC02> { [ s, S, U00DF, NoSymbol ] };
how does the 'us' file determine the compose key, or is that set through
the Control
Center? it must be possible to set it here instead.
in my case the 'us' file set for:
xkb_symbols "basic" {
name[Group1] = "English (US)";
....
I have not played with .xmodmap.
Felmon
Looking
in this folder:
/home/~/.trinity/share/config/
most likely candidates seem to be:
kxkbrc
kkbswitchrc
khotkeysrc
kglobalshortcutsrc
kdeglobals
thank you for doing my research for me! this is very helpful as [...]
27 Apr
27 Apr
12:15 p.m.
New subject: Umlauts fixed! Was: lost double quote mark
Am Montag, 11. April 2022 schrieb Felmon Davis:
Confirmed. (Disclaimer: I'm a native German :-)
Stefan
I am also not
entirely sure that the plural of Umlaut is Umläute.
According to the Duden I have, the plural of "Laut" is "Laute"
(without Umlaut). But I may be mistaken.
No, I think you are right!
30 Apr
30 Apr
11:27 p.m.
New subject: Umlauts fixed! Was: lost double quote mark
On Wed, 27 Apr 2022, Stefan Krusche wrote:
Am Montag, 11. April 2022 schrieb Felmon Davis:
Confirmed. (Disclaimer: I'm a native German :-)
Stefan
Danke. I know now.
--
Davis
Verbum sat sapienti.
I am also
not entirely sure that the plural of Umlaut is Umläute.
According to the Duden I have, the plural of "Laut" is "Laute"
(without Umlaut). But I may be mistaken.
No, I think you are right!
12 Feb
12 Feb
3 a.m.
On Fri February 11 2022 13:59:47 Felmon Davis wrote:
On Fri, 11 Feb 2022, William Morder via tde-users
wrote:
>> I probably have set something wrong, some configuration issue, but no
>> luck or insight yet.
If you boot into single user mode do you still have the problem?
https://help.pebblehost.com/en/article/how-to-boot-into-single-user-mode-de…
--Mike
11:43 a.m.
On Fri, 11 Feb 2022, Mike Bird wrote:
On Fri February 11 2022 13:59:47 Felmon Davis wrote:
be patient with me and I´ll try it out after I have some of this work
done.
f.
--
Felmon Davis
Verbum sat sapienti.
On Fri, 11 Feb 2022, William Morder via tde-users
wrote:
>> I probably have set something wrong, some configuration issue, but no
>> luck or insight yet.
If you boot into single user mode do you still have the problem?
https://help.pebblehost.com/en/article/how-to-boot-into-single-user-mode-de…
--Mike
727
days inactive
805
days old
20 comments
8 participants
participants (8)
-
Dan Youngquist -
Felmon Davis -
Gianluca Interlandi -
Michael -
Mike Bird -
nemo
-
Stefan Krusche -
William Morder