Bug 7763 - Strings Localization not working properly when multiple projects contain localized files with the same name
Summary: Strings Localization not working properly when multiple projects contain loca...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-10-09 23:10 UTC by Yiannis
Modified: 2013-12-05 18:35 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Yiannis 2012-10-09 23:10:02 UTC
If a solution contains multiple projects and each project contains a Localizable.strings for the same language, then at compile time only one Localizable.strings file is copied to the device and is taken into account.

Also another user mention it in the forum here: http://monotouch.2284126.n4.nabble.com/Localizable-strings-from-seperate-project-doesn-t-always-get-compiled-and-what-the-max-keylenght-in-e-td4657329.html
Comment 1 Mikayla Hutchinson [MSFT] 2012-10-10 14:24:52 UTC
The problem is, the files all have the same bundle-relative name, so they're all copying into the same place. In general, we should warn about such conflicts. Libraries should really use their own resource bundles, instead of placing files directly into the root of the app bundle.

I suppose in the case of strings files it would be possible to merge them, but 'm not sure how difficult that would be.
Comment 2 Yiannis 2012-10-11 01:18:17 UTC
A simple merge af all language files, without any check for duplicates will do the job.

About a project using its own resource bundle, is there any guide about a recommended way to do it?
Comment 3 Yiannis 2012-10-11 04:00:16 UTC
Please ignore my suggestion for the IDE to merge the files. I can merge the files myself.

You are correct that the libraries should use their own resource bundles, because of the way iOS handles localization.
If there is some guide on how to embed language resources for monotouch libraries, please let me know.
Comment 4 Jeffrey Stedfast 2013-06-07 13:23:54 UTC
Any suggestions on how this should be done?

Or should this be closed based on the latest comment?
Comment 5 PJ 2013-11-19 17:05:32 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 6 PJ 2013-12-05 18:35:59 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.