Bug 856 - gettext reader/write is inconsistent, incomprehensible and inefficient
Summary: gettext reader/write is inconsistent, incomprehensible and inefficient
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Windows
: Lowest normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2011-09-16 10:58 UTC by Mikayla Hutchinson [MSFT]
Modified: 2016-11-05 05:24 UTC (History)
3 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 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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Mikayla Hutchinson [MSFT] 2011-09-16 10:58:33 UTC
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.
Comment 1 Jeffrey Stedfast 2011-11-15 12:26:45 UTC
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.
Comment 2 Mike Krüger 2012-04-15 04:28:27 UTC
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.
Comment 3 Mikayla Hutchinson [MSFT] 2012-04-30 11:58:28 UTC
We should be able to replace it with this: https://github.com/rdio/vernacular/tree/master/Vernacular.Parsers