Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 15329 [details]
Screenshot showing the MORE and CANCEL items
The "MORE" and "CANCEL" context menu items in a ListView's context menu are not localized.
They always appear in English and don't honour the underlying OS's language.
This was tested under iOS.
Please either take the underlying OS's text strings or expose these strings as properties, so they can be localized by the app.
Screenshot is attached.
Thank you for taking the time to submit the bug. We tried to reproduce the issue you reported but were unable given the description. If you could please attach a reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue we would very much appreciate it.
Xamarin Forms Team
Created attachment 15386 [details]
Screenshot showing the bug in the DemoApp
Created attachment 15387 [details]
Demo project to reproduce the bug
Please change your simulator's locale to a non-English language to reproduce the bug.
Confirmed on iOS set to German; 'More' and 'Cancel' are not localized.
Should be fixed in 2.2.0-pre1
I have checked this issue with xamarin.forms 2.2.0-pre1 and I am still facing same issue.
Hence reopening this issue.
Please follow the screencast and let me know if I have missed anything.
@Parmendra: Thanks for testing.
You followed the steps to reproduce the issue exactly, so the bug seems to be still there.
Instead of a "Should be fixed" note, a more detailed description of HOW it was fixed would be helpful. Meaning: The localization is done automatically, OR the developer has now additional properties which he/she must localize manually.
(In reply to Joe Maier from comment #7)
> @Parmendra: Thanks for testing.
> You followed the steps to reproduce the issue exactly, so the bug seems to
> be still there.
> Instead of a "Should be fixed" note, a more detailed description of HOW it
> was fixed would be helpful. Meaning: The localization is done automatically,
> OR the developer has now additional properties which he/she must localize
> Best regards,
The localization should be handled automatically; you shouldn't have to do anything in order to see the localized button labels. Unfortunately, while the problem is fixed in code, we now have a deployment issue with the localized string assemblies and NuGet. We're working to address that now.
@hartez Has there been any change on the assembly issue since April?
Yes, this was fixed back in April: https://github.com/xamarin/Xamarin.Forms/pull/74
Bad bookkeeping on my part.
I have checked this issue with Xmarin.Forms 220.127.116.11 and its working fine. This issue has been fixed.
Hence marked this issue as Verified Fixed.