If we are to have BrailleBlaster used by people around the world, particularly in countries where the primary language is not English, it should be possible to localise BrailleBlaster. At the moment BrailleBlaster has some stuff in it to help support localisation, however this hasn't always been used and there are some hard coded strings. Also the localisation files which exist haven't always been maintained, they may contain strings which might not actually be used any more in the code. A good clean up of the localisation files and ensuring all strings use the localisation support would be a good start. There may be cases where complete localisation might require some changes to the localisation code (eg. good plurals support), but for now even getting to the point where all strings can be localised would be a significant improvement and we could deal with the perfecting it stuff later on.
If we are to have BrailleBlaster used by people around the world, particularly in countries where the primary language is not English, it should be possible to localise BrailleBlaster. At the moment BrailleBlaster has some stuff in it to help support localisation, however this hasn't always been used and there are some hard coded strings. Also the localisation files which exist haven't always been maintained, they may contain strings which might not actually be used any more in the code. A good clean up of the localisation files and ensuring all strings use the localisation support would be a good start. There may be cases where complete localisation might require some changes to the localisation code (eg. good plurals support), but for now even getting to the point where all strings can be localised would be a significant improvement and we could deal with the perfecting it stuff later on.