Today I stumbled over another case where TMCE editing killed topic
formatting on save, in two successive steps.
Occasionally, I write a non-breaking space
instead of a
"normal" space, to avoid an unwanted word wrap, or as a placeholder,
maybe several in a row. Another example is forcing a "table header"
formatting for an empty element, like the following (I'm giving
verbatim first, because some poor soul might inadvertedly destroy the
example with TMCE)
| *Col1* | * * | *Col2* |
On the
first save, the
is replaced by a simple blank,
so that the heading now reads:
| *Col1* | * * | *Col2* |
This still looks as desired. But on the second save, the boldface
space is gone, and the cell is formatted as plain empty cell.
Another use case where I've found
in our TWiki was to
disable a setting, but leave it "visible":
* Set FOO = bar
Regardless of verbatim, such a setting is ineffective. If
not in
verbatim, however, after a save the setting takes effect. Morale:
Don't try to outwit TWiki, or TMCE will outwit you.
TMCE allows to explicitly add a non-breaking space with its "insert
custom character" menu, but they enter the topic as a simple space.
The TWiki web in the distributions has 51 occurrences of
. If one of these is edited with TMCE, their formatting
might be weird.
I know that TMCE can hardly be prevented from replacing a
S
with a
S
, because that's what the encoding means. But a
non-breaking space is not a space!
--
TWiki:Main/HaraldJoerg
- 09 Dec 2007
We also use the nbsp often in empty table headers. Would not want to loose those. Seems this character needs special TLC.
--
TWiki:Main.KennethLavrsen
- 10 Dec 2007
An unprotected nbsp is taken through into the HTML edit. Once there, it is the same as any other nbsp. When the conversion back to TML happens, whitespace is optimised and nsbp's collapsed except where they are critical to TML.
Because nbsp plays a critical role in the conversion back to TML, I really don't want to change the way it is handled. On the flip side, protecting nbsp (so it appears as in the editor) would make a bit of a mess of the edit.
I appreciate there are a lot of topics that have never been edited using TMCE, but there's a tradeoff between maintaining 100% compatibility with old topics, and making the editor maintainable. I can't think of a simple solution to this.
Confirmed.
--
TWiki:Main.CrawfordCurrie
- 14 Dec 2007
I just checked, this is still an issue with latest
TinyMCE-3.5.8 integration.
--
TWiki:Main.PeterThoeny
- 2013-10-02
Workaround: Define a NBSP setting in
TWiki.TWikiPreferences.
--
TWiki:Main.PeterThoeny
- 2013-10-02
The workaround is now implemented:
VarNBSP.
--
TWiki:Main.PeterThoeny
- 2013-10-02