The problem stemmed from the concatenation process in the describeLocation [Movement.c] function. Specifically, when appending strings, the code did not consistently check if a space already existed at the end of one string before adding another space. This could result in double spaces when the next string was concatenated.
Suggested Solution:
To resolve this, I added a check to ensure that a space is only added if one does not already exist at the end of the string. The updated code snippet ensures that the verb string always ends with exactly one space before concatenating the next part of the sentence:
Fix: #711
Issue:
The problem stemmed from the concatenation process in the describeLocation [Movement.c] function. Specifically, when appending strings, the code did not consistently check if a space already existed at the end of one string before adding another space. This could result in double spaces when the next string was concatenated.
Suggested Solution:
To resolve this, I added a check to ensure that a space is only added if one does not already exist at the end of the string. The updated code snippet ensures that the verb string always ends with exactly one space before concatenating the next part of the sentence:
Before:
After: