LC_CTYPE locale must be of UTF-8 type (pt_BR locale)
- Dominant language
- C++
- Stars
- 834
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
```
# logkeys --start
logkeys: LC_CTYPE locale must be of UTF-8 type
root@motavia:/# locale -a
C
POSIX
pt_BR.utf8
root@motavia:/# locale
LANG=pt_BR.UTF-8
LANGUAGE=pt_BR:pt:en
LC_CTYPE="pt_BR.UTF-8"
LC_NUMERIC="pt_BR.UTF-8"
LC_TIME="pt_BR.UTF-8"
LC_COLLATE="pt_BR.UTF-8"
LC_MONETARY="pt_BR.UTF-8"
LC_MESSAGES="pt_BR.UTF-8"
LC_PAPER="pt_BR.UTF-8"
LC_NAME="pt_BR.UTF-8"
LC_ADDRESS="pt_BR.UTF-8"
LC_TELEPHONE="pt_BR.UTF-8"
LC_MEASUREMENT="pt_BR.UTF-8"
LC_IDENTIFICATION="pt_BR.UTF-8"
LC_ALL=
Version: 0.1.1a
OS: Debian 6.0
```
Original issue reported on code.google.com by `ottoteix...@gmail.com` on 14 Nov 2012 at 3:33
Attachments:
- [output-devices](https://storage.googleapis.com/google-code-attachments/logkeys/issue-99/comment-0/output-devices)
- [output-dumpkeys](https://storage.googleapis.com/google-code-attachments/logkeys/issue-99/comment-0/output-dumpkeys)
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce with `logkeys --start` under the shown pt_BR.UTF-8 environment, comparing `locale -a` with the reported failure. Trace the locale validation entry point; done means logkeys accepts the available UTF-8 locale instead of emitting the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100