This page is likely outdated. Visit the new documentation for updated content.
Support for editing .NET localization
MonoDevelop lacks support for localizing applications through standard .NET methods, instead opting for Mono specific GetText methods. .NET localization uses res/resx files like foo.res, foo.en-GB.res, foo.he.res to contain localized strings and System.Globalization.ResourceManager to access them. Support for these files would improve cross-platform internationalization.
Online database of common translation phrases
An online web service for sharing translations of common phrases in order to automate some parts of translations,
CIL Gettext Scanner
A gettext scanner that scans CIL binaries for arguments to calls to GetString. Would be more accurate, would work for all compiled managed languages, and could warn about passing concatenation of const strings and variables.
It could also follow call chains, so that any constant string that ends up at the GetString method would be localizable. This would enable things like attributes that run their arguments through gettext.
Some common methods that result in predictable string values, e.g. String.Concat, could also be handled.
ASP.NET Gettext Scanner
A gettext scanner for ASP.NET pages.
ASP.NET is tricky to parse an involves multiple languages. Probably the best way to do this is by combining the ASP.NET precompiler and the CIL gettext scanner.