What is the use-case for this library compared to Xcode - Export for Localization and import?

I am trying to better understand the use-case for this library compared to the standard localisation workflow in Xcode.

In the readme you say:

LocalizedStringKit is a tool that lets you write English strings directly into your source code and generate the required .strings files later. No more manually managing string keys or remembering to add them to the strings file later. All you do is change:
label.text = NSLocalizedString("TERMS_SCREEN_MAIN_HEADER", "Comment here...")
...

If you use NSLocalizedString, you can write English strings directly into the source code as the key parameter (in the same way as with the replacement function in this library). Then to generate the strings files for the other languages, in Xcode,

1. Select the project in the sidebar
2. Select, menu item Editor -> Export for Localization
3. Add the target translations to the resulting XLIFF
4. Then import again with Editor -> Import Localisation
   Result: Xcode will create the strings files and add them to the project

Furthermore, If you alternatively use keys such as NSLocalizedString("my.string.a", ..), you can export the development language, in the same way as described above, and import to generate the strings file for the development language.

Is this library for when you don't use Xcode, or don't want to use the xliff-based workflow (for some reason)?

结合 issue 中描述的 Xcode Editor → Export for Localization 和 Import Localization 工作流，审查 README 中的描述。明确该库的预期使用场景，以及它是否面向不使用 Xcode 或 XLIFF 工作流的项目；当 README 清楚地比较这些方法时即完成。