Cold Waters / Холодные воды – блог

Как вы знаете (надеюсь), у НАТО существовал (да и сейчас существует) собственный классификатор оружия и военной техники вероятного противника, названия в котором не совпадают с оригинальными – https://goo.gl/6P7tPI. Су-27 – это Flanker, Ка-27 – Helix и т.д. По моему мнению, переводить эти названия не следует, так что будьте внимательны, оно довольно часто встречается в тексте.
Названия моделей иностранных кораблей, оружия и техники тоже оставляем в оригинальном виде.

UPD В описании советских кораблей заголовок оставляем по кодификации НАТО, а в описании пишем уже отечественное название.
Например:
ShipClass=Sierra – перевод будет тоже ShipClass=Sierra
Description=Sierra-class Nuclear Attack Submarine – перевод будет Description=ПЛАТ проекта 945 «Барракуда» (Sierra).
Вики поможет найти названия.

Внимание! Слова в [квадратных] и <угловых> скобках переводить не надо! В строках, представляющих собой конструкцию вида XXXX=YYYY, переводится только YYYY (перед знаком «равно» название переменной, его переводить не надо). Поэтому в настройках сайта лучше включить галочку «Копировать текст оригинала при добавлении версии перевода». Пути к файлам и символы переноса строки (\n), если такие встречаются, тоже пропускаем.

Разработчики не занимаются локализацией, но готовы помочь любым желающим перевести игру. В гайде по моддингу (http://steamcommunity.com/sharedfiles/filedetails/?id=938593459) по поводу перевода написано следующее:
Language
All language content in Cold Waters is available in txt files.

Full Localisation of Cold Waters:
With your help, we can make Cold Waters available for other languages. Please contact us if you intend to make a full localisation so that we can add in-game support that language if needed as well as add any new fonts required and let you know if others are working on that same language.

There is one language folder in the parent folder which contains all language for the game interface and generic content. In addition, each campaign has its own language folder containing all language specific to each campaign.

Parent Language Folder:
aircraft – descriptions used in the Unit Reference.
weapon – descriptions used in the Unit Reference.
vessel – descriptions used in the Unit Reference.
sensor – descriptions used in the Unit Reference.

mission – single and training mission briefings as well as lists of single and training mission titles.
campaign – single file containing a list of names for campaigns.
training – texts for all tutorial missions

message – briefings, orders, action reports and other communications.

subsystem/subsystem_display_names – list of names in the same order as the subsystems are specified in «parent/subsystems»

dictionary/dictionary_interface – menu and HUD text.
dictionary/dictionary_message_log – crew message log.

help – contains all language content for the in-game help.

Campaign Language Folder:
Each campaign folder also contains their own language folder
campaign_map_data – all strategic map labels and positions.
description – description of the campaign displayed on the Campaign Selection page.
waypoints_region_names – defines the regions and each zone for the land based war.
waypoints_sea_names – defines names of ocean regions.

missions folder contains the orders for each mission in the campaign along with the messages received based on their outcome.

events folder contains:
Text for all events along with definitions of the image to display and the music to play when presenting that event.

events/content folder
Various texts for patrol outcomes, dynamic ground war text, ending and summary.
Single Missions
Single missions are made up of 3 files:

1) language/mission/missions_single
This is a list of all single mission titles. To add a new mission, add a new title for it to this list.
All mission names in this list correspond to two missionXXX files (one in the parent directory and one in the languages/mission folder) where XXX is a 3 digit number and represents the position of the mission in this list. For example the third mission in the list would have the number «003». The menu of Single Missions is built from this list.

2) language/mission/missionXXX
Contains the language portion of the mission including the briefing as well as the location.
Also contains a reference to the background image.
When creating a new mission, create a new file called «missionXXX» where XXX corresponds to the position of this mission in the «language/mission/missions_single» list.

3) missionXXX
In the parent folder, this file contains all the mission parameters as outlined below.
When creating a new mission, create a new file called «missionXXX» where XXX corresponds to the position of this mission in the «language/mission/missions_single» list.

For example if there are 4 missions already listed in «language/mission/missions_single»:
Add a new line to the bottom called «Mission Example».
This new line is #5 so the new mission number will be 005.
Create a file in «language/mission/» folder called «mission005» containing the language portion and background image reference.
Create a file in the parent folder called «mission005» containing the mission file data.
When creating these new files, you may want to copy/paste existing mission files to use as a template.