diff options
Diffstat (limited to 'data/doc/manuals_generated/sisu_manual/sisu_manual/faq.html')
| -rw-r--r-- | data/doc/manuals_generated/sisu_manual/sisu_manual/faq.html | 284 |
1 files changed, 142 insertions, 142 deletions
diff --git a/data/doc/manuals_generated/sisu_manual/sisu_manual/faq.html b/data/doc/manuals_generated/sisu_manual/sisu_manual/faq.html index 0c9e9fed..e094d7e5 100644 --- a/data/doc/manuals_generated/sisu_manual/sisu_manual/faq.html +++ b/data/doc/manuals_generated/sisu_manual/sisu_manual/faq.html @@ -23,7 +23,7 @@ <meta name="dc.language" content="English" /> <meta name="dc.rights" content="Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3" /> - <meta name="generator" content="SiSU 0.59.0 of 2007w38/0 (2007-09-23) (n*x and Ruby!)" /> + <meta name="generator" content="SiSU 0.59.1 of 2007w39/2 (2007-09-25) (n*x and Ruby!)" /> <link rel="generator" href="http://www.jus.uio.no/sisu" /> <link rel="shortcut icon" href="../_sisu/image/rb7.ico" /> @@ -192,7 +192,7 @@ </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 1925 + 1927 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> @@ -205,443 +205,421 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <h1 class="norm" id="o2011"><a name="2011" /> + <h1 class="norm" id="o2013"><a name="2013" /> 44. FAQ - Frequently Asked/Answered Questions <a name="44"></a> </h1> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2011 + 2013 </p> </td></tr> </table><h5 class="subtoc"> - <a href="#2012"> + <a href="#2014"> <i>44.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? </i> </a> </h5><h5 class="subtoc"> - <a href="#2016"> + <a href="#2018"> <i>44.2 I cannot find my output, where is it? </i> </a> </h5><h5 class="subtoc"> - <a href="#2024"> + <a href="#2026"> <i>44.3 I do not get any pdf output, why? </i> </a> </h5><h5 class="subtoc"> - <a href="#2029"> + <a href="#2031"> <i>44.4 Where is the latex (or some other interim) output? </i> </a> </h5><h5 class="subtoc"> - <a href="#2036"> + <a href="#2038"> <i>44.5 Why isn't SiSU markup XML </i> </a> </h5><h5 class="subtoc"> - <a href="#2044"> + <a href="#2046"> <i>44.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? </i> </a> </h5><h5 class="subtoc"> - <a href="#2053"> + <a href="#2055"> <i>44.7 How do I create GIN or GiST index in Postgresql for use in SiSU </i> </a> </h5><h5 class="subtoc"> - <a href="#2071"> + <a href="#2073"> <i>44.8 Where is version 1.0? </i> </a> </h5><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <a name="h44.1" id="h44.1"></a> - <p class="bold" id="o2012"><a name="2012" /> + <p class="bold" id="o2014"><a name="2014" /> 44.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2012 + 2014 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2013"><a name="2013" /> + <p class="norm" id="o2015"><a name="2015" /> Try the following rune: </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2013 + 2015 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2014"><a name="2014" /> + <li class="bullet" id="o2016"><a name="2016" /> sisu -W </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2014 + 2016 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2015"><a name="2015" /> + <p class="norm" id="o2017"><a name="2017" /> This should start the ruby webserver. It should be done after having produced some output as it scans the output directory for what to serve. </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2015 + 2017 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <a name="h44.2" id="h44.2"></a> - <p class="bold" id="o2016"><a name="2016" /> + <p class="bold" id="o2018"><a name="2018" /> 44.2 I cannot find my output, where is it? </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2016 + 2018 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2017"><a name="2017" /> + <p class="norm" id="o2019"><a name="2019" /> The following should provide help on output paths: </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2017 + 2019 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2018"><a name="2018" /> + <li class="bullet" id="o2020"><a name="2020" /> sisu --help env </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2018 + 2020 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2019"><a name="2019" /> + <li class="bullet" id="o2021"><a name="2021" /> sisu -V [same as the previous command] </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2019 + 2021 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2020"><a name="2020" /> + <li class="bullet" id="o2022"><a name="2022" /> sisu --help directory </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2020 + 2022 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2021"><a name="2021" /> + <li class="bullet" id="o2023"><a name="2023" /> sisu --help path </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2021 + 2023 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2022"><a name="2022" /> + <li class="bullet" id="o2024"><a name="2024" /> sisu -U [filename] </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2022 + 2024 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2023"><a name="2023" /> + <li class="bullet" id="o2025"><a name="2025" /> man sisu </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2023 + 2025 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <a name="h44.3" id="h44.3"></a> - <p class="bold" id="o2024"><a name="2024" /> + <p class="bold" id="o2026"><a name="2026" /> 44.3 I do not get any pdf output, why? </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2024 + 2026 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2025"><a name="2025" /> + <p class="norm" id="o2027"><a name="2027" /> <b>SiSU</b> produces LaTeX and pdflatex is run against that to generate pdf files. </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2025 + 2027 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2026"><a name="2026" /> + <p class="norm" id="o2028"><a name="2028" /> If you use <b>Debian</b> the following will install the required dependencies </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2026 + 2028 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2027"><a name="2027" /> + <li class="bullet" id="o2029"><a name="2029" /> aptitude install sisu-pdf </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2027 + 2029 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2028"><a name="2028" /> + <p class="norm" id="o2030"><a name="2030" /> the following packages are required: tetex-bin, tetex-extra, latex-ucs </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2028 + 2030 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <a name="h44.4" id="h44.4"></a> - <p class="bold" id="o2029"><a name="2029" /> + <p class="bold" id="o2031"><a name="2031" /> 44.4 Where is the latex (or some other interim) output? </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2029 + 2031 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2030"><a name="2030" /> + <p class="norm" id="o2032"><a name="2032" /> Try adding -M (for maintenance) to your command flags, e.g.: </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2030 + 2032 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2031"><a name="2031" /> + <li class="bullet" id="o2033"><a name="2033" /> sisu -HpMv [filename] </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2031 + 2033 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2032"><a name="2032" /> + <p class="norm" id="o2034"><a name="2034" /> this should result in the interim processing output being retained, and information being provided on where to find it. </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2032 + 2034 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2033"><a name="2033" /> + <li class="bullet" id="o2035"><a name="2035" /> sisu --help directory </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2033 + 2035 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <li class="bullet" id="o2034"><a name="2034" /> + <li class="bullet" id="o2036"><a name="2036" /> sisu --help path </li> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2034 + 2036 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2035"><a name="2035" /> + <p class="norm" id="o2037"><a name="2037" /> should also provide some relevant information as to where it is placed. </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2035 + 2037 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <a name="h44.5" id="h44.5"></a> - <p class="bold" id="o2036"><a name="2036" /> + <p class="bold" id="o2038"><a name="2038" /> 44.5 Why isn't SiSU markup XML </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2036 + 2038 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2037"><a name="2037" /> + <p class="norm" id="o2039"><a name="2039" /> I worked with text and (though I find XML immensely valuable) disliked noise ... better to sidestep the question and say: </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2037 + 2039 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2038"><a name="2038" /> + <p class="norm" id="o2040"><a name="2040" /> <b>SiSU</b> currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native <b>SiSU</b> markup for processing. The three types correspond to SAX (structure described), DOM (structure embedded, whole document must be read before structure is correctly discernable) and node based (a tree) forms of XML document structure representation. Problem is I use them very seldom and check that all is as it should be with them seldom, so I would not be surprised if something breaks there, but as far as I know they are working. I will check and add an XML markup help page before the next release. There already is a bit of information in the man page under the title <b>SiSU</b> VERSION CONVERSION </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2038 + 2040 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="i1" id="o2039"><a name="2039" /> + <p class="i1" id="o2041"><a name="2041" /> sisu --to-sax [filename/wildcard] </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2039 + 2041 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="i1" id="o2040"><a name="2040" /> + <p class="i1" id="o2042"><a name="2042" /> sisu --to-dom [filename/wildcard] </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2040 + 2042 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="i1" id="o2041"><a name="2041" /> + <p class="i1" id="o2043"><a name="2043" /> sisu --to-node [filename/wildcard] </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2041 + 2043 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2042"><a name="2042" /> + <p class="norm" id="o2044"><a name="2044" /> The XML should be well formed... must check, but lacks sensible headers. Suggestions welcome as to what to make of them. [For the present time I am satisfied that I can convert (both ways) between 3 forms of XML representation and <b>SiSU</b> markup]. </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2042 + 2044 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="i1" id="o2043"><a name="2043" /> + <p class="i1" id="o2045"><a name="2045" /> sisu --from-xml2sst [filename/wildcard] </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2043 + 2045 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <a name="h44.6" id="h44.6"></a> - <p class="bold" id="o2044"><a name="2044" /> + <p class="bold" id="o2046"><a name="2046" /> 44.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? </p> </td> <td width="2%" align="right" valign="top"> <p class="ocn"> - 2044 - </p> -</td></tr> -</table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> -<tr><td valign="top" align="justify"> - <p class="norm" id="o2045"><a name="2045" /> - <b>SiSU</b> is not really about type-setting. - </p> -</td> -<td width="2%" align="right" valign="top"> - <p class="ocn"> - 2045 - </p> -</td></tr> -</table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> -<tr><td valign="top" align="justify"> - <p class="norm" id="o2046"><a name="2046" /> - LaTeX is the ultimate computer instruction type-setting language for paper based publication. - </p> -</td> -<td width="2%" align="right" valign="top"> - <p class="ocn"> 2046 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2047"><a name="2047" /> - LaTeX is able to control just about everything that happens on page and pixel, position letters kerning, space variation between characters, words, paragraphs etc. formula. + <b>SiSU</b> is not really about type-setting. </p> </td> <td width="2%" align="right" valign="top"> @@ -652,7 +630,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2048"><a name="2048" /> - <b>SiSU</b> is not really about type-setting at all. It is about a lightweight markup instruction that provides enough information for an abstraction of the documents structure and objects, from which different forms of representation of the document can be generated. + LaTeX is the ultimate computer instruction type-setting language for paper based publication. </p> </td> <td width="2%" align="right" valign="top"> @@ -663,7 +641,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2049"><a name="2049" /> - <b>SiSU</b> with very little markup instruction is able to produce relatively high quality pdf by virtue of being able to generate usable default LaTeX; it produces "quality" html by generating the html directly; likewise it populates an SQL database in a useful way with the document in object sized chunks and its meta-data. But <b>SiSU</b> works on an abstraction of the document's structure and content and custom builds suitable uniform output. The html for browser viewing and pdf for paper viewing/publishing are rather different things with different needs for layout - as indeed is what is needed to store information in a database in searchable objects. + LaTeX is able to control just about everything that happens on page and pixel, position letters kerning, space variation between characters, words, paragraphs etc. formula. </p> </td> <td width="2%" align="right" valign="top"> @@ -674,7 +652,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2050"><a name="2050" /> - The pdfs or html produced for example by open office based on open document format and other office/word processor suits usually attempt to have similar looking outputs - your document rendered in html looks much the same, or in pdf... sisu is less this way, it seeks to have a starting point with as little information about appearance as possible, and to come up with the best possible appearance for each output that can be derived based on this minimal information. + <b>SiSU</b> is not really about type-setting at all. It is about a lightweight markup instruction that provides enough information for an abstraction of the documents structure and objects, from which different forms of representation of the document can be generated. </p> </td> <td width="2%" align="right" valign="top"> @@ -685,7 +663,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2051"><a name="2051" /> - Where there are large document sets, it provides consistency in appearance in each output format for the documents. + <b>SiSU</b> with very little markup instruction is able to produce relatively high quality pdf by virtue of being able to generate usable default LaTeX; it produces "quality" html by generating the html directly; likewise it populates an SQL database in a useful way with the document in object sized chunks and its meta-data. But <b>SiSU</b> works on an abstraction of the document's structure and content and custom builds suitable uniform output. The html for browser viewing and pdf for paper viewing/publishing are rather different things with different needs for layout - as indeed is what is needed to store information in a database in searchable objects. </p> </td> <td width="2%" align="right" valign="top"> @@ -696,7 +674,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2052"><a name="2052" /> - The excuse for going this way is, it is a waste of time to think much about appearance when working on substantive content, it is the substantive content that is relevant, not the way it looks beyond the basic informational tags - and yet you want to be able to take advantage of as many useful different ways of representing documents as are available, and for various types of output to to be/look as good as it can for each medium/format in which it is presented, (with different mediums having different focuses) and <b>SiSU</b> tries to achieve this from minimal markup. + The pdfs or html produced for example by open office based on open document format and other office/word processor suits usually attempt to have similar looking outputs - your document rendered in html looks much the same, or in pdf... sisu is less this way, it seeks to have a starting point with as little information about appearance as possible, and to come up with the best possible appearance for each output that can be derived based on this minimal information. </p> </td> <td width="2%" align="right" valign="top"> @@ -706,20 +684,19 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> -<a name="h44.7" id="h44.7"></a> - <p class="bold" id="o2053"><a name="2053" /> - 44.7 How do I create GIN or GiST index in Postgresql for use in SiSU + <p class="norm" id="o2053"><a name="2053" /> + Where there are large document sets, it provides consistency in appearance in each output format for the documents. </p> </td> <td width="2%" align="right" valign="top"> - <p class="ocn"> + <p class="ocn"> 2053 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2054"><a name="2054" /> - This at present needs to be done "manually" and it is probably necessary to alter the sample search form. The following is a helpful response from one of the contributors of GiN to Postgresql Oleg Bartunov 2006-12-06: + The excuse for going this way is, it is a waste of time to think much about appearance when working on substantive content, it is the substantive content that is relevant, not the way it looks beyond the basic informational tags - and yet you want to be able to take advantage of as many useful different ways of representing documents as are available, and for various types of output to to be/look as good as it can for each medium/format in which it is presented, (with different mediums having different focuses) and <b>SiSU</b> tries to achieve this from minimal markup. </p> </td> <td width="2%" align="right" valign="top"> @@ -729,19 +706,20 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2055"><a name="2055" /> - "I have tsearch2 slides which introduces tsearch2 <<a href="http://www.sai.msu.su/~megera/wiki/tsearch2slides" target="_top">http://www.sai.msu.su/~megera/wiki/tsearch2slides</a>> +<a name="h44.7" id="h44.7"></a> + <p class="bold" id="o2055"><a name="2055" /> + 44.7 How do I create GIN or GiST index in Postgresql for use in SiSU </p> </td> <td width="2%" align="right" valign="top"> - <p class="ocn"> + <p class="ocn"> 2055 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2056"><a name="2056" /> - FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. + This at present needs to be done "manually" and it is probably necessary to alter the sample search form. The following is a helpful response from one of the contributors of GiN to Postgresql Oleg Bartunov 2006-12-06: </p> </td> <td width="2%" align="right" valign="top"> @@ -752,7 +730,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2057"><a name="2057" /> - In your example I'd do ( simple way, just for demo): + "I have tsearch2 slides which introduces tsearch2 <<a href="http://www.sai.msu.su/~megera/wiki/tsearch2slides" target="_top">http://www.sai.msu.su/~megera/wiki/tsearch2slides</a>> </p> </td> <td width="2%" align="right" valign="top"> @@ -763,7 +741,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2058"><a name="2058" /> - <b>0.</b> compile, install tsearch2 and load tsearch2 into your database + FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. </p> </td> <td width="2%" align="right" valign="top"> @@ -773,8 +751,8 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="i1" id="o2059"><a name="2059" /> - cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql + <p class="norm" id="o2059"><a name="2059" /> + In your example I'd do ( simple way, just for demo): </p> </td> <td width="2%" align="right" valign="top"> @@ -785,7 +763,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2060"><a name="2060" /> - <b>1.</b> Add column fts, which holds tsvector + <b>0.</b> compile, install tsearch2 and load tsearch2 into your database </p> </td> <td width="2%" align="right" valign="top"> @@ -796,7 +774,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="i1" id="o2061"><a name="2061" /> - alter table documents add column fts tsvector; + cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql </p> </td> <td width="2%" align="right" valign="top"> @@ -807,7 +785,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2062"><a name="2062" /> - <b>2.</b> Fill fts column + <b>1.</b> Add column fts, which holds tsvector </p> </td> <td width="2%" align="right" valign="top"> @@ -818,7 +796,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="i1" id="o2063"><a name="2063" /> - update document set fts = to_tsvector(clean); + alter table documents add column fts tsvector; </p> </td> <td width="2%" align="right" valign="top"> @@ -829,7 +807,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2064"><a name="2064" /> - <b>3.</b> create index - just for performance ! + <b>2.</b> Fill fts column </p> </td> <td width="2%" align="right" valign="top"> @@ -840,7 +818,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="i1" id="o2065"><a name="2065" /> - create index fts_gin_idx on document using gin(fts); + update document set fts = to_tsvector(clean); </p> </td> <td width="2%" align="right" valign="top"> @@ -851,7 +829,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2066"><a name="2066" /> - <b>4.</b> Run vacuum + <b>3.</b> create index - just for performance ! </p> </td> <td width="2%" align="right" valign="top"> @@ -862,7 +840,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="i1" id="o2067"><a name="2067" /> - vacuum analyze document; + create index fts_gin_idx on document using gin(fts); </p> </td> <td width="2%" align="right" valign="top"> @@ -873,7 +851,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2068"><a name="2068" /> - That's all. + <b>4.</b> Run vacuum </p> </td> <td width="2%" align="right" valign="top"> @@ -883,8 +861,8 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2069"><a name="2069" /> - Now you can search: + <p class="i1" id="o2069"><a name="2069" /> + vacuum analyze document; </p> </td> <td width="2%" align="right" valign="top"> @@ -895,7 +873,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2070"><a name="2070" /> - select lid, metadata_tid, rank_cd(fts, q,2)as rank from document, plainto_tsquery('markup syntax') q where q @@ fts order by rank desc limit 10; + That's all. </p> </td> <td width="2%" align="right" valign="top"> @@ -905,20 +883,19 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> -<a name="h44.8" id="h44.8"></a> - <p class="bold" id="o2071"><a name="2071" /> - 44.8 Where is version 1.0? + <p class="norm" id="o2071"><a name="2071" /> + Now you can search: </p> </td> <td width="2%" align="right" valign="top"> - <p class="ocn"> + <p class="ocn"> 2071 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2072"><a name="2072" /> - <b>SiSU</b> works pretty well as it is supposed to. Version 1.0 will have the current markup, and directory structure. At this point it is largely a matter of choice as to when the name change is made. + select lid, metadata_tid, rank_cd(fts, q,2)as rank from document, plainto_tsquery('markup syntax') q where q @@ fts order by rank desc limit 10; </p> </td> <td width="2%" align="right" valign="top"> @@ -928,19 +905,20 @@ </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> - <p class="norm" id="o2073"><a name="2073" /> - The feature set for html, <a name="-110" href="#_110"> <sup>110</sup> </a> LaTeX/pdf and opendocument is in place. XML, and plaintext are in order. +<a name="h44.8" id="h44.8"></a> + <p class="bold" id="o2073"><a name="2073" /> + 44.8 Where is version 1.0? </p> </td> <td width="2%" align="right" valign="top"> - <p class="ocn"> + <p class="ocn"> 2073 </p> </td></tr> </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2074"><a name="2074" /> - html and LaTeX/pdf may be regarded as reference copy outputs + <b>SiSU</b> works pretty well as it is supposed to. Version 1.0 will have the current markup, and directory structure. At this point it is largely a matter of choice as to when the name change is made. </p> </td> <td width="2%" align="right" valign="top"> @@ -951,7 +929,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2075"><a name="2075" /> - With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. + The feature set for html, <a name="-110" href="#_110"> <sup>110</sup> </a> LaTeX/pdf and opendocument is in place. XML, and plaintext are in order. </p> </td> <td width="2%" align="right" valign="top"> @@ -962,7 +940,7 @@ </table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> <p class="norm" id="o2076"><a name="2076" /> - We are still almost there. + html and LaTeX/pdf may be regarded as reference copy outputs </p> </td> <td width="2%" align="right" valign="top"> @@ -970,6 +948,28 @@ 2076 </p> </td></tr> +</table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> +<tr><td valign="top" align="justify"> + <p class="norm" id="o2077"><a name="2077" /> + With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. + </p> +</td> +<td width="2%" align="right" valign="top"> + <p class="ocn"> + 2077 + </p> +</td></tr> +</table><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> +<tr><td valign="top" align="justify"> + <p class="norm" id="o2078"><a name="2078" /> + We are still almost there. + </p> +</td> +<td width="2%" align="right" valign="top"> + <p class="ocn"> + 2078 + </p> +</td></tr> </table><p class="center" id="endnotes"> <a href="#top">^</a></p><table summary="normal text css" width="100%" border="0" bgcolor="white" cellpadding="2" align="center"> <tr><td valign="top" align="justify"> @@ -1110,7 +1110,7 @@ <a href="http://www.jus.uio.no/sisu" > SiSU </a> - 0.59.0 2007-09-23 (2007w38/0) + 0.59.1 2007-09-25 (2007w39/2) <br /> <a href="http://www.jus.uio.no/sisu" > <b>SiSU</b> |