Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 194417

Summary:

add ISO-8859-15 to encoding dropdown list choice

Product:

[Eclipse Project] Platform

Reporter:

Victor Volle <victor.volle>

Component:

Text

Assignee:

Platform-Text-Inbox <platform-text-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

carl-eric.menzel

Version:

3.2

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Bug Depends on:

195541

Bug Blocks:

Attachments:

Description	Flags
Plug-in that adds encoding(s)	none

Description Victor Volle

2007-06-26 10:03:38 EDT

+++ This bug was initially created as a clone of Bug #170366 +++

please add ISO-8859-15 to list of possible encodings.
For the european currency symbol EUR we need the support of ISO-8859-15. We cannot switch to UTF-8 because not all systems we need to use support it.

Comment 1 Dani Megert

2007-06-27 03:11:53 EDT

ISO-8859-1 is there. What else do you need?

Comment 2 Carl-Eric Menzel

2007-06-27 03:44:50 EDT

ISO-8859-1 doesn't contain the Euro currency symbol. As far as I know, that is the only difference, but a crucial one in Europe. I meanwhile found out that we can manually enter the string "ISO-8859-15" into the combobox and it actually works then. So this comes down to only a minor inconvenience, nothing serious. Still, for European users it would be great to add this option to the default list.

Comment 3 Dani Megert

2007-06-27 04:06:10 EDT

Sorry, of course.

Why don't you use the default encoding that comes out of the box on Windows machines (Cp1251)? It contains the € symbol. Is that encoding also not available on some of your systems? If so, what systems are you talking about?

Comment 4 Dani Megert

2007-06-27 04:41:49 EDT

If there's good enough reasoning why the combination of UTF-8 and Cp1251 doesn't work we might reconsider.

Comment 5 Carl-Eric Menzel

2007-06-27 05:13:42 EDT

We're developing on Windows, running in WebSphere on Solaris and using an Oracle DB that unfortunately is not ours exclusively, other applications use it as well. Currently it's all on 8859-1. Switching to UTF-8 would be preferable in the long run, but nobody is willing to take the risk with the heterogenous environment in the short run. 8859-15 is the easy way out for now, because the difference is minimal.

But since Eclipse even remembers what I entered into the combobox, I'd file this entry under "nice to have". The inconvenience is only that it's not immediately obvious to the user that other encodings are supported as well.

Comment 6 Dani Megert

2007-06-27 05:24:27 EDT

>The inconvenience is only that it's not
>immediately obvious to the user that other encodings are supported as well.
Would it help if the encoding in the combo would get selected and/or get the blincking caret?

Another thing you can do is write a very little plug-in that adds. This way all your developers can get it out of the box. Let me know if you want to do this but don't know how.

Comment 7 Carl-Eric Menzel

2007-07-05 08:40:29 EDT

Selecting the text in the encoding combobox would be the perfect thing to do from a usability point of view, if you ask me - that way we don't pollute the list with any additional encodings not everybody needs, and it is also immediately obvious that we can write stuff there.

The plugin would be interesting too, but only out of personal curiosity. No need to rush to any assistance there immediately. Thank you though!

Comment 8 Dani Megert

2007-07-05 11:28:25 EDT

Created attachment 73127 [details]
Plug-in that adds encoding(s)

Comment 9 Dani Megert

2007-07-05 11:33:48 EDT

See bug 194417 for the suggested improvements.

Comment 10 Dani Megert

2007-07-05 11:34:33 EDT

See bug 195541 for the suggested improvements.