You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2014/07/24 18:27:22 UTC
svn commit: r917299 - in /websites/staging/xmlgraphics/trunk/content: ./
fop/1.0/events.html fop/1.1/events.html fop/trunk/events.html
Author: buildbot
Date: Thu Jul 24 16:27:21 2014
New Revision: 917299
Log:
Staging update by buildbot for xmlgraphics
Modified:
websites/staging/xmlgraphics/trunk/content/ (props changed)
websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 24 16:27:21 2014
@@ -1 +1 @@
-1613173
+1613178
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html Thu Jul 24 16:27:21 2014
@@ -548,17 +548,17 @@ $(document).ready(function () {
[ (See position {loc})| (See { #gatherContextInfo})| (No context info available)]
<span class="nt"></message></span>
<span class="nt"><message</span> <span class="na">key=</span><span class="s">"org.apache.fop.render.rtf.RTFEventProducer.explicitTableColumnsRequired"</span><span class="nt">></span>
- RTF output requires that all table-columns for a table are defined. Output will be incorrect.{{locator}}
+ RTF output requires that all table-columns for a table are defined. Output will be incorrect.
<span class="nt"></message></span>
<span class="nt"><message</span> <span class="na">key=</span><span class="s">"org.apache.fop.render.rtf.RTFEventProducer.ignoredDeferredEvent"</span><span class="nt">></span>
- Ignored deferred event for {node} ({start,if,start,end}).{{locator}}
+ Ignored deferred event for {node} ({start,if,start,end}).
<span class="nt"></message></span>
<span class="nt"></catalogue></span>
</pre></div>
<p>The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is <code>org.apache.fop.util.text.AdvancedMessageFormat</code> which is more powerful than the <code>MessageFormat</code> classes provided by the Java class library (<code>java.util.text</code> package).</p>
-<p>"locator" is a template that is reused by the other message templates by referencing it through "{{locator}}". This is some kind of include command.</p>
+<p>"locator" is a template that is reused by the other message templates by referencing it through "". This is some kind of include command.</p>
<p>Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the <code>toString()</code> method to turn the object into a string, unless there is an <code>ObjectFormatter</code> registered for that type (there's an example for <code>org.xml.sax.Locator</code>).</p>
<p>The single curly braces pattern supports additional features. For example, it is possible to do this: "{start,if,start,end}". "if" here is a special field modifier that evaluates "start" as a boolean and if that is true returns the text right after the second comma ("start"). Otherwise it returns the text after the third comma ("end"). The "equals" modifier is similar to "if" but it takes as an additional (comma-separated) parameter right after the "equals" modifier, a string that is compared to the value of the variable. An example: {severity,equals,EventSeverity:FATAL,,some text} (this adds "some text" if the severity is not FATAL).</p>
<p>Additional such modifiers can be added by implementing the <code>AdvancedMessageFormat$Part</code> and <code>AdvancedMessageFormat$PartFactory</code> interfaces.</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html Thu Jul 24 16:27:21 2014
@@ -548,17 +548,17 @@ $(document).ready(function () {
[ (See position {loc})| (See { #gatherContextInfo})| (No context info available)]
<span class="nt"></message></span>
<span class="nt"><message</span> <span class="na">key=</span><span class="s">"org.apache.fop.render.rtf.RTFEventProducer.explicitTableColumnsRequired"</span><span class="nt">></span>
- RTF output requires that all table-columns for a table are defined. Output will be incorrect.{{locator}}
+ RTF output requires that all table-columns for a table are defined. Output will be incorrect.
<span class="nt"></message></span>
<span class="nt"><message</span> <span class="na">key=</span><span class="s">"org.apache.fop.render.rtf.RTFEventProducer.ignoredDeferredEvent"</span><span class="nt">></span>
- Ignored deferred event for {node} ({start,if,start,end}).{{locator}}
+ Ignored deferred event for {node} ({start,if,start,end}).
<span class="nt"></message></span>
<span class="nt"></catalogue></span>
</pre></div>
<p>The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is <code>org.apache.fop.util.text.AdvancedMessageFormat</code> which is more powerful than the <code>MessageFormat</code> classes provided by the Java class library (<code>java.util.text</code> package).</p>
-<p>"locator" is a template that is reused by the other message templates by referencing it through "{{locator}}". This is some kind of include command.</p>
+<p>"locator" is a template that is reused by the other message templates by referencing it through "". This is some kind of include command.</p>
<p>Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the <code>toString()</code> method to turn the object into a string, unless there is an <code>ObjectFormatter</code> registered for that type (there's an example for <code>org.xml.sax.Locator</code>).</p>
<p>The single curly braces pattern supports additional features. For example, it is possible to do this: "{start,if,start,end}". "if" here is a special field modifier that evaluates "start" as a boolean and if that is true returns the text right after the second comma ("start"). Otherwise it returns the text after the third comma ("end"). The "equals" modifier is similar to "if" but it takes as an additional (comma-separated) parameter right after the "equals" modifier, a string that is compared to the value of the variable. An example: {severity,equals,EventSeverity:FATAL,,some text} (this adds "some text" if the severity is not FATAL).</p>
<p>Additional such modifiers can be added by implementing the <code>AdvancedMessageFormat$Part</code> and <code>AdvancedMessageFormat$PartFactory</code> interfaces.</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html Thu Jul 24 16:27:21 2014
@@ -548,17 +548,17 @@ $(document).ready(function () {
[ (See position {loc})| (See { #gatherContextInfo})| (No context info available)]
<span class="nt"></message></span>
<span class="nt"><message</span> <span class="na">key=</span><span class="s">"org.apache.fop.render.rtf.RTFEventProducer.explicitTableColumnsRequired"</span><span class="nt">></span>
- RTF output requires that all table-columns for a table are defined. Output will be incorrect.{{locator}}
+ RTF output requires that all table-columns for a table are defined. Output will be incorrect.
<span class="nt"></message></span>
<span class="nt"><message</span> <span class="na">key=</span><span class="s">"org.apache.fop.render.rtf.RTFEventProducer.ignoredDeferredEvent"</span><span class="nt">></span>
- Ignored deferred event for {node} ({start,if,start,end}).{{locator}}
+ Ignored deferred event for {node} ({start,if,start,end}).
<span class="nt"></message></span>
<span class="nt"></catalogue></span>
</pre></div>
<p>The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is <code>org.apache.fop.util.text.AdvancedMessageFormat</code> which is more powerful than the <code>MessageFormat</code> classes provided by the Java class library (<code>java.util.text</code> package).</p>
-<p>"locator" is a template that is reused by the other message templates by referencing it through "{{locator}}". This is some kind of include command.</p>
+<p>"locator" is a template that is reused by the other message templates by referencing it through "". This is some kind of include command.</p>
<p>Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the <code>toString()</code> method to turn the object into a string, unless there is an <code>ObjectFormatter</code> registered for that type (there's an example for <code>org.xml.sax.Locator</code>).</p>
<p>The single curly braces pattern supports additional features. For example, it is possible to do this: "{start,if,start,end}". "if" here is a special field modifier that evaluates "start" as a boolean and if that is true returns the text right after the second comma ("start"). Otherwise it returns the text after the third comma ("end"). The "equals" modifier is similar to "if" but it takes as an additional (comma-separated) parameter right after the "equals" modifier, a string that is compared to the value of the variable. An example: {severity,equals,EventSeverity:FATAL,,some text} (this adds "some text" if the severity is not FATAL).</p>
<p>Additional such modifiers can be added by implementing the <code>AdvancedMessageFormat$Part</code> and <code>AdvancedMessageFormat$PartFactory</code> interfaces.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org