I've been using a handy tool specifically designed for this purpose: XCStrings File Processor: (https://www.swifthub.org/xcstringstool/). It's a browser-based tool that lets you easily manage languages in your .xcstrings files. The workflow is straightforward: 1.Upload your .xcstrings file (drag & drop or click to select) 2. You'll see a list of all available languages in your file 3. Simply uncheck the languages you want to remove 4. Click "Process File" and download the updated version What I particularly like about it is that everything is processed locally in your browser - no file uploads to any server, which is great for sensitive project files. It's also quite useful when you need to create region-specific builds or want to reduce your app size by removing unused localizations. I've found it much more efficient than manually editing the .xcstrings file, especially when dealing with large localization files. The tool is free to use and doesn't require any registration. Hope this helps with your localization management!

I've been using a handy tool specifically designed for this purpose: XCStrings File Processor: (https://www.swifthub.org/xcstringstool/). It's a browser-based tool that lets you easily manage languages in your .xcstrings files. The workflow is straightforward: 1.Upload your .xcstrings file (drag & drop or click to select) 2. You'll see a list of all available languages in your file 3. Simply uncheck the languages you want to remove 4. Click "Process File" and download the updated version What I particularly like about it is that everything is processed locally in your browser - no file uploads to any server, which is great for sensitive project files. It's also quite useful when you need to create region-specific builds or want to reduce your app size by removing unused localizations. I've found it much more efficient than manually editing the .xcstrings file, especially when dealing with large localization files. The tool is free to use and doesn't require any registration. Hope this helps with your localization management!

same issue