Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #91436 > unrolled thread

Re: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd)

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd) Laura Creighton <lac@openend.se> - 2015-05-29 10:41 +0200

#91436 — Re: Fwd: Lossless bulletproof conversion to unicode (backslashing) (fwd)

In a message of Fri, 29 May 2015 11:05:07 +0300, anatoly techtonik writes:

>Added Mailman to my suxx tracker:
>https://github.com/techtonik/suxx-tracker#mailman

You are damning the wrong piece of software -- this is not a problem
with mailman; mailman doesn't care at all what software you use to
read mail and reply to it with.  The problem is with the various
readers and repliers that people are using.  In particular, people on
the other side of one the usenet -> python-list gateway may not be seeing
this as mail at all, or sending their replies as mail.

But back to your original problem.

I still don't understand why you need to go from some lossless
representation of your filename, back to the original.  You start
with the binary version of the filename  -- a series of bytes which
turns out to be good Cyrillic text, but could be anything.  You store
that as the first so many bytes of your file. If ever you need to have
the original representation of your filename, you already have it,
right there, by reading the first so many bytes of your file.  Why
care about what the user sees as a filename?

Laura

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web