Community
Participate
Working Groups
Build ID: I20070601-1539 Steps To Reproduce: Xpand uses the french << >> signs to mark template directives. Unfortunately, these are represented differently in various character encodings. If you import the org.eclipse.gmf.codegen plug-in, you have to manually set the encoding of the xpt folder to ISO-8859-1. You also cannot write xpt aspect using a different encoding. This is especially annoying, because the error doesn't show up before the generation step, and you might have to rewrite the complete file then. The standard char encoding for Java is UTF-8. It is most likely, GMF users are coding Java in the same workspace. To avoid switching, I'd suggest the encoding should be changed to UTF-8.
Guess, with all these QVTO migrations/changes, modification of xpt file encoding is not as troublesome as it could be otherwise ;) I've committed the change to use UTF-8 as default encoding for the GMF Xpand templates. I did my best to ensure old templates, with ISO-8859-1 encoding are recognized and don't need to be changed right away (i.e. we try to detect whether .xpt file comes in UTF-8 or UTF-16 encoding, and, if neither's BOM is detected, we look for << and >> characters, and suggest old, ISO-8859-1 encoding if found any) Until tomorrow, when there's a new gmf/xpand build that is capable to recognize .xpt files both in UTF-8 and ISO-8859-1, I won't commit updated GMF templates (GMFGen and GMFGraph codegen)
If I forgot to CC anyone who'd better know about the change, please go ahead and do it yourself. Thanks ;)
GMF templates (codegen, codegen.lite, graphdef.codegen) were updated to use UTF-8
[target cleanup] 2.2 M6 was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Templates was the original product and component for this bug
