Re: [ jEdit-users ] Name for new Encoding searched - please suggest

[Jarek C. <jar...@po...>]

After new discoveries I suggest the name is just

java

. It's used only in java. Java does not use any other special encoding. 
It's not only for the properties but also for source code. So it's the 
shortest possible name and in the same time says all. Long encoding 
names would look ugly in status bar widget.

Jarek

W dniu 10/02/2011 04:29 PM, Vampire pisze:
> Hi,
>
> as suggested in the thread http://goo.gl/ufnIN of this list I've
> implemented an Encoding with which you can conveniently edit
> Properties files.
> This means the encoding automatically translates unicode escape
> sequences to characters when loading a file and reverse when saving a
> file.
> Any Java developer who has used Properties files is probably aware of
> the format restriction of those files.
> If not, http://goo.gl/jeDF0 describes the format in which Properties
> files have to be.
>
> What I'm missing now is a good name for the encoding as shown in the
> encoding dropdowns and lists.
> If you have any idea for names, please reply here with your suggestions.
> Eventually I will set up a poll with some of the suggestions on the
> community page.
>
> Here are some first ideas:
>
> - ISO-8859-1-for-Properties
> - Properties
> - ISO-8859-1-with-Escapes
> - ISO-8859-1-with-Unicode-Escapes
>
> Regards
> Vampire
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
>
>