dims 01/06/21 06:09:03
Modified: . build.xml
xdocs actions.xml docs-book.xml i18n.xml site-book.xml
Removed: src/org/apache/cocoon/acting README
webapp/docs/samples/stream ReadMeAdd.txt telnet.txt
webapp/i18n/translations readme.txt
Log:
Cleaning up docs:
- Added doc for StreamGenerator based on Kinga's Readme
- Moved README under acting to xdocs
- Added stuff from i18n\translations\readme.txt into i18n.xml
Revision Changes Path
1.18 +1 -0 xml-cocoon2/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/build.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- build.xml 2001/06/15 18:07:58 1.17
+++ build.xml 2001/06/21 13:08:56 1.18
@@ -471,6 +471,7 @@
<include name="**/*.gif"/>
<include name="**/*.png"/>
<include name="**/*.jpg"/>
+ <include name="**/*.txt"/>
</fileset>
</copy>
1.3 +3 -2 xml-cocoon2/xdocs/actions.xml
Index: actions.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/actions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- actions.xml 2001/05/29 20:13:12 1.2
+++ actions.xml 2001/06/21 13:09:00 1.3
@@ -20,7 +20,7 @@
at run time, we surmised that sometimes we need to adjust the pipeline
based on runtime parameters, or even the contents of the Request parameter.
Without the use of Actions this would make the sitemap almost
- incomprehensable.
+ incomprehensable.
</p>
<p>
The quick and dirty definition of an Action is "a Sitemap Component that
@@ -29,7 +29,8 @@
form processing, and even dynamic navigation. The Action is
differentiated from the other sitemap components (Generator, Transformer,
Serializer, and Reader) primarily by the fact that it does not produce
- any display data.
+ any display data. <link href="actions.txt">actions.txt</link> contains
+ excerpts from discussions on the cocoon-dev@ mailing list regarding Actions.
</p>
<s2 title="When to use an Action instead of XSP">
<p>
1.11 +1 -0 xml-cocoon2/xdocs/docs-book.xml
Index: docs-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/docs-book.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- docs-book.xml 2001/06/21 11:07:59 1.10
+++ docs-book.xml 2001/06/21 13:09:00 1.11
@@ -19,6 +19,7 @@
<page id="extending" label="Extending C2" source="extending.xml"/>
<page id="avalon" label="Avalon" source="avalon.xml"/>
<page id="i18n" label="Internationalization" source="i18n.xml"/>
+ <page id="stream" label="Stream Generator" source="stream-generator.xml"/>
<separator/>
<page id="xsp" label="XSP" source="xsp.xml"/>
<page id="xsp-internals" label="XSP Internals" source="xsp-internals.xml"/>
1.5 +50 -0 xml-cocoon2/xdocs/i18n.xml
Index: i18n.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/i18n.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- i18n.xml 2001/06/15 15:01:20 1.4
+++ i18n.xml 2001/06/21 13:09:01 1.5
@@ -292,6 +292,56 @@
bug is fixed.
</note>
</s1>
+ <s1 title="Usage Pattern for Dictionary Generator Stylesheet">
+ <p>
+ Desciption is given for a real world example:
+ To correct/add Spanish translation in/to an existing dictionary:
+ </p>
+ <s2 title="Key generation">
+ <p>
+ Generate a dictionary with keys and placeholders for Spanish
translations.
+ Optionaly, for one of the languages existing translations can be kept.
+ To do it set stylesheet params (manually in stylesheet or in
command-line):
+ mode = keys (indicates, that only keys must be in result)
+ new-lang = es (language to be added)
+ keep-lang = en (language to be kept in result, for convenience)
+
+ Command line for Xalan (Of course, Xerces and Xalan must be in your
classpath):
+ </p>
+ <source><![CDATA[
+java org.apache.xalan.xslt.Process -IN simple_dict.xml -XSL merge.xsl -OUT
simple_dict_es.xml -PARAM mode keys -PARAM new-lang es -PARAM keep-lang en
+]]></source>
+ <p>
+ This will create a file simple_dict_es.xml with entries, keys and
placeholders.
+ </p>
+ </s2>
+ <s2 title="Translation">
+ <p>
+ Replace placeholders with translation according to the keys or original
+ translations, if they were kept during generation.
+ </p>
+ </s2>
+ <s2 title="Add to the original dictionary">
+ <p>
+ (Note. This step will be unnecessary when multiple dictionary
+ support will be implemented. Hope, this will be soon)
+
+ Use the same stylesheet for this purpose with this params:
+ </p>
+ <source><![CDATA[
+mode = merge
+new-lang = es
+new-dict = simple_dict_es.xml
+]]></source>
+
+ <p>
+ Command line for Xalan:
+ </p>
+ <source><![CDATA[
+java org.apache.xalan.xslt.Process -IN simple_dict.xml -XSL merge.xsl -OUT
simple_dict_new.xml -PARAM mode merge -PARAM new-lang es -PARAM new-dict
simple_dict_es.xml
+]]></source>
+ </s2>
+ </s1>
<s1 title="Finally">
<s2 title="To be done">
<ul>
1.14 +1 -0 xml-cocoon2/xdocs/site-book.xml
Index: site-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/site-book.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- site-book.xml 2001/06/21 11:08:00 1.13
+++ site-book.xml 2001/06/21 13:09:01 1.14
@@ -23,6 +23,7 @@
<page id="extending" label="Extending C2" source="extending.xml"/>
<page id="avalon" label="Avalon" source="avalon.xml"/>
<page id="i18n" label="Internationalization" source="i18n.xml"/>
+ <page id="stream" label="Stream Generator" source="stream-generator.xml"/>
<separator/>
<page id="xsp" label="XSP" source="xsp.xml"/>
<page id="xsp-internals" label="XSP Internals" source="xsp-internals.xml"/>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
