Bug 48471 - licq is looking for translations in non-existing directory
Summary: licq is looking for translations in non-existing directory
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: licq
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-10 19:24 UTC by Leonid Kanter
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-07-10 19:44:59 UTC
Embargoed:

Attachments (Terms of Use)
this patch works for me (2.12 KB, patch)
2001-07-10 19:27 UTC, Leonid Kanter 		no flags Details | Diff
more simple patch (600 bytes, patch)
2001-07-10 19:42 UTC, Leonid Kanter 		no flags Details | Diff
View All

Description Leonid Kanter 2001-07-10 19:24:35 UTC 
Description of Problem:

If you try to select translation from list, error message appears that licq
is unable to find translation file in your ~/.licq/translations. But it can
use translation file from /usr/share/licq/translations.

How Reproducible:

always

Steps to Reproduce:
1. start licq (qt gui or kde gui).
2. go to options menu
3. Select eny encoding from list.

Actual Results:

You'll see error window: [Err] unable to open
/home/leon/.licq/translations/RUSSIAN_WIN for reading: no such file or
directory

Expected Results:

It must silently use /usr/share/licq/translations/RUSSIAN_WIN

Additional Information:
	
Patch will be attached
Comment 1 Leonid Kanter 2001-07-10 19:27:35 UTC 
Created attachment 23227 [details]
this patch works for me
Comment 2 Leonid Kanter 2001-07-10 19:42:00 UTC 
Created attachment 23228 [details]
more simple patch
Comment 3 Bernhard Rosenkraenzer 2001-07-11 10:34:42 UTC 
Thanks, added a similar patch in 1.0.3-6.
(I've added an if(!QFile::exists(szTranslationPath)) construct to allow 
per-user translation installations).
Note You need to log in before you can comment on or make changes to this bug.