Bug 2599 - Better support for exporting paths with non-ASCII characters on UNIX
Summary: Better support for exporting paths with non-ASCII characters on UNIX
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Local drive redirection (show other bugs)
Version: 1.6.0
Hardware: PC Unknown
: P2 Enhancement
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-12 10:57 CET by Peter Åstrand
Modified: 2017-02-07 11:10 CET (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Peter Åstrand cendio 2007-12-12 10:57:38 CET 
Exporting paths with non-ASCII characters with tlclient on UNIX doesn't work perfect. For example, the FLTK file browser doesn't understand UTF-8 locales, so with UTF-8 file names, the directory listing looks ugly. 

One solution to this might be to override fl_filename_list by implementing it in tlclient. It could convert from the locale encoding to Latin1. 

Also, we are currently storing path names in tlclient.conf encoded as UTF-8 (which i believe is a very good). When tlclient loads these paths, it should convert to Latin1, so that these are correctly displayed in the GUI.
Comment 1 Pierre Ossman cendio 2017-02-07 11:10:33 CET 
This was probably fixed when we upgraded to a version of FLTK which handles UTF-8. We need to confirm it though. Perhaps the reoccuring tests need to include this?
Note You need to log in before you can comment on or make changes to this bug.