GetStatisticsInfo is counting non-breaking spaces as words

[Bob]

Hello, we recently implemented a word count feature in the RadRichTextBox by using the GetStatisticsInfo method of the RadDocument class.  We noticed word counts are not accurate and determined that the document contained some non-breaking spaces (0xA0) instead of normal spaces (0x20), and when these non-breaking spaces were positioned in span text separately like this: <t:Paragraph> <t:Span Text=" " /> </t:Paragraph>, then the word count included this as a word.

Since we can't control the document content that is imported, we could work around this issue by replacing the non-breaking spaces with normal spaces before getting a word count, but I am not sure of the best approach for doing so.  Please let me know a solution for the replacement, or if this is something you will be fixing at some point.

 

Thanks,

Bob

[Bob]

We have also determined that if a non-breaking space is placed between two words, then the count is one word instead of two.  To work around this issue for now, I have done a simple replace on the imported text string.

private string FixupNonBreakingSpaces(string textToFix)
{
    return textToFix.Replace(Convert.ToChar(160), ' ');
}

[Martin]

Hello Bob,

Thank you for the information provided and for the suggested workaround.

Both the scenarios are related to a currently not supported functionality that we have logged in our backlog: RichTextBox: Support for Non-Breaking Spaces. You can cast your vote for the implementation as well as subscribe to the task by clicking the Follow button so you can receive updates when its status changes.

I hope you find this information helpful.

Regards,
Martin
Progress Telerik

[Bob]

Thank you Martin, I have upvoted the issue.

I also changed the workaround slightly to handle directly imported or pasted content from Html:

private string FixupNonBreakingSpaces(string textToFix)
{
    return textToFix.Replace(Convert.ToChar(160), ' ').Replace(" ", " ");
}

[Martin]

Hello Bob,

Thank you again! Do not hesitate to contact us if any additional questions arise.

Regards,
Martin
Progress Telerik