Difference between revisions of "Oldunreal Localization Project"

From Oldunreal-Wiki
Jump to navigation Jump to search
m
Line 26: Line 26:
* [[File:CatalanFlag.png|20px|border|]] [[Catalan .ctt]], ''work in progress''.
* [[File:CatalanFlag.png|20px|border|]] [[Catalan .ctt]], ''work in progress''.
** [[Catalan .ctt/UT]] - Unreal Tournament Catalan localization. ''Work in progress''.
** [[Catalan .ctt/UT]] - Unreal Tournament Catalan localization. ''Work in progress''.
*  [[Dutch .nlt]], ''work in progress''.
** [[Dutch .nlt/UT]] - Unreal Tournament Dutch localization. ''Work in progress''.


==Status and Procedure==
==Status and Procedure==
Line 33: Line 35:
* '''Polish''':  Mostly done, some work is still needed, but it's being covered.
* '''Polish''':  Mostly done, some work is still needed, but it's being covered.
* '''German, Italian and Portuguese''': These languages need a lot of work. Translation might be shaky, and some files may be obsolete resulting in broken menus or defaulting to the .int files. Some of the most urgent changes were made using automatic translation tools and need to be reviewed by a native speaker.
* '''German, Italian and Portuguese''': These languages need a lot of work. Translation might be shaky, and some files may be obsolete resulting in broken menus or defaulting to the .int files. Some of the most urgent changes were made using automatic translation tools and need to be reviewed by a native speaker.
* '''Czech, Hungarian''' and '''Swedish''' are new additions. They are undergoing translation, which will then have to be checked.
* '''Czech, Hungarian, Swedish, Catalan''' and '''Dutch''' are new additions. They are undergoing translation, which will then have to be checked.


=== Unreal Tournament ===
=== Unreal Tournament ===
Line 39: Line 41:
* '''Spanish''': Language complete. This does not necessarily mean that there is absolutely nothing to improve for these, but they work flawlessely and all the lines have been translated. The remaining changes that may be done are purely cosmetic : rephrasing, correcting typos and spelling errors...
* '''Spanish''': Language complete. This does not necessarily mean that there is absolutely nothing to improve for these, but they work flawlessely and all the lines have been translated. The remaining changes that may be done are purely cosmetic : rephrasing, correcting typos and spelling errors...
* '''French''':  Mostly done, some work is still needed, but it's being covered.
* '''French''':  Mostly done, some work is still needed, but it's being covered.
* '''Russian, Polish, German, Italian, Portuguese, Czech, Hungarian and Swedish''': These languages need a lot of work. Translation might be shaky, and some files may be obsolete resulting in broken menus or defaulting to the .int files. Some of the most urgent changes were made using automatic translation tools and need to be reviewed by a native speaker.
* '''German, Italian, Russian and Hungarian''': These have retail and/or fan translations translations, but their errors need to be checked.
* '''Polish, Portuguese, Czech, Swedish, Catalan and Dutch''': These languages are new additions.


== Useful tools ==
== Useful tools ==

Revision as of 23:25, 23 June 2020

Unreal is very easy to translate as most strings in the maps and all of the menus are stored in plain text files with file extensions relative to the language of the game. New translation can easily be added and modified with any tool, even the simplest notepad - they are in fact regular .txt files. However, a lot of time is needed to fully complete a translation of the game. OldUnreal can use all the help you can give.

Languages

Status and Procedure

Unreal

  • English: The English .int files need to be compared to the other language files, as they are always up to date and complete. To complete a localisation, missing entries have to be added, some unecessary ones have to be deleted, wrong or incorrect translations have to be replaced and the entire thing has to be thoroughly tested. When Unreal is set to a language that is not English, it uses the translation files of the specific language. When a line - or even an entire file - is missing from the localization, Unreal defaults to the English line in the .int file of the same name, or the entire .int file if the entire localized file is blank or missing.
  • French, Russian and Spanish: All of these languages are complete. This does not necessarily mean that there is absolutely nothing to improve for these, but they work flawlessely and all the lines have been translated. The remaining changes that may be done are purely cosmetic : rephrasing, correcting typos and spelling errors...
  • Polish: Mostly done, some work is still needed, but it's being covered.
  • German, Italian and Portuguese: These languages need a lot of work. Translation might be shaky, and some files may be obsolete resulting in broken menus or defaulting to the .int files. Some of the most urgent changes were made using automatic translation tools and need to be reviewed by a native speaker.
  • Czech, Hungarian, Swedish, Catalan and Dutch are new additions. They are undergoing translation, which will then have to be checked.

Unreal Tournament

  • English: The English .int files need to be compared to the other language files, as they are always up to date and complete. To complete a localisation, missing entries have to be added, some unecessary ones have to be deleted, wrong or incorrect translations have to be replaced and the entire thing has to be thoroughly tested. When Unreal is set to a language that is not English, it uses the translation files of the specific language. When a line - or even an entire file - is missing from the localization, Unreal defaults to the English line in the .int file of the same name, or the entire .int file if the entire localized file is blank or missing. ATM the only missing entries are those belonging to the Game of the Year edition mods Rocket Arena and Chaos: UT, which will be added soon.
  • Spanish: Language complete. This does not necessarily mean that there is absolutely nothing to improve for these, but they work flawlessely and all the lines have been translated. The remaining changes that may be done are purely cosmetic : rephrasing, correcting typos and spelling errors...
  • French: Mostly done, some work is still needed, but it's being covered.
  • German, Italian, Russian and Hungarian: These have retail and/or fan translations translations, but their errors need to be checked.
  • Polish, Portuguese, Czech, Swedish, Catalan and Dutch: These languages are new additions.

Useful tools

  • OpenOffice and Libreoffice have an extension for Wiki's WikiPublisher, which can export any text into wiki formatted text files. Give it a try if you plan on adding your translation or modifying an existing one.

Return to Na Pali notes

Cutscenes with subtitles

  • Crashsite2
  • End
  • Inter1...14
  • InterCrashsite
  • InterIntro
  • Intro1

Important Changes

Gender support has been added to Polish and French. If you are localizing Unreal for a language where articles and verbs are neutral (such as English, where "a" has no gender and verbs do not show the gender of the subject/object), this is irrelevant to you. If the verb changes depending on the gender of the subject, as in Polish or certain situations in French, consult UnrealI.plt and UnrealI.frt, and look at the lines which have a "Fem" variation, as in UnrealI.plt: 

[fell] 
AltName="spadł" 
FemAltName="spadła"

Since 227j every RTNP cutscene map contains a new actor called TransitionGenderEvent. This event is using different Hud types to draw the subtitles (UnrealHud, TransitionNullHud, CSHud). You can set up your subtitle text for both, female and male or only female or only male in your localization file. The settings are depending on the genders written and spoken output in some languages. The index value is the same if you are using FemaleText and MaleText. Here is a example: 

[TransitionGenderEvent]
CommonText[0]="CommonText" is drawn used by female or male with sound output without written and spoken verb differences.
MaleText[1]=Use "MaleText" if your verb only typically for male
FemaleText[1]="FemaleTExt" this is for the ladies ;)
CommonText[2]=...
CommonText[3]=..
CommonText[4]=.

Unreal Tournament notes

Audio packages with spoken lines

There are some languages which include packages with spoken lines such as english (for obvious reasons), spanish, french, deutsch and italian. Packages are located in the Sounds/ folder with the extension .<lang>_uax (For example, the spanish language package for the Male1Voice.uax would be Male1Voice.est_uax). Only the english language is excepted from this, just having files with .uax extension (for ezample, the aforementioned Male1Voice is Male1Voice.uax). For the rest of the languages, new lines must be created in order to supplant them. These are the packages with their respective sound files. As for the text to be replicated, it's located in botpack.int or its equivalent in every language:

  • Announcer.<ext>_uax - Announcer lines.
  • BossVoice.<ext>_uax - Boss/Xan lines.
  • Female1Voice.<ext>_uax - Female Commando lines.
  • Female2Voice.<ext>_uax - Female Soldier lines.
  • Male1Voice.<ext>_uax - Male Commando lines.
  • Male2Voice.<ext>_uax - Male Soldier lines.
  • OpeningWave.<ext>_uax - Opening Narration.
  • TutVoiceAS.<ext>_uax - Assault Tutorial lines.
  • TutVoiceCTF.<ext>_uax - CTF Tutorial lines.
  • TutVoiceDM.<ext>_uax - DM Tutorial lines.
  • TutVoiceDOM.<ext>_uax - DOM Tutorial lines.

Linux

Linux users need to encode the files in unicode (UTF-16) format to make it work.

It is also possible to create or modify localizations for the original Unreal in its 226 version. Because great changes have been done to some files and some have been completely restructured, 227 and 226 files should not be mixed up. A dedicated page for legacy localizations has been set up. Feel free to create a new localization or modify the original one there too.

Adding new languages

If you would add your own native language to Unreal, please use a two-letter code of your language from the ISO 639-1 list + a "t" at the end of the file extension as an acronym for the translation file.

For example:

Native Language ISO-639-1 language code File extension
Bulgarian bg .bgt
Greek el .elt
Korean ko .kot

Links for more information

Retrieved from "https://www.oldunreal.com/wiki/index.php?title=Oldunreal_Localization_Project&oldid=11674"