Andi,
Can you elaborate more, -1 is not very descriptive.
The code I have written for EggTranslations does support non-ascii file
paths.
However, the underlying setuptools API does not claim to support this.
Can you think of a case in an egg where a non-ascii file path is needed.
I would of course prefer to support any character set file path, however
is the return worth
the investment at this stage?
This is something that can be added later if it is deemed necessary.
I still need to look in to the zip format and libraries PJE is using.
If non-ascii file paths are supported, then long as the platform supports
the character set it should work fine.
PJE can elaborate more since he is the author of setuptools.
But again I question whether developers really need non-ascii file paths
in their
translation eggs.
-Brian
Andi Vajda wrote:
On Mon, 31 Jul 2006, Brian Kirsch wrote:
However, requiring only ASCII file paths in the egg is fine. I think
anything beyond that is merely a nice to have
feature and not a must have feature.
-1
Andi..
--
Brian Kirsch
Internationalization Architect/ Mail Service Engineer
Open Source Applications Foundation
543 Howard Street 5th Floor
San Francisco, CA 94105
http://www.osafoundation.org
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
