Localization Merger

What It Does

This tool helps users, translators, and patch authors create their own S. T. A. L. K. E. R. 2 Localization_P compatibility patches.

Main features:

• []Merges two Localization_P containers into one output set.[/]

  []Accepts mod folders or direct Localization_P.utoc files.[/]

  []Automatically merges keys that only exist in one input.[/]

  []Shows a conflict review when both inputs contain different text for the same key.[/]

  []Includes language filtering for focused review work.[/]

  []Includes a full text browser for inspecting all compared localization entries.[/]

  []Exports packed LocalizationDB content into readable split JSON files.[/]

  []Imports edited split JSON files back into a rebuilt Localization_P output.[/]

  []Writes CSV/JSON logs for patch authors and translators.[/]

  Conflict Review

  Conflicts are shown in a three-row compare view:

  • []Row 1: Input 1 text[/]

    []Row 2: Input 2 text[/]

    []Row 3: final result[/]

    • []F1: use Input 1 and jump to the next visible conflict[/]

      []F2: use Input 2 and jump to the next visible conflict[/]

      []F3: use typed Row 3 result and jump to the next visible conflict[/]

      Pending rows are shown in red/reddish colors. Decided rows are shown in green.

      Text Browser

      The Browse texts view can show every localization entry, not only conflicts.

      It supports:

      • []language filter[/]

        []status filter: identical, Input 1 only, Input 2 only, conflict[/]

        []key/text search[/]

        []result preview[/]

        This is useful for translators and patch authors who want to inspect what changed before creating a compatibility patch.

        JSON Export / Import

        The Export JSON button reads a packed Localization_P input and exports decoded LocalizationDB content as split JSON files.

        The export contains:

        • []manifest.json[/]

          []per-block/per-language JSON files[/]

          []additional part_###/part files when a block is very large[/]

          The exported entries use a direct key/value format:

          "sid_example_key": "Translated text"

          The Import JSON button can rebuild a packed Localization_P from edited split JSON files.

          Existing base keys are overwritten when the edited JSON contains the same block/key. Missing JSON keys are left unchanged. Unknown JSON keys are ignored and counted in json_import_report.json.

          Merge Output

          Merge output contains: