Community
Participate
Working Groups
Shorty after Galileo, bugs.eclipse.org will be converted to UTF-8. The Mylyn template will need to be updated to reflect this.
Since the conversion won't take place at the time of release (but is planned for end of July). We could have some confused users if we put this in the 3.2 release. Might be worth the month of bug reports since this build will be long term (until sr1).
Can't we auto-detect this, e.g. from the HTTP headers?
Assuming the database is encoded correctly to match what the server thinks it is serving up, yes, I suppose we could. I not certain if a missmatch can arise here with bugzilla.
The headers don't seem to return the encoding so this may not be feasible. Solution may be to ask webmaster at eclipse.org to include the encoding in the configuration but I'd like a better solution that isn't unique to eclipse.org.
Will use encoding as declared in configuration (bug#280361) and will update template for 3.2.1 if eclipse.org has moved to utf-8 by then.
Awaiting results of this weekends migration to bugzilla 3.4.1. If The migration happens to UTF-8, we'll update the template accordingly. Will need to ensure the eclipse.org configuration rdf is updated as well.
Denis, any word on the UTF-8 conversion?
Moving to backlog since the UTF-8 conversion of Eclipse.org is not expected before the Galileo SR2 release. Denis, please post here once this is happening and we'll update the Mylyn template.
Adding the dependency.
Created attachment 186024 [details] fix
Created attachment 186025 [details] mylyn/context/zip
Created attachment 186026 [details] backported patch
Patch applied to head and e_3_6_m_3_4_x branch.
