Skip to content
This repository has been archived by the owner on May 26, 2021. It is now read-only.

Encoding

Jump to bottom
Leo Roos edited this page Dec 17, 2011 · 1 revision

Encoding is an important issue because Tigerseye supports Unicode characters which have a different representation depending on the encoding.

Encoding for Plug-in Users

The user defined dsl files are parsed with the eclipse defined project encoding. DSL files can be written in a different encoding, as long as the project settings are consistent.

Encoding during Plug-in Development

During development all Eclipse projects should have their encoding set to UTF-8. Doing so guarantees correct representation of source code on all platforms.

Encoding during the build

When building the update site the system encoding can have an impact. If the site.xml is executed on a machine with a different encoding than UTF-8, typically Windows, the resulting bytecode can contain invalid unicode characters. This happens for the Set example DSL. The ∪ (union) and ∩ (intersection) will have an invalid representation. As a result dsl files using the Set language with a correct encoding of their file won't be transformed correctly.

Clone this wiki locally