lipu lawa pi esun kama

lipu lawa pi esun kama

lipu lawa pi esun kama: a contract for future sales

see it larger

This conceptual piece was born in the toki pona discussion forums where Matthew Martin (jan Mato) proposed writing up a sales contract in toki pona. He reasoned that if contracts in foreign languages could be held valid, than one in an artificial language should be valid as well. As a challenge, he asked if anyone wanted to sell him something using a toki pona contract.

I responded by proposing that we write a contract in toki pona for the sale of a sitelen sitelen drawing. The entire negotiation took place in toki pona, aside from grammatical corrections proposed by others during the project, and a brief exchange in English when I wanted to assure him that I was looking to do this for the experiment, not the money.

The contract loosely translated proposed this: we as two agents will create a contract for an exchange of goods. The contract language will then be translated into the hieroglyphics, and I will draw two copies of the contract, sign both, and send them to Matthew. He in turn signs both, keeps one and returns the other with payment. In the end we both have a copy of the artwork which doubles as a contract for the sale of itself.

Here is the forum post where Matthew proposes creating a contract.
Here is the forum where the contract was publicly negotiated.
Here is a forum where Matthew describes his experiences in the exchange.

One of the most absurd things for me in the exchange was the absence of numbers in toki pona. the unofficial convention for 100 is to use ale but this also means all. So where the contract says “mani Mewika pi nanpa ale”. Does this looks like all the numbers of American money or $100? Toki pona would probably the better in a barter economy, but at some point, aren’t you still going to have to say “100 sheep for your house”? Maybe numbers should be a non verbal exchange — you throw down the number your are talking about in beans. Need to express a very big number? Better get a bunch of beans!

I was going to translate word for word the contract here, but now I realize it’s never been done. We were both satisfied with the results of the exchange, so I think the goal of the language worked. But I’m curious just how much of what I thought the contract said actually comes across. If you want to take a stab at translating some or all of it, go ahead and post it in the comments section. Here is the contract as written:

lipu lawa pi esun kama

jan Mato li jan pi wile jo. jan josan li jan pali. jan pi wile jo en jan pali li wile e esun.

nanpa wan la, jan pi wile jo en jan pali li sitelen e lipu lawa pi esun kama.

nanpa tu la, lipu lawa pi esun kama li pona tawa ona tu la, jan pali li pali e sitelen. sitelen ni li kepeken e toki sama toki pi lipu lawa pi esun kama. jan pali li pali e sitelen tu. sitelen tu li sama.

nanpa tu wan la, jan pali li pana e sitelen tu tawa jan pi wile jo.

nanpa tu tu la, jan pi wile jo li pana e linja nimi ona lon sitelen nanpa wan en sitelen nanpa tu. jan pi wile jo li awen jo e sitelen nanpa wan. jan pi wile jo li pana e sitelen nanpa tu tawa jan pali, li pana e mani Mewika pi nanpa ale tawa jan pali.

nanpa luka la, jan kama jo li jo e sitelen nanpa wan. jan pali li jo e sitelen nanpa tu li jo e mani. ale li pona.

namako:

jan pi wile jo li pana e lipu toki kepeken nimi nanpa mute mute mute (mute anu weka) kepeken toki pona la, jan pali li sitelen e sitelen namako kepeken toki ni.

jan pi wile jo: __________________
jan Mato

jan pali: __________________
jan Josan

lipu lawa pi esun kama

Project: t47
Year:
Dimensions:

4 replies to “lipu lawa pi esun kama

  1. toki! mi lukin e lipu lawa sina li musi.

    I translated the contract this way. (I found a couple of problems: you used “la” twice in a single sentence, which is questionable although easy to understand, and you misspelled “nanpa” several times in different ways.)

    Also, I understood “toki sama toki pi lipu lawa” as ‘the same language [toki pona] as the contract’, rather than ‘the same text as the contract’. So before I looked at your English explanation in detail, I thought that the contract was for an unspecified document in toki pona rather than for a picture of the contract itself.

    Governing page of future sale

    jan Mato is the person that wants to have. jan Josan is the maker. The person that wants to have and the maker want a sale.

    First, the person that wants to have and the maker wrote a governing page of the future sale.

    Second, if the governing page of the future sale is good for those two, the maker will make a document. This document will use the same language as the language of the governing page of the future sale. The maker will make two documents. Both documents will be the same.

    Third, the maker will give both documents to the person that wants to have.

    Fourth, the person that wants to have will put his linear name on document number one and document number two. The person that wants to have will continue to have document number one. The person that wants to have will give document number two to the maker and will give American money of the universal number [one hundred] to the maker.

    Fifth, the getting person will have document number one. The maker will have document number two and money. Everything will be good.

    Extra:

    When the person that wants to have gives a linguistic document using many many many (more or less) words in toki pona, the maker will create an extra document using this text.

    Person that wants to have: __________________
    jan Mato

    Maker: __________________
    jan Josan

  2. Very nice translation! I’m not sure I’d change anything from the way you put it — and thanks for catching all the “nanpa”s — they were corrected at some point, but I must have copied and pasted from the earlier version.

  3. pona a. taso mi wile sona e ni: “sitelen namako” lon lipu lawa sina li seme? jan Mato li ken pali e lipu toki seme?

Leave a Reply

Your email address will not be published. Required fields are marked *

Add HTML attributes--more info here.

©2015 jonathan gabel . com