Fix incorrect URL detection in SwiftUI Text#794
Open
vistar941 wants to merge 1 commit intoXcodesOrg:mainfrom
Open
Fix incorrect URL detection in SwiftUI Text#794vistar941 wants to merge 1 commit intoXcodesOrg:mainfrom
vistar941 wants to merge 1 commit intoXcodesOrg:mainfrom
Conversation
Updated links in Japanese and Korean translations for clarity.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This issue occurred only in the Japanese and Korean localized versions.
In those translations, the URL was written without whitespace before the following text, causing SwiftUI's automatic URL detection to incorrectly include trailing characters (such as the closing parenthesis and subsequent text) as part of the link.
As a result, the generated URL became invalid and led to a 404 error.
This PR fixes the issue by correcting the Japanese and Korean localized strings to ensure the URL is properly recognized and navigates to the intended page.
No changes were made to application logic or other localizations.