Welcome to the selo repository. It contains all the files you need to typeset your own edition of lipu tenpo. This file has all the instructions you need to do that.
At least, on the long term. Because, as of now, this document is not yet complete. jan Kasape, the designer, is working on it. Please don’t trip over the ‹TODO›s.
The instructions may also change over time, because the design style of lipu tenpo is constantly being worked on. The folder structure also changed over time, because I gradually learn what works best.
To make an edition of lipu tenpo, you need
git
Sometimes, a bitmap-processing tool like [GIMP]() can also be helpful. I needed it once.
Scribus is the main tool that you will use. This section contains some tips for your workflow.
Turn off hyphenation.
If you use Inkscape, copy the file /lipu-tenpo.gpl
to where Inkscape stores its palettes, which is probably ~/.config/inkscape/palettes
if you use Linux. Then, in Inkscape, select it using TODO.
Copy the template file TODO into the folder of the edition.
This table contains the entire palette. TODO
The palette is in the GIMP .gpl
format. To convert the palette into CSS colours, you can use this script.
Properties, Item Properties, Align and Distribute, Scrapbook, TODO
TODO Show margins, boxes, text flow, rulers relative to page. Toggle these options all on or off using F11.
Clone the selo repository onto your device. If you already have the edition, ensure it is up-to-date using git pull
.
If you make a new edition, TODO.
If you make a different version of an edition, make its folder.
In the root of the directory, make a new folder for the edition. Its name must be the name of the edition. For instance, /nanpa lipu
. In the folder of the edition, create three folders: ijo
, sitelen
, and toki
.
In addition, you must know the following:
TODO use the files that you need for all editions, move them to /ali
import with Control + i
.
Line breaks are like paragraph breaks to Scribus. You must adjust them manually.
text wrap positioning: integers. this is for the greyscale version. illustrator: in footnote style next to the image
Footnote in the text: regular letter (or superscript? TODO), and apply the style nanpa lili sewi TODO.
Every article has a title, and every title has a background shape. You must draw this background shape manually. For every article, do this:
ijo/ko.svg
in Inkscape.ijo/ko.svg
in Inkscape.Now that you have drawn all the blobs, it is time to export them.
l
.path0053
TODO would be replaced by jan li toki pona
.e
.You now have a file for each background shape. Let’s put it in Scribus. For every article, do this:
i
.Change the text in the textbox to the name of the edition. The textbox is positioned TODO.
The proportions of the front-cover image are preferably TODO.
The front-cover image is usually in SVG format, because jan Simo usually draws it.
The second page of an edition has four parts.
The edge is a vector file. It has a bleed of 3 mm. You must make one yourself for each edition. Use one blob for each of the four colours. On either side of the cover, exactly three must be visible. Make sure that the distribution of these blobs is not the same as in the previous two editions. TODO
Add attributes Generate Table of Contents
The jan pali section contains the names of all people who contributed to the edition.
For each part, the names are sorted alphabetically, that is: a e i j k l m n o p s t u w
,
and the pseudo-letter ‹end of word› goes before all of them, as usual.
But we use some extra rules, because, in Toki Pona, the structure of a name is [one or more nouns] [one or more proper names], where a noun is lowercased and the first letter of a proper name is capitalised.
These are the rules:
Sort by proper name, not noun.
If two people have the same proper name, but a different headnoun, break the tie using the noun.
If a name contains multiple proper names, ignore the spaces between them.
If different people with the same name contributed, include them both.
TODO add no-break spaces in the names and after <
.
If a name does not follow the structure [one or more nouns] [one or more proper names], then do what makes most sense.
If someone prefers their proper name to be spelt with a lowercase letter, then treat it as if it were capitalised.
If a name contains only a headnoun, treat it as a proper name.
But if a name consists of multiple words and no proper name, many orderings may make sense. You might want to ignore particles like ‹pi›, and put ‹jan pi nimi ala› before TODO, such as in nanpa TODO.
jan Nalu ? jan pi nimi ala
Once the names are sorted, do the following:
+
. It resembles the ‹en› of the sitelen pona writing system.+
, and a no-break space after the +
.A no-break space is the symbol
.
u
, a0
, Return.If you don’t want to type it, break the paragraph manually with soft breaks. These move to the next line without starting a new paragraph. In Scribus, and in many other places too, you can insert a soft break with Shift + Return.
jan Sonatan will usually break the lines for you in a good way.
First and last line is in the style toki wawa and has colour unu pimeja.
In the last line, use an en dash (–
), like this: – jan Sonatan
.
manual adjustment: arrows, pini, table of contents
images: use integers for scaling and panning, because you have to remember them
checks
SVG images, such as front cover: in Properties, set the right dimensions and position.
images must have same dimensions and same positioning
ungroup the front and back cover with Control + Shift + g
.
you can remove the objects that are not displayed on the page, but it’s not necessary. If you do, then the pre-flight verifier in Scribus will raise some errors like ‹Object is not on a Page TODO› before you export the document. You can ignore them.
Front cover: use your imagination; make front and back look good. Use only the colours ‹kiwen› and ‹kiwen walo›
16 - 1 , 2 - 15 , 14 - 3 , 4 - 13, 12 - 5, 6 - 11, 10 - 7, 8 - 9
Please see https://github.com/lipu-tenpo/selo/issues/2
I have never made a sitelen pona version yet, so I don’t know what it’s like. Once I have done it, I’ll share my experiences in this document.