Скачать или смотреть Solving the SwiftUI Localization Issue: Not All Strings Are Localized

Discover how to ensure all strings in SwiftUI applications are properly localized with this helpful guide on using `LocalizedStringKey`.
---
This video is based on the question https://stackoverflow.com/q/64135199/ asked by the user 'William Hu' ( https://stackoverflow.com/u/291240/ ) and on the answer https://stackoverflow.com/a/64135409/ provided by the user 'Mohammad Rahchamani' ( https://stackoverflow.com/u/2810741/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: SwiftUI not all strings are localized

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Solving the SwiftUI Localization Issue: Not All Strings Are Localized

In today's globalized world, app localization is essential for reaching a wider audience. However, developers often encounter issues where not all strings are localized correctly when using SwiftUI. One such problem arises when you define a variable for a text label, leading to confusion about why localization fails. In this guide, we will address this common issue, shedding light on how to achieve proper localization in SwiftUI applications.

The Problem Explained

You may have encountered a scenario where your localized strings do not appear correctly in your SwiftUI user interface. For instance, you might define a string directly, and it works fine:

[[See Video to Reveal this Text or Code Snippet]]

This code snippet correctly displays the localized version of "Name" as "姓名". However, if you declare a variable like this:

[[See Video to Reveal this Text or Code Snippet]]

You might notice that the localization does not work as expected; instead of seeing "姓名," the label remains in English. So what’s going wrong?

Identifying the Cause

The issue stems from the fact that SwiftUI treats title in the second code snippet as a regular String, which does not automatically get localized. In contrast, when you use a string directly in the Text() view, it recognizes it as a localization key and looks up the appropriate translated string.

The Solution: Use LocalizedStringKey

To fix the localization problem, you need to explicitly indicate that your variable title is of the type LocalizedStringKey. This small change lets SwiftUI know that it should look for the localized version of the string based on the key you defined.

Here’s how to implement it:

Change the Variable Declaration:
Define your variable with the type LocalizedStringKey instead of String:

[[See Video to Reveal this Text or Code Snippet]]

Utilize it in the Text View:
You can continue to use it in your Text view without any changes:

[[See Video to Reveal this Text or Code Snippet]]

By making these modifications, your SwiftUI application will correctly display the localized string "姓名" when the title variable is used.

Conclusion

Localization in SwiftUI can seem tricky, especially when dealing with variable strings. The key takeaway is to always use LocalizedStringKey for variables that need to be localized. This ensures that your app can accurately present text in the desired language, enhancing the user experience significantly. Remember to check your variable types and keep localization in mind while coding!

By following these guidelines, your SwiftUI applications will effectively cater to a global audience, reflecting the importance of language and cultural relevance in app development.