public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ross A. Osborn <rosborn@motorola.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [OT] character sets
Date: Thu, 28 Oct 2004 09:11:04 -0400	[thread overview]
Message-ID: <20041028131104.GE7377@motorola.com> (raw)
In-Reply-To: <371748FC-287F-11D9-9DB4-000A95A5473A@rungie.com>

On Wed, Oct 27, 2004 at 06:18:03PM -0700, Craig Hughes wrote:
> On Oct 27, 2004, at 3:19 PM, Dan Poirot wrote:
> 
> >>-----Original Message-----
> >>
> >>Not sure how one would do this if one is Chinese and using
> >>hotmail for email...  In the 21st century one might suggest
> >>that if a base64-encoded message in a non-western character
> >>set is unreadable, the problem is on the receiving side not
> >>the sending side.
> >>
> >>C
> >
> >
> >...so perhaps you would prefer if Wolfgand responded to the list in 
> >German
> >calligraphy script in the form of a 10 megabyte TIFF file?
> >
> >Hard to use 'grep' on that...
> 
> Looks, if your mail-searching tool doesn't decode base64 before doing 
> its search, then your mail-searching tool is broken.  If your mailing 
> list archive tool won't map character sets for you so that "foo" 
> matches the representation of "foo" in some oddball character set, then 
> your mailing list archive tool is broken.  And if you want to search an 
> un-indexed mail spool which hasn't been QP/base64/uuencode/MIME decoded 
> using grep, then you should seriously look into the "formail" utility 
> which comes as part of the procmail package.  You can then apply MIME 
> transforms on each message in your un-indexed file before piping to 
> grep.  Of course it'll be slower than an amputee sloth, but hey, if you 
> want to search large archives quickly, then index them.
> 
> Look, ultimately, Wolfgang gets to make the rules for his list, and I'm 
> not suggesting otherwise, but really, when the only reason you choose 
> to not read someone's email message asking for help is because your 
> email app is broken, it seems a little bit rude to suggest that the 
> problem is on the other end.

I don't see it as being rude at all.  It seems like your argument is
that things should be made easier on the users by making things harder
on Wolfgang.  If the business of the list is conducted in English
I don't see why anybody needs to use base64 encoding.  If it makes
things easier for Wolfgang it seems like a very simple thing to ask from
the users.

Ross

      reply	other threads:[~2004-10-28 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041028010516.E29D21955E8@belphegore.hughes-family.org>
2004-10-28  1:18 ` [U-Boot-Users] [OT] character sets Craig Hughes
2004-10-28 13:11   ` Ross A. Osborn [this message]

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=20041028131104.GE7377@motorola.com \
    --to=rosborn@motorola.com \
    --cc=u-boot@lists.denx.de \
    /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