[Babeldoc-devel] babeldoc/modules/core/config/i18n messages.properties,1.20,1.21

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/core/config/i18n
In directory sc8-pr-cvs1:/tmp/cvs-serv10999/modules/core/config/i18n

Modified Files:
	messages.properties 
Log Message:
Made some of the pipeline stage descriptions a whole log more descriptive

Index: messages.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/config/i18n/messages.properties,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -d -r1.20 -r1.21
*** messages.properties	14 Aug 2003 01:33:24 -0000	1.20
--- messages.properties	16 Aug 2003 01:23:27 -0000	1.21
***************
*** 220,223 ****
--- 220,224 ----
  100021=Write the "done" file when the document is written.  This can act as a flag for other disk scanning processes
  100024=Write the document to the FTP host
+ core.pipeline.stage.ftpwriter.desc=Write the document using the FTP protocol to an FTP server.  This will enable pipelines to distribute documents on the internet using this well supported protocol
  100025=FTP hostname or ip address
  100026=FTP username to login with
***************
*** 286,292 ****
  100089=default text for alt attribute
  100090=JTidy error - see logfile: {0}
! 100100=Null stage
! 100110=Route this document to a number of specified stages
! 100111=Stage name to route to if the script resolves to "true"
  100112=If this script resolves to true, then associated stages is routed
  100120=Write an item entry to an RSS Channel
--- 287,293 ----
  100089=default text for alt attribute
  100090=JTidy error - see logfile: {0}
! 100100=Null stage.  This do-nothing stage is useful in certain situations like a tracking placeholder or just a placeholder for some future pipeline stage.
! 100110=Route this document to a number of specified stages.  This stage would be used to specialize processing based on some criterion very much like an if-else statement.  Usually the criteria used would be an attribute on the document like time of processing, filename, etc but could be a script.  The nextStage complex parameter must evaluate to the literal 'true'.  If more than one of the nextStages resolves to true, then the document is routed to each of those stages.  If none of the matches are made, the regular nextStage configuration option is used.  This provides the 'else' part.
! 100111=Stage name to route to if the script resolves to 'true'.  Each of the matching nextStages will be routed.
  100112=If this script resolves to true, then associated stages is routed
  100120=Write an item entry to an RSS Channel
***************
*** 305,309 ****
  100133=Error writing: {0}
  100134=Regenerated RSS file: {0}
! 100140=Email the document using SMTP
  100141=The SMTP host to communicate with
  100142=The email address of the sender
--- 306,310 ----
  100133=Error writing: {0}
  100134=Regenerated RSS file: {0}
! 100140=Email the document using the SMTP protocol.  This will allow for documents to be transmitted via email to a number of recipients.  The document is normally the body of the email but could also be an attachment.
  100141=The SMTP host to communicate with
  100142=The email address of the sender
***************
*** 323,330 ****
  100210=Velocity templatize the document
  100211=Error templatizing the document
! 100220=Use XPath expressions to extract attributes from the document
  100221=The name of the xpath configuration option is the attribute to assign to the document
  100222=The results of the xpath expression is the value to assign to the attribute
! 100230=Split the XML document using xpath expressions.  This will result in a number of documents being forwarded to the next stage
  100231=Omit the XML PI declaration from the output document
  100232=Indent the output document
--- 324,331 ----
  100210=Velocity templatize the document
  100211=Error templatizing the document
! 100220=Use XPath expressions to extract nodes from the document and store them as attributes on the document.  This pipeline stage is widely use when data needs to be extracted from XML documents for router or calculation steps.  The extracted attributes can be quickly and easily obtained using velocity $document.get and from the scripting stages.  Routing decisions based on the document contents are also possible using this technique.
  100221=The name of the xpath configuration option is the attribute to assign to the document
  100222=The results of the xpath expression is the value to assign to the attribute
! 100230=Split the XML document using xpath expressions.  This will result in a number of documents being forwarded to the next stage.  This is useful when each of the split nodes represents a document that needs to be actioned.  An example would be splitting out each of the orders from an XML document that is a collection of orders.
  100231=Omit the XML PI declaration from the output document
  100232=Indent the output document
***************
*** 338,342 ****
  100270=Compress the document
  100271=Error during decompression
! 100289=Execute script during pipelining
  100290=Scripting language
  100291=Script to be executed
--- 339,343 ----
  100270=Compress the document
  100271=Error during decompression
! 100289=Execute a user supplied script.  This pipeline stage enables pipeline developers to create and manipulate documents in novel and unforeseen ways.
  100290=Scripting language
  100291=Script to be executed