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

Bug 319284

Summary:

[ui] Windows-1252 not in html encoding list

Product:

[WebTools] WTP Source Editing

Reporter:

Rik Bartolini <riksoft>

Component:

wst.html

Assignee:

wst.html-triaged <wst.html-triaged>

Status:

NEW ---

QA Contact:

Nick Sandonato <nsand.dev>

Severity:

enhancement

Priority:

CC:

mauromol, nsand.dev, rakes123, thatnitind

Version:

3.2

Flags:

nsand.dev: review-

Target Milestone:

Future

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
patch	none

Description Rik Bartolini

2010-07-08 12:20:30 EDT

Build Identifier: 20100218-1602

Little Problem: in preferences->web->html->Encoding, I can't enter an arbitrary IANA name/encoding nor I find what I need (Windows-1252) or cp1252. I can do that for workspace file encoding or project encoding, but not on html encoding.

So happens that when I create a new html file, automatically I got a meta http-equiv that I must change manually from utf-8 or iso-8859-1 to windows-1252 or cp1252
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" />

This happens on Linux but also on Windows platforms.

A simple solution is to change the template, or the workaround I received here
http://www.eclipse.org/forums/index.php?t=msg&goto=545278&#msg_545278

but I want anyway hilight this point because, I quote: "the draft HTML 5 specification requires that documents advertised as ISO-8859-1 actually be parsed with the Windows-1252 encoding."

So, shouldn't be possibile to set html encoding to cp1252 or Windows-1252?


Reproducible: Always

Comment 1 Rakesh

2010-07-12 09:58:04 EDT

We can have one item in combo as 'Other', whenever it is selected IANA field  will become editable and user can enter his choice.For validation , we can use same approach as done in platform.

Comment 2 Rakesh

2010-07-14 04:36:00 EDT

Created attachment 174265 [details]
patch

Created patch based on above comment

Comment 3 Nick Sandonato

2011-02-24 17:51:24 EST

Hi, Rakesh. Thanks for the patch, but I don't think we'll use this one. I don't feel comfortable with adding "Other" to the dropdown as it doesn't fit the flow with the other options in the list.

I'd like to consider other options like pulling the stored value from the Content Types preferences, which I think would create a more unified experience. But seeing Bug 315945 completed so you have a dropdown of encodings to choose from might be nice to have first.

Another workaround for the time being is to create a new template based on the existing HTML template, but replace the ${encoding} in the template with windows-1252, that way you don't have to worry about messing up your encoding list and having to muck with the preferences manually. Then you can always create a windows-1252 document from one template and another one based on the encoding in your preferences.

Comment 4 Nick Sandonato

2012-11-02 15:44:47 EDT

Converting to an enhancement to align with the Platform's enhancement.