This is a heads up about a change in the behaviour of WOLips in future
builds when managing component encoding types.
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. This will automaticaly edit
the woo file, or create one if necessary, and explicitly set the
encoding type of the .html and .wod files. This process requires that
you use a valid Java charset instead of the old NS* obj-c style
charset name.
This change also means that the encoding type of a component can be
inherited from the parent folder. 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).
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.
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10) Ph: +61 419 729 806
This archive was generated by hypermail 2.0.0 : Sat Dec 08 2007 - 16:05:41 EST