Plug-ins that interpret text files, such as editors and builders, should consult the workbench encoding preference rather than assume that the installed operating system encoding is in use.Ĭurrently, creating a new project will generate the above warning in the Main component, but that can be fixed by doing the following: Change the encoding for a resource (project, folder or file)
Users may choose from the available encoding choices in the General > Workspace preference page or type in their own encoding. For this reason, the workbench defines its own encoding profile that is specified by the user in the Preferences dialog. Given the ability to use the platform in a networked team environment, it's certainly possible that users will want to work with text files that use a different encoding scheme than their native encoding scheme so that they can easily interchange files with another team. Note from Eclipse Help pages about text encoding Any components you create from now on using the default encoding should all match. This should set the encoding for all the resources in your workspace. In Eclipse, go to Preferences>General>Workspace and select UTF-8 as the Text File Encoding. There are a couple of ways to go about this: Change the encoding for your entire Workbench html file manually does not get rid of the warning. WOO Encoding type UTF-8 doesn't match component MacRoman (Main.woo)Ĭhanging the encoding type in the. Creating a new WO Application/WOnder application project in today's version of WOLips generates the following warning:
0 kommentar(er)
