Bug 351656

Summary:	UTF-8 not accepted during PDE-export
Product:	[Technology] UOMo	Reporter:	Werner Keil <werner.keil>
Component:	Units	Assignee:	Werner Keil <werner.keil>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	P3	CC:	davidmichonneau
Version:	0.6.0	Keywords:	investigate, nl, ui
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	350289

Description Werner Keil

2011-07-10 10:13:12 EDT

During a PDE-export of UOMo Units the following error occurs:
# 10.07.11 19:35:16 IST
# Eclipse Compiler for Java(TM) 0.A68_R36x, 3.6.1, Copyright IBM Corp 2000, 2010. All rights reserved.
----------
1. ERROR in C:\Users\Werner\workspace\sts-2.5.0.RELEASE\units\org.eclipse.uomo\bundles\org.eclipse.uomo.units\src\main\java\org\eclipse\uomo\units\impl\DimensionImpl.java (at line 81)
	public static final Dimension TEMPERATURE = new DimensionImpl('Θ');
	                                                              ^^^^
Invalid character constant
----------
1 problem (1 error)

Current workaround is using "Q" (its Latin equivalent) instead of the Greek character Theta until this problem is fixed. This only occurs for PDE build as both Eclipse internal compiler and Maven have correctly been set to UTF-8.

Comment 1 David Michonneau

2012-02-07 05:16:07 EST

the error also happens on the first character of a file that is encoded as utf-8: ï»¿/*, and it reports an error:

(I have a java file that start with /*)

----------
1. ERROR in <filename>.java (at line 1)
	/*
	^^^
Syntax error on tokens, delete these tokens

Comment 2 Werner Keil

2012-02-07 06:20:05 EST

Sorry, but I have a feeling, the file starting with /* violates a whole lot of naming conventions for Java and/or Eclipse.

/* generally starts comments in Java, e.g. it is good practice to start the name with an uppercase ASCII character (no special cases like äÄöÖüÖ, ß or similar either;-) 

Can you explain in more detail why you would need that odd file name?

Comment 3 Werner Keil

2013-04-28 09:30:02 EDT

Given UOMo is now generally built using Tycho/Maven, this issue may only arise, if manual PDE export used a wrong encoding, i.E. NOT UTF8, thus the issue may be considered resolved, as it doesn't affect Tycho build of all plugins/bundles.