RE: [nant-dev] L16N - resx files

2005-02-17 Thread Greco Giuseppe
How about somthing like 'NA1001' for errors and warnings. !--Build Error Strings -- data name=NA1001 valueCould not find a '{0}' file in '{1}'/value commentSome descriptive comment/comment /data What about this? Could be a valid alternative? Error messages: data

RE: [nant-dev] L16N - resx files

2005-02-17 Thread Greco Giuseppe
Hmm - well I'd like the keep the number in there - for errors/warnings at least. It will make finding the use of a given error message easier later on. Okay, but tell me which one of the following formats: data name=NA1001 valueCould not find a '{0}' file in '{1}'/value

Re: [nant-dev] L16N - resx files

2005-02-17 Thread Ian MacLean
Greco Giuseppe wrote: Hmm - well I'd like the keep the number in there - for errors/warnings at least. It will make finding the use of a given error message easier later on. Okay, but tell me which one of the following formats: data name=NA1001 valueCould not find a '{0}' file in

[nant-dev] L16N - resx files

2005-02-16 Thread Giuseppe Greco
Ian, attached to this email you'll find a tar.gz containing the RESX skeletons. Could you please integrate them into the project and import them into CVS? The next steps would be: 1. Decide a standard for string IDs 2. Decide who does what 3. Fill the RESX skeletons 4. Replace hardcoded