callsheet-localizations

Localization Files for Callsheet.

There are two sections:

Current Status

As of 77578a6:

Language % Complete App Store Authors
English (Modern) N/A ✔️ cliss
English (Traditional) N/A ✔️ cliss
English (Simplified) N/A ✔️ cliss
Dutch 100% 🎉 ✔️ Deddiekoel, icod
French (🇫🇷) 100% 🎉 EricEEEEE, samthegeek, DonSqueak, sayrer
French (🇨🇦) 100% 🎉 EricEEEEE, samthegeek, DonSqueak
German 100% 🎉 ✔️ DonSqueak, technocidal, fweber-de
Hebrew 100% 🎉 ✔️ orisraeli
Italian 100% 🎉 ✔️ cdf1982
Norwegian (Bokmål) 100% 🎉 ✔️ lognseth
Portuguese (🇵🇹) 100% 🎉 ✔️ apfernandes, sayrer
Russian 100% 🎉 ✔️ gkeep, ChatGPT-4.o
Spanish (🇲🇽) 100% 🎉 ccavazos, sayrer
Spanish (🇪🇸) 100% 🎉 ✔️ unaiherran
Spanish (🌎) 100% 🎉 ccavazos
Swedish 100% 🎉 ✔️ sebdanielsson
Ukrainian 100% 🎉 ✔️ zemlanin, buzbohdan
Polish 100% 🎉 spitfire, DonSqueak
Portuguese (🇧🇷) 73% insidegui
Japanese 58% kenroy, jaddkeita
Korean 46% EdogawaKun
Danish 5% hanse00

Basics

This repository contains a series of string catalog files. They contain a series of translatable snippets, and, eventually, their translations.

I am not concerned with word-for-word, direct translations. I'd vastly prefer translations that capture the spirit and tone of what's being said — and Callsheet in general — even if that means rephrasing what I've written, using locally-appropriate idioms, etc. Please have fun with this, and make choices that are appropriate for the audience that speaks your language.

The easiest way to open and modify these files — other than using Xcode — is to use the free macOS app Loca Studio.

Be careful with Loca Studio though! Save your work often!

Using Loca Studio

Generally speaking, you can look at the ID column, and provide a translation in the Target column. However, there are some special cases:

Plurality

For some items, like age, will occasionally have a singular and a plural form. Look at the ages shown here:

Screenshot 2024-05-10 at 8 27 46 PM

This isn't super obvious in Loca Studio:

Screenshot 2024-05-10 at 8 24 59 PM

Note that the Source column kind of hints at what's going on here, but the ID column shows plural.one for the singular version and plural.other for the plural version. Fill each in as appropriate, please.

Language Plural Rules

Some languages have more complicated pluralization rules than English speakers are used to. Words can be pluralized in ways that English speakers would recognize from ordinal numerals, like 20th, 21st, 22nd, 23rd. You can look these up in the rules table above.

As an example, these are the rules for Polish:

Pluralization English Polish Numbers
one 1 month 1 miesiąc 1
few 2 months 2 miesiące 2-4, 22-24, 32-34, 42-44, 52-54, 62, 102, 1002, …
many 5 months 5 miesięcy 0, 5-19, 100, 1000, 10000, 100000, 1000000, …
other 1.5 months 1,5 miesiąca 0.0-1.5, 10.0, 100.0, 1000.0, 10000.0, 100000.0, 1000000.0, …

Gender

English doesn't have very many gendered nouns, but it does have a few relevant to Callsheet. The words "actor" and "actress" are a good example.

However, other languages have a lot more words that can vary this way. Here is an example problem using the term "Director of Photography" in French:

Pronoun English French
She/her Director of Photography: Directrice de la Photographie:
He/him Director of Photography: Directeur de la Photographie:

Here, the problem is that the gender of a person is ambiguous in translation to French. The origin data is in English, so it can be best to avoid this ambiguity by rephrasing.

English French
Cinematography by: Cinématographie par:

Uses of grammatical gender are fine. The trailing parts of the first example say "de la Photographie". That's in the feminine for both, because "photographie" has that grammatical gender.

Other languages have even more of these.

In general, where it's appropriate and doesn't sound clunky, please use your language's equivalent of "they"/"them" or a genderless word. If not possible, not appropriate, or it just sounds super funky, please choose a sensible default.

Submission Flow

I've never done this before, so I'm working this out as we go, as well. But here's my vision for how I hope this will work:

  1. Fork this repository
  2. Perform whatever translations you want
    • Please don't feel obligated to do the whole document! Any little bit helps!
  3. Create a pull request to this repository
  4. I'll review, and, short of a major issue, accept the PR
  5. We both get to enjoy Callsheet being in one more language!
  6. If you happen to be an ATP listener, and if you do complete an entire language's localization, let me know, and maybe an ATP sticker will get mailed to you. 😏

Wait, there are forks other than cutlery and roads?

I'm guessing you're not experienced with Github. No problem! Reach out (see below) and we'll see if there's an alternative approach we can use. 😊

What if my language isn't here?

Reach out (see below) and I'll be happy to add it!

Questions?

Please say something on Mastodon or contact me.