Re: resource_feeder feedback

Michael Koziarski wrote:
>> Next, consider internationalization / character encoding issues.
>> Builder prefers utf-8; but with Builder 2.0 it will fall back to
>> iso-8859-1/win-1252.  This is the right default for a wide number of
>> cases, but it will be wrong in a case that you might care about: native
>> Mac applications.
> 
> I had a little trouble following this.   Is UTF-8 the right default
> for a number of cases?  or latin1?  Our position in the other thread
> of 'utf-8 everywhere' seems to me to be a natural position to take
> here,  but I'm bound to be missing something.

 From a Builder 2.0 perspective, utf-8 everywhere is ideal.

Now, not every random stream of bytes is valid utf-8.  Builder 2.0 tries 
really hard not produce invalid XML, so if the input isn't utf-8, it 
falls back to the web-centric (or US centric) iso-8859-1 default; as 
embraced and extended by Microsoft in the form of win-1252.

And by fall back, I mean convert to utf-8.

- Sam Ruby


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to 
rubyonrails-core-unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core
-~----------~----~----~----~------~----~------~--~---