After some discussing and testing this on the OOo for translators list, we found
that the bug is indeed there after all, but it is only *at the wrapped end of a
wrapped line* that the space disappears.
IMHO, the bug summary should be changed to "Show spaces at wrapped end of a line
in Writer", to avoid confusion and better pinpoint the problem. I believe this
is one reason why nobody addressed or even set this issue to "confirmed" or
"worksforme".
In a table this bug shows as a downright ridiculous breakage of the WYSIWYG
paradigm: after typing past a line wrapping, one can insert as many new spaces
as one likes, none at all show. Hard spaces show the behaviour one might expect
from normal space.
If inserting all those spaces didn't result in a corresponding amount of space
characters being inserted, it might not have mattered (in some senses, although
it would of course be a serious thing in other ways), but it does. Copy-pasting
the portion from the table reveals all those spaces again.
If OOo is used to process tables that are used for importing e. g. proofread
material into some application, the results can be more or less disastrous. This
is not an academic excercise, I and many other translators use such applications
every day to make a living.
I suggest raising this bugs priority as much as possible, it's a serious bug.
After some discussing and testing this on the OOo for translators list, we found
that the bug is indeed there after all, but it is only *at the wrapped end of a
wrapped line* that the space disappears.
IMHO, the bug summary should be changed to "Show spaces at wrapped end of a line
in Writer", to avoid confusion and better pinpoint the problem. I believe this
is one reason why nobody addressed or even set this issue to "confirmed" or
"worksforme".
In a table this bug shows as a downright ridiculous breakage of the WYSIWYG
paradigm: after typing past a line wrapping, one can insert as many new spaces
as one likes, none at all show. Hard spaces show the behaviour one might expect
from normal space.
If inserting all those spaces didn't result in a corresponding amount of space
characters being inserted, it might not have mattered (in some senses, although
it would of course be a serious thing in other ways), but it does. Copy-pasting
the portion from the table reveals all those spaces again.
If OOo is used to process tables that are used for importing e. g. proofread
material into some application, the results can be more or less disastrous. This
is not an academic excercise, I and many other translators use such applications
every day to make a living.
I suggest raising this bugs priority as much as possible, it's a serious bug.