Summary: | displaying of threads in slrn | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Mikolaj Machowski <mikmach> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.5 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
slrnbad.png
slrngood.png |
Description
Mikolaj Machowski
2005-06-11 21:52:49 UTC
SVN HEAD How about a screen shot? As I have no idea what you are talking about... :-) > How about a screen shot? As I have no idea what you are
> talking about... :-)
Attaching two screenshots. slrnbad.png is a bad one, with slrn session
started as special type of session in Konsole.
slrn.desktop
[Desktop Entry]
Cwd=~\s
Exec=slrn
Font=
Icon=mail_generic
KeyTab=
Name=slrn
Schema=GreenOnBlack.schema
Term=linux
Type=KonsoleApplication
If I start slrn just by typing name in command line everything works OK
as seen on slrngood.png . The same when starting konsole with shortcut
on desktop: konsole -e slrn
Created an attachment (id=11526)
slrnbad.png
Created an attachment (id=11527)
slrngood.png
Can you test KDE 3.5.x ? Still confirming for KDE 3.5 branch svn version: 537524 (last change: 5 May) Note: this only apply to slrn started as session type. When started normally from command line thread characters are displayed as they should be. Here is .desktop file: [Desktop Entry] Cwd=~\s Exec=slrn Font= Icon=mail_generic KeyTab= Name=slrn Schema=GreenOnBlack.schema Term=linux Type=KonsoleApplication Note2: tree characters in Midnight Commander are displayed normally when started as session or as from command line. Using your slrn.desktop, % konsole --type slrn This works fine for me... I get the correct | and > for threads... slrn: 0.9.8.1 The same version of slrn. Maybe some local problem with locales but still: in such case thread characters should be broken in *all* situations. Hello, Can you still reproduce this? Please try changing the character encoding to Utf-8 if it is not already that via the Settings -> Encoding menu. > Can you still reproduce this? Yes in 3.5 branch. > Please try changing the character > encoding to Utf-8 if it is not already that via the Settings -> Encoding > menu. It doesn't help for main problem + everything else in iso-8859-2 (like 99% of usenet posts in Polish groups) is broken. Does this problem occur in KDE 4? > 03:02 ------- Does this problem occur in KDE 4?
Didn't occur in konsole 2.1 (KDE 4.0.98) run under KDE3.
Well, works in KDE4. In kde3 still broken. |