I have just run into a most curious problem. It might be a bug, but if it’s a bug then it’s a bug in both RM7 and RM9. Namely, I was just adding a 1950 Census fact for someone in my database who was enumerated in 1950 in Washington, D. C. The sentence template of my own design ended with
<,< [Place:Plain]>>.
Note in particular that the last character in the sentence template is a period.
The result when I run a report that includes the 1950 Census fact for Washington, D. C. is that the sentence ends with a double period. The first period at the end of the sentence is from the second period of D. C. and the second period at the end of the sentence is from the sentence template itself.
If there is a bug, then the bug is that perhaps RM itself should identify the double period and should convert it to single period as the report is being produced. I do realize that’s a stretch, and I’m not sure if I were the RM developer that I would want to make this sort of change.
I’m not willing to enter the place name as Washington, DC nor as Washington, District of Columbia nor as Washington, D. C., United States nor as anything like that - even though any of those place name variants would solve my problem. It looks as if my best solution is that both RM7 and RM9 support a one off customization of a sentence for one particular fact for one particular person. Much to my surprise, this particular customization was not lost when I tested it with a drag and drop operation. So that’s what I’m going to go with.
By the way, similar customizations of citation sentences do seem to be subject to problems during a drag and drop. So the drag and drop support for fact sentence customizations seems to be a bit more robust than is the drag and drop support for citation sentence customizations.