Re: Strange behaviour with identity.sl and accented characters

On Nov 24, 2007 6:49 AM, John E. Davis <[email protected]> wrote:
> Rudy Taraschi <[email protected]> wrote:
> > Using the latest identity.sl macro, everything is fine until you get
> > to an identity that has an accented character such as "é" in the
> > signoff_string.  When entering a group that uses a signoff_string with
> > an accented characer, slrn throws a "signoff_string is not a valid
> > variable name" error.  This used to work perfectly in 0.9.8.1pl1.
>
> What are you using for the "config" charset?  Are you running in a
> UTF-8 locale?  When in UTF-8 mode, the interpreter assumes that all
> strings are encoded as UTF-8.  Are you using UTF-8 in your slang
> files?  Also, how are you representing é in your .sl file?  As é, or
> \xE9, \x{E9}?

Being an English speaking North American, I've never messed with
charsets or locales, and when I hear things like UTF-8, my eyes glaze
over.  Due to my lack of knowledge on locales and charsets, I really
have no clue what you're asking, but everything under locale saye
en_US, and I can't find any charset definitions in env or .slrnrc.  If
that doesn't answer your questions, please tell me what to look for
specifically.

I'm representing my é as é, not \xE9 or \xE9}

--
R/T

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/