In an earlier question posted to this mailing,
I asked about the best way to handle i18n in
I have several clients that contact to a database
to get their messages. I'm considering storing their
message as encoded text (i.e. an encoding support
by MIME spec) along with a column for the charset.
This way when a user reads their messages, the following
1. The user's e-mail client can check the charset column
in the db to see if the charset for that particular
message is supported.
2. The user's e-mail client will decode (MIME decode) the
message text before displaying it.
Pro: Since MIME encoded text is always represented as 7/8-bit
ASCII, I'm always sure to have my text store in the database
without worrying about charset support.
Con: I think there's a limit to the size of text stored in a column.
Is it better to stick with a BLOB?
Has anyone tried this?
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:05 EDT