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 for Bug 856 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The gettext addins reader/write are inconsistent in the way they they escape and unescape values, which could lead to text becoming corrupted. Unfortunately they're also very difficult to follow, and are very inefficient.
This does sound scary, but none of our users depend on this feature at the moment, so we can probably put off a fix for a bit.
They're not really pretty. We got a contribution to CatalogParser which makes things a bit better.
I've looked at that stuff, but don't really see a justification to work on that - only if we have a use case where it doesn't work.
I rarely use the addin, but when I do it works so far.
We should be able to replace it with this: https://github.com/rdio/vernacular/tree/master/Vernacular.Parsers