Skip to content

Conversation

svobs
Copy link
Contributor

@svobs svobs commented Jun 16, 2023


Description:
See issue #4463.

Copy link
Contributor

@low-batt low-batt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The somewhat confusing IINA rules on localization require both the base and english localization files be updated. The rest are updated through Crowdin. So Localizable.strings under en.lproj also needs to be updated as a part of this PR.

I've been confused as to why we have to duplicate strings like this. Seems wrong. This PR got me to look into that. From Enabling Base Internationalization:

Xcode modifies your project folder according to the selections you make in this dialog. Xcode creates a Base.lproj folder in your project folder and adds to it the resource files you select. Xcode creates a language folder for the development language but only adds resources that need translation to the folder. For example, if you select English as the development language, Xcode inserts the resource file in the Base.lproj project folder but not the en.lproj folder because the resource is already in English.

Checking info.plist confirms the development language is set to English:

<key>CFBundleDevelopmentRegion</key>
<string>en</string>

From the Apple documentation it sounds like en.lproj is not needed.

A separate issue for another day…

@low-batt low-batt linked an issue Jun 16, 2023 that may be closed by this pull request
@svobs
Copy link
Contributor Author

svobs commented Jun 16, 2023

The somewhat confusing IINA rules on localization require both the base and english localization files be updated. The rest are updated through Crowdin. So Localizable.strings under en.lproj also needs to be updated as a part of this PR.

And here I was feeling clever that I finally got it right! I made another commit with the additions.

From the Apple documentation it sounds like en.lproj is not needed.

Interesting! I played with this and you are correct. This file appears to be [worse than] redundant.

A separate issue for another day…

But looks like a trivial fix. Can't resist this low-hanging fruit. I will file a bug report and PR.

@svobs svobs force-pushed the pr-music-mode-menu-item-text branch from 2ab94d3 to 24910bb Compare June 16, 2023 23:00
@svobs
Copy link
Contributor Author

svobs commented Jun 16, 2023

Sorry, inadvertently committed extra lines. Force-pushed the correct commit...

@svobs svobs force-pushed the pr-music-mode-menu-item-text branch from 24910bb to 8d1653d Compare August 4, 2023 01:09
@svobs svobs marked this pull request as ready for review August 4, 2023 01:09
Copy link
Contributor

@low-batt low-batt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good to me.

@uiryuu uiryuu merged commit a731628 into iina:develop Dec 26, 2023
@uiryuu
Copy link
Member

uiryuu commented Dec 26, 2023

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prepend "Enter" and "Exit" to "Music Mode" menu item
3 participants