Alex Blewitt wrote:
> On 06/02/07, Tim Ellison <[EMAIL PROTECTED]> wrote:
>> The pack200 code does have to be internationalized -- why would there be
>> an exception for that module?
>
> Mostly because it's a work-in-progress, and at present when I detect
> an error condition (or part of the parsing tree that I can't handle) I
> throw new Error("Not yet implemented"). In other words, it's a marker
> to let me know I need to go back there and fix it.
>
> These strings were internationalised into .properties files in an
> earlier change by others, and whilst 'real' messages should be
> internationalised when it's complete, they shouldn't be done so during
> development.
>
> There's also potentially some constants I've not marked with //
> NON-NLS at present, but like I said, it's a work in progress :-)
All our code is work-in-progress<g>, Why not internationalize the code
as you are developing it (leaving aside the not yet implemented
messages). So, for example, couldn't you externalize a number of the
strings in PopulationCodec ?
What if people offered to help by doing some of it with you?
Regards,
Tim
