*Workaround: Instead of using a "normal" space character, insert a Unicode space character, such as U+2003 which is the "EM SPACE (mutton)" character. Inkscape will not strip/remove these.
I'm also still experiencing this issue with multiline, flowed text in Inkscape 0.92.1 r15371 on Debian Stretch (Linux). Flowed textbox lines which contain a single blank space appear fine in the editor *until* the file is saved and re-opened in Inkscape. After re-opening, all lines that previously had a blank space no longer appear in the text box (they were stripped).
Each line of a flowed text box is represented in SVG by a node like <svg:flowPara id="flowPara7293">. The value of the line (in this case, the single space character) is added as content to this node. After re-loading the file, Inkscape strips out the lone space character, making the content of the node blank... which of course alters the presentation of the document without the author's consent.
*Workaround: Instead of using a "normal" space character, insert a Unicode space character, such as U+2003 which is the "EM SPACE (mutton)" character. Inkscape will not strip/remove these.
I'm also still experiencing this issue with multiline, flowed text in Inkscape 0.92.1 r15371 on Debian Stretch (Linux). Flowed textbox lines which contain a single blank space appear fine in the editor *until* the file is saved and re-opened in Inkscape. After re-opening, all lines that previously had a blank space no longer appear in the text box (they were stripped).
Each line of a flowed text box is represented in SVG by a node like <svg:flowPara id="flowPara7293">. The value of the line (in this case, the single space character) is added as content to this node. After re-loading the file, Inkscape strips out the lone space character, making the content of the node blank... which of course alters the presentation of the document without the author's consent.