|
This is still an issue, but will be complicated to solve. Reading the specifications on http://www.w3.org/TR/html401/struct/text.html#whitespace
For Moodle 2.0, I think this should be fowarded upstream, to the TinyMCE team, though they already have plenty of white space related bugs: http://sourceforge.net/search/?words=white+space&sort=open_date&sortdir=desc&offset=0&group_id=103281&type_of_search=artifact&pmode=0 I'm sorry everyone for cross-posting. But did this issue relate to my issue (http://tracker.moodle.org/browse/MDL-12190)?
The issue is that: I can type Zero-Width Space in HTML Editor without any problem but when I switch to HTML mode (or click Save Changes), all the ZWSP have changed to Space. We can't accept this writing (space between all words) in our Khmer language, so our temporary solution for now is using TinyMCE. But it's not the proper solution. Is it? Well, actually ... As HTMLArea is not supported/developed anymore, this might be the proper solution. The next version of Moodle will come with TinyMCE, so if this editor works for you, all the better.
Thank you Mathieu for the information. It's really great to have TinyMCE as the editor for the next Moodle.
And do you mean the next version of Moodle is 2.0? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
htmlarea.php 1.46 in CVS does not have the problem but 1.47 has. A new function formathtml() introduced in 1.47 removes all newline codes in html, so you can reproduce the problem by:
Toggle to HTML source mode and enter
a b
c d
and toggle to wysiwyg mode, then again toggle to HTML source mode.
I think formathtml() should remove newline codes only at the beginning and the end of the html source. Replacing newline codes to spaces may cause another problem for other languages such as Japanese. A single newline code in Japanese text is just simply ignored but a space code is took into account.
From Gustav Delius (gwd2 at york.ac.uk) Thursday, 28 April 2005, 07:15 PM:
It seems to me that Janne has now fixed this. Thank you both for your work on this. Should the bug be closed?
From Janne Mikkonen (janne.mikkonen at julmajanne.com) Thursday, 28 April 2005, 07:31 PM:
Lets not close this one until it's really gone...