#943 closed PBI Packaging Bug (3rdpartybug)

Can not change language encoding to Japanese in Konsole/KDE4 PCBSD9.2

Reported by: NaomasaMaruyama Owned by: kenmoore
Priority: critical Milestone:
Component: Misc Version: 9.2-RELEASE
Keywords: Language encoding Konsole Cc: trac-bugs@…

Description

Changing language encoding to Japanese in Konsole/KDE4 on PCBSD9.2(11-25-2013-x64) does not work. I see the following messages in .xesssion-error:

konsole(26708) KCodecAction::mibForName: Invalid codec name: "&EUC-JP"
konsole(26708) KCodecAction::mibForName: Invalid codec name: "&sjis"
konsole(26708) KCodecAction::mibForName: Invalid codec name: "&jis7"

This was not the case on PCBSD9.1. For Chinese and Korean, same thing happens:

konsole(26708) KCodecAction::mibForName: Invalid codec name: "&EUC-KR"
konsole(26708) KCodecAction::mibForName: Invalid codec name: "&Big5"
konsole(26708) KCodecAction::mibForName: Invalid codec name: "&GB18030

For other languages, similar thing seems NOT to happen. I sincerely hope that the PCBSD team does NOT have hostile thinking to these three countries.

Change History (5)

comment:1 Changed 15 months ago by kenmoore

  • Resolution set to deferred
  • Status changed from new to closed

Please re-test with the latest PC-BSD 10.0 image.
There has been a significant number of fixes related to keyboard/language localization through the installer and login manager that might fix the issues you are experiencing.

comment:2 Changed 15 months ago by NaomasaMaruyama

  • Resolution deferred deleted
  • Status changed from closed to reopened

This flaw still exists in PC-BSD 10.0(PCBSD10.0-RELEASE-p4-01-17-2014-x64-DVD-USB.iso).

comment:3 Changed 15 months ago by kenmoore

After logging in to KDE, could you run "env | grep LANG" to see if your localization code is set properly?
I am hearing that the login manager settings for localization/keyboard settings are working perfectly from others, so I am wondering if there is a KDE startup service that is overriding those system settings when you log in.

For keyboard layout/settings, I do have confirmation that you need to de-activate the "Keyboard" startup service in the KDE settings in order to use the system keyboard layout (which is properly set by the login manager).

comment:4 Changed 15 months ago by kenmoore

  • Owner set to kenmoore
  • Status changed from reopened to new

OK, I have been doing some checking into this and I think the Konsole problem is specifically a KDE issue.

When you have a Konsole open, go to View->Set Encoding->Japanese and pick one. If you do it again, it is still set to the default UTF-8.

UTF-8 is the default encoding from the login manager (as you can see from the LANG environment variable: ja_JA.UTF-8), so this might also be related to the IBUS issue in ticket #950, since IBUS should help change the system keyboard settings around as necessary.

I am a bit unfamiliar with using different encodings, so perhaps you could help me out. Does it normally affect the text language, or is it a keyboard input modification? That will help me narrow down where the issue(s) may be.

comment:5 Changed 15 months ago by kenmoore

  • Resolution set to 3rdpartybug
  • Status changed from new to closed

Nevermind, I did a bit of research on the different character encodings.
UTF-8 should be able to handle everything just fine (and is a sane default), but it is probably a good idea to add the ability to change the encoding in the login manager just in case.

This is a bit bigger of a code change, so I am not sure I can get it finished in time for 10.0-release, but it should be included in the first new package set after the release.

I am going to close this ticket as a 3rd party bug (KDE/Konsole). Feel free to re-open it if you find any additional settings/configurations that we can modify to make it work better for you!

Note: See TracTickets for help on using tickets.