TextPacker

[adastmin]

Overview​

"Base pak" is no longer needed to make a PAK out of XLSX file. Converting a file into a different format is now performed in a single step. TextPacker reads paths directly from the first column of XLSX file and creates all folders and files from scratch. Content of the text files is read directly from the second column.


Similarly, PAK file can be converted into XLSX without any unnecessary steps, all you need is to enter two file names.


Starting from branch, the whole concept of "ELK project" becomes obsolete - instead, you are supposed to work with one and the same XLSX file within a branch, converting it into a PAK whenever you wish to test the localization or send the PAK to us for building a version.


Legacy columns ("State", "Owner", "Description", "Source" "Glossary Item") were removed, as they are no longer needed. You can use the third and any subsequent columns for the source text, notes, comments etc., they are not processed during the conversion.


Also, names of column headers are no longer relevant. All that matters to TextPacker are columns A and B of the spreadsheet, excluding line 1.


Format of generated PAK file has been fixed - you no longer need to unpack it to see the localization in game, you can simply copy your PAK file into the data\Packs folder and delete pack.loc file from your BaseLoc.pak.


Last but not least, TextPacker works much faster than ELK

Precautions​

It is recommended to use a single-sheet XLSX file (in case of different sheets, if you copy-pasted data from one sheet to another, renamed and/or moved the sheets, TextPacker may attempt to use the wrong sheet for conversion). TextPacker always converts a PAK into a single-sheet XLSX.


Very large cells containing more than 20,000 characters are not supported (actually they are not supported by Excel, so we cannot reliably process them). If your DeniedWords or ChatFilterForbidden lists are more than 20k characters long, please add them into the PAK manually for the time being. We are currently working on addressing this issue (DeniedWords are going to be removed from the localization, they will be uploaded directly on server.).

Usage​

Both GUI and console versions operate using the same logic.

Syntax (ConsoleTextPacker.exe)​

- Create excel file from pak file:

[CODE]ConsoleTextPacker.exe pak2xls <PakFileName> <ExcelFileName>

[/CODE]

- Create pak file from excel file:

ConsoleTextPacker.exe xls2pak <ExcelFileName> <PakFileName>

- Create excel file from source folder. Source folder is where the PAK file is unpacked (although there is no need to unpack it at normal circumstances). Root folder is also used only in conjunction with unpacked PAKs. For most cases, Root folder and Source folder should be the same.

ConsoleTextPacker.exe src2xls <RootFolder> <SourceFolder> <ExcelFileName>

- Create pak file from source folder:

ConsoleTextPacker.exe src2pak <RootFolder> <SourceFolder> <PakFileName>

Examples​

ConsoleTextPacker.exe pak2xls x.0.00.pak x.0.00.xlsx


ConsoleTextPacker.exe pak2xls E:\TextPacker\x.0.00.pak E:\TextPacker\x.0.00.xlsx
ConsoleTextPacker.exe xls2pak x.0.00.xlsx x.0.00.pak


ConsoleTextPacker.exe xls2pak E:\TextPacker\x.0.00.xlsx E:\TextPacker\x.0.00.pak

Windows Explorer Integration​

You can easily integrate TextPacker into Windows Explorer context menu:

registry.reg include archive​

It is assumed that your TextPacker program is located in "C:\TextPacker" folder. If you wish to use another folder, please amend the Registry.reg file accordingly. You can edit it using Notepad or any other text editor.


Double-click Registry.reg file and select "Yes" to add the entries into Windows registry.


Should you decide to remove these options from the context menu, run Regedit.exe and delete these two entries:
HKEY_CLASSES_ROOT\*\shell\TextPacker: Convert to PAK
HKEY_CLASSES_ROOT\*\shell\TextPacker: Convert to XLSX




Password:adastmin_love_ragezone