I'll make it a subtask, and make sure derbyall passes when I'm done. I'm not sure what you mean by "gotchas in the locale files," any tips would be appreciated; otherwise I'm going to focus on cleaning up the text and fixing any necessary diffs in test output.
Cheers, David Jean T. Anderson wrote: > David Van Couvering wrote: > >>I could do this; every time I talk to customers they hammer into me that >>clear and helpful error messages are key. > > > Users would definitely appreciate your contribution! > > >>It would *really* help if I knew which message texts were modified in >>the doc. Is it limited to the Derby-specific messages with SQLStates >>starting with "X"? > > > Unfortunately Jeff is on vacation, will be back June 6 if I remember > right. So all I know is what he posted to Jira. > > >>Would I submit this as an independent patch to the same JIRA item? Note > > > Or maybe open a sub task and submit a patch to that? > > My guess is there are additional things to watch out for; for example, > updating the tests to reflect the changed messages so derbyall passes. > Also, I don't know what gotchas might be out in the locale files -- > would be another thing to follow up on. Anything else, derby developers? > > >>also that I may find "bugs" in the messages that would require a redo of >>the documentation... > > > In my opinion, the docs (including any doc patches submitted) should be > changed to match the code. > > -jean > >
