Smart quotes and dashes in rich text documents only: Select to automatically substitute straight quotes for curly quotes and double hyphens for em dashes in rich text documents only. See Adjust paragraphs.Дata detectors: Automatically detect dates, times, and contact information in your documents. Show ruler: Select to view the ruler in rich text documents. Set default options to check or autocorrect spelling and grammar as you type. Otherwise, text wraps to the documentвЂ™s window size.Д¬hoose a default font style and size for plain and rich text documents.ДЇor rich text documents, you can set the document properties by adding the authorвЂ™s name, the organization name, and the copyright information. Wrap to page: Wrap text within the documentвЂ™s page margins. Plain text doesnвЂ™t allow text formatting. Plain text: Set the default format to plain text. Rich text allows formatting, such as bulleted lists, that plain text doesnвЂ™t. The WOComponent creation wizard hasn't yet been updated to reflect these changes, so a newly created component will still be created the same as before, and may have warnings about the character encoding of the woo file not matching that of the component, this will change in the future.Rich text: Set the default format to rich text. So you can manage the encoding type of all components within a folder by changing the default encoding type of the parent folder (assuming the contained components still inherit their encoding type, the default behaviour). This change also means that the encoding type of a component can be inherited from the parent folder. This process requires that you use a valid Java charset instead of the old NS* obj-c style charset name. This will automaticaly edit the woo file, or create one if necessary, and explicitly set the encoding type of the. It should now be possible to change the encoding type of a component using just the eclipse 'Resource->Text file encoding' context menu on the component in the WO Package Explorer. Original note about text encoding in WOLips from Q Select Other - UTF-8 and Apply to make the warning go away. You should see 'Inherited from container (UTF-8)' if you've made the change above, otherwise it will be (MacRoman). Right (or Control) click on the resource in the WO Package Explorer and select the Properties option at the bottom of the contextual menu. 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:

Default text encoding