Only if you lack the forethought to abstract string functions and types in a header.
Basically, with Python 2.x, the default string type was ascii and there was a separate unicode type for unicode. With Python 3.x unicode is the default string type and there's a byte buffer type for everything else. When extension sources fail to differentiate between byte strings and unicode the migration becomes much more difficult. For translations, you certainly want unicode used for all strings in any event. If you abstract these types and functions in a header, and unicode used everywhere for strings, you'll be fine. As for the Python code, there's a 2to3 tool which can be run during compile to migrate automatically unless there's funky stuff going on (byte buffers and unicode strings used interchangeably). On Thu, Jan 8, 2009 at 11:16 AM, David Philippi <[email protected]> wrote: > > So you will get lots of trouble replacing string and t_string, keeping > translations working and so on. The scale of such a patch is called fork > IMHO. > >
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
