2. Software inc

Style The game uses a very informal tone sprinkled with bad jokes. Unless frowned upon, I would prefer sticking to the informal tone when possible.

Key separation Keys can be separated by a '|'-character.

Plural keys If the key starts with Plural, e.g. 'Plural|Key|Keys', the translation should always be formatted as '{0} [Key|Keys] ', with the first letter of the words in upper case, if applicable. Such that the game can output '1 key' or '2 keys'. If the word doesn’t pluralize in your language, you should write the word twice, e.g. '{0} [Key|Key] '.

Grouped keys If the key ends with a number, e.g. 'Key|0', it belongs to a group, e.g. 'Table|0' can be the table's name and 'Table|1' might be its description.

Replacements Translations can contain replacements, which are in the format: '{number}'. These replacements can be anything from employee names, company names, amounts of money, etc. Replacements can also contain functions, e.g. '{number:function name:parameters}' or just '{function name}' for tutorial messages.

Replacement functions Vowel, e.g. {0:Vowel:an,a}. This determines if the replacement word starts with a vowel sound, and if so, replaces it with an 'an', otherwise 'a'. If your language doesn’t differentiate, you should just remove this replacement. Plural, e.g. {0:Plural:have,has}. This determines whether the replacement input amount has 1 element or not, and if so, replaces it with 'has' otherwise 'have'. If your language doesn’t use this, you can safely remove this replacement. PluralKey, e.g. {0:PluralKey:Piece}. This uses the same logic as the Plural function, but it uses an already defined pluralization, e.g. with a 'Plural|Word|Words' key. FirstOrCount, e.g. {0:FirstOrCount:employees}. This will return the name of the first element, e.g. 'John Doe' or '15 employees' if there are multiple elements in the input. NotNull, e.g. {1:NotNull: by *}. This will replace * with the input, if the input is not empty, e.g. ' by John' if the input was John. The spacing is important, as you might add double spacing if you wrote something like 'You are being sued {1:NotNull:by *} for 10 dollars' would output: 'You are being sued--for 10 dollars', with a double space in between 'sued' and 'for'. Currency, e.g. {0:Currency}. Converts the input number to the player's chosen currency. KeyBind, e.g. {KeyBind:SweepSelect}. Replaces it with the key the player has mapped to the specified action. Constant, e.g. {Constant:NightShiftStart}. Replaces it with a named constant value from the game. Furthermore, the tutorial will often use H, e.g. {H:Key}, to highlight specific important words, that are repeated in the game.

Article generation The 'Article Generation' category consists of sentences that will be strung together to form an article in the game's newspaper. This may not work properly in your language, which would require a rewrite of the article generation files, but this is not supported yet.

Final review Keys starting with FinalReview will sometimes use square brackets, e.g. [ProductName], these should not be translated.