On May 3, 2009, at 8:49 AM, Shawn Willden wrote: > On Saturday 02 May 2009 08:01:45 pm Zooko O'Whielacronx wrote: >> The best thing to do for Tahoe is likely to define valid UTF-8 as the >> encoding for all Tahoe file names and to raise an error when people >> try to stick anything else in there.
Actually I didn't write that -- one of my interlocutors from python- dev did. To be clear, my current plan is like this: http://allmydata.org/trac/tahoe/ticket/534#comment:66 > I suppose one way to handle it in interactive mode is try try all > available > decoders and show the user a list of the results from all that > succeeded, > then let them pick the one that looks right, assuming they know, > and assuming > the current font has the glyphs required to display the correct > decoding. I like this idea. Our current scheme involves preserving enough information in the metadata that a tool like this could later be useful. Regards, Zooko _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
