Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333434 - update encoding in config.xml to UTF-8
Summary: update encoding in config.xml to UTF-8
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Bugzilla (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 333536 333555 334111 (view as bug list)
Depends on:
Blocks: 220717
  Show dependency tree
 
Reported: 2011-01-03 12:51 EST by Steffen Pingel CLA
Modified: 2011-01-13 16:35 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2011-01-03 12:51:48 EST
The encoding in the configuration needs to be updated to UTF-8. Looking at http://mirror.csclub.uwaterloo.ca/eclipse/arch/config.xml it's still set to ISO-8859-1 which confuses Mylyn: <db_encoding>ISO-8859-1</db_encoding> . Thanks!
Comment 1 Steffen Pingel CLA 2011-01-05 14:06:58 EST
*** Bug 333536 has been marked as a duplicate of this bug. ***
Comment 2 Steffen Pingel CLA 2011-01-05 14:07:53 EST
*** Bug 333555 has been marked as a duplicate of this bug. ***
Comment 3 Frank Becker CLA 2011-01-05 15:39:24 EST
For your information.

Please look into bug# 244441 c43

I think we need to change the config.rdf.tmpl that is changed in the eclipse installation to
<db_encoding>UTF-8</db_encoding>
Comment 4 Denis Roy CLA 2011-01-06 09:26:10 EST
Instead of updating it, can I just remove it?  Here's what I'm seeing:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Note: this interface is experimental and under development.
   - We may and probably will make breaking changes to it in the future. -->

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:bz="http://www.bugzilla.org/rdf#">

<bz:installation rdf:about="https://bugs.eclipse.org/bugs/">
  <bz:install_version>3.6.3</bz:install_version>
  <db_encoding>ISO-8859-1</db_encoding>


The encoding is already specified in the first line.
Comment 5 Steffen Pingel CLA 2011-01-06 13:39:18 EST
Frank, can you check if the XML header reflects the database encoding? All Bugzilla instances I looked at returned UTF-8 but they might have all indeed been configured for UTF-8. 

The earliest we could release support for parsing the header would be in February as part of Helios SR2 (Mylyn 3.4.3 ). To support older Mylyn versions we need the <db_encoding/> tag around for a while.
Comment 6 Frank Becker CLA 2011-01-06 14:04:29 EST
(In reply to comment #5)
> Frank, can you check if the XML header reflects the database encoding? All
> Bugzilla instances I looked at returned UTF-8 but they might have all indeed
> been configured for UTF-8. 

The XML header is only for the XML content and not the database encoding, so we must stay with the db_encoding until we have an better way.

> The earliest we could release support for parsing the header would be in
> February as part of Helios SR2 (Mylyn 3.4.3 ). To support older Mylyn versions
> we need the <db_encoding/> tag around for a while.

Yes I can do some work for this but we should define what to do.
Comment 7 Denis Roy CLA 2011-01-06 14:36:19 EST
This change is done on our end.  It may take a while for config.xml to propagate to the mirrors but you can see our local copy on d.e.org:

http://download.eclipse.org/arch/config.xml
Comment 8 Steffen Pingel CLA 2011-01-06 14:48:00 EST
Thanks Denis.

Frank, let's make sure that we have an open bug and patch against Bugzilla to get this into the standard configuration schema.
Comment 9 Frank Becker CLA 2011-01-06 16:22:38 EST
(In reply to comment #7)
> This change is done on our end.  It may take a while for config.xml to
> propagate to the mirrors but you can see our local copy on d.e.org:
> 
> http://download.eclipse.org/arch/config.xml

Thanks Denis.

It may take a while until all mylyn clients have the updated configuration. Expect that you get many account locked until every user have the new version.
Comment 10 Steffen Pingel CLA 2011-01-13 16:35:33 EST
*** Bug 334111 has been marked as a duplicate of this bug. ***