I fail to see why should one touch
/etc/login.conf for the aforementioned issues whereas
~/.login_conf sounds way better an option to handle it, at least to me.
lebarondemerde My
~/.login_conf:
Code:
me:\
:charset=UTF-8:\
:lang=en_US.UTF-8:
And have no issues displaying accents or 'ç'. It'll work as long as UTF-8 is being applied within environment, regardless of
LANG remaining
en_US.UTF-8. Also, I wonder
LC_COLLATE would still require being changed if using
en_US.UTF-8 as noted, but
cpm@ (or anyone well-acquainted with said detailing as well) should provide an actual answer to this matter. I shall add to everything I've pointed so far that doing so works fine and all the same on either Bourne shell (sh), (t)csh, and even bash once installed.
As a reminder: for the procedure just described, don't forget to run
# cap_mkdb .login_conf in your user's home dir then reboot so to get the desired results.
A
keymap="br" line in
/etc/rc.conf is all I need for my ABNT2 keyboard to work. Make sure to use
vt(4) instead of
sc(4) though.
I'm using twm (nobody uses it, but me) and there are two kind of terminal: uxterm and xterm.
Probably the former was compiled and configured to works with wide chars, but both are work well with accented letters.
After read this thread I could configure both my keyboard and screen fonts.
But some gotchas persist:
- when I type accented letters in console, using sh, it log me out, but "del" key works
- doing same typing, using csh, it works, but "del", don't
Please confirm deletion through both backspace and del works fine with (u)xterm along with accents as noted in my first highlight. As for the other one, I'll read it as in "system console", and with that I mean basically no X nor anything alike, just plain old
vt(4) in a ttyv.
Should both be confirmed, twm would be unrelated to the problem at hand. As for what
is related, not only "sh" and "(t)csh" differ as noted (by
lebarondemerde), they also would require their own fix in their own ways for each issue presented. For example, proceeding as told by could put (t)csh to work, but won't prevent your Bourne shell ("sh") to log you out or whatever it does wrong if trying to enter accented letters. For
that to be fixed as well, a second procedure somewhat resembling the one described for
~/.(t)cshrc would
normally be required.
Noted the bold part in the end? Accented letters are not the same as deleting forward/backwards or using any other macro of sorts, which would then require an
~/.inputrc file, or changes in, say,
.shrc, in order to workaround. Rather, this problem with accented letters can be solved through adequate setting. You'll need your keyboard properly set so keycodes are sent as meant to instead of re-binding garbage as done in the former approach related to macros and used to fix deletion in (t)csh. You'll also make sure to use UTF-8 through the proceedings I first described regarding
~/.login_conf then
# cap_mkdb and so on.
