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: Fri, 24 May 2002 22:07:18 +0200	[thread overview]
Message-ID: <87k7ptz4w9.fsf@easynet.be> (raw)
In-Reply-To: <vafbsb5angp.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai writes:

> remi.letot@easynet.be (Rémi Letot) writes:
>
>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai writes:
>>
>>> remi.letot@easynet.be (Rémi Letot) writes:
>>>
>>>> Still no match :-(
>>>
>>> Then it's probably the new BBDB version.  Sorry for wasting your time.
>>
>> You didn't waste my time. Is the new bbdb version usable without
>> problems ? If you don't experience the problem I describe, I might
>> consider switching.
>
> Well, I encountered some problems related to bbdb-file-coding-system,
> but other than that, 2.35 seems worthwhile.
>
> I'm not exactly sure what were the "problems" I alluded to above.
> Might as well have been a mistake on my part.  I noticed something
> strange.  Maybe the strangeness was that BBDB asked me again and
> again to change Kai Großjohann to Kai Großjohann (from Latin-1 to
> Latin-9, I guess), even after I had accepted the change and saved
> BBDB.  Then I started to mess with the encoding myself, and of course
> now I'm responsible for any damage this might have caused.

That seems to be related to what I experience : my .bbdb file is
encoded in Latin-1 whatever I do, which prevents me from searching it
with Latin-9 characters.

You problem seems to be the same kind : your name always reverted to
Latin-1. 

Have you found a way around that ?

-- 
Rémi Letot


  reply	other threads:[~2002-05-24 20:07 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
     [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 [this message]
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=87k7ptz4w9.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).