Skip to main content

Currencies Without Borders: How much is a million spesmiloj?

As I write more and more Esperanto fiction, I find myself referencing the currency spesmiloj in an attempt to create an immersive Esperanto environment for the reader. Here's an example from my mikronovelo La Kristala Ananso:

“Kun aroga certeco, juna entreprenisto proponis unu milionon da spesmiloj. Neniu aĆ­dacis proponi pli.”

The narrative doesn’t change whether it’s a million USD, a million CAD, or a million EUR... so why not a million spesmiloj? I’m certain most of my readers aren’t millionaires, so the exact amount really doesn’t mean much beyond “a lot of money.”

But then I wondered: how much is a million spesmiloj, really?

According to Wikipedia, the spesmilo was "equivalent to one thousand spesoj, and worth 0.733 grams (0.0259 oz) of pure gold (0.8 grams of 22 karat gold).”

So 0.733 g × 1,000,000 = 733,000 g

At the current spot price for gold per gram of 107.75 USD / 92.87 EUR, we get:

733,000 g × 107.75 USD = 78,980,750 USD
733,000 g × 92.87 EUR = 68,073,710 EUR

Yes, that’s a substantial amount of money in any currency.

... Or is it?

Thinking a little bit more on this, I realized there's another problem here. The number exists mainly to create atmosphere, but readers from different economies will perceive numbers differently.

Let's consider the Korean won. 4,000 KRW is less than 3 USD. To an American reader, 4,000 looks substantial. To a Korean, 3 is laughably small. Meanwhile, 1,000,000 KRW is roughly 720 USD.

I guess if I were to formalize it, perhaps I would say, “Numbers need context”. And in the case of prices, we expect that context to be the currency. This is an important point because if I’m writing in Esperanto, I am writing for an international audience. And if I'm not relying on currency, I have to provide the context in a different way.

Thankfully, I did this intuitively: “Neniu aĆ­dacis proponi pli.” It's the world reacting to the number that provides context.

At least now I realized I shouldn’t rely on readers to understand what constitutes expensive or cheap; I need to support it with prose to signal its weight. Yes, it's show, don't tell.

Maybe this lesson will be of help to other writers who use fictional currencies, too. Let your characters and their world respond to provide valuable context.

Comments

Popular posts from this blog

Composing Music with PHP

I’m not an expert on probability theory, artificial intelligence, and machine learning. And even my Music 201 class from years ago has been long forgotten. But if you’ll indulge me for the next 10 minutes, I think you’ll find that even just a little knowledge can yield impressive results if creatively woven together. I’d like to share with you how to teach PHP to compose music. Here’s an example: You’re looking at a melody generated by PHP. It’s not the most memorable, but it’s not unpleasant either. And surprisingly, the code to generate such sequences is rather brief. So what’s going on? The script calculates a probability map of melodic intervals and applies a Markov process to generate a new sequence. In friendlier terms, musical data is analyzed by a script to learn which intervals make up pleasing melodies. It then creates a new composition by selecting pitches based on the possibilities it’s observed. . Standing on Shoulders Composition doesn’t happen in a vacuum. Bach wa...

Learning Prolog

I'm not quite sure exactly I was searching for, but somehow I serendipitously stumbled upon the site learnprolognow.org a few months ago. It's the home for an introductory Prolog programming course. Logic programming offers an interesting way to think about your problems; I've been doing so much procedural and object-oriented programming in the past decade that it really took effort to think at a higher level! I found the most interesting features to be definite clause grammars (DCG), and unification. Difference lists are very powerful and Prolog's DCG syntax makes it easy to work with them. Specifying a grammar such as: s(s(NP,VP)) --> np(NP,X,Y,subject), vp(VP,X,Y). np(np(DET,NBAR,PP),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y), pp(PP). np(np(DET,NBAR),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y). np(np(PRO),X,Y,Z) --> pro(PRO,X,Y,Z). vp(vp(V),X,Y) --> v(V,X,Y). vp(vp(V,NP),X,Y) --> v(V,X,Y), np(NP,_,_,object). nbar(nbar(JP),X,3) --> jp(JP,X). pp(pp(PREP,N...

What's Wrong with OOP

Proponents of Object Oriented Programming feel the paradigm yields code that is better organized, easier to understand and maintain, and reusable. They view procedural programming code as unwieldy spaghetti and embrace OO-centric design patterns as the "right way" to do things. They argue objects are easier to grasp because they model how we view the world. If the popularity of languages like Java and C# is any indication, they may be right. But after almost 20 years of OOP in the mainstream, there's still a large portion of programmers who resist it. If objects truly model the way people think of things in the real world, then why do people have a hard time understanding and working in OOP? I suspect the problem might be the focus on objects instead of actions. If I may quote from Steve Yegge's Execution in the Kingdom of Nouns : Verbs in Javaland are responsible for all the work, but as they are held in contempt by all, no Verb is ever permitted to wander about ...