From a72e66db913de3a2e508080c8b1fc8d1342a899b Mon Sep 17 00:00:00 2001 From: Ralph Amissah Date: Tue, 25 Sep 2007 23:23:03 +0100 Subject: remove generated output from main package --- .../sisu_manual/sisu_faq/concordance.html | 1015 ------------ .../sisu_manual/sisu_faq/digest.txt | 160 -- .../sisu_manual/sisu_faq/doc.html | 1629 -------------------- .../manuals_generated/sisu_manual/sisu_faq/dom.xml | 883 ----------- .../sisu_manual/sisu_faq/endnotes.html | 452 ------ .../sisu_manual/sisu_faq/faq.html | 1228 --------------- .../sisu_manual/sisu_faq/index.html | 550 ------- .../sisu_manual/sisu_faq/landscape.pdf | Bin 110271 -> 0 bytes .../sisu_manual/sisu_faq/metadata.html | 591 ------- .../sisu_manual/sisu_faq/opendocument.odt | Bin 11417 -> 0 bytes .../sisu_manual/sisu_faq/plain.txt | 381 ----- .../sisu_manual/sisu_faq/portrait.pdf | Bin 111291 -> 0 bytes .../manuals_generated/sisu_manual/sisu_faq/sax.xml | 547 ------- .../sisu_manual/sisu_faq/scroll.xhtml | 545 ------- .../sisu_manual/sisu_faq/sisu_faq.sst | 191 --- .../sisu_manual/sisu_faq/sisu_manifest.html | 200 --- .../sisu_manual/sisu_faq/sisupod.zip | Bin 6364 -> 0 bytes .../sisu_manual/sisu_faq/sitemap.xml | 30 - .../sisu_manual/sisu_faq/toc.html | 550 ------- 19 files changed, 8952 deletions(-) delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/concordance.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/digest.txt delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/doc.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/dom.xml delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/endnotes.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/faq.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/index.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/landscape.pdf delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/metadata.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/opendocument.odt delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/plain.txt delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/portrait.pdf delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/sax.xml delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/scroll.xhtml delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_faq.sst delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_manifest.html delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/sisupod.zip delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/sitemap.xml delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_faq/toc.html (limited to 'data/doc/manuals_generated/sisu_manual/sisu_faq') diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/concordance.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/concordance.html deleted file mode 100644 index 1ce3a613..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/concordance.html +++ /dev/null @@ -1,1015 +0,0 @@ - - - - - SiSU created WordIndex for: SiSU - FAQ - Frequently Asked/Answered Questions - - - - - - - - - - - - - - - - -
- -
SiSU -->
-
- - - - - - - - - - - - - - -
- - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
-
-   - TOC -   -
-

-
 

SiSU - FAQ - Frequently Asked/Answered Questions

Ralph Amissah

- -

Word index links are to html versions of the text the segmented version followed by the scroll (single document) version.
[For segmented text references [T1], [T2] or [T3] appearing without a link, indicates that the word appears in a title (or subtitle) of the text (that is identifiable by the appended object citation number).]

-

(The word listing/index is Case sensitive: Capitalized words appear before lower case)

-

- word (number of occurences)
linked references to word within document
- [if number of occurences exceed number of references - word occurs more than once in at least one reference. Footnote/endnotes are either assigned to the paragraph from which they are referenced or ignored, so it is relevant to check the footnotes referenced from within a paragraph as well.] -

-

- (After the page is fully loaded) you can jump directly to a word by appending a hash (#) and the word to the url for this text, (do not forget that words are case sensitive, and may be listed twice (starting with and without an upper case letter)), #your_word # [ http://[web host]/sisu_faq/concordance.html#your_word ] -

- -

Able

(4)

-

38, 40, 43,

-

About

(7)

-

35, 36, 38, 39, 41, 43,

-

Abstraction

(2)

-

39, 40,

-

Accurately

(1)

-

29,

-

Achieve

(1)

-

43,

-

Add

(3)

-

29, 51, 52,

-

Adding

(1)

-

21,

-

Advantage

(1)

-

43,

-

After

(1)

-

6,

-

Against

(1)

-

16,

-

All

(3)

-

29, 39, 59,

-

Almost

(1)

-

67,

-

Already

(1)

-

29,

-

Also

(1)

-

26,

-

Alter

(2)

-

45, 52,

-

Amissah

(1)

-

[H]1,

-

Analyze

(1)

-

58,

-

And

(27)

-

3, 16, 23, 28, 29, 33, 38, 39, 40, 41, 43, 45, 49, 63, 64, 65, 66,

-

Answered

(2)

-

[H]1, 2,

-

Any

(2)

-

15, 47,

-

Appearance

(4)

-

41, 42, 43,

-

Aptitude

(1)

-

18,

-

Are

(8)

-

3, 19, 29, 40, 42, 43, 64, 67,

-

Asked

(2)

-

[H]1, 2,

-

Attempt

(1)

-

41,

-

Available

(1)

-

43,

-

Bartunov

(1)

-

45,

-

Based

(4)

-

29, 37, 41,

-

Basic

(1)

-

43,

-

Been

(1)

-

64,

-

Before

(2)

-

29,

-

Being

(3)

-

23, 40,

-

Best

(1)

-

41,

-

Better

(1)

-

28,

-

Between

(2)

-

33, 38,

-

Beyond

(1)

-

43,

-

Bin

(1)

-

19,

-

Bit

(2)

-

29, 66,

-

Both

(1)

-

33,

-

Breaks

(1)

-

29,

-

Browser

(1)

-

40,

-

Builds

(1)

-

40,

-

But

(3)

-

29, 33, 40,

-

Can

(6)

-

33, 35, 39, 41, 43, 60,

-

Cannot

(1)

-

7,

-

Change

(1)

-

63,

-

Characters

(1)

-

38,

-

Check

(3)

-

29, 33,

-

Choice

(1)

-

63,

-

Chunks

(1)

-

40,

-

Claims

(1)

-

35,

-

Clean

(1)

-

54,

-

Column

(3)

-

51, 52, 53,

-

Come

(1)

-

41,

-

Command

(2)

-

10, 21,

-

Compile

(1)

-

49,

-

Compliance

(1)

-

64,

-

Computer

(1)

-

37,

-

Consistency

(1)

-

42,

-

Content

(3)

-

40, 43,

-

Contrib

(1)

-

50,

-

Contributors

(1)

-

45,

-

Control

(1)

-

38,

-

CONVERSION

(1)

-

29,

-

Convert

(1)

-

33,

-

Converts

(1)

-

29,

-

Copy

(1)

-

65,

-

Correctly

(1)

-

29,

-

Correspond

(1)

-

29,

-

Create

(3)

-

44, 55, 56,

-

Current

(1)

-

63,

-

Currently

(1)

-

29,

-

Custom

(1)

-

40,

-

Data

(1)

-

40,

-

Database

(3)

-

40, 49,

-

Databases

(1)

-

66,

-

Debian

(1)

-

17,

-

Default

(1)

-

40,

-

Demo

(1)

-

48,

-

Dependencies

(1)

-

17,

-

Derived

(1)

-

41,

-

Desc

(1)

-

61,

-

Described

(1)

-

29,

-

Different

(6)

-

39, 40, 43,

-

Directly

(1)

-

40,

-

Directory

(4)

-

6, 11, 24, 63,

-

Discernable

(1)

-

29,

-

Disliked

(1)

-

28,

-

Document

(13)

-

29, 35, 39, 40, 41, 42, 54, 56, 58, 61,

-

Documents

(4)

-

39, 42, 43, 52,

-

DOM

(1)

-

29,

-

Dom

(1)

-

31,

-

Done

(3)

-

6, 45, 66,

-

Each

(3)

-

41, 42, 43,

-

Embedded

(1)

-

29,

-

Enough

(1)

-

39,

-

Env

(1)

-

9,

-

Etc

(1)

-

38,

-

Everything

(1)

-

38,

-

Example

(2)

-

41, 48,

-

Excuse

(1)

-

43,

-

Extra

(1)

-

19,

-

FAQ

(2)

-

[H]1, 2,

-

Faq

(1)

-

2,

-

Far

(1)

-

29,

-

Feature

(1)

-

64,

-

Filename

(6)

-

13, 22, 30, 31, 32, 34,

-

Files

(1)

-

16,

-

Fill

(1)

-

53,

-

Find

(3)

-

7, 23, 28,

-

Flag

(1)

-

3,

-

Flags

(1)

-

21,

-

Focuses

(1)

-

43,

-

Following

(5)

-

4, 8, 17, 19, 45,

-

For

(20)

-

6, 21, 29, 33, 35, 37, 39, 40, 41, 42, 43, 44, 48, 55, 64,

-

Form

(1)

-

45,

-

Format

(3)

-

41, 42, 43,

-

Formed

(1)

-

33,

-

Forms

(4)

-

29, 33, 39,

-

Formula

(1)

-

38,

-

Frequently

(2)

-

[H]1, 2,

-

From

(6)

-

29, 34, 39, 43, 45, 61,

-

FTS

(1)

-

47,

-

Fts

(7)

-

51, 52, 53, 54, 56, 61,

-

Functionality

(1)

-

47,

-

Generate

(2)

-

16, 40,

-

Generated

(1)

-

39,

-

Generating

(1)

-

40,

-

Get

(1)

-

15,

-

Gin

(2)

-

45, 56,

-

GIN

(2)

-

44, 47,

-

GiST

(2)

-

44, 47,

-

Going

(1)

-

43,

-

Good

(1)

-

43,

-

Happens

(1)

-

38,

-

Has

(1)

-

64,

-

Have

(4)

-

41, 46, 63,

-

Having

(2)

-

6, 43,

-

Headers

(1)

-

33,

-

Help

(7)

-

8, 9, 11, 12, 24, 25, 29,

-

Helpful

(1)

-

45,

-

High

(2)

-

35, 40,

-

Holds

(1)

-

51,

-

How

(1)

-

44,

-

Hpmv

(1)

-

22,

-

Html

(8)

-

40, 41, 64, 65,

-

Immensely

(1)

-

28,

-

Indeed

(1)

-

40,

-

Index

(3)

-

44, 55, 56,

-

Indices

(2)

-

47,

-

Information

(7)

-

23, 26, 29, 39, 40, 41,

-

Informational

(1)

-

43,

-

Input

(1)

-

29,

-

Install

(4)

-

17, 18, 49, 50,

-

Installcheck

(1)

-

50,

-

Instruction

(3)

-

37, 39, 40,

-

Interim

(2)

-

20, 23,

-

Into

(1)

-

49,

-

Introduces

(1)

-

46,

-

Isn

(1)

-

27,

-

Its

(1)

-

40,

-

Just

(3)

-

38, 48, 55,

-

Kerning

(1)

-

38,

-

Know

(1)

-

29,

-

Lacks

(1)

-

33,

-

Language

(1)

-

37,

-

Large

(1)

-

42,

-

Largely

(2)

-

63, 64,

-

Latex

(9)

-

16, 19, 20, 35, 37, 38, 40, 64, 65,

-

Layout

(1)

-

40,

-

Less

(1)

-

41,

-

Letters

(1)

-

38,

-

Lid

(1)

-

61,

-

Lightweight

(1)

-

39,

-

Likewise

(1)

-

40,

-

Limit

(1)

-

61,

-

Little

(2)

-

40, 41,

-

Load

(1)

-

49,

-

Look

(1)

-

43,

-

Looking

(1)

-

41,

-

Looks

(2)

-

41, 43,

-

Made

(1)

-

63,

-

Maintenance

(1)

-

21,

-

Make

(4)

-

33, 50,

-

Man

(2)

-

14, 29,

-

Manually

(1)

-

45,

-

Many

(1)

-

43,

-

Markup

(9)

-

27, 29, 33, 39, 40, 43, 61, 63,

-

Matter

(1)

-

63,

-

May

(1)

-

65,

-

Medium

(1)

-

43,

-

Mediums

(1)

-

43,

-

Met

(1)

-

64,

-

Meta

(1)

-

40,

-

Minimal

(2)

-

41, 43,

-

More

(1)

-

29,

-

Much

(2)

-

41, 43,

-

Must

(2)

-

29, 33,

-

Name

(1)

-

63,

-

Native

(1)

-

29,

-

Necessary

(1)

-

45,

-

Needed

(1)

-

40,

-

Needs

(2)

-

40, 45,

-

Next

(1)

-

29,

-

Node

(2)

-

29, 32,

-

Noise

(1)

-

28,

-

Not

(6)

-

15, 29, 36, 39, 43, 47,

-

Now

(1)

-

60,

-

Object

(1)

-

40,

-

Objects

(2)

-

39, 40,

-

Office

(2)

-

41,

-

Oleg

(1)

-

45,

-

One

(1)

-

45,

-

Open

(2)

-

41,

-

Opendocument

(1)

-

64,

-

Order

(2)

-

61, 64,

-

Other

(2)

-

20, 41,

-

Output

(11)

-

6, 7, 8, 15, 20, 23, 40, 41, 42, 43,

-

Outputs

(2)

-

41, 65,

-

Packages

(1)

-

19,

-

Page

(3)

-

29, 38,

-

Paper

(2)

-

37, 40,

-

Paragraphs

(1)

-

38,

-

Path

(2)

-

12, 25,

-

Paths

(1)

-

8,

-

Pdf

(8)

-

15, 16, 18, 40, 41, 64, 65,

-

Pdflatex

(1)

-

16,

-

Pdfs

(1)

-

41,

-

Performance

(2)

-

47, 55,

-

Pixel

(1)

-

38,

-

Place

(1)

-

64,

-

Placed

(1)

-

26,

-

Plaintext

(1)

-

64,

-

Point

(3)

-

3, 41, 63,

-

Populates

(1)

-

40,

-

Populating

(1)

-

66,

-

Port

(1)

-

3,

-

Position

(1)

-

38,

-

Possible

(2)

-

41,

-

Postgresql

(3)

-

44, 45, 66,

-

PostgreSQL

(1)

-

47,

-

Preparation

(1)

-

35,

-

Present

(2)

-

33, 45,

-

Presented

(1)

-

43,

-

Pretty

(1)

-

63,

-

Previous

(1)

-

10,

-

Probably

(1)

-

45,

-

Problem

(1)

-

29,

-

Processing

(2)

-

23, 29,

-

Processor

(1)

-

41,

-

Produce

(1)

-

40,

-

Produced

(3)

-

3, 6, 41,

-

Produces

(2)

-

16, 40,

-

Provide

(3)

-

8, 26, 47,

-

Provided

(2)

-

23, 47,

-

Provides

(2)

-

39, 42,

-

Psql

(1)

-

50,

-

Publication

(1)

-

37,

-

Publishing

(1)

-

40,

-

Quality

(3)

-

35, 40,

-

Question

(1)

-

28,

-

Questions

(2)

-

[H]1, 2,

-

Ralph

(1)

-

[H]1,

-

Rank

(2)

-

61,

-

Rather

(1)

-

40,

-

Read

(1)

-

29,

-

Really

(2)

-

36, 39,

-

Reference

(1)

-

65,

-

Regard

(1)

-

66,

-

Regarded

(1)

-

65,

-

Relatively

(1)

-

40,

-

Release

(1)

-

29,

-

Relevant

(2)

-

26, 43,

-

Rendered

(1)

-

41,

-

Representation

(3)

-

29, 33, 39,

-

Representations

(1)

-

29,

-

Representing

(1)

-

43,

-

Required

(2)

-

17, 19,

-

Response

(1)

-

45,

-

Result

(1)

-

23,

-

Retained

(1)

-

23,

-

Ruby

(1)

-

6,

-

Run

(2)

-

16, 57,

-

Rune

(1)

-

4,

-

Said

(1)

-

35,

-

Same

(3)

-

10, 35, 41,

-

Sample

(1)

-

45,

-

Satisfied

(1)

-

33,

-

SAX

(1)

-

29,

-

Sax

(1)

-

30,

-

Say

(1)

-

28,

-

Scans

(1)

-

6,

-

Search

(2)

-

45, 60,

-

Searchable

(1)

-

40,

-

Seeks

(1)

-

41,

-

Seldom

(2)

-

29,

-

Select

(1)

-

61,

-

Sensible

(1)

-

33,

-

Serve

(1)

-

6,

-

Server

(1)

-

3,

-

Set

(2)

-

54, 64,

-

Sets

(1)

-

42,

-

Setting

(3)

-

36, 37, 39,

-

Should

(8)

-

6, 8, 23, 26, 29, 33, 47,

-

Sidestep

(1)

-

28,

-

Similar

(1)

-

41,

-

Simple

(1)

-

48,

-

SiSU

(15)

-

[H]1, 16, 27, 29, 33, 35, 36, 39, 40, 43, 44, 63,

-

Sisu

(16)

-

5, 9, 10, 11, 12, 13, 14, 18, 22, 24, 25, 30, 31, 32, 34, 41,

-

Sized

(1)

-

40,

-

Slides

(1)

-

46,

-

Some

(3)

-

6, 20, 26,

-

Something

(1)

-

29,

-

Space

(1)

-

38,

-

Sql

(2)

-

50, 66,

-

SQL

(1)

-

40,

-

Sqlite

(1)

-

66,

-

Start

(1)

-

6,

-

Starting

(1)

-

41,

-

Still

(1)

-

67,

-

Store

(1)

-

40,

-

Structure

(7)

-

29, 39, 40, 63,

-

Substantive

(2)

-

43,

-

Suggestions

(1)

-

33,

-

Suitable

(1)

-

40,

-

Suits

(1)

-

41,

-

Supposed

(1)

-

63,

-

Surprised

(1)

-

29,

-

Syntax

(1)

-

61,

-

System

(1)

-

35,

-

Table

(1)

-

52,

-

Tags

(1)

-

43,

-

Take

(1)

-

43,

-

Tetex

(2)

-

19,

-

Text

(1)

-

28,

-

That

(9)

-

3, 16, 29, 33, 38, 39, 41, 43, 59,

-

The

(41)

-

3, 4, 6, 8, 10, 17, 19, 20, 23, 28, 29, 33, 35, 37, 39, 40, 41, 42, 43, 45, 63, 64, 66,

-

Them

(3)

-

29, 33,

-

There

(5)

-

29, 42, 66, 67,

-

They

(1)

-

29,

-

Things

(1)

-

40,

-

Think

(1)

-

43,

-

This

(8)

-

6, 23, 41, 43, 45, 63,

-

Though

(1)

-

28,

-

Three

(3)

-

29,

-

Time

(2)

-

33, 43,

-

Title

(1)

-

29,

-

Tree

(1)

-

29,

-

Tries

(1)

-

43,

-

Try

(2)

-

4, 21,

-

Tsearch2

(7)

-

46, 47, 49, 50,

-

Tsvector

(2)

-

51, 52,

-

Type

(3)

-

36, 37, 39,

-

Types

(2)

-

29, 43,

-

Typesetting

(1)

-

35,

-

Ucs

(1)

-

19,

-

Ultimate

(1)

-

37,

-

Under

(1)

-

29,

-

Understands

(1)

-

29,

-

Uniform

(1)

-

40,

-

Update

(1)

-

54,

-

Urls

(1)

-

3,

-

Usable

(1)

-

40,

-

Use

(3)

-

17, 29, 44,

-

Useful

(2)

-

40, 43,

-

Using

(1)

-

56,

-

Usually

(1)

-

41,

-

Vacuum

(2)

-

57, 58,

-

Valuable

(1)

-

28,

-

Variation

(1)

-

38,

-

Various

(1)

-

43,

-

Version

(2)

-

62, 63,

-

VERSION

(1)

-

29,

-

Very

(2)

-

29, 40,

-

Viewing

(2)

-

40,

-

Virtue

(1)

-

40,

-

W3c

(1)

-

64,

-

Want

(1)

-

43,

-

Waste

(1)

-

43,

-

Way

(5)

-

40, 41, 43, 48,

-

Ways

(2)

-

33, 43,

-

Web

(1)

-

3,

-

Webserver

(1)

-

6,

-

Welcome

(1)

-

33,

-

Well

(2)

-

33, 63,

-

What

(3)

-

6, 33, 40,

-

When

(2)

-

43, 63,

-

Where

(7)

-

7, 20, 23, 26, 42, 61, 62,

-

Which

(5)

-

39, 43, 46, 47, 51,

-

Whole

(1)

-

29,

-

Why

(3)

-

3, 15, 27,

-

Wildcard

(4)

-

30, 31, 32, 34,

-

Will

(3)

-

17, 29, 63,

-

With

(10)

-

3, 28, 29, 40, 41, 43, 66,

-

Without

(1)

-

47,

-

Word

(1)

-

41,

-

Words

(1)

-

38,

-

Worked

(1)

-

28,

-

Working

(2)

-

29, 43,

-

Works

(3)

-

40, 47, 63,

-

Would

(1)

-

29,

-

XML

(9)

-

27, 28, 29, 33, 64,

-

Xml2sst

(1)

-

34,

-

Yet

(1)

-

43,

-

You

(3)

-

17, 43, 60,

-

Your

(4)

-

21, 41, 48, 49,

- - - - - - -
- -
-

- - SiSU - -

-
- -

- Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
- - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
- - SiSU - - is software for document structuring, publishing and search, -
- - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
- w3 since October 3 1993 - - ralph@amissah.com - -

-
-

- SiSU using: -
Standard SiSU markup syntax, -
Standard SiSU meta-markup syntax, and the -
Standard SiSU object citation numbering and system, (object/text positioning system) -
- Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

-
-

- - GPLv3 - -

-
-

- - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

-
-

- SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
- Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
- Get With the Future - - Way Better! - -

-
- \ No newline at end of file diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/digest.txt b/data/doc/manuals_generated/sisu_manual/sisu_faq/digest.txt deleted file mode 100644 index 736f37ae..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/digest.txt +++ /dev/null @@ -1,160 +0,0 @@ -SiSU - FAQ - Frequently Asked/Answered Questions -Ralph Amissah -sisu_faq.sst ----------------------------------------------- -SiSU Document Content Certificate (Digest/DCC) ----------------------------------------------- - md5 digests ------------- -Sourcefile digest: 41577c9fc063cd232914a1a11a59e91a - source filename: sisu_faq.sst -available outputs: http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisu_manifest.html - time generated: Tue Sep 25 02:53:56 +0100 2007 - SiSU version used: SiSU 0.59.1 of 2007w39/2 (2007-09-25) - Ruby version used: ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux] ------------- -Document Digest Tree (from dal): -level (if any), ocn: digest clean (no markup/notes), digest all (includes markup & endnotes) - [endnote number] endnote digest clean - - :A - 1 954dee7d47a32f1be0efb0c091655fe8 dc8b754d483856008c1e950912044892 - 1 - 2 9864de686c4581ecf89788407a13d6d1 2ee5961e1d8109426293fc4234e328bb - 2 - 3 22194c2cbad5bbd0b8750d74139d94a9 b6b6bf4b078ede2d57b83b5a204b25d3 - - 4 c6a4e93bbe505331d1ad1d0ff84f6618 57e789c99862c2b5a111990b32557fb5 - - 5 2eb57e726f7a6d7fcea2d72a32846427 e20a9ec7ce4db71a7c4045ae9b7ccd8f - - 6 867cf539fc38c128b7fe5cbb7c60d9c3 9275c09e9b902e4bfbfb60b4c0166901 - 2 - 7 3fb96d2be8c9ee55d4230332e0543f23 a9c7f840da388591b4c8dab02a608872 - - 8 82330ed6edabde34c16146603aca6328 9383e4c66559cc8db16de8f9ce2b9059 - - 9 0854d88e42da691dfaff1cbec5f7764c 65d472589f81b16dfae8ae75432dd648 - - 10 f95cd1b72da9059fe63af02b17b90c1f 8cbf63c3986504b24c3e89a40664e688 - - 11 b72a42b860601b4c9e38b4cb436ffc12 17dd8106db2303cdd10cddc6f9df13e6 - - 12 f4b83ce44b9507c3bad75d75a8651d2f 84c65557639667fbf3da221767d67582 - - 13 a0e24a81b3dd6398f60898f95e61bd96 62ad67c7dbedfba9716efba012d9942c - - 14 bc1f0f9b15f4187672d8db242e2073ee 8633e9f8e070079933bd49850af73304 - 2 - 15 86fdf876fa91d6b635e5144d601ab30c ca4f198a9b8c88873e7982b86645b10f - - 16 e768287213edb79ba808ac55e74e61a2 39df14abec54d3310f6c6713f41cfe34 - - 17 9032fbebaaae18f11cbaaf20b43543c8 fced4202c373dfbae13ee9baef6a34d3 - - 18 dc95d64cb3cc2008cde01461f734f3d8 81d692808659f853fe184670e5cc93e2 - - 19 049e41bf98c552a7ea14ff6e499e4e80 48cff5fe05dcc2fbcd480da9ba078b6c - 2 - 20 1d5d6728ca48c598533b03ce1837fc8d 39eda6ffa9e5e9b38c33a5cfc60fadbc - - 21 0e5b4b71f7fa45f73e8ac89ea355f615 a3520183037c2253e02d16b738fabb79 - - 22 db8c8e7e3bd57f6dcc1f433a1b0b48ac b4eb86e7fd1986ea15ca6dbec5c185fb - - 23 613c5741d9e9ccfc3ac300286cbd85d5 dd2b0933de4a7aee6567269ceea56f0f - - 24 b72a42b860601b4c9e38b4cb436ffc12 b42edfe965c9f71ca771984f708e8531 - - 25 f4b83ce44b9507c3bad75d75a8651d2f c454133941f1ff9e8238c0fa5c104b33 - - 26 2a377c3e5630976a3f9dfb15431d8744 6c456bf9f71c76838478e678820ed5dd - 2 - 27 f3a23678b1c5a318d13663910e709c9a 9bd9d6ac48f286b13840d93004d7620d - - 28 9573d50a035ff408803de164d7f648ee 6a974374d7cc9732c10a274be8c06ca9 - - 29 264fc3225fbc10992fa06122dba73739 18eec2ec2c5ee4217b60c3ba4bb1a7ad - - 30 b4ffa05e1a863df5d93e0e1fb2dd5e3f 2f9fa3da7a54b92d0ab51df8bc96c4bf - - 31 3e18ace83b37df2ea369d77561ad8292 9dbd93b0df82a89c740520efec685fa3 - - 32 d5a12cd3d77cd0960cb4a45195a435ad 95f505b8d96d6dabc70dd1493b78d574 - - 33 27cb5b570bb9df2866ab6875a0a3e27e ce604eaef166ed9de35b5ab1e047f68c - - 34 522fb38591dee62aa3d3b9367c8511e5 20e479f71f28862aac932a9b54a8fbdb - 2 - 35 8a006076ca2db31156e7084d25ae9aae 100f85f7595715b3e6eacdcf25bd5330 - - 36 7d9fa1ed97e7787b3a7b50d7a97652a5 05659638c3a5799d69a3377d902230bf - - 37 f6a0816b251104519329d76d75e36653 24379f0b25b7688ec74b2eafeb19ee41 - - 38 802150d3e41b115cb92185d46745da68 39b44cd3994fe6382e00ddea7f74da9f - - 39 00c6c19ec11f46c01db2fbed4b22399f 131621240fa3dc08fbb571e27c336672 - - 40 11cc6e2152de5403c0602c21615b6aff f87cc3deefb1b536452436aa1a537590 - - 41 d22b003c2c9467a54511d64ae3af6c17 9768010f60a494f3bd9d326d491ae31d - - 42 8246c0da37c5e8fddbac893857a972fb f0bee67c18da905061bc3e6f7345d501 - - 43 10323b9690881eeb46f8bd59ae4a611b 9678d47b6d40161d99ff360c918e6ec2 - 2 - 44 017d84b20fe486388640d15884d117b1 2626dc3a6efb600ebd7c525c8d4c47ba - - 45 3d8ac5ed0bc41953d3d9cb56fef3eb71 0853c899bcfe2a394c092c9d1294cceb - - 46 9239ca052ceed70adfd69d6f27d15a2d 96a6fbc4c36d966075eee1951bf3a207 - - 47 09bf7f83f123d521f2d144aec3c41a1a 017b07c9f46048e15144356d559d32cf - - 48 ba57616f00bab7a61dad1e7265ba3d99 61031565224d7c56a781e50b8f5d60d1 - - 49 d97369f844a6a5a12ee28ab41653b0c1 14da317f4416641555dc1e951a0b817a - - 50 e3e28cc116d6f455f44d3218ed4bcc3c cbb77997e39062d7402a5e0232b2dbf5 - - 51 69e9fca41042f7224d6d6637a7d4a21f aeb487c5acfc5065c4745d088ad199ee - - 52 28584cd09a89933ced0e0b074592e6ce edb51d2baa70785c8dbcfa297c74e381 - - 53 8092aaf5a33bfa90535097d379956953 cefa9412d68415b7896e9dde55a7733e - - 54 39c8ef343c794b936e8c581cf55b2911 46047de8cc6c6ded641a1abf89eb94da - - 55 2fc4c2b1d105daacdc9eae8ca7f624e5 7469202978fffec05c942e086c6f7350 - - 56 6569589e044c54853459f86c657b8eb1 35f2bedacd66cb04e3edd43d6744e3ee - - 57 6155979d548fdefd0d6148551b9f53ae c0705c1500591ce846a4ec111b02b3da - - 58 dbc41858b9ce690d68238e4f5aa79b99 982d32265cf88740278ed548ed888e28 - - 59 e24e76ad25cac7b6fc80a8a67c628b27 edd2250288b826dd72bfad845c7502de - - 60 17a9a363d785cce5af333fa6022a0bf3 0e2324514ee6cd4a62d46ba846c7b0be - - 61 1a178946d7956e974c95d12b490ba73a 2489f4327b16abdb905eb1fb84c8feeb - 2 - 62 20afdb26827cd963c5f7339acd62c5b9 5199e427d5dd151fb6bfe06ef3e8a265 - - 63 276af3fef427c71e36af56de63db2b8c 21191dfd1b0dfbef5e29691557b58009 - - 64 085090e07a1eb5e4ef84732262e988bb 8581a37e86dca905e9d585216da706f1 - [1] 1310a195231243179d1e002d044c6367 - - 65 15e8375b047cce33a8a22deccc07375d 7ec47ee61ee65b7990193f61c701a8bf - - 66 395a9c9a6397829d4614b6e269426f95 a8269b55c2273a9febde73fbcb367e50 - - 67 1cba13c72dfa127d69863d8f42a6cba8 eee1b4c1a6274cd0e9a8528708bcfc5a - 1 - 0 cc4947558ec26d67c755c76262f85131 c7a5392e3bd6d769d940d79b19a68e4c - :A - 0 5b23a6f796c80555992b9b68cfdbc2bb 5fbbfb7933004e25553d56929ed7e545 - 1 - 0 ce21470ab49d1d1976bc3dc72438c183 f2709633c4c07e46bf6aeef624e8a736 - - 0 ef62c6f19d38a1e0540168bbd798348c 235ea3f29c058683e6adc40d7867fe75 - - - 0 3bca2a5af45d3d764dd73c03690cd66e ac56056f12b17cdaf50a68e61c70c01e - - - 0 ebd0aa03a5f7fa6f0e2d38b9676fb155 6f43d92a036c9944794c8582322b5875 - -dc title - 0 bb8fc4cc8429eb32223a2bdff6c852ee c60097280d65fc3f33c5a66b786b8164 - -dc creator - 0 0679b0c2bbba4dc8a8eea763236c903f e64313bcf0600cea90bc0935c74877cc - -dc rights - 0 0e230d9710d8294315f77233e2b11ef9 94f3688a12e01bb32bff91cf018e0aae - -dc type - 0 7ff1b8f5fc0daaa20ab922214e3a045c ff73c0e3a5d9de30b22e26cd2ad33690 - -dc date created - 0 2ad9d8750091fa63ff5c1acc50d49dda 14d54761028e880531d324ad2200847a - -dc date available - 0 ab83341a16a4931c6a2680915caceccd 71a58c5023d33383fa5b721e51c7e20e - -dc date issued - 0 752135ec36eb8d6c4a15a0bcd5fcae47 0cfacd1166506a462a7b0e05e5993ee2 - -dc date modified - 0 d325bb430d51f592e18ecd88b488cf97 0140c70c106aab09eb65289d8332dec0 - -dc date - 0 c8d7d2f3fe839d8e3a4f8f0abb18e8b1 0e048ac65f0bf92fba616933ffe7acbe - - - 0 9d11e23779d9604067dd20e359117573 3f883fb08147a237efaeb152bfaaa1ee - -sourcefile - 0 06f9ee1a5fa700b8ae844b5e07d84dc1 6e8d6aa013a3b517f9df5307a6c6aea8 - - - 0 794ce8cc422272c64a3d3821caf6c214 f2b54639d1bf563e60268bc3eb417571 - - - 0 d871d1706f5f1d631178d10c3b685d7c 00e6cc22b0bcbf61b90629881776b5c6 - source 41577c9fc063cd232914a1a11a59e91a sisu_faq.sst - - - 0 2b89344dabed7858bf918b451f4942f6 ba5182e9541159cc6a5b9b2c055b13e4 - skin 20fc43cf3eb6590bc3399a1aef65c5a9 skin_sisu_manual.rb - - - 0 5c5f06440fcb85cd5c8cfafe32e34b78 d8f5595da03dd0c38d62b56492f5eb0f - -document (metaverse) last generated - 0 74285f9ec1d1727a662f04b60a8cf7de 8a8f9726582b99491b0335c2ad812474 - -generated by - 0 6c5edbc75adaa6dc22ef77d914d5b52e 857948399ac1b384fa1ec734c7b46782 - -ruby version - 0 37cf2ede6f4722230340c84e2753e412 4ccb32a8ff87fa8b6600884d16e2d685 ------------- -document structure[*] -:A - 1 - 2 - 2 - 2 - 2 - 2 - 2 - 2 - 2 - 1 -:A - 1 - [*] heading levels ------------- -document structure[*] -@ = 15 -:A = 2 -1 = 3 -2 = 8 -objects (ocn) = 67 -endnotes = 1 - [*] number of headers (@) and of each heading level (:A to :C and 1 to 3) ------------- -Note: the time generated related fields (text and digests) will vary between otherwise identical document outputs diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/doc.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/doc.html deleted file mode 100644 index fb7198f0..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/doc.html +++ /dev/null @@ -1,1629 +0,0 @@ - - - - - - SiSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - -
- -
SiSU -->
-
- - - - - - - - - - - - - - - -
- - Full Text  scroll  - - - - - TOC linked  toc  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
-
-   -
-

- -

- -
- - -
- -

SiSU -

- -

FAQ - Frequently Asked/Answered Questions -

- -

Ralph Amissah -

- -copy @ - - SiSU - - -
- - - -

Rights: Copyright ©  Ralph Amissah 2007, part of SiSU documentation, License GPL 3

-

- -
- -

- SiSU - FAQ - Frequently Asked/Answered Questions,
Ralph Amissah
-

- -

- 1. FAQ - Frequently Asked/Answered Questions -

- -
- 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? -
- -
- 1.2 I cannot find my output, where is it? -
- -
- 1.3 I do not get any pdf output, why? -
- -
- 1.4 Where is the latex (or some other interim) output? -
- -
- 1.5 Why isn't SiSU markup XML -
- -
- 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? -
- -
- 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU -
- -
- 1.8 Where is version 1.0? -
- -

- -

- - - Document Information (metadata) - - - - - -
-

- - SiSU - FAQ - Frequently Asked/Answered Questions,
Ralph Amissah -

-
-

-   1 -

-
- - - - -
-

- - 1. FAQ - Frequently Asked/Answered Questions -

-
-

-   2 -

-
- - - - -
-
- - 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? -
-
-

-   3 -

-
- - - - -
-

- Try the following rune: -

-
-

-   4 -

-
- - - - -
-
  • - sisu -W -
  • -
    -

    -   5 -

    -
    - - - - -
    -

    - 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. -

    -
    -

    -   6 -

    -
    - - - - -
    -
    - - 1.2 I cannot find my output, where is it? -
    -
    -

    -   7 -

    -
    - - - - -
    -

    - The following should provide help on output paths: -

    -
    -

    -   8 -

    -
    - - - - -
    -
  • - sisu --help env -
  • -
    -

    -   9 -

    -
    - - - - -
    -
  • - sisu -V [same as the previous command] -
  • -
    -

    -   10 -

    -
    - - - - -
    -
  • - sisu --help directory -
  • -
    -

    -   11 -

    -
    - - - - -
    -
  • - sisu --help path -
  • -
    -

    -   12 -

    -
    - - - - -
    -
  • - sisu -U [filename] -
  • -
    -

    -   13 -

    -
    - - - - -
    -
  • - man sisu -
  • -
    -

    -   14 -

    -
    - - - - -
    -
    - - 1.3 I do not get any pdf output, why? -
    -
    -

    -   15 -

    -
    - - - - -
    -

    - SiSU produces LaTeX and pdflatex is run against that to generate pdf files. -

    -
    -

    -   16 -

    -
    - - - - -
    -

    - If you use Debian the following will install the required dependencies -

    -
    -

    -   17 -

    -
    - - - - -
    -
  • - aptitude install sisu-pdf -
  • -
    -

    -   18 -

    -
    - - - - -
    -

    - the following packages are required: tetex-bin, tetex-extra, latex-ucs -

    -
    -

    -   19 -

    -
    - - - - -
    -
    - - 1.4 Where is the latex (or some other interim) output? -
    -
    -

    -   20 -

    -
    - - - - -
    -

    - Try adding -M (for maintenance) to your command flags, e.g.: -

    -
    -

    -   21 -

    -
    - - - - -
    -
  • - sisu -HpMv [filename] -
  • -
    -

    -   22 -

    -
    - - - - -
    -

    - this should result in the interim processing output being retained, and information being provided on where to find it. -

    -
    -

    -   23 -

    -
    - - - - -
    -
  • - sisu --help directory -
  • -
    -

    -   24 -

    -
    - - - - -
    -
  • - sisu --help path -
  • -
    -

    -   25 -

    -
    - - - - -
    -

    - should also provide some relevant information as to where it is placed. -

    -
    -

    -   26 -

    -
    - - - - -
    -
    - - 1.5 Why isn't SiSU markup XML -
    -
    -

    -   27 -

    -
    - - - - -
    -

    - I worked with text and (though I find XML immensely valuable) disliked noise ... better to sidestep the question and say: -

    -
    -

    -   28 -

    -
    - - - - -
    -

    - SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU 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 SiSU VERSION CONVERSION -

    -
    -

    -   29 -

    -
    - - - - -
    -

    - sisu --to-sax [filename/wildcard] -

    -
    -

    -   30 -

    -
    - - - - -
    -

    - sisu --to-dom [filename/wildcard] -

    -
    -

    -   31 -

    -
    - - - - -
    -

    - sisu --to-node [filename/wildcard] -

    -
    -

    -   32 -

    -
    - - - - -
    -

    - 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 SiSU markup]. -

    -
    -

    -   33 -

    -
    - - - - -
    -

    - sisu --from-xml2sst [filename/wildcard] -

    -
    -

    -   34 -

    -
    - - - - -
    -
    - - 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? -
    -
    -

    -   35 -

    -
    - - - - -
    -

    - SiSU is not really about type-setting. -

    -
    -

    -   36 -

    -
    - - - - -
    -

    - LaTeX is the ultimate computer instruction type-setting language for paper based publication. -

    -
    -

    -   37 -

    -
    - - - - -
    -

    - 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. -

    -
    -

    -   38 -

    -
    - - - - -
    -

    - SiSU 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. -

    -
    -

    -   39 -

    -
    - - - - -
    -

    - SiSU 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 SiSU 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. -

    -
    -

    -   40 -

    -
    - - - - -
    -

    - 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. -

    -
    -

    -   41 -

    -
    - - - - -
    -

    - Where there are large document sets, it provides consistency in appearance in each output format for the documents. -

    -
    -

    -   42 -

    -
    - - - - -
    -

    - 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 SiSU tries to achieve this from minimal markup. -

    -
    -

    -   43 -

    -
    - - - - -
    -
    - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU -
    -
    -

    -   44 -

    -
    - - - - -
    -

    - 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: -

    -
    -

    -   45 -

    -
    - - - - -
    -

    - "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> -

    -
    -

    -   46 -

    -
    - - - - -
    -

    - FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. -

    -
    -

    -   47 -

    -
    - - - - -
    -

    - In your example I'd do ( simple way, just for demo): -

    -
    -

    -   48 -

    -
    - - - - -
    -

    - 0. compile, install tsearch2 and load tsearch2 into your database -

    -
    -

    -   49 -

    -
    - - - - -
    -

    - cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql -

    -
    -

    -   50 -

    -
    - - - - -
    -

    - 1. Add column fts, which holds tsvector -

    -
    -

    -   51 -

    -
    - - - - -
    -

    - alter table documents add column fts tsvector; -

    -
    -

    -   52 -

    -
    - - - - -
    -

    - 2. Fill fts column -

    -
    -

    -   53 -

    -
    - - - - -
    -

    - update document set fts = to_tsvector(clean); -

    -
    -

    -   54 -

    -
    - - - - -
    -

    - 3. create index - just for performance ! -

    -
    -

    -   55 -

    -
    - - - - -
    -

    - create index fts_gin_idx on document using gin(fts); -

    -
    -

    -   56 -

    -
    - - - - -
    -

    - 4. Run vacuum -

    -
    -

    -   57 -

    -
    - - - - -
    -

    - vacuum analyze document; -

    -
    -

    -   58 -

    -
    - - - - -
    -

    - That's all. -

    -
    -

    -   59 -

    -
    - - - - -
    -

    - Now you can search: -

    -
    -

    -   60 -

    -
    - - - - -
    -

    - 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; -

    -
    -

    -   61 -

    -
    - - - - -
    -
    - - 1.8 Where is version 1.0? -
    -
    -

    -   62 -

    -
    - - - - -
    -

    - SiSU 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. -

    -
    -

    -   63 -

    -
    - - - - -
    -

    - The feature set for html,  1  LaTeX/pdf and opendocument is in place. XML, and plaintext are in order. -

    -
    -

    -   64 -

    -
    - - - - -
    -

    - html and LaTeX/pdf may be regarded as reference copy outputs -

    -
    -

    -   65 -

    -
    - - - - -
    -

    - With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. -

    -
    -

    -   66 -

    -
    - - - - -
    -

    - We are still almost there. -

    -
    -

    -   67 -

    -
    - - - - -
    -

    - - Endnotes -

    -
    -

    -   0 -

    -
    - - - -
    - -

    -


    -

    -   -
    - - - - -
    -

    -  1. html w3c compliance has been largely met. -

    -
    -   -
    - - - - -
    -

    - - Document Information (metadata) -

    -
    -

    -   0 -

    -
    - -

    - Metadata -

    - - -     - - - - - -
    -

    - <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisu_manifest.html> -

    -
    - - - -
    -

    - Dublin Core (DC) -

    -
    - - - -
    -

    - DC tags included with this document are provided here. -

    -
    - - - -
    -

    - DC Title: SiSU - FAQ - Frequently Asked/Answered Questions -

    -
    - - - -
    -

    - DC Creator: Ralph Amissah -

    -
    - - - -
    -

    - DC Rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 -

    -
    - - - -
    -

    - DC Type: information -

    -
    - - - -
    -

    - DC Date created: 2006-09-06 -

    -
    - - - -
    -

    - DC Date available: 2006-09-06 -

    -
    - - - -
    -

    - DC Date issued: 2006-09-06 -

    -
    - - - -
    -

    - DC Date modified: 2007-09-16 -

    -
    - - - -
    -

    - DC Date: 2007-09-16 -

    -
    - - - -
    -

    - Version Information -

    -
    - - - -
    -

    - Sourcefile: sisu_faq.sst -

    -
    - - - -
    -

    - Filetype: SiSU text 0.57 -

    -
    - - - -
    -

    - Sourcefile Digest, MD5(sisu_faq.sst)= 41577c9fc063cd232914a1a11a59e91a -

    -
    - - - -
    -

    - Skin_Digest: MD5(/home/ralph/grotto/theatre/dbld/builds/sisu/sisu/data/doc/sisu/sisu_markup_samples/sisu_manual/_sisu/skin/doc/skin_sisu_manual.rb)= 20fc43cf3eb6590bc3399a1aef65c5a9 -

    -
    - - - -
    -

    - Generated -

    -
    - - - -
    -

    - Document (metaverse) last generated: Tue Sep 25 02:53:56 +0100 2007 -

    -
    - - - -
    -

    - Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25) -

    -
    - - - -
    -

    - Ruby version: ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux] -

    -
    - - - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - -
    - - Full Text  scroll  - - - - - TOC linked  toc  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    -   -
    -

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - - - - - - -

    - -
    -
    - - -
    - - -
    - - - - idx - txt - - -
    -
    - -
    -

    - - -SiSU manual - -

    - - - - - - - - - - - -
    -

    - - -SiSU - -

    - - - - - - - - - - - - - - - - -
    - - - - diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/dom.xml b/data/doc/manuals_generated/sisu_manual/sisu_faq/dom.xml deleted file mode 100644 index f5d26e72..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/dom.xml +++ /dev/null @@ -1,883 +0,0 @@ - - - - - - - - -
    - Title: - - SiSU - FAQ - Frequently Asked/Answered Questions - -
    - -
    - Creator: - - Ralph Amissah - -
    - -
    - Rights: - - Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 - -
    - -
    - Type: - - information - -
    - -
    - Subject: - - ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search - -
    - -
    - Date created: - - 2006-09-06 - -
    - -
    - Date available: - - 2006-09-06 - -
    - -
    - Date issued: - - 2006-09-06 - -
    - -
    - Date modified: - - 2007-09-16 - -
    - -
    - Date: - - 2007-09-16 - -
    - - - - - - - - - - - - - - 1 - SiSU - FAQ - Frequently Asked/Answered Questions,
    Ralph Amissah
    -
    -
    - - - - - 2 - faq - - 1. FAQ - Frequently Asked/Answered Questions - - - - - - - - - - 3 - 1.1 - - 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? - - - - - - - - 4 - - - Try the following rune: - - - - - - - - 5 - - - sisu -W - - - - - - - - 6 - - - 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. - - - - - - - - - - - - 7 - 1.2 - - 1.2 I cannot find my output, where is it? - - - - - - - - 8 - - - The following should provide help on output paths: - - - - - - - - 9 - - - sisu --help env - - - - - - - - 10 - - - sisu -V [same as the previous command] - - - - - - - - 11 - - - sisu --help directory - - - - - - - - 12 - - - sisu --help path - - - - - - - - 13 - - - sisu -U [filename] - - - - - - - - 14 - - - man sisu - - - - - - - - - - - - 15 - 1.3 - - 1.3 I do not get any pdf output, why? - - - - - - - - 16 - - - SiSU produces LaTeX and pdflatex is run against that to generate pdf files. - - - - - - - - 17 - - - If you use Debian the following will install the required dependencies - - - - - - - - 18 - - - aptitude install sisu-pdf - - - - - - - - 19 - - - the following packages are required: tetex-bin, tetex-extra, latex-ucs - - - - - - - - - - - - 20 - 1.4 - - 1.4 Where is the latex (or some other interim) output? - - - - - - - - 21 - - - Try adding -M (for maintenance) to your command flags, e.g.: - - - - - - - - 22 - - - sisu -HpMv [filename] - - - - - - - - 23 - - - this should result in the interim processing output being retained, and information being provided on where to find it. - - - - - - - - 24 - - - sisu --help directory - - - - - - - - 25 - - - sisu --help path - - - - - - - - 26 - - - should also provide some relevant information as to where it is placed. - - - - - - - - - - - - 27 - 1.5 - - 1.5 Why isn't SiSU markup XML - - - - - - - - 28 - - - I worked with text and (though I find XML immensely valuable) disliked noise ... better to sidestep the question and say: - - - - - - - - 29 - - - SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU 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 SiSU VERSION CONVERSION - - - - - - - - 30 - - - sisu --to-sax [filename/wildcard] - - - - - - - - 31 - - - sisu --to-dom [filename/wildcard] - - - - - - - - 32 - - - sisu --to-node [filename/wildcard] - - - - - - - - 33 - - - 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 SiSU markup]. - - - - - - - - 34 - - - sisu --from-xml2sst [filename/wildcard] - - - - - - - - - - - - 35 - 1.6 - - 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? - - - - - - - - 36 - - - SiSU is not really about type-setting. - - - - - - - - 37 - - - LaTeX is the ultimate computer instruction type-setting language for paper based publication. - - - - - - - - 38 - - - 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. - - - - - - - - 39 - - - SiSU 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. - - - - - - - - 40 - - - SiSU 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 SiSU 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. - - - - - - - - 41 - - - 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. - - - - - - - - 42 - - - Where there are large document sets, it provides consistency in appearance in each output format for the documents. - - - - - - - - 43 - - - 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 SiSU tries to achieve this from minimal markup. - - - - - - - - - - - - 44 - 1.7 - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU - - - - - - - - 45 - - - 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: - - - - - - - - 46 - - - "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> - - - - - - - - 47 - - - FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. - - - - - - - - 48 - - - In your example I'd do ( simple way, just for demo): - - - - - - - - 49 - - - 0. compile, install tsearch2 and load tsearch2 into your database - - - - - - - - 50 - - - cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql - - - - - - - - 51 - - - 1. Add column fts, which holds tsvector - - - - - - - - 52 - - - alter table documents add column fts tsvector; - - - - - - - - 53 - - - 2. Fill fts column - - - - - - - - 54 - - - update document set fts = to_tsvector(clean); - - - - - - - - 55 - - - 3. create index - just for performance ! - - - - - - - - 56 - - - create index fts_gin_idx on document using gin(fts); - - - - - - - - 57 - - - 4. Run vacuum - - - - - - - - 58 - - - vacuum analyze document; - - - - - - - - 59 - - - That's all. - - - - - - - - 60 - - - Now you can search: - - - - - - - - 61 - - - 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; - - - - - - - - - - - - 62 - 1.8 - - 1.8 Where is version 1.0? - - - - - - - - 63 - - - SiSU 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. - - - - - - - - 64 - - - The feature set for html,1html w3c compliance has been largely met. LaTeX/pdf and opendocument is in place. XML, and plaintext are in order. - - - - - - - - 65 - - - html and LaTeX/pdf may be regarded as reference copy outputs - - - - - - - - 66 - - - With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. - - - - - - - - 67 - - - We are still almost there. - - - - - - - - - - - - - - 0 - endnotes - - Endnotes - - - - - - - -
    - - - -
    - diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/endnotes.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/endnotes.html deleted file mode 100644 index 7cfe6400..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/endnotes.html +++ /dev/null @@ -1,452 +0,0 @@ - - - - - - endnotes - - SiSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - - - -
    - - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    - - - - - - -
    - - << previous - - - - TOC - - - - next >> - - -
    -
    - - - - -
    - - < - - - - ^ - - - - > - -
    - -
    -

    - SiSU -

    -

    - FAQ - Frequently Asked/Answered Questions -

    -

    - Ralph Amissah - -

    - -
    -

    Endnotes

    - - -
    -

    -  1. html w3c compliance has been largely met. -

    -
      -

    -^

     
    - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - - - -
    - - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    - - - - - - -
    - - << previous - - - - TOC - - - - next >> - - -
    -
    - - - - -
    - - < - - - - ^ - - - - > - -

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - - - - -
    -
    - - -
    - - -
    - - - - idx - txt - - -
    -
    - -
    -

    - - -SiSU manual - -

    - - - - - - - - - - - -
    -

    - - -SiSU - -

    - - - - - - - - - - - - - - - - -
    - \ No newline at end of file diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/faq.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/faq.html deleted file mode 100644 index 90656b54..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/faq.html +++ /dev/null @@ -1,1228 +0,0 @@ - - - - - - faq - - SiSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - - - -
    - - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    - - - - - - -
    - - TOC - - - - next >> - - -
    -
    - - - - -
    - - < - - - - ^ - - - - > - -

    - SiSU -

    -

    - FAQ - Frequently Asked/Answered Questions -

    -

    - Ralph Amissah - -

    -

    - copy @ - - SiSU - -

    - - -
    -

    - SiSU - FAQ - Frequently Asked/Answered Questions,
    Ralph Amissah -

    -
      -

    -   1 -

    -
    - - -
    - -   -
    - - -
    -

    - - 1. FAQ - Frequently Asked/Answered Questions -

    -
    -

    -   2 -

    -
    - - 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? - -
    - - 1.2 I cannot find my output, where is it? - -
    - - 1.3 I do not get any pdf output, why? - -
    - - 1.4 Where is the latex (or some other interim) output? - -
    - - 1.5 Why isn't SiSU markup XML - -
    - - 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? - -
    - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU - -
    - - 1.8 Where is version 1.0? - -
    - - -
    - -

    - 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? -

    -
    -

    -   3 -

    -
    - - -
    -

    - Try the following rune: -

    -
    -

    -   4 -

    -
    - - -
    -
  • - sisu -W -
  • -
    -

    -   5 -

    -
    - - -
    -

    - 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. -

    -
    -

    -   6 -

    -
    - - -
    - -

    - 1.2 I cannot find my output, where is it? -

    -
    -

    -   7 -

    -
    - - -
    -

    - The following should provide help on output paths: -

    -
    -

    -   8 -

    -
    - - -
    -
  • - sisu --help env -
  • -
    -

    -   9 -

    -
    - - -
    -
  • - sisu -V [same as the previous command] -
  • -
    -

    -   10 -

    -
    - - -
    -
  • - sisu --help directory -
  • -
    -

    -   11 -

    -
    - - -
    -
  • - sisu --help path -
  • -
    -

    -   12 -

    -
    - - -
    -
  • - sisu -U [filename] -
  • -
    -

    -   13 -

    -
    - - -
    -
  • - man sisu -
  • -
    -

    -   14 -

    -
    - - -
    - -

    - 1.3 I do not get any pdf output, why? -

    -
    -

    -   15 -

    -
    - - -
    -

    - SiSU produces LaTeX and pdflatex is run against that to generate pdf files. -

    -
    -

    -   16 -

    -
    - - -
    -

    - If you use Debian the following will install the required dependencies -

    -
    -

    -   17 -

    -
    - - -
    -
  • - aptitude install sisu-pdf -
  • -
    -

    -   18 -

    -
    - - -
    -

    - the following packages are required: tetex-bin, tetex-extra, latex-ucs -

    -
    -

    -   19 -

    -
    - - -
    - -

    - 1.4 Where is the latex (or some other interim) output? -

    -
    -

    -   20 -

    -
    - - -
    -

    - Try adding -M (for maintenance) to your command flags, e.g.: -

    -
    -

    -   21 -

    -
    - - -
    -
  • - sisu -HpMv [filename] -
  • -
    -

    -   22 -

    -
    - - -
    -

    - this should result in the interim processing output being retained, and information being provided on where to find it. -

    -
    -

    -   23 -

    -
    - - -
    -
  • - sisu --help directory -
  • -
    -

    -   24 -

    -
    - - -
    -
  • - sisu --help path -
  • -
    -

    -   25 -

    -
    - - -
    -

    - should also provide some relevant information as to where it is placed. -

    -
    -

    -   26 -

    -
    - - -
    - -

    - 1.5 Why isn't SiSU markup XML -

    -
    -

    -   27 -

    -
    - - -
    -

    - I worked with text and (though I find XML immensely valuable) disliked noise ... better to sidestep the question and say: -

    -
    -

    -   28 -

    -
    - - -
    -

    - SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU 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 SiSU VERSION CONVERSION -

    -
    -

    -   29 -

    -
    - - -
    -

    - sisu --to-sax [filename/wildcard] -

    -
    -

    -   30 -

    -
    - - -
    -

    - sisu --to-dom [filename/wildcard] -

    -
    -

    -   31 -

    -
    - - -
    -

    - sisu --to-node [filename/wildcard] -

    -
    -

    -   32 -

    -
    - - -
    -

    - 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 SiSU markup]. -

    -
    -

    -   33 -

    -
    - - -
    -

    - sisu --from-xml2sst [filename/wildcard] -

    -
    -

    -   34 -

    -
    - - -
    - -

    - 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? -

    -
    -

    -   35 -

    -
    - - -
    -

    - SiSU is not really about type-setting. -

    -
    -

    -   36 -

    -
    - - -
    -

    - LaTeX is the ultimate computer instruction type-setting language for paper based publication. -

    -
    -

    -   37 -

    -
    - - -
    -

    - 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. -

    -
    -

    -   38 -

    -
    - - -
    -

    - SiSU 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. -

    -
    -

    -   39 -

    -
    - - -
    -

    - SiSU 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 SiSU 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. -

    -
    -

    -   40 -

    -
    - - -
    -

    - 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. -

    -
    -

    -   41 -

    -
    - - -
    -

    - Where there are large document sets, it provides consistency in appearance in each output format for the documents. -

    -
    -

    -   42 -

    -
    - - -
    -

    - 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 SiSU tries to achieve this from minimal markup. -

    -
    -

    -   43 -

    -
    - - -
    - -

    - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU -

    -
    -

    -   44 -

    -
    - - -
    -

    - 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: -

    -
    -

    -   45 -

    -
    - - -
    -

    - "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> -

    -
    -

    -   46 -

    -
    - - -
    -

    - FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. -

    -
    -

    -   47 -

    -
    - - -
    -

    - In your example I'd do ( simple way, just for demo): -

    -
    -

    -   48 -

    -
    - - -
    -

    - 0. compile, install tsearch2 and load tsearch2 into your database -

    -
    -

    -   49 -

    -
    - - -
    -

    - cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql -

    -
    -

    -   50 -

    -
    - - -
    -

    - 1. Add column fts, which holds tsvector -

    -
    -

    -   51 -

    -
    - - -
    -

    - alter table documents add column fts tsvector; -

    -
    -

    -   52 -

    -
    - - -
    -

    - 2. Fill fts column -

    -
    -

    -   53 -

    -
    - - -
    -

    - update document set fts = to_tsvector(clean); -

    -
    -

    -   54 -

    -
    - - -
    -

    - 3. create index - just for performance ! -

    -
    -

    -   55 -

    -
    - - -
    -

    - create index fts_gin_idx on document using gin(fts); -

    -
    -

    -   56 -

    -
    - - -
    -

    - 4. Run vacuum -

    -
    -

    -   57 -

    -
    - - -
    -

    - vacuum analyze document; -

    -
    -

    -   58 -

    -
    - - -
    -

    - That's all. -

    -
    -

    -   59 -

    -
    - - -
    -

    - Now you can search: -

    -
    -

    -   60 -

    -
    - - -
    -

    - 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; -

    -
    -

    -   61 -

    -
    - - -
    - -

    - 1.8 Where is version 1.0? -

    -
    -

    -   62 -

    -
    - - -
    -

    - SiSU 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. -

    -
    -

    -   63 -

    -
    - - -
    -

    - The feature set for html,  1  LaTeX/pdf and opendocument is in place. XML, and plaintext are in order. -

    -
    -

    -   64 -

    -
    - - -
    -

    - html and LaTeX/pdf may be regarded as reference copy outputs -

    -
    -

    -   65 -

    -
    - - -
    -

    - With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. -

    -
    -

    -   66 -

    -
    - - -
    -

    - We are still almost there. -

    -
    -

    -   67 -

    -

    -^

    - - -
    -

    -  1. html w3c compliance has been largely met. -

    -
      -
     
    - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - - - -
    - - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    - - - - - - -
    - - TOC - - - - next >> - - -
    -
    - - - - -
    - - < - - - - ^ - - - - > - -

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - - - - -
    -
    - - -
    - - -
    - - - - idx - txt - - -
    -
    - -
    -

    - - -SiSU manual - -

    - - - - - - - - - - - -
    -

    - - -SiSU - -

    - - - - - - - - - - - - - - - - -
    - \ No newline at end of file diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/index.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/index.html deleted file mode 100644 index 543d4b4e..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/index.html +++ /dev/null @@ -1,550 +0,0 @@ - - - - - - SiSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - -
    - - TOC linked  toc  - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    -   - next >> -   -
    -

    - -

    - -
    - - -
    - -

    SiSU -

    - -

    FAQ - Frequently Asked/Answered Questions -

    - -

    Ralph Amissah -

    - -copy @ - - SiSU - - -
    - - - -

    - SiSU - FAQ - Frequently Asked/Answered Questions,
    Ralph Amissah -

    - -

    - - 1. FAQ - Frequently Asked/Answered Questions - -

    - -
    - - 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? - -
    - -
    - - 1.2 I cannot find my output, where is it? - -
    - -
    - - 1.3 I do not get any pdf output, why? - -
    - -
    - - 1.4 Where is the latex (or some other interim) output? - -
    - -
    - - 1.5 Why isn't SiSU markup XML - -
    - -
    - - 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? - -
    - -
    - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU - -
    - -
    - - 1.8 Where is version 1.0? - -
    - -

    - - Endnotes - -

    - - - Document Information (metadata) - - -

    Rights: Copyright ©  Ralph Amissah 2007, part of SiSU documentation, License GPL 3

    -

    - -

    - - - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - -
    - - TOC linked  toc  - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    -   - next >> -   -
    -

    - -

     

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - - - - - - -
    - -
    -
    - - -
    - - -
    - - - - idx - txt - - -
    -
    - -
    -

    - - -SiSU manual - -

    - - - - - - - - - - - -
    -

    - - -SiSU - -

    - - - - - - - - - - - - - - - - -
    - - - - diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/landscape.pdf b/data/doc/manuals_generated/sisu_manual/sisu_faq/landscape.pdf deleted file mode 100644 index 77efde9f..00000000 Binary files a/data/doc/manuals_generated/sisu_manual/sisu_faq/landscape.pdf and /dev/null differ diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/metadata.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/metadata.html deleted file mode 100644 index bc17bc04..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/metadata.html +++ /dev/null @@ -1,591 +0,0 @@ - - - - - - - - SiSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - - - -
    - - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    - - - - - - -
    - - << previous - - - - TOC - - -
    -
    - - - - -
    - - < - - - - ^ - - - - > - -

    - SiSU -

    -

    - FAQ - Frequently Asked/Answered Questions -

    -

    - Ralph Amissah - -

    -

    - copy @ - - SiSU - -

    - - -
    -

    - Document Information (metadata) -

    -
      -

    -   0 -

    -
    - - -
    - -   -
    - - -
    -

    - - Metadata -

    -
    -

    -   0 -

    -
    - -
    -

    - <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisu_manifest.html> -

    -
    - -
    -

    - Dublin Core (DC) -

    -
    - -
    -

    - DC tags included with this document are provided here. -

    -
    - -
    -

    - DC Title: SiSU - FAQ - Frequently Asked/Answered Questions -

    -
    - -
    -

    - DC Creator: Ralph Amissah -

    -
    - -
    -

    - DC Rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 -

    -
    - -
    -

    - DC Type: information -

    -
    - -
    -

    - DC Date created: 2006-09-06 -

    -
    - -
    -

    - DC Date available: 2006-09-06 -

    -
    - -
    -

    - DC Date issued: 2006-09-06 -

    -
    - -
    -

    - DC Date modified: 2007-09-16 -

    -
    - -
    -

    - DC Date: 2007-09-16 -

    -
    - -
    -

    - Version Information -

    -
    - -
    -

    - Sourcefile: sisu_faq.sst -

    -
    - -
    -

    - Filetype: SiSU text 0.57 -

    -
    - -
    -

    - Sourcefile Digest, MD5(sisu_faq.sst)= 41577c9fc063cd232914a1a11a59e91a -

    -
    - -
    -

    - Skin_Digest: MD5(/home/ralph/grotto/theatre/dbld/builds/sisu/sisu/data/doc/sisu/sisu_markup_samples/sisu_manual/_sisu/skin/doc/skin_sisu_manual.rb)= 20fc43cf3eb6590bc3399a1aef65c5a9 -

    -
    - -
    -

    - Generated -

    -
    - -
    -

    - Document (metaverse) last generated: Tue Sep 25 02:53:56 +0100 2007 -

    -
    - -
    -

    - Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25) -

    -
    - -
    -

    - Ruby version: ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux] -

    -

    -^

     
    - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - - - -
    - - - TOC linked  toc  - - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    - - - - - - -
    - - << previous - - - - TOC - - -
    -
    - - - - -
    - - < - - - - ^ - - - - > - -

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - - - - -
    -
    - - -
    - - -
    - - - - idx - txt - - -
    -
    - -
    -

    - - -SiSU manual - -

    - - - - - - - - - - - -
    -

    - - -SiSU - -

    - - - - - - - - - - - - - - - - -
    - \ No newline at end of file diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/opendocument.odt b/data/doc/manuals_generated/sisu_manual/sisu_faq/opendocument.odt deleted file mode 100644 index a82555ec..00000000 Binary files a/data/doc/manuals_generated/sisu_manual/sisu_faq/opendocument.odt and /dev/null differ diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/plain.txt b/data/doc/manuals_generated/sisu_manual/sisu_faq/plain.txt deleted file mode 100644 index b45a3fa6..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/plain.txt +++ /dev/null @@ -1,381 +0,0 @@ -SISU - FAQ - FREQUENTLY ASKED/ANSWERED QUESTIONS, -RALPH AMISSAH -**************************************************************** - -1. FAQ - FREQUENTLY ASKED/ANSWERED QUESTIONS --------------------------------------------- - -1.1 WHY ARE URLS PRODUCED WITH THE -V (AND -U) FLAG THAT POINT TO A WEB SERVER -ON PORT 8081? -.............................................................................. - -Try the following rune: - - -* sisu -W - - -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. - - -1.2 I CANNOT FIND MY OUTPUT, WHERE IS IT? -......................................... - -The following should provide help on output paths: - - -* sisu --help env - - -* sisu -V [same as the previous command] - - -* sisu --help directory - - -* sisu --help path - - -* sisu -U [filename] - - -* man sisu - - -1.3 I DO NOT GET ANY PDF OUTPUT, WHY? -..................................... - -*SiSU* produces LaTeX and pdflatex is run against that to generate pdf files. - - -If you use *Debian* the following will install the required dependencies - - -* aptitude install sisu-pdf - - -the following packages are required: tetex-bin, tetex-extra, latex-ucs - - -1.4 WHERE IS THE LATEX (OR SOME OTHER INTERIM) OUTPUT? -...................................................... - -Try adding -M (for maintenance) to your command flags, e.g.: - - -* sisu -HpMv [filename] - - -this should result in the interim processing output being retained, and -information being provided on where to find it. - - -* sisu --help directory - - -* sisu --help path - - -should also provide some relevant information as to where it is placed. - - -1.5 WHY ISN'T SISU MARKUP XML -............................. - -I worked with text and (though I find XML immensely valuable) disliked noise -... better to sidestep the question and say: - - -*SiSU* currently "understands" three XML input representations - or more -accurately, converts from three forms of XML to native *SiSU* 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 *SiSU* VERSION CONVERSION - - - sisu --to-sax [filename/wildcard] - - - sisu --to-dom [filename/wildcard] - - - sisu --to-node [filename/wildcard] - - -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 *SiSU* markup]. - - - sisu --from-xml2sst [filename/wildcard] - - -1.6 LATEX CLAIMS TO BE A DOCUMENT PREPARATION SYSTEM FOR HIGH-QUALITY -TYPESETTING. CAN THE SAME BE SAID ABOUT SISU? -.............................................................................. - -*SiSU* is not really about type-setting. - - -LaTeX is the ultimate computer instruction type-setting language for paper -based publication. - - -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. - - -*SiSU* 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. - - -*SiSU* 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 *SiSU* 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. - - -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. - - -Where there are large document sets, it provides consistency in appearance in -each output format for the documents. - - -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 *SiSU* tries to achieve -this from minimal markup. - - -1.7 HOW DO I CREATE GIN OR GIST INDEX IN POSTGRESQL FOR USE IN SISU -................................................................... - -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: - - -"I have tsearch2 slides which introduces tsearch2 - - - -FTS in PostgreSQL is provided by tsearch2, which should works without any -indices (GiST or GIN) ! Indices provide performance, not functionality. - - -In your example I'd do ( simple way, just for demo): - - -*0.* compile, install tsearch2 and load tsearch2 into your database - - - cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < - tsearch2.sql - - -*1.* Add column fts, which holds tsvector - - - alter table documents add column fts tsvector; - - -*2.* Fill fts column - - - update document set fts = to_tsvector(clean); - - -*3.* create index - just for performance ! - - - create index fts_gin_idx on document using gin(fts); - - -*4.* Run vacuum - - - vacuum analyze document; - - -That's all. - - -Now you can search: - - -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; - - -1.8 WHERE IS VERSION 1.0? -......................... - -*SiSU* 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. - - -The feature set for html,[^1] LaTeX/pdf and opendocument is in place. XML, and -plaintext are in order. - - -- [1]: html w3c compliance has been largely met. - -html and LaTeX/pdf may be regarded as reference copy outputs - - -With regard to the populating of sql databases (postgresql and sqlite), there -is a bit to be done. - - -We are still almost there. - - -DOCUMENT INFORMATION (METADATA) -******************************* - -METADATA --------- - -Document Manifest @ - - - -*Dublin Core* (DC) - - -/DC tags included with this document are provided here./ - - -DC Title: _SiSU - FAQ - Frequently Asked/Answered Questions_ - - -DC Creator: _Ralph Amissah_ - - -DC Rights: _Copyright (C) Ralph Amissah 2007, part of SiSU documentation, -License GPL 3_ - - -DC Type: _information_ - - -DC Date created: _2006-09-06_ - - -DC Date available: _2006-09-06_ - - -DC Date issued: _2006-09-06_ - - -DC Date modified: _2007-09-16_ - - -DC Date: _2007-09-16_ - - -*Version Information* - - -Sourcefile: _sisu_faq.sst_ - - -Filetype: _SiSU text 0.57_ - - -Sourcefile Digest, MD5(sisu_faq.sst)= _41577c9fc063cd232914a1a11a59e91a_ - - -Skin_Digest: -MD5(/home/ralph/grotto/theatre/dbld/builds/sisu/sisu/data/doc/sisu/sisu_markup_samples/sisu_manual/_sisu/skin/doc/skin_sisu_manual.rb)= -_20fc43cf3eb6590bc3399a1aef65c5a9_ - - -*Generated* - - -Document (metaverse) last generated: _Tue Sep 25 02:53:56 +0100 2007_ - - -Generated by: _SiSU_ _0.59.1_ of 2007w39/2 (2007-09-25) - - -Ruby version: _ ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux]_ - - - -============================================================================== - - title: SiSU - FAQ - Frequently Asked/Answered Questions - - creator: Ralph Amissah - - rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, - License GPL 3 - - type: information - - subject: ebook, epublishing, electronic book, electronic publishing, - electronic document, electronic citation, data structure, - citation systems, search - - date.created: 2006-09-06 - - date.available: 2006-09-06 - - date.issued: 2006-09-06 - - date.modified: 2007-09-16 - - date: 2007-09-16 - - - - - -============================================================================== -nil - -Other versions of this document: -manifest: - http://www.jus.uio.no/sisu/sisu_faq/sisu_manifest.html -html: - http://www.jus.uio.no/sisu/sisu_faq/toc.html -pdf: - http://www.jus.uio.no/sisu/sisu_faq/portrait.pdf - http://www.jus.uio.no/sisu/sisu_faq/landscape.pdf -plaintext (plain text): - http://www.jus.uio.no/sisu/sisu_faq/plain.txt -at: - http://www.jus.uio.no/sisu -* Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25) -* Ruby version: ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux] -* Last Generated on: Tue Sep 25 02:53:56 +0100 2007 -* SiSU http://www.jus.uio.no/sisu diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/portrait.pdf b/data/doc/manuals_generated/sisu_manual/sisu_faq/portrait.pdf deleted file mode 100644 index cd71e50a..00000000 Binary files a/data/doc/manuals_generated/sisu_manual/sisu_faq/portrait.pdf and /dev/null differ diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/sax.xml b/data/doc/manuals_generated/sisu_manual/sisu_faq/sax.xml deleted file mode 100644 index 52745cdc..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/sax.xml +++ /dev/null @@ -1,547 +0,0 @@ - - - - - - - Title: - - SiSU - FAQ - Frequently Asked/Answered Questions - -
    - Creator: - - Ralph Amissah - -
    - Rights: - - Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 - -
    - Type: - - information - -
    - Subject: - - ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search - -
    - Date created: - - 2006-09-06 - -
    - Date available: - - 2006-09-06 - -
    - Date issued: - - 2006-09-06 - -
    - Date modified: - - 2007-09-16 - -
    - Date: - - 2007-09-16 - -
    - - - - 1 - - SiSU - FAQ - Frequently Asked/Answered Questions,
    Ralph Amissah -
    -
    - - 2 - - 1. FAQ - Frequently Asked/Answered Questions - - - - 3 - - 1.1 Why are urls produced with the -v (and -u) flag that point to a web -server on port 8081? - - - - 4 - - Try the following rune: - - - - 5 - - sisu -W - - - - 6 - - 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. - - - - 7 - - 1.2 I cannot find my output, where is it? - - - - 8 - - The following should provide help on output paths: - - - - 9 - - sisu --help env - - - - 10 - - sisu -V [same as the previous command] - - - - 11 - - sisu --help directory - - - - 12 - - sisu --help path - - - - 13 - - sisu -U [filename] - - - - 14 - - man sisu - - - - 15 - - 1.3 I do not get any pdf output, why? - - - - 16 - - SiSU produces LaTeX and pdflatex is run against that to generate -pdf files. - - - - 17 - - If you use Debian the following will install the required -dependencies - - - - 18 - - aptitude install sisu-pdf - - - - 19 - - the following packages are required: tetex-bin, tetex-extra, latex-ucs - - - - 20 - - 1.4 Where is the latex (or some other interim) output? - - - - 21 - - Try adding -M (for maintenance) to your command flags, e.g.: - - - - 22 - - sisu -HpMv [filename] - - - - 23 - - this should result in the interim processing output being retained, and -information being provided on where to find it. - - - - 24 - - sisu --help directory - - - - 25 - - sisu --help path - - - - 26 - - should also provide some relevant information as to where it is placed. - - - - 27 - - 1.5 Why isn't SiSU markup XML - - - - 28 - - I worked with text and (though I find XML immensely valuable) disliked -noise ... better to sidestep the question and say: - - - - 29 - - SiSU currently "understands" three XML input representations - -or more accurately, converts from three forms of XML to native -SiSU 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 SiSU VERSION CONVERSION - - - - 30 - - sisu --to-sax [filename/wildcard] - - - - 31 - - sisu --to-dom [filename/wildcard] - - - - 32 - - sisu --to-node [filename/wildcard] - - - - 33 - - 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 SiSU markup]. - - - - 34 - - sisu --from-xml2sst [filename/wildcard] - - - - 35 - - 1.6 LaTeX claims to be a document preparation system for high-quality -typesetting. Can the same be said about SiSU? - - - - 36 - - SiSU is not really about type-setting. - - - - 37 - - LaTeX is the ultimate computer instruction type-setting language for -paper based publication. - - - - 38 - - 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. - - - - 39 - - SiSU 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. - - - - 40 - - SiSU 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 SiSU -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. - - - - 41 - - 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. - - - - 42 - - Where there are large document sets, it provides consistency in -appearance in each output format for the documents. - - - - 43 - - 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 SiSU tries to achieve this -from minimal markup. - - - - 44 - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU - - - - 45 - - 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: - - - - 46 - - "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> - - - - 47 - - FTS in PostgreSQL is provided by tsearch2, which should works without -any indices (GiST or GIN) ! Indices provide performance, not -functionality. - - - - 48 - - In your example I'd do ( simple way, just for demo): - - - - 49 - - 0. compile, install tsearch2 and load tsearch2 into your -database - - - - 50 - - cd contrib/tsearch2; -make&&make&&install&&make installcheck; psql DB -< tsearch2.sql - - - - 51 - - 1. Add column fts, which holds tsvector - - - - 52 - - alter table documents add column fts tsvector; - - - - 53 - - 2. Fill fts column - - - - 54 - - update document set fts = to_tsvector(clean); - - - - 55 - - 3. create index - just for performance ! - - - - 56 - - create index fts_gin_idx on document using gin(fts); - - - - 57 - - 4. Run vacuum - - - - 58 - - vacuum analyze document; - - - - 59 - - That's all. - - - - 60 - - Now you can search: - - - - 61 - - 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; - - - - 62 - - 1.8 Where is version 1.0? - - - - 63 - - SiSU 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. - - - - 64 - - The feature set for html,1 LaTeX/pdf and opendocument is in -place. XML, and plaintext are in order. - - - 1 - - html w3c compliance has been largely met. - - - - - 65 - - html and LaTeX/pdf may be regarded as reference copy outputs - - - - 66 - - With regard to the populating of sql databases (postgresql and sqlite), -there is a bit to be done. - - - - 67 - - We are still almost there. - - - - 0 - - Endnotes - - - -
    diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/scroll.xhtml b/data/doc/manuals_generated/sisu_manual/sisu_faq/scroll.xhtml deleted file mode 100644 index f67820e2..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/scroll.xhtml +++ /dev/null @@ -1,545 +0,0 @@ - - - - - - - - Title: - - SiSU - FAQ - Frequently Asked/Answered Questions - -
    - Creator: - - Ralph Amissah - -
    - Rights: - - Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 - -
    - Type: - - information - -
    - Subject: - - ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search - -
    - Date created: - - 2006-09-06 - -
    - Date available: - - 2006-09-06 - -
    - Date issued: - - 2006-09-06 - -
    - Date modified: - - 2007-09-16 - -
    - Date: - - 2007-09-16 - -
    - - - - - SiSU - FAQ - Frequently Asked/Answered Questions,
    Ralph Amissah -
    - 1 -
    - - - 1. FAQ - Frequently Asked/Answered Questions - - 2 - - - - 1.1 Why are urls produced with the -v (and -u) flag that point to a web -server on port 8081? - - 3 - - - - Try the following rune: - - 4 - - - - sisu -W - - 5 - - - - 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. - - 6 - - - - 1.2 I cannot find my output, where is it? - - 7 - - - - The following should provide help on output paths: - - 8 - - - - sisu --help env - - 9 - - - - sisu -V [same as the previous command] - - 10 - - - - sisu --help directory - - 11 - - - - sisu --help path - - 12 - - - - sisu -U [filename] - - 13 - - - - man sisu - - 14 - - - - 1.3 I do not get any pdf output, why? - - 15 - - - - SiSU produces LaTeX and pdflatex is run against that to generate -pdf files. - - 16 - - - - If you use Debian the following will install the required -dependencies - - 17 - - - - aptitude install sisu-pdf - - 18 - - - - the following packages are required: tetex-bin, tetex-extra, latex-ucs - - 19 - - - - 1.4 Where is the latex (or some other interim) output? - - 20 - - - - Try adding -M (for maintenance) to your command flags, e.g.: - - 21 - - - - sisu -HpMv [filename] - - 22 - - - - this should result in the interim processing output being retained, and -information being provided on where to find it. - - 23 - - - - sisu --help directory - - 24 - - - - sisu --help path - - 25 - - - - should also provide some relevant information as to where it is placed. - - 26 - - - - 1.5 Why isn't SiSU markup XML - - 27 - - - - I worked with text and (though I find XML immensely valuable) disliked -noise ... better to sidestep the question and say: - - 28 - - - - SiSU currently "understands" three XML input representations - -or more accurately, converts from three forms of XML to native -SiSU 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 SiSU VERSION CONVERSION - - 29 - - - - sisu --to-sax [filename/wildcard] - - 30 - - - - sisu --to-dom [filename/wildcard] - - 31 - - - - sisu --to-node [filename/wildcard] - - 32 - - - - 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 SiSU markup]. - - 33 - - - - sisu --from-xml2sst [filename/wildcard] - - 34 - - - - 1.6 LaTeX claims to be a document preparation system for high-quality -typesetting. Can the same be said about SiSU? - - 35 - - - - SiSU is not really about type-setting. - - 36 - - - - LaTeX is the ultimate computer instruction type-setting language for -paper based publication. - - 37 - - - - 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. - - 38 - - - - SiSU 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. - - 39 - - - - SiSU 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 SiSU -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. - - 40 - - - - 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. - - 41 - - - - Where there are large document sets, it provides consistency in -appearance in each output format for the documents. - - 42 - - - - 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 SiSU tries to achieve this -from minimal markup. - - 43 - - - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU - - 44 - - - - 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: - - 45 - - - - "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> - - 46 - - - - FTS in PostgreSQL is provided by tsearch2, which should works without -any indices (GiST or GIN) ! Indices provide performance, not -functionality. - - 47 - - - - In your example I'd do ( simple way, just for demo): - - 48 - - - - 0. compile, install tsearch2 and load tsearch2 into your -database - - 49 - - - - cd contrib/tsearch2; -make&&make&&install&&make installcheck; psql DB -< tsearch2.sql - - 50 - - - - 1. Add column fts, which holds tsvector - - 51 - - - - alter table documents add column fts tsvector; - - 52 - - - - 2. Fill fts column - - 53 - - - - update document set fts = to_tsvector(clean); - - 54 - - - - 3. create index - just for performance ! - - 55 - - - - create index fts_gin_idx on document using gin(fts); - - 56 - - - - 4. Run vacuum - - 57 - - - - vacuum analyze document; - - 58 - - - - That's all. - - 59 - - - - Now you can search: - - 60 - - - - 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; - - 61 - - - - 1.8 Where is version 1.0? - - 62 - - - - SiSU 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. - - 63 - - - - The feature set for html,1 LaTeX/pdf and opendocument is in -place. XML, and plaintext are in order. - - - 1. html w3c compliance has been largely met. - - 64 - - - - html and LaTeX/pdf may be regarded as reference copy outputs - - 65 - - - - With regard to the populating of sql databases (postgresql and sqlite), -there is a bit to be done. - - 66 - - - - We are still almost there. - - 67 - - - - Endnotes - - 0 - - -
    diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_faq.sst b/data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_faq.sst deleted file mode 100644 index 73ce274d..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_faq.sst +++ /dev/null @@ -1,191 +0,0 @@ -% SiSU 0.57 - -@title: SiSU - -@subtitle: FAQ - Frequently Asked/Answered Questions - -@creator: Ralph Amissah - -@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 - -@type: information - -@subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search - -@date.created: 2006-09-06 - -@date.available: 2006-09-06 - -@date.issued: 2006-09-06 - -@date.modified: 2007-09-16 - -@date: 2007-09-16 - -@level: new=C; break=1; num_top=1 - -@skin: skin_sisu_manual - -@bold: /Gnu|Debian|Ruby|SiSU/ - -@links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/ -{ Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html -{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU -{ SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/ -{ SiSU @ Ruby Application Archive }http://raa.ruby-lang.org/project/sisu/ -{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html -{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html -{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html -{ SiSU help }http://www.jus.uio.no/sisu/sisu_manual/sisu_help/ -{ SiSU help sources }http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/ - -% @rcs: $Id$ - -:A~? @title @creator - -1~faq FAQ - Frequently Asked/Answered Questions - -2~ Why are urls produced with the -v (and -u) flag that point to a web server on port 8081 ? - -Try the following rune: - -_* sisu -W - -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. - -2~ I cannot find my output, where is it? - -The following should provide help on output paths: - -_* sisu --help env - -_* sisu -V [same as the previous command] - -_* sisu --help directory - -_* sisu --help path - -_* sisu -U [filename] - -_* man sisu - -2~ I do not get any pdf output, why? - -SiSU produces LaTeX and pdflatex is run against that to generate pdf files. - -If you use Debian the following will install the required dependencies - -_* aptitude install sisu-pdf - -the following packages are required: tetex-bin, tetex-extra, latex-ucs - -2~ Where is the latex (or some other interim) output? - -Try adding -M (for maintenance) to your command flags, e.g.: - -_* sisu -HpMv [filename] - -this should result in the interim processing output being retained, and information being provided on where to find it. - -_* sisu --help directory - -_* sisu --help path - -should also provide some relevant information as to where it is placed. - -2~ Why isn't SiSU markup XML - -I worked with text and (though I find XML immensely valuable) disliked noise -... better to sidestep the question and say: - -SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU 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 SiSU VERSION CONVERSION - -_1 sisu --to-sax [filename/wildcard] - -_1 sisu --to-dom [filename/wildcard] - -_1 sisu --to-node [filename/wildcard] - -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 SiSU markup]. - -_1 sisu --from-xml2sst [filename/wildcard] - -2~ LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? - -% what are some similarities and differences between LaTex and SiSU? - -SiSU is not really about type-setting. - -LaTeX is the ultimate computer instruction type-setting language for paper based publication. - -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. - -SiSU 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. - -SiSU 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 SiSU 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. - -% SiSU is a lightweight document abstraction, meta-(structure and markup) syntax designed to make use of a minimal amount of preparation detail that can be used across very different ways of representing documents - -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. - -Where there are large document sets, it provides consistency in appearance in each output format for the documents. - -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 SiSU tries to achieve this from minimal markup. - -2~ How do I create GIN or GiST index in Postgresql for use in SiSU - -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: - -"I have tsearch2 slides which introduces tsearch2 -http://www.sai.msu.su/~megera/wiki/tsearch2slides - -FTS in PostgreSQL is provided by tsearch2, which should works without -any indices (GiST or GIN) ! Indices provide performance, not functionality. - -In your example I'd do ( simple way, just for demo): - -!_ 0. -compile, install tsearch2 and load tsearch2 into your database - -_1 cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql - -!_ 1. -Add column fts, which holds tsvector - -_1 alter table documents add column fts tsvector; - -!_ 2. -Fill fts column - -_1 update document set fts = to_tsvector(clean); - -!_ 3. -create index - just for performance ! - -_1 create index fts_gin_idx on document using gin(fts); - -!_ 4. -Run vacuum - -_1 vacuum analyze document; - -That's all. - -Now you can search: - -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; - -2~ Where is version 1.0? - -SiSU 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. - -The feature set for html,~{ html w3c compliance has been largely met. }~ LaTeX/pdf and opendocument is in place. -XML, and plaintext are in order. - -html and LaTeX/pdf may be regarded as reference copy outputs - -With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. - -We are still almost there. diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_manifest.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_manifest.html deleted file mode 100644 index 290042f0..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/sisu_manifest.html +++ /dev/null @@ -1,200 +0,0 @@ - - - - -SiSU manifest: SiSU - - - - - - - - - - -
    SiSU -->

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/>

    - -
    - - -
    - - - idx - txt - -
    -
    -
    - -

    SiSU - FAQ - Frequently Asked/Answered Questions

    -

    Ralph Amissah

    - - -

    SiSU manifest

    - - - - - - - - - - - - - - -

    description

    filename

    file size

    (kB)

    TOC linked table of contents (for segmented HTML text)

    toc.html

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/toc.html>

    16.9

    Full Text full length document (HTML)

    doc.html

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/doc.html>

    51.8

    PDF portrait full length document (PDF portrait / vertical - recommended for printing)

    portrait.pdf

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/portrait.pdf>

    108.6

    PDF landscape full length document (PDF landscape / horizontal - recommended for screen viewing)

    landscape.pdf

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/landscape.pdf>

    107.6

    ODF/ODT full length document (ODF:ODT - Open Document Format)

    opendocument.odt

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/opendocument.odt>

    11.1

    full length document (XHTML)

    scroll.xhtml

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/scroll.xhtml>

    13.5

    full length document (XML SAX)

    sax.xml

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sax.xml>

    13.4

    full length document (XML DOM)

    dom.xml

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/dom.xml>

    16.3

    full length document (plaintext (UTF-8))

    plain.txt

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/plain.txt>

    9.7

    Concordance file (HTML - wordmap, alphabetical wordlist)

    concordance.html

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/concordance.html>

    84.2

    Digest/DCC - Document Content Certificate (md5)

    digest.txt

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/digest.txt>

    10.3

    - - -

    Markup (SiSU source)

    sisu_faq.sst   41577c9fc063cd232914a1a11a59e91a
    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisu_faq.sst>

    8.1

    -

    SiSU doc (zip)

    sisupod.zip   bb45a9bfb89b1919664d84d92a797ed1
    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisupod.zip>

    6.2

    -

    SiSU manifest of document metadata

    - - - - - - - - - - - - - - - - - - - - - - - -

    metadata

    description

    DC Title:

    SiSU - FAQ - Frequently Asked/Answered Questions

    Title:

    SiSU

    Subtitle:

    FAQ - Frequently Asked/Answered Questions

    DC Creator:

    Ralph Amissah

    DC Publisher:

    SiSU http://www.jus.uio.no/sisu (this copy)

    DC Subject:

    ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search

    DC Type:

    information

    DC Rights:

    Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3

    DC Date:

    2007-09-16

    DC Date created:

    2006-09-06

    DC Date issued:

    2006-09-06

    DC Date available:

    2006-09-06

    DC Date modified:

    2007-09-16

    DC Language:

    English

    DC Identifier:

    http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/toc.html

    Sourcefile:

    sisu_faq.sst

    Word Count approximate:

    1201

    Sourcefile Digest (md5):

    41577c9fc063cd232914a1a11a59e91a

    Document (metaverse) last generated:

    Tue Sep 25 02:54:45 +0100 2007

    Generated by:

    SiSU 0.59.1 2007w39/2 (2007-09-25)

    Ruby version:

    ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux]

    - - - - - - - - - - - - -

    metadata suggested links:

    SiSU Manual

      <http://www.jus.uio.no/sisu/sisu_manual/>

    Book Samples and Markup Examples

      <http://www.jus.uio.no/sisu/SiSU/2.html>

    SiSU @ Wikipedia

      <http://en.wikipedia.org/wiki/SiSU>

    SiSU @ Freshmeat

      <http://freshmeat.net/projects/sisu/>

    SiSU @ Ruby Application Archive

      <http://raa.ruby-lang.org/project/sisu/>

    SiSU @ Debian

      <http://packages.qa.debian.org/s/sisu.html>

    SiSU Download

      <http://www.jus.uio.no/sisu/SiSU/download.html>

    SiSU Changelog

      <http://www.jus.uio.no/sisu/SiSU/changelog.html>

    SiSU help

      <http://www.jus.uio.no/sisu/sisu_manual/sisu_help/>

    SiSU help sources

      <http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/>

    -

    Document Language Versions, manifests

    - - - - -

    filename

    description

     

    English

    English

    <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisu_manifest.html>

     

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/sisupod.zip b/data/doc/manuals_generated/sisu_manual/sisu_faq/sisupod.zip deleted file mode 100644 index 2eb149e3..00000000 Binary files a/data/doc/manuals_generated/sisu_manual/sisu_faq/sisupod.zip and /dev/null differ diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/sitemap.xml b/data/doc/manuals_generated/sisu_manual/sisu_faq/sitemap.xml deleted file mode 100644 index f7ca3c1d..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/sitemap.xml +++ /dev/null @@ -1,30 +0,0 @@ - - - - - - http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/toc.html - 2007-09-16 - monthly - 0.7 - - - http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/doc.html - 2007-09-16 - 0.5 - - - http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/sisu_manifest.html - 2007-09-16 - 0.5 - - diff --git a/data/doc/manuals_generated/sisu_manual/sisu_faq/toc.html b/data/doc/manuals_generated/sisu_manual/sisu_faq/toc.html deleted file mode 100644 index 543d4b4e..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_faq/toc.html +++ /dev/null @@ -1,550 +0,0 @@ - - - - - - SiSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - - - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - -
    - - TOC linked  toc  - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    -   - next >> -   -
    -

    - -

    - -
    - - -
    - -

    SiSU -

    - -

    FAQ - Frequently Asked/Answered Questions -

    - -

    Ralph Amissah -

    - -copy @ - - SiSU - - -
    - - - -

    - SiSU - FAQ - Frequently Asked/Answered Questions,
    Ralph Amissah -

    - -

    - - 1. FAQ - Frequently Asked/Answered Questions - -

    - -
    - - 1.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? - -
    - -
    - - 1.2 I cannot find my output, where is it? - -
    - -
    - - 1.3 I do not get any pdf output, why? - -
    - -
    - - 1.4 Where is the latex (or some other interim) output? - -
    - -
    - - 1.5 Why isn't SiSU markup XML - -
    - -
    - - 1.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? - -
    - -
    - - 1.7 How do I create GIN or GiST index in Postgresql for use in SiSU - -
    - -
    - - 1.8 Where is version 1.0? - -
    - -

    - - Endnotes - -

    - - - Document Information (metadata) - - -

    Rights: Copyright ©  Ralph Amissah 2007, part of SiSU documentation, License GPL 3

    -

    - -

    - - - - - -
    - -
    SiSU -->
    -
    - - - - - - - - - - - - - - - -
    - - TOC linked  toc  - - - - - Full Text  scroll  - - - - - - PDF portrait -   pdf  - - - - - - PDF landscape -   pdf  - - - - - - ODF/ODT  odt  - - - - - - -   A-Z  - - - - - - Document Manifest  - - - - - @ -
    -
    -   - next >> -   -
    -

    - -

     

    - - - - - - - - -
    - -
    -

    - - SiSU - -

    -
    - -

    - Output generated by - - SiSU - - 0.59.1 2007-09-25 (2007w39/2) -
    - - SiSU - - Copyright © Ralph Amissah - 1997, current 2007. - All Rights Reserved. -
    - - SiSU - - is software for document structuring, publishing and search, -
    - - www.jus.uio.no/sisu - - and - - www.sisudoc.org - -
    - w3 since October 3 1993 - - ralph@amissah.com - -

    -
    -

    - SiSU using: -
    Standard SiSU markup syntax, -
    Standard SiSU meta-markup syntax, and the -
    Standard SiSU object citation numbering and system, (object/text positioning system) -
    - Copyright © Ralph Amissah 1997, current 2007. - All Rights Reserved. -

    -
    -

    - - GPLv3 - -

    -
    -

    - - SiSU - - is released under - GPLv3 - or later, - <http://www.gnu.org/licenses/gpl.html> -

    -
    -

    - SiSU, developed using - - Ruby - - on - - Debian/Gnu/Linux - - software infrastructure, - with the usual GPL (or OSS) suspects. -
    - Better - "performance, reliability, scalability, security & total cost of ownership" - [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre. -
    - Get With the Future - - Way Better! - -

    -
    - - - - - - - -
    - - - - - - -- cgit v1.2.3