Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: remi.letot@easynet.be (Rémi Letot)
Subject: Re: bbdb and searching
Date: Tue, 21 May 2002 14:04:23 +0200	[thread overview]
Message-ID: <87off9hflk.fsf@easynet.be> (raw)
In-Reply-To: <vaf1yc5rc6o.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> remi.letot@easynet.be (Rémi Letot) writes:
>
>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>>
>>> In Emacs from CVS, you can turn on unify-8859-on-decoding-mode and
>>> this will help somewhat because it reduces the number of times that ä
>>> from different charsets appears in your file.  
>>
>> Herm, unify-8859-on-decoding-mode and unify-8859-on-encoding-mode are
>> both on on my machine. And yet I still have different charsets in my
>> bbdb it seems.
>
> Hm.
>
>> Is there some way to convert everything in it to Latin-9 ?
>
> C-x C-f ~/.bbdb RET C-x RET f latin-9 RET C-x C-s

Didn't do the trick. Tried with latin-1 and latin-9, but Rémi doesn't
match my entry. I can't event find it with C-s in ~/.bbdb

Another idea ? :-)

With M-x bbdb I can search it with 'R.mi', but that's not very user
friendly :-)

>
>>> Work is currently in progress to change the internal encoding of
>>> Emacs from Mule to something based on Unicode (ie, Unicode with some
>>> extensions).  When this happens, all ä characters will be the same
>>> inside of Emacs.  Then the searching problem will be gone.  (It also
>>> means that Pavel's name will be affected, one way or another.)
>>
>> When will that be in a usable state ?
>
> Who knows?  I'm sure even the people doing the work don't know.  Such
> is (often) the nature of free software: people do the work when they
> have time.

Yep, I know that and in no way would criticize those people. I
actually would like to contribute something useful, but haven't found
it yet :-)

> But I can say that 21.3 is planned as a bugfix release.  Then people
>are working on 21.4.  And Emacs 22 will surely come after that.  So
>don't hold your breath.

That's the answer I wanted : imminent or not. Thanks, now I know I
have to find a way around that problem. *That* could be usefull :
write a howto for non us-ascii people when the problem is solved.

-- 
Rémi Letot


  reply	other threads:[~2002-05-21 12:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wutztdus.fsf@easynet.be>
     [not found] ` <vafd6vrhzrh.fsf@lucy.cs.uni-dortmund.de>
     [not found]   ` <87n0uvt636.fsf@easynet.be>
2002-05-20 14:06     ` Kai Großjohann
     [not found]       ` <1mlmaedfwx.fsf@Tempo.Update.UU.SE>
     [not found]         ` <vafy9ee96qj.fsf@lucy.cs.uni-dortmund.de>
2002-05-20 16:07           ` Fredrik Staxeng
     [not found]       ` <871yc6e62y.fsf@easynet.be>
2002-05-21 11:07         ` Kai Großjohann
2002-05-21 12:04           ` Rémi Letot [this message]
     [not found]             ` <vafelg5o9n0.fsf@lucy.cs.uni-dortmund.de>
2002-05-21 19:31               ` Rémi Letot
     [not found]                 ` <vafelg4771p.fsf@lucy.cs.uni-dortmund.de>
2002-05-22 18:37                   ` Robert Marshall
     [not found]                   ` <87hel084uh.fsf@easynet.be>
     [not found]                     ` <vaflmabdx8a.fsf@lucy.cs.uni-dortmund.de>
     [not found]                       ` <873cwj57c4.fsf@easynet.be>
2002-05-23 14:19                         ` Kai Großjohann
     [not found]                           ` <874rgy8sar.fsf@easynet.be>
2002-05-23 21:45                             ` Josh Huber
2002-05-24  9:45                             ` Kai Großjohann
2002-05-24 20:07                               ` Rémi Letot
2002-05-24 20:25                                 ` Erwan David

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=87off9hflk.fsf@easynet.be \
    --to=remi.letot@easynet.be \
    /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).