{5} Assigned, Active Tickets by Owner (Full Description) (4 matches)

It's time we started thinking about how we are going to handle internationalization.

On Windows, the project currently uses string resources (albeit without any other languages). This solution, however, is not portable.

Options:

1. Transition to a portable library such as GNU gettext. This is less work than it sounds since almost all string lookups are done via a utility function. This has the advantage that both Windows and Linux contributors can (relatively) easily submit changes in a single feature-rich format and we can make use of open source coverage tools to pinpoint what needs translating.
2. Use a portable library only for the Linux build, and have a script extract the string resources, similar to what we do with the version info but on a much bigger scale. We'll probably miss out on the more advanced features provided by gettext (and the like) due to incompatible ways of handling them.

I personally don't think we currently have enough strings to justify any time savings from the second option, but there's an out-of-the-box solution already available, we should still consider the option.

(Setting component to "Build System" since this is mostly build-time work that affects all parts of the project).

On some tracks, such as "Balls to This", distant rooms are getting rendered on top of distant 3D objects. This is visible at higher resolutions as a thin (usually 1-pixel tall) horizontal line.