Opened 11 years ago

Closed 9 years ago

Last modified 9 years ago

#2334 closed bug (fixed)

[StyledEdit] problems editing special chars

Reported by: diver Owned by: zooey
Priority: normal Milestone: R1
Component: Applications/StyledEdit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


There are problems editing special chars in StyledEdit. open /boot/beos/etc/KanBe/default open some files which contains special chars and try to insert some char before it. You should see that it (special chars) will disappear in this case. There could be more effects.

Change History (7)

comment:1 Changed 9 years ago by diver

Reproducible with /system/data/Canna/default/default.canna
Still here in hrev35569.

comment:2 Changed 9 years ago by diver

Version: R1/pre-alpha1R1/Development

comment:3 Changed 9 years ago by jackburton

Could this have been fixed as well, like #5598 ?

comment:4 Changed 9 years ago by zooey

Owner: changed from korli to zooey
Status: newin-progress

Unfortunately, the original bugreport doesn't mention *how* the file was opened with StyledEdit. As it does not contain utf-8 characters, StyledEdit will display garbage. Editing near the garbage characters will indeed confuse BTextView (at least I now know how to reproduce the bug).

If you convert the file from its original EUC-JP encoding to utf-8 (e.g. in Pe) and then copy & paste the contents into StyledEdit, things will be better, but there are still caret positioning problems.

Trying to figure this one out ...

comment:5 Changed 9 years ago by zooey

Resolution: fixed
Status: in-progressclosed

Should be fixed in hrev38034.

comment:6 Changed 9 years ago by diver

There are still some weirdness with default.canna and .canna. Select line with EUC-JP character and press End key. Caret should move to the end of that line, but it somewhere in-between instead. Also I've got 2 app_server crashes while playing with those files, not sure if it related, though.

comment:7 Changed 9 years ago by zooey

Yep, when you open the file as utf-8 (i.e. withouth converting it from EUC-JP), StyledEdit/BTextView will get confused. But that's not really a surprise, as StyledEdit is basically passing bogus UTF-8 text into BTextView.

That's still a problem of course, but a different one - see #6447.

Note: See TracTickets for help on using tickets.