I have a question and a request that aren't really about the hacks (I would leave that to more experienced programmers) but about the plugin. First, about 'db_unicode_client.rb' - isn't this functionality (setting client encoding) already present by specifying 'encoding' attribute in database.yml? Second: when setting "content-type" header for output, could you not force text/html but put in a variable which value defaults to text/html so we can provide 'application/xhtml+xml' or other content types in specific controllers?
Sorry to bug you with such somewhat not very relevant issues, but I feel that this needs to be a truly universally droppable plugin and these kind of minor tweaks will make it such.
Keep up the good i18n work,
-Mislav
On 6/11/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote:
...after some more tweaks I have come to the
simple idea of having proxy access to the characters instead of
subclassing. Maybe this can be useful for ActiveSupport (it is going
to be able to address the more expensive routines only where
characters are involved, and when Matz finally comes up with a good
M17N engine - doh - it will be a matter of aliasing a method to self.
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
