I work with many remote servers which often have files in different encodings so it's
not enough just one global default encoding in this case.
It would be nice to have a possibility to define default encodings for particular
severs.
(see also http://community.jedit.org/?q=node/view/4766)
| Submitted | ru1234 - 2011-06-24 - 23:02:08z | Assigned | xuhdev |
|---|---|---|---|
| Priority | 5 | Category | None |
| Status | Open | Group | None |
| Resolution | None | Visibility | No |
| 2011-06-25 - 01:39:31z ezust |
Perhaps "path regex" makes more sense than "server" since server only means something
when you are using the FTP plugin. A mapping of path regexes to encodings would be quite convenient. Perhaps that should also include line separator character. |
|---|---|
| 2011-06-25 - 01:44:48z ru1234 |
ezust, you're right, particularly about line separator (I forgot about it). From other hand, different charsets are rare when on the same machine. It is much more hot for remote servers, so I would put "path/server" in the topic. |
| 2013-04-05 - 05:29:54z ezust |
From the file system browser, you can right click a folder and go to encoding, and
select the default encoding for opening files under that location. How different is
that from what you are asking? |
| 2013-04-05 - 05:38:40z ezust |
I suppose there still needs to be a gui to see/remove/edit the different path/encoding
pairs in the encoding options pane. |
| 2013-04-05 - 11:07:00z ru1234 |
> From the file system browser, you can right click a folder and go to encoding, and select the default encoding for opening files under that location. How different is that from what you are asking? Hmm.. Didn't know about this opportunity. Though, encoding chosen for a particular folder resets every time default encoding is changed. Encoding settings are not portable between installations as well. Considering aforementioned, I think those settings should be saved somewhere explicitly. |
| 2013-04-23 - 16:27:17z ezust |
I am not sure if this works on remote file systems, but the EditorConfig plugin allows
you to specify an encoding of all files in a directory, via a .ini file |
| 2013-04-23 - 19:43:46z ezust |
EditorConfig doesn't yet set encoding for jEdit. Opened an issue about it. https://github.com/editorconfig/editorconfig/issues/95 |
| 2013-04-24 - 21:31:41z ezust |
Moving to Plugin Feature Requests. This can be done in a plugin. EditorConfig handles 5 standard encodings while jEdit can handle many others. |
| 2013-04-26 - 08:47:58z ezust |
Git master of EditorConfig plugin now supports jedit_encoding which means half of
this feature request is satisfied by EditorConfig. How to handle Remote VFS is a problem that is under discussion still. Currently, EditorConfig loads its .editorconfig files with java.io.file instead of the more generic VFS API. If EditorConfig could load remote .editorconfig files like jEdit does, this would solve the problem. |
| 2013-04-26 - 17:12:18z xuhdev |
Correct @ezust a detail: jedit_charset not jedit_encoding |
| 2013-04-26 - 19:23:43z ezust |
New ticket opened for handling remote VFS: https://github.com/editorconfig/editorconfig/issues/101#issuecomment-17088076 |