Ticket #215 (new bug)

Opened 2 years ago

Last modified 3 months ago

Problem with special characters

Reported by: fekdahl@gmail.com Assigned to: jackburton
Priority: high Milestone: R1/alpha1
Component: Applications/Terminal Version:
Cc: diver, revol@free.fr 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

DataTranslations.png (61.2 kB) - added by fekdahl@gmail.com on 02/19/06 09:22:28.
Screenshot…

Change History

02/19/06 09:22:28 changed by fekdahl@gmail.com

  • attachment DataTranslations.png added.

Screenshot...

02/19/06 13:50:12 changed by sikosis

  • status changed from new to assigned.

02/21/06 10:48:26 changed by korli

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.

02/21/06 21:42:58 changed by fekdahl@gmail.com

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.

03/06/06 21:56:33 changed by jackburton

Bug is still showing up. Italian multibyte characters like "?", "?", etc. aren't
drawn correctly either.

03/11/06 03:25:18 changed by axeld

  • status changed from assigned to new.

03/11/06 03:25:25 changed by axeld

  • owner changed from sikosis to axeld.

03/11/06 05:46:15 changed by korli

Must be a tty problem, as we write good bytes and read wrong ones.
Changing component ...

03/11/06 05:46:29 changed by korli

  • component changed from Applications to Kernel.

03/11/06 09:02:51 changed by korli

Last comment is wrong : it seems bash hasn't been built multibyte support (yet)

03/11/06 09:02:59 changed by korli

  • component changed from Kernel to Applications.

03/15/06 23:18:43 changed by jackburton

There is a patch done by mmu_man around. Maybe he even sent it to our mailing list?

04/07/06 01:15:58 changed by diver

  • cc set to diver.

04/27/06 03:08:40 changed by korli

  • bug_group set to developers.

06/01/06 07:28:55 changed by johndrinkwater

  • cc set to revol@free.fr.

06/01/06 07:29:00 changed by johndrinkwater

Following on from comment 7, added Fran?ois to CC

06/05/06 08:17:35 changed by revol@free.fr

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 ?

11/19/07 09:02:00 changed by nielx

  • owner changed from axeld to jackburton.
  • platform set to All.
  • component changed from - Applications to - Applications/Terminal.

Move to the proper component.

01/07/08 14:18:16 changed by nielx

Bug #1699 is marked as a duplicate of this bug.

01/11/08 06:49:54 changed by jackburton

It's a bash problem, though, not Terminal's.

(follow-up: ↓ 21 ) 02/22/08 03:54:38 changed by jackburton

  • milestone changed from R1 to R1/alpha1.

Interestingly bash 3.2 suffers from the same problem. Maybe it's a (bash) build configuration issue?

(in reply to: ↑ 20 ; follow-up: ↓ 22 ) 02/25/08 09:49:16 changed by jackburton

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).

(in reply to: ↑ 21 ) 02/25/08 10:02:51 changed by jackburton

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.

02/26/08 03:51:04 changed by jackburton

depends on #1855.