| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
we have to convert strings to or from unicode. Given by Tokio
Kikuchi, modified slightly by Barry (if it's still broken, it's my
mistake).
|
| |
|
|
| |
files won't get imported, so do it explicitly here.
|
| |
|
|
| |
realname string.
|
| |
|
|
|
|
|
|
|
|
| |
better Japanese support. If we're converting to &#XYZ; form, use
chr() if the integer is < 256 otherwise use unichr(). If the
resulting joined string is already a Unicode, don't convert it.
uncanonstr(): Use u'' instead of '' as the string when s is None. The
Japanese codecs require a Unicode string as its argument, not an 8-bit
string.
|
| |
|
|
|
| |
we'll also strip their addresses from CC headers in the list copy.
This helps keep the CC lines from growing astronomically.
|
| |
|
|
|
|
|
|
|
|
| |
for the log file (defaults to iso-8859-1, which works for xterms and
xemacs buffers, although we may have to change this to us-ascii for
release). We try to open the log file using the codecs module so
output will be encoded by the proper stream writer.
I'm not 100% sure about these changes, but they seem right and work
for me.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
outgoing message, we must be sure to properly MIME encode the header,
otherwise if the name has non-ascii characters in it, we'll be sending
illegally formatted messages. So if the name has non-ascii characters
in it, we'll encode it using the character set of the language of the
outgoing message. Kludge: if the charset is us-ascii, we'll use
iso-8859-1 for a slightly wider utility (more non-ascii names can be
used in English lists).
Closes SF bug # 601082 by Tokio Kikuchi.
|
| |
|
|
|
| |
form, we need to convert it to a unicode string using the charset of
the language of the page.
|
| |
|
|
|
|
|
|
| |
need to convert it to a unicode string using the charset of the
language of the page.
options_page(): When printing the member's full name, be sure to
encode it to the charset of the language of the page.
|
| |
|
|
|
|
| |
showing the unsub'ing (or changing, or re-enabling) member's name, use
the version converted to the charset of the web page (or with &#XYZ;
conversion).
|
| |
|
|
|
| |
the version converted to the charset of the web page (or with &#XYZ;
conversion).
|
| |
|
|
|
|
|
|
|
|
| |
appropriate for the web page we're spitting out. Take the unicode
name string and uncanonstr() it so that it'll either be a string
encoded in the charset of the page, or an ascii string containing html
&#XYZ; entities.
change_options(): Take the full name string received in the web form
and canonstr() it so that we get a unicode string.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
page, which possibly could contain &#XYZ; entities, and convert the
string to a Unicode string using the charset of the language provided
in the argument list. As a practical kludge, if the charset is
us-ascii, we'll use iso-8859-1 instead (which allows a larger number
of non-ASCII names in English lists).
uncanonstr(): The opposite (sorta) of canonstr(), this takes a Unicode
string and returns the encoded string in the charset of the provided
language. If a strict conversion fails, then 8-bit characters are
converted to their &#XYZ; entities.
|
| |
|
|
|
| |
to make it clear that the full name (not RealName) will be a Python
Unicode string if it contains non-ASCII characters.
|
| |
|
|
|
|
|
| |
all the strings aren't properly encoded. To make life as easy as
possible, make sure that all the items in the split sequence are 8-bit
strings, encoded if necessary in the charset of the language given in
the argument list.
|
| |
|
|
|
| |
translated. Closes SF bug #596361 by Tokio Kikuchi, albeit with a
slightly different patch.
|
| |
|
|
| |
Les Niles.
|
| |
|
|
| |
language keys, but we already have that information in LC_DESCRIPTIONS.
|
| |
|
|
|
|
| |
problems where stray directories are added to $prefix/templates. We
already know all the acceptable language codes from LC_DESCRIPTIONS so
use that instead. Closes SF bug #605557 reported by Emilio Delgado.
|
| |
|
|
|
|
| |
problems where stray directories are added to $prefix/templates. We
already know all the acceptable language codes from LC_DESCRIPTIONS so
use that instead. Closes SF bug #605557 reported by Emilio Delgado.
|
| |
|
|
|
| |
subscribe_policy is 2 or 3. Fixes bug #605933 reported by Ron
Jarrell.
|
| |
|
|
| |
already a member. Fixes bug #605933 reported by Ron Jarrell.
|
| | |
|
| |
|
|
| |
607469 by John Parise.
|
| | |
|
| |
|
|
| |
existing X-Originally-To header before we place our own there.
|
| | |
|
| |
|
|
|
| |
it's not there. It could be that all the interesting bits get
executed as a side effect of the execfile().
|
| |
|
|
|
| |
adding some command line switches. Note that those switches must
appear /after/ the list name.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
named paths" is caused (somehow) by the distutils package not being
available. Some Linux distros package distutils in the python-devel
package instead of the main Python package (erroneously IMO --
distutils is critical).
These configure changes exit early if distutils isn't importable.
More detail is given in the README.LINUX file. Hopefully this will
eliminate this FAQ.
|
| | |
|
| |
|
|
|
|
| |
global opts are requested. This adds a __nonzero__() method to class
Global and tests for truth before doing the gmlist loop. Closes SF
patch #602084.
|
| | |
|
| | |
|
| |
|
|
| |
GNU version.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
mailman-developers. There's an inconsistent use of the MemberAdaptor
API -- authenticateMember() is never called. This change seems to
work just fine.
Also: whitespace normalization.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
that the digest may contain unparseable messages, e.g. with missing
start boundaries. Instead of crashing, such messages should simply be
ignored. If lax parsing can't grok it, it has a high likelihood of
being spam.
Specific changes here:
send_i18n_digests(): The end case is now that "msg is None", not
false, and if msg is the empty string, it was unparseable and we
should skip it.
|
| |
|
|
|
|
| |
the base class's .next() method will never raise them (it's factory
masks them). However, the end condition is now that "m is None"
instead of m being false.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that the digest may contain unparseable messages, e.g. with missing
start boundaries. Instead of crashing, such messages should simply be
ignored. If lax parsing can't grok it, it has a high likelihood of
being spam.
Specific changes here:
_safeparser(): New helper factory for PortableUnixMailbox, which
returns the empty string if a MessageParseError occurs. Note that ''
is used instead of None because the latter will stop the Mailbox's
default iterator (in Python 2.2).
Mailbox.__init__(): Use the _safeparser() function instead of
email.message_from_file().
scrubber(): We can use _safeparser() here and simply not scrub the
empty string return value.
|