Menu
▾
▴
babeldoc-devel
|
From: McDonald, B. <Bru...@ba...> - 2003-08-11 14:59:21
|
This certainly seems broken - I am looking into it now. -----Original Message----- From: David Glick [mailto:dg...@co...] Sent: Sunday, August 10, 2003 4:24 PM To: bab...@li... Subject: [Babeldoc-devel] Journal tool broken? Hello to the great and powerful list, I can't get the journal tool to do anything besides printUsage(), regardless of the command options I try. Have I forgotten to set something? Thanks, David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: McDonald, B. <Bru...@ba...> - 2003-08-11 17:34:32
|
Ok good - I will make the change. On another note, I am expanding the CallStage pipeline stage so that it can call another stage based on a test. If the test resolves true, then it calls otherwise nothing. -----Original Message----- From: David Glick [mailto:dg...@co...] Sent: Monday, August 11, 2003 1:24 PM To: bab...@li... Subject: Re: [Babeldoc-devel] Journal tool broken? Won't be a problem for me. I need the ticket number for testing, but it's not important to me how I get it (I actually didn't know where else to place it, so I took the easy route). David On Monday 11 August 2003 10:07 am, McDonald, Bruce wrote: > I have found the problem. it was in the move away from the ostermiller > utils CSV code. I have a fixed SimpleJournal.java which I will check in > tonight. > > Now, I have noticed that you have updated the processor so that it prints > the ticket number. I am not sure that this is a good idea (run the new > documentation pipeline to see why). It would be better just to print it > out from the Babeldoc process command just prior to actually processing the > document - is this going to be a problem for you? > > -----Original Message----- > From: David Glick [mailto:dg...@co...] > Sent: Monday, August 11, 2003 11:18 AM > To: bab...@li... > Subject: Re: [Babeldoc-devel] Journal tool broken? > > > Thanks, Bruce. With any luck, fixing this will also fix the journalbrowser > tool (did I mention that it didn't work for me, either?). > > David > > On Monday 11 August 2003 7:58 am, McDonald, Bruce wrote: > > This certainly seems broken - I am looking into it now. > > > > -----Original Message----- > > From: David Glick [mailto:dg...@co...] > > Sent: Sunday, August 10, 2003 4:24 PM > > To: bab...@li... > > Subject: [Babeldoc-devel] Journal tool broken? > > > > > > Hello to the great and powerful list, > > > > I can't get the journal tool to do anything besides printUsage(), > > regardless of the command options I try. Have I forgotten to set > > something? > > > > > > Thanks, > > > > David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: McDonald, B. <Bru...@ba...> - 2003-08-11 17:41:55
|
I have found the problem. it was in the move away from the ostermiller utils CSV code. I have a fixed SimpleJournal.java which I will check in tonight. Now, I have noticed that you have updated the processor so that it prints the ticket number. I am not sure that this is a good idea (run the new documentation pipeline to see why). It would be better just to print it out from the Babeldoc process command just prior to actually processing the document - is this going to be a problem for you? -----Original Message----- From: David Glick [mailto:dg...@co...] Sent: Monday, August 11, 2003 11:18 AM To: bab...@li... Subject: Re: [Babeldoc-devel] Journal tool broken? Thanks, Bruce. With any luck, fixing this will also fix the journalbrowser tool (did I mention that it didn't work for me, either?). David On Monday 11 August 2003 7:58 am, McDonald, Bruce wrote: > This certainly seems broken - I am looking into it now. > > -----Original Message----- > From: David Glick [mailto:dg...@co...] > Sent: Sunday, August 10, 2003 4:24 PM > To: bab...@li... > Subject: [Babeldoc-devel] Journal tool broken? > > > Hello to the great and powerful list, > > I can't get the journal tool to do anything besides printUsage(), > regardless of the command options I try. Have I forgotten to set > something? > > > Thanks, > > David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: David G. <dg...@co...> - 2003-08-11 17:19:46
|
Won't be a problem for me. I need the ticket number for testing, but it's not important to me how I get it (I actually didn't know where else to place it, so I took the easy route). David On Monday 11 August 2003 10:07 am, McDonald, Bruce wrote: > I have found the problem. it was in the move away from the ostermiller > utils CSV code. I have a fixed SimpleJournal.java which I will check in > tonight. > > Now, I have noticed that you have updated the processor so that it prints > the ticket number. I am not sure that this is a good idea (run the new > documentation pipeline to see why). It would be better just to print it > out from the Babeldoc process command just prior to actually processing the > document - is this going to be a problem for you? > > -----Original Message----- > From: David Glick [mailto:dg...@co...] > Sent: Monday, August 11, 2003 11:18 AM > To: bab...@li... > Subject: Re: [Babeldoc-devel] Journal tool broken? > > > Thanks, Bruce. With any luck, fixing this will also fix the journalbrowser > tool (did I mention that it didn't work for me, either?). > > David > > On Monday 11 August 2003 7:58 am, McDonald, Bruce wrote: > > This certainly seems broken - I am looking into it now. > > > > -----Original Message----- > > From: David Glick [mailto:dg...@co...] > > Sent: Sunday, August 10, 2003 4:24 PM > > To: bab...@li... > > Subject: [Babeldoc-devel] Journal tool broken? > > > > > > Hello to the great and powerful list, > > > > I can't get the journal tool to do anything besides printUsage(), > > regardless of the command options I try. Have I forgotten to set > > something? > > > > > > Thanks, > > > > David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |
|
From: David G. <dg...@co...> - 2003-08-11 15:15:53
|
Thanks, Bruce. With any luck, fixing this will also fix the journalbrowser tool (did I mention that it didn't work for me, either?). David On Monday 11 August 2003 7:58 am, McDonald, Bruce wrote: > This certainly seems broken - I am looking into it now. > > -----Original Message----- > From: David Glick [mailto:dg...@co...] > Sent: Sunday, August 10, 2003 4:24 PM > To: bab...@li... > Subject: [Babeldoc-devel] Journal tool broken? > > > Hello to the great and powerful list, > > I can't get the journal tool to do anything besides printUsage(), > regardless of the command options I try. Have I forgotten to set > something? > > > Thanks, > > David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |
Thanks for helping keep SourceForge clean.
X