On 23/02/2009, at 10:34 PM, Lachlan Deck wrote:
> On 23/02/2009, at 10:23 PM, Q wrote:
>
>> On 23/02/2009, at 5:58 PM, Andrew Lindesay wrote:
>>
>>> Hello Lachlan and Quinton;
>>>
>>>> Optional WOO file creation was previously a feature of the
>>>> wizard, but was removed for good reasons (that I don't recall
>>>> right now).
>>>
>>> I was quite keen on not having the woo with my components.
>>
>> What I do remember of the problem is that this happened at a time
>> when quite a number of people were migrating from xcode and having
>> no end of character encoding related issues.
>> As a result the Apple WO team proposed that character encoding
>> validation be added to WOLips to ensure that eclipse's idea of the
>> character encoding matched what WO was expecting.
>
> For the woo, wod, html or all three?
woo file is always UTF-8, wod and html are whatever is specified in
the woo file, if not specified a check for UTF-16 content is performed
then otherwise assumed to be whatever the WO runtime default encoding
is.
>> This was done by me, and it sort of worked, except that WO doesn't
>> have a default encoding type, it uses the JDK default which is
>> different depending on the platform you use, so it was not possible
>> to validate the encoding type when it was unspecified because this
>> could change depending on the JDK you used to run the app.
>>
>> More recently the move in the wolips & wonder communities has been
>> to standardise on using UTF-8 as the default component encoding
>> type, which is only possible to do correctly, due to WO's lack of
>> defaulting to UTF-8, if your component includes a .woo file stating
>> that you are explicitly using UTF-8.
>
> Interesting. So, if the parent container is MacOSRoman and the woo
> is UTF-8 what happens?
Assuming the html and wod files inherit from the parent container, you
would get an encoding mismatch warning in your project's problems view.
> So when a user defines the Components folder, for example, as UTF-8
> and the stuff in there inherits this ... you're saying that this
> only has meaning for Eclipse and not the runtime (obvious) and that
> the woo is needed for the runtime, correct?
Yes. That is why WOLips includes a listener that will automagically
manage the encoding in the .woo file for you when you change the
encoding type of a component through the eclipse preferences interface.
> I suppose this could be negated, however, if there were some way to
> ensure WOMessage.defaultEncoding...
>
>> So it's just better to let eclipse take care of things for you and
>> live with the fact that .woo files mean you don't need to worry
>> about the character encoding.
>
> So the default will be UTF-8.
The default in 5.4 is UTF-8 I believe.
The default for new WO projects in WOLips is UTF-8
-- 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 : Mon Feb 23 2009 - 09:39:33 EST