help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: i18n search/replace with input methods latin-4-postfix and rfc1345


From: B.T. Raven
Subject: Re: i18n search/replace with input methods latin-4-postfix and rfc1345
Date: Wed, 16 Mar 2005 11:18:29 -0600

Thanks again, monsieur Monnier. I posted a note about my problem to
gnu.emacs.bug. As a forlorn hope, I changed my encoding of .emacs from
emacs-mule to utf-8 but it didn't make any difference. A fresh latin-4
character is still different from the same one after it has been saved
and revisited.
Although I downloaded the entire suite of cygwin packages (including cvs
and stunnel) I know how to use only the shell tools (grep, sed, sort,
etc) but these things aren't unicode aware and I couldn't conveniently
input strange characters from the command line anyway (if for instance I
wanted make changes with sed by looking at the emacs buffer in one
window and the command line in a Dos Window.

Ed.

"Stefan Monnier" <monnier@iro.umontreal.ca> wrote in message
877jk8kxtt.fsf-monnier+gnu.emacs.help@gnu.org">news:877jk8kxtt.fsf-monnier+gnu.emacs.help@gnu.org...
> >> > (unify-8859-on-decoding-mode 1)
> >>
> >> Good.
> >>
> >> >  '(unify-8859-on-encoding-mode t nil (ucs-tables))
> >>
> >> Good as well.  Except that the two do the same thing redundantly,
so
> > it's
> >> better to get rid of one of them.  I.e. if you like to configure
your
> > system
> >> with Custom, then keep the second, else keep the first.
>
> > They shouldn't do the same thing since one is for decoding and the
other
> > for encoding.
>
> Oops, sorry, I wasn't careful enough.
>
> > Anyway I think I'll stick with Custom since it's probably the less
error
> > prone method.  Apparently unify on encoding is safe but the other
one can
> > cause information loss.
>
> Indeed, but only in "unusual" situations (e.g. if you use encodings
like
> iso-2022).  And in your case, unification on decoding is exactly what
you
> need (provided you're not bumping into a bug that prevents it from
doing
> its job, of course).
>
> > I am using the NT build and am not comfortable compiling from
source. I
> > have cygwin running under MS win but have never tried to build
anything
> > with gcc.
>
> I think cygwin has a precompiled cygwin version of the CVS code.
>
>
>         Stefan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]