C++跨平台可翻译插件：XML字符串资源嵌入存储方案咨询

Great question—this is a common pain point for cross-platform plugin developers who want clean, self-contained localization without shipping extra assets. Let’s walk through practical, robust solutions that fit your requirements:

1. Compile-Time Embedded String Headers #

The simplest approach is to store localized strings directly in C++ header files, compiled right into your plugin binary. Here’s how to implement it:

• Create per-locale header files (e.g., locale_en.hpp, locale_fr.hpp) with const string mappings. For example:

  // locale_en.hpp
  #pragma once
  #include <unordered_map>
  #include <string>
  
  inline const std::unordered_map<std::string, std::string> EN_STRINGS = {
      {"welcome_msg", "Welcome to the plugin!"},
      {"error_save", "Failed to save your settings"}
  };
  

• Your Dictionary class can load the appropriate header based on the current locale—either via preprocessor directives at build time, or runtime checks if you need dynamic locale switching.
• Pros: No external files, fully cross-platform (works with GCC, Clang, MSVC), fast access since strings live in memory.
• Cons: Requires a rebuild to add/update strings; dynamic locale switching needs extra logic to load the right map at runtime.

2. Binary Resource Blobs (Embedded in Plugin) #

If you prefer keeping your localization data in a structured format like XML/JSON during development but don’t want to ship it, pack the data into a binary blob and embed it into your plugin:

• Use a tool to convert your XML/JSON to a compact binary format (e.g., Google Protobuf, or a custom lightweight format).
• Embed the binary blob into your plugin binary:
  • On Linux/macOS: Use objcopy to turn the binary file into an object file, then link it into your plugin. Example command:

    objcopy --input binary --output elf64-x86-64 --binary-architecture i386 strings_en.bin strings_en.o
    

  • On Windows: Add the binary file to your .rc resource script, which the MSVC linker will embed into the plugin.
• Your Dictionary class can read the embedded blob at runtime, parse it into an in-memory map, and serve strings.
• Pros: Keeps development workflow clean (use XML/JSON for editing), no external files to ship, supports dynamic locale switching if you embed multiple blobs.
• Cons: Requires writing/using a binary parser and embedding scripts, slightly more setup than header files.

3. Code-Generated C++ Structures #

Automate the conversion of your development-time XML files into C++ code, so you never have to ship the raw XML:

• Write a small script (Python, Perl, or even a C++ tool) that parses your XML localization files and generates C++ source code. For example, a script could turn your XML entries into:

  // Generated localized_strings.cpp
  #include "localized_strings.hpp"
  
  namespace Locale {
      const std::unordered_map<std::string, std::unordered_map<std::string, std::string>> ALL_STRINGS = {
          {"en", {{"welcome_msg", "Welcome!"}, {"error_save", "Save failed"}}},
          {"fr", {{"welcome_msg", "Bienvenue!"}, {"error_save", "Échec de sauvegarde"}}}
      };
  }
  

• Add this script to your build pipeline (e.g., CMake pre-build step) so it regenerates the code whenever your XML files change.
• Your Dictionary class can simply look up strings from the generated ALL_STRINGS map at runtime.
• Pros: Combines the ease of XML editing with the portability of compiled code; no external files, cross-platform, supports dynamic locale switching out of the box.
• Cons: Requires maintaining the generation script, but this is a one-time setup.

Final Tips for Your Dictionary Class #

• Make sure your Dictionary interface is locale-agnostic: expose a method like std::string get(const std::string& key, const std::string& locale) that abstracts the underlying storage.
• For performance, cache parsed string maps once at plugin initialization instead of reloading them every time.
• Test across target platforms to ensure embedding/loading works as expected (e.g., resource handling on Windows vs. Linux).

内容的提问来源于stack exchange，提问作者Dave Stott