Mishandling of the degree symbol in legal descriptions
Posted: Thu Aug 11, 2016 7:48 am
Context: Select 4.0 version 4.0.30302.1069
We have observed a problem when generating documents that contain the field Order.Properties.CommitmentLegal.Description (i.e. Legal Description page, first rich text box). If we embed the degree symbol in the field, which is somewhat common when entering legal description surveys, it appears properly. When we query the database (SelectDb.pfm.Property's CommitmentLegal#Description field) we find RTF-encoded text that, when copied and pasted to a file, can be opened in WordPad where the degree symbol is properly rendered. However, when we generate one of our documents that includes this field on it, all of the degree symbols are replaced with question marks. Given our analysis it seems like the problem must lie in the document generation process or with the document itself.
Unfortunately it's very hard to analyze the internals of the resulting PDF. The best we've been able to do so far is to compare the results of opening the original survey text in Notepad and comparing it to the text that is generated when we export the PDF to text. I tried to attach some images showing the issue but apparently the forum won't accept upload for some reason.
Can anyone offer an insight into what's going on and how we can correct the issue? TIA
We have observed a problem when generating documents that contain the field Order.Properties.CommitmentLegal.Description (i.e. Legal Description page, first rich text box). If we embed the degree symbol in the field, which is somewhat common when entering legal description surveys, it appears properly. When we query the database (SelectDb.pfm.Property's CommitmentLegal#Description field) we find RTF-encoded text that, when copied and pasted to a file, can be opened in WordPad where the degree symbol is properly rendered. However, when we generate one of our documents that includes this field on it, all of the degree symbols are replaced with question marks. Given our analysis it seems like the problem must lie in the document generation process or with the document itself.
Unfortunately it's very hard to analyze the internals of the resulting PDF. The best we've been able to do so far is to compare the results of opening the original survey text in Notepad and comparing it to the text that is generated when we export the PDF to text. I tried to attach some images showing the issue but apparently the forum won't accept upload for some reason.
Can anyone offer an insight into what's going on and how we can correct the issue? TIA