Karl Dahlke <[email protected]> writes: > I propose that andTranslate turn every &whatever; symbol into its utf8 > equivalent, and that's all.
I like this idea, but I think we have a problem since we support both source documents and output in ISO-8859-1. Here's a scenario. The user's console charset is ISO-8859-1. We receive a source document that is also ISO-8859-1. It is never converted to UTF-8. If andTranslate starts inserting UTF-8 into the formatted text, we'll be mixing character sets. In order to use UTF-8 in andTranslate, I think we need to expect that the user's console is always UTF-8 capable. All formatted text needs to be UTF-8. Maybe that's not an unreasonable expectation in 2014. UTF-8 has been around since 1993, and the unibyte charsets should have gone the way of the dinosaur years ago. Allowing the user to configure the translations would also be a nice touch! -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
