Menu
▾
▴
[Babeldoc-devel] babeldoc/modules/core/config/i18n messages.properties,1.29,1.30
|
From: bruce m. <tr...@us...> - 2004-08-06 18:46:05
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/config/i18n In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv24050/modules/core/config/i18n Modified Files: messages.properties Log Message: documentation, javadoc and formatting here. Index: messages.properties =================================================================== RCS file: /cvsroot/babeldoc/babeldoc/modules/core/config/i18n/messages.properties,v retrieving revision 1.29 retrieving revision 1.30 diff -C2 -d -r1.29 -r1.30 *** messages.properties 28 Jul 2004 21:44:18 -0000 1.29 --- messages.properties 6 Aug 2004 18:45:56 -0000 1.30 *************** *** 231,235 **** 100032=Could not login into ftp server 100033=Using the java.beans.XMLDecoder object to unpersist the document contents in Java objects ! 100034=Format the document using JTidy 100035=default indentation 100036=default wrap margin --- 231,235 ---- 100032=Could not login into ftp server 100033=Using the java.beans.XMLDecoder object to unpersist the document contents in Java objects ! 100034=Format the pipeline document using JTidy. This is used to "clean-up" HTML documents into well-formed documents. 100035=default indentation 100036=default wrap margin *************** *** 319,328 **** 100150=Error setting attachments 100151=The mail format - text/plain or text/html - Deafult is text/plain ! 100170=Send this document to a tcp/ip socket 100171=The name of the host 100172=The ip address of the host 100173=The port number 100174=Neither host ip or host name provided ! 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. --- 319,328 ---- 100150=Error setting attachments 100151=The mail format - text/plain or text/html - Deafult is text/plain ! 100170=Send the pipeline document contents to a tcp/ip socket. This is useful for low-level operations. 100171=The name of the host 100172=The ip address of the host 100173=The port number 100174=Neither host ip or host name provided ! 100210=This stage uses Velocity to templatize the document. The results of the operation will replace the original template. 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. *************** *** 335,343 **** 100250=Transform the document using XSL 100251=The name of the XSL to convert the document ! 100260=Compress the document 100261=Compression type (zip or gzip) 100262=Error during compression 100263=Invalid compression type: {0} ! 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. --- 335,343 ---- 100250=Transform the document using XSL 100251=The name of the XSL to convert the document ! 100260=Compress the document using either zip or gzip compression. **EXPERIMENTAL** 100261=Compression type (zip or gzip) 100262=Error during compression 100263=Invalid compression type: {0} ! 100270=Decompress the document using either zip or gzip compression **EXPERIMENTAL** 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. *************** *** 369,373 **** 100315=mail subject not specified ! core.pipeline.stage.domify.desc=Domify the document and save as an attribute core.pipeline.stage.domify.validate=Validate the XML. Default is false. core.pipeline.stage.domify.schema=The schema file to validate against --- 369,373 ---- 100315=mail subject not specified ! core.pipeline.stage.domify.desc=Domify the document contents (assumed to be XML) and save as an attribute on the pipeline document. core.pipeline.stage.domify.validate=Validate the XML. Default is false. core.pipeline.stage.domify.schema=The schema file to validate against *************** *** 378,383 **** core.pipeline.stage.callstage.discard=Discard the pipeline document from the called stage. ! core.pipeline.stage.enrich.desc=Adds attributes to the document. The value can be a velocity script. ! core.pipeline.stage.filewriter.desc=Writes the document to a disk file. The contents are written as binary or text data depending on the binary flag on the document. core.pipeline.stage.xslTransform.desc=Transform the document (has to be XML) using this XSL script. The script can access all of the babeldoc internals via a number of parameters. The parameters (accessed through the xsl:param element) which are always placed in the transformer are: pipelinestage and document. Other parameters may be placed on the transformer using the param option. --- 378,383 ---- core.pipeline.stage.callstage.discard=Discard the pipeline document from the called stage. ! core.pipeline.stage.enrich.desc=Adds attributes to the document. The value of the attribute can be a constant value or a velocity script. ! core.pipeline.stage.filewriter.desc=Writes the document to a disk file. The contents are written as binary or text data depending on the binary flag on the document. When the pipeline document has been written to disk, this stage can optionally create a 'done' file which could act as a flag file for external processes indicating that the output file is completely written. core.pipeline.stage.xslTransform.desc=Transform the document (has to be XML) using this XSL script. The script can access all of the babeldoc internals via a number of parameters. The parameters (accessed through the xsl:param element) which are always placed in the transformer are: pipelinestage and document. Other parameters may be placed on the transformer using the param option. *************** *** 387,391 **** core.pipeline.stage.xslTransform.nodoc=The input document to this pipeline stage has zero length. The pipeline stage requires a valid XML document for processing. ! core.pipeline.stage.externalapplication.description=This pipeline stage allows for external applications to be run. Optionally the pipeline document is piped to the application. core.pipeline.stage.externalapplication.opt.application=Full path to the application to run core.pipeline.stage.externalapplication.opt.pipeout=Pipe the current document to the script - the script must fully accept the stardard input otherwise an exception is thrown. Boolean default is false. --- 387,391 ---- core.pipeline.stage.xslTransform.nodoc=The input document to this pipeline stage has zero length. The pipeline stage requires a valid XML document for processing. ! core.pipeline.stage.externalapplication.description=This pipeline stage allows for external applications to be run. Optionally the pipeline document contents is piped to the application as standard input or the output of the application can be read as a new pipeline document. core.pipeline.stage.externalapplication.opt.application=Full path to the application to run core.pipeline.stage.externalapplication.opt.pipeout=Pipe the current document to the script - the script must fully accept the stardard input otherwise an exception is thrown. Boolean default is false. *************** *** 401,406 **** core.pipeline.stageinfo.stageType=Type of pipeline stage core.pipeline.stageinfo.nextStage=Name of the next stage in pipeline or null if this is the last stage. ! core.pipeline.stageinfo.ignored=If this is set then this stage is ignored? ! core.pipeline.stageinfo.tracked=If this is set then this stage is tracked? core.pipeline.stageinfo.encoding=Encoding of resulting document. This is used for text documents. Default is system file.encoding core.pipeline.stageinfo.error.complex=Can't apply pipeline stage configuration data to non-complex option --- 401,406 ---- core.pipeline.stageinfo.stageType=Type of pipeline stage core.pipeline.stageinfo.nextStage=Name of the next stage in pipeline or null if this is the last stage. ! core.pipeline.stageinfo.ignored=If this is set then this stage is ignored - the pipeline document is simply passed, unprocessed, to the next stage. Useful to quickly disable parts of a pipeline. ! core.pipeline.stageinfo.tracked=If this is set then this stage is tracked - the pipeline document is written to the journal. core.pipeline.stageinfo.encoding=Encoding of resulting document. This is used for text documents. Default is system file.encoding core.pipeline.stageinfo.error.complex=Can't apply pipeline stage configuration data to non-complex option |
