Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 163821 - Allow encoding to be specified on copy and paste
Summary: Allow encoding to be specified on copy and paste
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: Kushal Munir CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
: 161081 (view as bug list)
Depends on:
Blocks: 163820
  Show dependency tree
 
Reported: 2006-11-08 11:19 EST by Kushal Munir CLA
Modified: 2008-08-13 13:17 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kushal Munir CLA 2006-11-08 11:19:05 EST
RSE needs to provide a user interface to be able to specify the encoding a user wants when copying and pasting (or drag and drop) to a certain target. A user might want the files to be in an encoding different from the target platform encoding when copying a file to a remote host for example. It will be better to allow this option on a granular level, i.e. allow an encoding to be specified for a folder so that any content in that folder is deemed to have the encoding specified for the folder and to use that encoding value when copying to the folder.
Comment 1 Martin Oberhuber CLA 2006-11-09 05:04:09 EST
Hm, the Eclipse Resource System already deals with Encoding preferences on a folder level. If we'd fully integrate EFS and handle remote resources as Workspace resources through EFS, we'd get the desired functionality.

Another option might be that copy&paste leaves encodings as-is, but we allow the user to change encodings after the transfer (note that this would involve multiple transfers client <-> host in order to recode the files, but one problem with changing the encoding on upload / download only is that if the user sets something wrong by mistake there must be a possibility to revert).

I'm not sure where RSE would store encoding preferences for remote systems?
Leaving target milestone open for now.
Comment 2 Kushal Munir CLA 2006-11-21 08:45:33 EST
*** Bug 161081 has been marked as a duplicate of this bug. ***
Comment 3 Kushal Munir CLA 2007-03-20 17:33:59 EDT
This was fixed in M5.
Comment 4 Martin Oberhuber CLA 2008-08-13 13:17:43 EDT
[target cleanup] 2.0 M6 was the original target milestone for this bug