[ jEdit-devel ] [ jedit-Plugin Feature Requests-3328961 ] EditorConfig: set character encoding per path/server regex

[SourceForge.net <no...@so...>]

Plugin Feature Requests item #3328961, was opened at 2011-06-24 16:02
Message generated for change (Comment added) made by xuhdev
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=997936&aid=3328961&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mikhail Serov (ru1234)
Assigned to: Hong Xu (xuhdev)
Summary: EditorConfig: set character encoding per path/server regex

Initial Comment:
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)

----------------------------------------------------------------------

>Comment By: Hong Xu (xuhdev)
Date: 2013-04-26 10:12

Message:
Correct @ezust a detail:

jedit_charset not jedit_encoding

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2013-04-26 01:47

Message:
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.



----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2013-04-24 14:31

Message:
Moving to Plugin Feature Requests. 
This can be done in a plugin.  EditorConfig handles 5 standard encodings
while jEdit can handle many others.


----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2013-04-23 12:43

Message:
EditorConfig doesn't yet set encoding for jEdit. Opened an issue about it.
https://github.com/editorconfig/editorconfig/issues/95


----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2013-04-23 09:27

Message:
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


----------------------------------------------------------------------

Comment By: Mikhail Serov (ru1234)
Date: 2013-04-05 04:07

Message:
> 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.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2013-04-04 22:38

Message:
I suppose there still needs to be a gui to see/remove/edit the different
path/encoding pairs in the encoding options pane.


----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2013-04-04 22:29

Message:
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?



----------------------------------------------------------------------

Comment By: Mikhail Serov (ru1234)
Date: 2011-06-24 18:44

Message:
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.


----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2011-06-24 18:39

Message:
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.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=997936&aid=3328961&group_id=588