Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 86310 - slrn is unable to display cyrillic text in UTF-8 locale
slrn is unable to display cyrillic text in UTF-8 locale
Status: CLOSED DUPLICATE of bug 75191
Product: Red Hat Linux
Classification: Retired
Component: slrn (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jindrich Novy
Depends On:
  Show dependency treegraph
Reported: 2003-03-19 07:38 EST by Alexey Neyman
Modified: 2013-07-02 18:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-08 11:11:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
slrn screenshot (132.98 KB, image/png)
2003-03-19 07:39 EST, Alexey Neyman
no flags Details

  None (edit)
Description Alexey Neyman 2003-03-19 07:38:55 EST
Description of problem:  
slrn cannot display the cyrillic text. If the newsserver serves them in  
the KOI8-R encoding, the cyrillic text is not display at all (blank  
symbols appear). If the server enconding is UTF-8, the content is hardly  
readable (see screenshot): most of the symbols are replaced with question  
I guess there are two problems: 
First, it seems not to convert the article to the UTF-8 character set 
(and in its config file, /etc/slrn.rc, utf-8 is not indicated as a valid 
charset value). 
Second, it seems that it incorrectly determines printable characters even 
for UTF-8 charset. 
Version-Release number of selected component (if applicable):  
How reproducible:  
Run slrn on any USENET group with Russian posts.
Comment 1 Alexey Neyman 2003-03-19 07:39:46 EST
Created attachment 90661 [details]
slrn screenshot
Comment 2 Jindrich Novy 2005-09-08 11:11:33 EDT

*** This bug has been marked as a duplicate of 75191 ***

Note You need to log in before you can comment on or make changes to this bug.