In May of 2014 we introduced a WYSIWYG editor into QuestionPoint. (See: 5/18/2014 QP Release Notes). Unfortunately a few bugs were discovered that are now repaired:
A. Line breaks in Scripted Messages when used in WYSIWYG
The Scripted Messages configured for the Ask module are currently written in plain text. Line breaks can be created by using the “Enter” key on the keyboard, as well as by using the <br> tag.
Unfortunately, the carriage return “Enter” key method was not recognized by the new WYSIWYG editor. As a result, formatted scripts were suffering “run-on” appearance if <br> tags had not been used, and therefore had to be manually edited from within the editor.
A temporary work around was offered, suggesting that <br> tags be used until the previously used formatting became available in WYSIWYG.
We have implemented a retroactive fix, and “Enter” key returns are now preserved, allowing those previously formatted scripts to behave correctly when added to the WYSIWYG editing screen in Answers, Clarification Requests, and Messages. Going forward, both “Enter” key returns and /or <br> tags will create a single space line break in all three levels of Scripted Messages (Individual, Institution, and BME Shared Messages.)
B. Line Breaks from within WYSIWYG
When using any of the WYSIWYG screens, the original default behavior line break implemented by using the “Enter” key was to create a double line break space (i.e. a paragraph break). It was only possible to create a single line break by using Shift+Enter. This was deemed counter-intuitive to expected behavior; therefore we have reversed this rule.
Enter key now creates a single line break. To create a double line break, use Enter key twice, or Shift+Enter.
C. Foreign Language sets now recognized when QP sessions are moved into KB.
As we proceed with the process of updating QuestionPoint features to use html in Answers, Patron replies, Clarification Requests and Messages, some processes sitll using plain text that import content from QP sessions were negatively affected when foreign language sets or diacritics were used. We discovered that Answers promoted to the KB, emails received by librarians upon referral, and those sent to email partners contained some unreadable text under certain conditions. That has been repaired and character sets of our supported languages will now render correctly when imported to the Knowledge Bases, and when sent out via email.