Bug 26027 - pango MeasureStringRanges wrong for nonASCII strings
Summary: pango MeasureStringRanges wrong for nonASCII strings
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: libgdiplus ()
Version: 3.4.0
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-01-14 13:15 UTC by Stephen McConnel
Modified: 2015-01-14 13:59 UTC (History)
1 user (show)

Tags:
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 26027 on GitHub or Developer Community 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: GitHub Markdown or Developer Community HTML
  • 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:
Status:
NEW

Description Stephen McConnel 2015-01-14 13:15:33 UTC
The implementation of pango_MeasureCharacterRanges() passes incorrect index values to pango_layout_index_to_pos().  This results in string width measurements being incorrect (usually too narrow).  I have a fix which I'll post shortly as a pull request.

The index values currently used are into the UCS-2 string, but the documentation clearly indicates that they should be indexes into the UTF-8 string.
Comment 1 Stephen McConnel 2015-01-14 13:59:11 UTC
A proposed fix has been submitted as https://github.com/mono/libgdiplus/pull/29