Well, most of the problems with internationalization on my projects are
interaction between the transport and ICQ. =/ So it's not something
that's actually common between the two. ICQ has some wackity ways of
handling encoding in some areas... sucks. ;D
That said, I do think it could benefit James and I to 'stablize' the base
(non ICQ/non AIM) code at some point. However, we haven't even really
seen each other online at the same time in a long time really. =/ My
prediction is that some point the stuff under src/ will be the same and
the stuff under src/legacy will be different. src/tlib is still
questionable as we work with Twisted on some things.
Daniel
--
"The most addictive drug in the world is music."
- The Lost Boyz
> Quoting Daniel Henninger <[EMAIL PROTECTED]>:
>> I'm afraid I'm not. I loath merged projects like that. Sorry to be a
>> party pooper.
>
> I don't think we need merging, really. We just need the common things to
> move
> into a project where they can be improved in one place, rather than all
> three
> projects veering off into their own directions.
>
> Maybe Twisted already has enough re-use... but when I hear things like
> internationalisation being fixed separately on each transport, I can't
> help but
> think that these projects are wasting a lot of time fixing the same
> problem
> multiple times.
>
> TX
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
>
>
