Opened 19 years ago
Closed 15 years ago
#215 closed bug (fixed)
Problem with special characters
Reported by: | Owned by: | nobody | |
---|---|---|---|
Priority: | high | Milestone: | R1 |
Component: | Applications/Command Line Tools | Version: | R1/Development |
Keywords: | Cc: | diver, revol@… | |
Blocked By: | #1855 | Blocking: | #3047 |
Platform: | All |
Description
Writing swedish special characters (??????) doesn't work in Terminal. Nothing appears on screen, except when pressing ?; then it says "(arg: 6)". Using these characters in all other tested apps work fine.
Attachments (1)
Change History (33)
by , 19 years ago
Attachment: | DataTranslations.png added |
---|
comment:1 by , 19 years ago
Status: | new → assigned |
---|
comment:2 by , 19 years ago
I did a fix in revision 16496 for 1 byte characters which need option key. I don't know if the bug was about this.
comment:3 by , 19 years ago
I haven't tried that revision yet, but it doesn't sound like the same problem since you don't need to press any additional key to type ??? or ??? on swedish keyboards.
comment:4 by , 19 years ago
Bug is still showing up. Italian multibyte characters like "?", "?", etc. aren't drawn correctly either.
comment:5 by , 19 years ago
Status: | assigned → new |
---|
comment:6 by , 19 years ago
Owner: | changed from | to
---|
comment:7 by , 19 years ago
Must be a tty problem, as we write good bytes and read wrong ones. Changing component ...
comment:8 by , 19 years ago
Component: | Applications → Kernel |
---|
comment:9 by , 19 years ago
Last comment is wrong : it seems bash hasn't been built multibyte support (yet)
comment:10 by , 19 years ago
Component: | Kernel → Applications |
---|
comment:11 by , 19 years ago
There is a patch done by mmu_man around. Maybe he even sent it to our mailing list?
comment:12 by , 19 years ago
Cc: | added |
---|
comment:13 by , 19 years ago
bug_group: | → developers |
---|
comment:14 by , 18 years ago
Cc: | added |
---|
comment:16 by , 18 years ago
It could be simpler to switch to bash 3.0 right away. It has problems in Zeta re. utf-8 but that's because the glibc in zeta is old. Which glibc do we use btw ?
comment:17 by , 17 years ago
Component: | - Applications → - Applications/Terminal |
---|---|
Owner: | changed from | to
Platform: | → All |
Move to the proper component.
follow-up: 21 comment:20 by , 17 years ago
Milestone: | R1 → R1/alpha1 |
---|
Interestingly bash 3.2 suffers from the same problem. Maybe it's a (bash) build configuration issue?
follow-up: 22 comment:21 by , 17 years ago
Replying to jackburton:
Interestingly bash 3.2 suffers from the same problem. Maybe it's a (bash) build configuration issue?
Replying to myself: Yes, it's a build configuration issue. Defining HAVE_WCTYPE and HAVE_MBSTATE to 1 enables multibyte support in bash. Doing so, though, triggers a problem: haiku doesn't boot anymore (hangs on INIT: Bootscript started).
comment:22 by , 17 years ago
Yes, it's a build configuration issue. Defining HAVE_WCTYPE and HAVE_MBSTATE to 1 enables multibyte support in bash. Doing so, though, triggers a problem: haiku doesn't boot anymore (hangs on INIT: Bootscript started).
Replying to myself, again: It's pretty obvious it doesn't work, since our mbrtowc() method is a no-op.
comment:24 by , 16 years ago
Blocked By: | 1855 added |
---|
comment:26 by , 16 years ago
Blocking: | 3047 added |
---|
comment:27 by , 16 years ago
I added some printfs() in the code, and it seems that, like korli said in a comment, 3 years ago, "Must be a tty problem, as we write good bytes and read wrong ones". I have no idea if bash is involved: IOW: I don't know how the data flow looks like. But in Shell::Write(), the bytes look correct (for the "à" character, it's 0xc3 0xa0). But this sequence never show up in TermParse::_ReadParserBuffer(). Actually, nothing shows up there when I hit this key.
comment:28 by , 16 years ago
Version: | → R1 development |
---|
its not a tty problem. i checked the code and did not see any problem with it. it does not show up in TermParse::_ReadParserBuffer() because the shell is interpreting the char not correctly.
comment:29 by , 15 years ago
Can someone recheck this one now that wchar fix is in place? Does it have any effect?
comment:30 by , 15 years ago
I checked right after the merging with trunk, and the problem is still there.
comment:31 by , 15 years ago
Component: | Applications/Terminal → Applications/Command Line Tools |
---|---|
Owner: | changed from | to
Version: | R1/pre-alpha1 → R1/Development |
Fixed in hrev34150. Of course it was just a readline configuration issue...
comment:32 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Screenshot...