-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This commit represents a fix for the issue reported by Roland F in wh…
…ich the presence of an \nd* inline binding end marker inside the middle of a word, was causing the remaining part of the word to be parsed as a separate source phrase (leaving what appeared as a space, but was a pile gap between the parts of the word). To effect a fix I added a wordSuffix ref parameter to the ParsePostWordPunctsAndEndMkrs() call to cover the situation where an inline binding end marker such as \nd* occurs in the middle of a word. The wordSuffix ref parameter will return any such word-building suffix part of the word that occurs directly following the inline binding end marker. Otherwise, as Roland F reported some of his words that had, for example, \nd<word-first-part>\nd*<word-suffix-part><space-between-words> were getting broken up resulting in the <word-suffix-part> being parsed as a separate source phrase. We can also utilize any returned wordSuffix to update the m_key and m_srcPhrase members with such suffix Some code for doing this was borrowed from ParseAWord(). Ensured that the m_srcSinglePattern value gets any form of the ParseWord() function call that has an embedded inline binding end marker within it. This makes it possible to reconstruct the correct position of an embedded inline binding end marker when exporting the source text. This commit also modifies the export source text routine FromSingleMakeSstr2() to utilize the m_srcSinglePattern value to achieve more accurate positioning of inline binding end markers like \nd* for more robust exports of the source text.
- Loading branch information
Showing
4 changed files
with
173 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.