Community
Participate
Working Groups
The Papyrus source code in git is encoded in a mix of * UTF-8 encoding * Windows Cp1252 (I think, could be ISO 8859-1 in at least some cases as there is overlap) This is especially noticeable in Xtend sources, which are becoming ever more prominent in our code, as the «» guillemets are represented very differently in these encodings (for the most part, Java sources contain only ASCII characters, which are common to all of these encodings). Consequently, when bringing such files into a workspace that uses UTF-8 encoding by default (such as any created by Oomph, especially on non-Windows platforms that don't even support Cp1252), Xtend fails to compile to Java. In many cases this is already accounted for by resource encoding preferences in the project's .settings/, but this is only to tell Eclipse what the encoding is. These files are still not UTF-8. Consequently, external tools such as graphical merge tools still have trouble dealing with these files. We also often see garbage characters in place of diacriticals in the names of contributors in the copyright headers, for example, although that is not a severe problem. We really ought to standardize the source file encoding across the board as UTF-8, managed in the project .settings/. I can volunteer to update the project settings of all active source projects and to convert files to UTF-8 encoding where necessary. The priority is the Xtend sources.
