From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] andTranslate
Date: Wed, 26 Feb 2014 06:04:17 -0800 [thread overview]
Message-ID: <87k3ci3r8e.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140126080627.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 26 Feb 2014 08:06:27 -0500")
Karl Dahlke <eklhad@comcast.net> 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
next prev parent reply other threads:[~2014-02-26 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 13:06 Karl Dahlke
2014-02-26 14:04 ` Chris Brannon [this message]
2014-02-26 14:10 Karl Dahlke
2014-02-26 17:17 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3ci3r8e.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).