OpenLLM-France/wikimedia huggingface dataset:
# Scribus

Scribus is a desktop publishing program (DTP) that is free software licensed under the GNU General Public License. It is cross-platform: There are versions available for GNU/Linux, Mac OS X, OS/2, and Windows. This makes Scribus suitable for minor to medium audience publications, which were designed collaboratively in non-corporate organizations. The current stable version is 1.4.6. SLA files are the native format for Scribus. You can export files into PDF, EPS, SVG and raster images.
This book is addressed to readers who are not yet familiar with any DTP software. Applications like OpenOffice, LibreOffice, and MS Word are word-processing software, not desktop publishing software. Word processors are concerned primarily with editing text. Desktop publishing software is concerned primarily with layout (e.g. placement of columns, images, headlines, etc.)

## Content

* Overview
** Installation
** LaTeX
* Workflow
** Basic concepts
** Introduction into textframes
** Images
** Textframes
* Appendix
** Shortcut reference
** External links
# Scribus/External links

Links:
* Scribus, archive.flossmanuals.net, 2013 -- pdf; license: stated as None, whatever that means
* Scribus: An introduction to desktop publishing by Dave Baker, 2012-2014, weblearn.ox.ac.uk -- license: CC BY-NC-SA
* scribus, sourceforge.net
* Scribus web site, cribus.net -- currently down
# Scribus/Installation

Scribus can be installed in a number of ways.

## On GNU/Linux

Scribus can typically be installed via a package manager.
# Scribunto: An Introduction/Using invoke

If you are used to the syntax of MediaWiki templates, then you might be wondering about the syntax of the #invoke statement we saw in the previous chapter. The #invoke statement looked like this:
As you can see, there are three parts: #invoke:, Hello, and hello_world. If we compare this to a template that does the same thing - outputs the text "Hello, world!" - we can see that there is only one part.
The shared part is Hello, and in both cases this corresponds to the page name. For #invoke, it corresponds to the page Module:Hello, and for the template it corresponds to the page Template:Hello. This leaves us with two extra parts to the #invoke statement: the #invoke: code itself, and hello_world.
The #invoke: code is quite straightforward; all it is there to do is to tell the MediaWiki software that it is dealing with a Lua module, and not with a template or any other kind of special text. The hello_world code is where things get interesting.
You may have noticed that hello_world appears in the middle of Module:Hello:
It appears in a block of that starts with the keyword "function" and ends with the keyword "end". This is a function. Functions in Lua are a lot like MediaWiki templates. You give templates input, the template processes the input, and it gives you some output. Functions are just the same; you give them input, the function processes the input, and it returns some output.
In this case, we are not providing any input, as our function is very simple. (Later we will learn how to use the parentheses after hello_world to control input we are given.) The output in Lua functions is provided by the return keyword. In this case we are saying, "make a function with no inputs that outputs the text 'Hello, world!'" At the same time, we have given the function a name. While there are other ways to define a function in Lua, in this example the function name is everything after the code function and before the parentheses. In other words, the function name is p.hello_world.
So why the p.? Why not just make the name hello_world? The answer is that the p. is how we tell Scribunto that we want our function to be available from #invoke. If we leave out the p., then we cannot run our function directly from any wiki pages. (There are ways that the function can be run indirectly, but we will not cover those for now.)

## Notes

* ↑ Text that has a special function in MediaWiki is known as a magic word, and technically an #invoke statement is a particular kind of magic word called a parser function. You can see more documentation about magic words and parser functions at https://www.mediawiki.org/wiki/Help:Magic_words.
# Scribus/Printable version

The current, editable version of this book is available in Wikibooks, the open-content textbooks collection, at
https://en.wikibooks.org/wiki/Scribus

# Installation

Scribus can be installed in a number of ways.

## On GNU/Linux

Scribus can typically be installed via a package manager.

# Basic concepts
## Tools
### Select Item

Shortcut: c
Used to select and move items.
Insert Text Frame Shortcut: t
Insert Image Frame
* Shortcut: i
To add an image, draw an image frame in the document. Right-click on the frame and select Get Image (or press Ctrl-D). The X, Y, Z panel of the Properties panel controls the settings of the image (position and scale). To make text wrap around the picture, in the Shape panel, check the box next to "Text Flows Around Frame."
Insert Table
* Shortcut: a
Insert Shape
* Shortcut: s
Insert Polygon
* Shortcut: p
Insert Line
* Shortcut: l

## Properties Panel

This is at the bottom of the menu you get from selecting and right-clicking an item. You can also open it by pressing F2. There are 6 sections to the Properties panel:
* X, Y, Z
* Shape
* Text
* Image
* Line
* Colors

## Tips

Objects are layered on top of each other in a "stack". You can select items that are stacked below other items by ctrl-shift-clicking on the stack.

# External links

Links:
* Scribus, archive.flossmanuals.net, 2013 -- pdf; license: stated as None, whatever that means
* Scribus: An introduction to desktop publishing by Dave Baker, 2012-2014, weblearn.ox.ac.uk -- license: CC BY-NC-SA
* scribus, sourceforge.net
* Scribus web site, cribus.net -- currently down
# Scribus/Basic concepts
## Tools
### Select Item

Shortcut: c
Used to select and move items.
Insert Text Frame Shortcut: t
Insert Image Frame
* Shortcut: i
To add an image, draw an image frame in the document. Right-click on the frame and select Get Image (or press Ctrl-D). The X, Y, Z panel of the Properties panel controls the settings of the image (position and scale). To make text wrap around the picture, in the Shape panel, check the box next to "Text Flows Around Frame."
Insert Table
* Shortcut: a
Insert Shape
* Shortcut: s
Insert Polygon
* Shortcut: p
Insert Line
* Shortcut: l

## Properties Panel

This is at the bottom of the menu you get from selecting and right-clicking an item. You can also open it by pressing F2. There are 6 sections to the Properties panel:
* X, Y, Z
* Shape
* Text
* Image
* Line
* Colors

## Tips

Objects are layered on top of each other in a "stack". You can select items that are stacked below other items by ctrl-shift-clicking on the stack.
# ROSE Compiler Framework/Constant Propagation

Please see also ROSE Compiler Framework/Generic Dataflow Framework since this analysis is implemented using the framework.

## overview

See http://en.wikipedia.org/wiki/Constant_folding for the examples of constant folding and constant propagation "Constant propagation is the process of substituting the values of known constants in expressions at compile time. "

## Example

The analysis will only generate lattices representing the propagated constant values. It will NOT actually transform the AST! So the example code below is used to only illustrate the propagation of values.
Input code
Propagating x yields:
Continuing to propagate yields the following:

## Source files

List
* rose/tests/roseTests/programAnalysisTests/generalDataFlowAnalysisTests/constantPropagation.h
* rose/tests/roseTests/programAnalysisTests/generalDataFlowAnalysisTests/constantPropagation.C
TODO
* move them into rose/src/midend/programAnalysis/genericDataflow/simpleAnalyses

## Tests

test translator
* rose/tests/roseTests/programAnalysisTests/generalDataFlowAnalysisTests/constantPropagationTest.C github-link
The test translator will
* generate dot graph for the CFG and attached constant lattice.
* verify the generated results are expected (given as pragmas in the input test input file)
test input with verification
* rose/tests/roseTests/programAnalysisTests/generalDataFlowAnalysisTests/cp_test1.C
# ROSE Compiler Framework/FailSafe Assertion Language

An experimental source code annotation language to support resilient computing.
Quick information
* source files: ROSE/src/roseExtensions/failSafe/ failSafePragma.C failSafePragma.h
* test directory: ROSE/tests/CompileTests/FailSafe_tests
# ROSE Compiler Framework/Documentation

ROSE uses a range of materials to document the project.
The website uses WordPress as frontend. Most documentations can also be directly accessed by using the old static webpage: http://rosecompiler.org/index.html
* ROSE manual: the design, algorithm, and implementation details. Written in LaTeX, the content of the manual can come from published papers. It may contain intense academic citations and math formula.
** http://rosecompiler.org/ROSE_UserManual/ROSE-UserManual.pdf
* ROSE tutorial: short code examples for tools built on top of ROSE, step-by-step instructions for doing things. Tightly integrated into ROSE's build system so each example is always verified to work with ROSE.
** http://rosecompiler.org/ROSE_Tutorial/ROSE-Tutorial.pdf
* Doxygen web reference: class/namespace references of source code
** http://rosecompiler.org/ROSE_HTML_Reference/index.html
Wiki
# Political History of New Zealand
## Chapters

    Preface
    Introduction
* Pre-European Government
* The Treaty of Waitangi
* Early European Government in New Zealand
* The First Political Parties in New Zealand
* Provincial Governments
* Political Policies in the Twentieth Century
* MMP Introduced
* The New Zealand Government Today
    Bibliography
    Authors and Contributors

## External links

* Government and Nation: Te Ara Encyclopedia of New Zealand
# Political History of New Zealand/Early European Government

‹ Back to The Treaty of Waitangi

## Early European Government in New Zealand

After New Zealand was annexed by Britain, it was initially set up as a dependency of New South Wales. However, by 1841, New Zealand was made a colony in its own right. As a colony, it inherited political practices and institutions of government from the United Kingdom.
The United Kingdom Government started the first New Zealand Government by appointing governers, being advised by appointed executive and legislative councils.
In 1852, the British Parliament passed the New Zealand Constitution Act, which provided for the elected house of representitives and legislative council. The General Assembly (the House and Council combined) first met in 1854.
New Zealand was effectively self-governing in all domestic matters except 'native policy' by 1856. Control over native policy was passed to the Colonial Government in the mid-1860s.
Forward to The First Political Parties ›
# Political History of New Zealand/Introduction

‹ Back to the Preface

## Introduction to Political History of New Zealand

This textbook covers the history of Government in New Zealand, from the early Maori independence, through to the modern Westminister form of Government.
Its main topics include:
* The Constitution.
* The Introduction of the Westminister system.
* Political Parties.
* Provincial Governments.
* First Past the Post and MMP systems.
* Policies of Government.
Forward to Pre-European Government ›
# Political History of New Zealand/Authors

‹ Back to the Bibliography

## Authors and Contributors

Original Author: Helpfulstuffnz
# Political History of New Zealand/Provincial Governments

‹ Back to The First Political Parties in New Zealand

## Provincial Governments in New Zealand

From 1841 until 1876, provinces had their own Provincial Governments. Originally, there were only three provinces, set up by the Royal Charter:
* New Ulster (North Island north of Patea River)
* New Munster (North Island south of Patea River, plus the South Island)
* New Leinster (Stewart Island)
In 1846, the provinces were reformed. The New Leinster province was removed, and the two remaining provinces were enlarged and separated from the Colonial Government. The reformed provinces were:
* New Ulster (All of North Island)
* New Munster (The South Island plus Stewart Island)
The provinces were reformed yet again by the New Zealand Constitution Act 1852. In this constitution, the old provinces of New Ulster and New Munster were abolished and six new provinces were set up:
* Auckland
* New Plymouth
* Wellington
* Nelson
* Canterbury
* Otago
Each province had its own legislature that elected its own Speaker and Superintendent. Any male 21 years or older that owned freehold property worth £50 a year could vote. Elections were held every four years.
Four new provinces were introduced between November 1858 and December 1873. Hawkes Bay broke from Wellington, Marlborough from Nelson, Westland from Canterbury, and Southland from Otago.
Not long after they had begun, Provincial Governments were under political debate in the General Assembly. Eventually, under the premiership of Harry Atkinson, the Colonial Government passed the Abolition of Provinces Act 1876 which wiped out the Provincial Governments, replacing them with regions. Provinces finally ceased to exist on 1 January 1877.
Forward to Political Policies in the Twentieth Century ›
# Political History of New Zealand/Bibliography

‹ Back to The New Zealand Government Today

## Bibliography

Websites
* Te Ara Encyclopedia of New Zealand
Forward to Authors and Contributers ›
# Political History of New Zealand/Preface
## Intention of this book

The intention of this book is to provide the first, to the best of our knowledge, open-content textbook on the political history of New Zealand that is easy for anyone who is interested to read.

## A Note to Authors

This book is a work in progress, so feel free to contribute to it in places you see as unfinished or lacking information.
The only major guidelines that authors of this project should follow, are to use New Zealand (British) spelling and to follow the Wikibooks rules on unbiased writing.
Continue to the Introduction ›
# Spanish/Infinitive

The infinitive is the simple, unconjugated form of a verb. It does not indicate who is doing the action or any time reference. "To be" is a verb in the English infinitive form. "Ser" is a verb in the Spanish infinitive form. When you look up a verb in the dictionary it is found in the infinitive form.
In Spanish the infinitive forms always end with "ar", "er" or "ir". Examples: "amar" (to love), "temer" (to fear), "partir" (to leave).
The infinitive can be used for a lot of things in Spanish grammar. It functions as a gerund in Spanish. In the following examples, I will use "nadar" (to swim):
* Yo quiero "nadar".--- I want to swim.
* Yo pensaba que "nadar" era divertido---I used to think that swimming was fun
# Spanish/Ir

Ir is an irregular verb that means to go.
    Infinitive: ir
    Present Participle: yendo
    Past Participle: ido

## Indicative
### Present

    Yo voy
    Tú vas
    Él/Ella/Ud. va
    Nosotros vamos
    Vosotros váis
    Ellos/Uds. van

### Preterite

    Yo fui
    Tú fuiste
    Él/Ella/Ud. fue
    Nosotros fuimos
    Vosotros fuistéis
    Ellos/Uds. fueron

### Imperfect

    Yo iba
    Tú ibas
    Él/Ella/Ud. iba
    Nosotros íbamos
    Vosotros ibáis
    Ellos/Uds. iban

### Future

    Yo iré
    Tú irás
    Él/Ella/Ud. irá
    Nosotros iremos
    Vosotros iréis
    Ellos/Uds. irán

## Subjunctive
### Present

    Yo vaya
    Tú vayas
    Él/Ella/Ud. vaya
    Nosotros vayamos
    Vosotros vayáis
    Ellos/Uds. vayan
Back to Spanish.
# Spanish/Imperative

Verbs | Verb Tenses | Verbs List

## Imperativo

This form gives commands.
To form the imperative mood of verbs, one normally takes the present subjunctive of the verb.
The major exceptions to this rule are the second person singular and plural forms of positive command. To form a positive second person singular command, use the third person singular indicative. To form a positive second person plural command, take the stem of the verb and add:
-ad if the verb is an ar verb.
-id if the verb is an ir verb.
-ed if the verb is an er verb.
Note that when making a negative command, such as "no cantes" (don't sing), the present subjunctive is used.
There are many exceptions to these rules.
* Imperativo o, "el mandato"
# Spanish/Lesson 10

| Lessons: | 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 |

## Grammar - Future

In Spanish, the future has the same function as the future in English - to state things that will happen. Its use is equal to verbs ending in -ar, -er and -ir for regular verbs.
Example:
| Verb | Hablar | Comer | Vivir |
| yo | hablar - é | comer - é | viver - é |
| tu | hablar - ás | comer - ás | viver - ás |
| el/usted | hablar - á | comer - á | viver - á |
| nosotros | hablar - emos | comer - emos | viver - emos |
| vosotros | hablar - éis | comer - éis | viver - éis |
| ellos/ustedes | hablar - án | comer - án | viver - án |
There are some irregular verbs that have different conjugations in the future for the first person - yo:
* venir: vendr - é
* tener: tendr - é
* poner: pondr - é
* salir: saldr - é
* poder: podr - é
* hacer: har - é
* querer: querr - é

## Functions
### Soon realization

To express a plan for soon realization you need to use ir a + infinitivo. Example: Voy a visitar mi amigo. This means I'll leave to visit my friend soon, maybe in the next hour.

### Realization decided

To express that a plan is really going to happen you need to use pensar + infinitivo. Example: Penso visitar mi amigo. This means I will, but maybe in weekend, maybe next week.

### Realization not decided yet

To express that a plan may happen as you are not sure use estar pensando en + infinitivo. Example: Estoy pensando en visitar mi amigo. This means I am just planning, not sure yet.
| Lessons: | 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 |
# Spanish/Imperfect

Verbs
The imperfect tense communicates:
* continuing past events (translates English was/were __ing)
* customary, habitual events in the past
* planned future events
Verbs are conjugated to the imperfect by taking off the last two letters of the infinitive and replacing them with an ending based on -ía or -aba.

## Conjugating regular verbs in the imperfect

This is probably the easiest verb tense to conjugate.
-AR verbs take on the -aba endings. Here is an example:
Bailar (to dance)
bailaba: I danced bailabas: you danced bailaba: he, she, it, you (formal) danced bailábamos: we danced
bailabais: you danced
bailaban: they, you (plural, formal) danced
-IR and -ER verbs take on -ía endings. Examples:
Venir (to come)
venía: I came
venías: you came
venía: he, she, it, you came
veníamos: we came
veníais: you came venían: they, you (formal) came
Comer (to eat)
comía: I ate
comías: you ate
comía: he, she, it, you ate
comíamos: we ate
comíais: you ate comían: they, you (formal) ate

## Irregular verbs

There are only three.
Ser (to be)
era: I was
eras: you were
era: he, she, it was, you were
éramos: we were
erais: you were
eran: they were
Notice the accent in the "nosotros" form of "ser" and "ir."
Ir (to go)
iba: I used to go ibas: you used to go
iba: he, she, it, you used to go
íbamos: we used to go
ibais: you used to go
iban: they used to go
Ver (to see)
veía: I used to see veías: you used to see
veía: he, she, it, you used to see
veíamos: we used to see veíais: you used to see veían: they used to see
That's it! Those are all the irregulars.
# Spanish/Imperfect Subjunctive

Verbs | Verb Tenses
The Imperfect Subjunctive is related to the pretérito and imperfecto de indicativo as the presente de subjuntivo is related to the presente de indicativo. That is, when the verb of the independent clause is in the present, the present subjunctive is used in the dependent clause, and when the verb of the independent clause is in the preterite or imperfect, the imperfect subjunctive is used.
    No quiero que rompas la lámpara. —I don't want you to break the lamp.
    No quería que rompieras la lámpara. —I didn't want you to break the lamp.

### Conjugations

Similar to the presente de subjuntivo, begin with the third-person plural-form of the pretérito (ellos, ellas, and Ustedes). Then, remove the -ron and add the following endings.
Hablar hablaron -> habla-
Comer comieron -> comie-
Vivir vivieron -> vivie-
# Spanish/Indicative

Verbs | Verb Tenses | Verbs List

## El indicativo

These eight simple verb tenses and four compound tenses refer to an objective reality and are categorized by time: present, past, and future. These verb tenses are the simplest and most commonly used.
    Tiempos presentes
* Presente, presente progresivo
* Presente perfecto
    Tiempos pasados
* Imperfecto, imperfecto progresivo
* Pretérito, Pretérito progresivo
* Pluscuamperfecto o, perfecto pasado indicativo
* Pretérito perfecto o, pasado anterior indicativo
    Tiempos futuros
* Futuro
* Futuro perfecto o, futuro anterior, futuro anterior indicativo
# Sikhism

Sikhism is a religion from the Indian sub-continent. It originated in the Punjab region during the 15th century from a sectarian split within the Hindu tradition. Sikhs consider their faith to be a separate religion from Hinduism. Sikhs call their religion Gurmat, which is Punjabi for "way of the guru". The guru is a fundamental aspect of all Indian religions but in Sikhism has taken on an importance that forms the core of Sikh beliefs. The religion was founded in the 15th century by Guru Nanak (1469–1539). There followed in succession a further 10 gurus. Sikhs acknowledge the last physical human body guru to be Guru Gobind Singh (1666–1708). The Sikh's holy book is Guru Granth Sahib (The Granth as the Guru) and this is considered the summation of the ten gurus and their beliefs. The title reflects the Sikh belief that their holy book is now the sole "guru" for guidance and instruction.

## Contents

* Introduction
* Sri Guru Nanak Dev Ji
* Sri Guru Angad Dev Ji
* Sri Guru Amar Das Ji
* Sri Guru Ram Das Ji
* Sri Guru Arjun Dev Ji
* Sri Guru Hargobind Ji
* Sri Guru Har Rai Ji
* Sri Guru Harkrishan Ji
* Sri Guru Tegh Bahadur Ji
* Sri Guru Gobind Singh Ji
* Sri Guru Granth Sahib Ji
* Dictionary
# Sikhism/Dictionary

This dictionary contains words and terms used in Sikhism arranged alphabetically.

## Dictionary

* Amrit is a drink of water and sugar that young Sikhs take during their initiation into the Khalsa brotherhood. The drink is served in an iron bowl.
* Khālsā (Punjabi: ਖ਼ਾਲਸਾ, literally "Pure") is a term of Persian origin which refers to the collective body of all baptized Sikhs. The Khalsa was originally established as a military order of "saint-soldiers" on March 30, 1699, by Guru Gobind Singh, the tenth Sikh Guru. It was the name given by the Guru to all his disciples baptized in the Amrit Sanchar ceremony.
* Sat Nam is a mantra. In Sanskrit, sat means "truth" and nam means "identity". There are various interpretations of this mantra: truth is my identity or The essence of God is within me. Other common interpretations include: express the truth within you or in name there is truth and the light shines in you with light as a metaphor for truth.
# Signetics 2650 & 2636 programming/Tutorial code - programming colours
## Tutorial code - Programming colours

This is the code for the tutorial Programming colours
# Signetics 2650 & 2636 programming/Tutorial code - score
## Tutorial code - Score

This is the code for the tutorial Score
# Signetics 2650 & 2636 programming/Tutorial code - objects
## Tutorial code - Objects

This is the code for the tutorial Objects
# Signetics 2650 & 2636 programming/Tutorial code - sync to VRST
## Tutorial code - Sync to VRST

This is the code for the tutorial Sync to VRST
# Signetics 2650 & 2636 programming/Tutorial code - sync to object completion
## Tutorial code - Sync to object completion

This is the code for the tutorial Sync to Object completion
# OpenURI

OpenURI can be used to download a web page. Ex:
See also Net::HTTP
# Ripper

Ripper is a C-based Ruby parser available in MRI 1.9+
It parses ruby code into an AST, including comments. YARD for example, uses it, as does the assert2 gem.
Note that there are some other ruby parsers available (some written in ruby), for example the Redparse gem.