The latter suggests that WebKit developers may be close to resolving or working around a significant issue. However: this is _not_ an issue that I should expect to affect a minimally-configured Kupu in UIs within Diigo.
It's often said that FCKeditor excels at dealing with the monstrosity that is Microsoft HTML. However, re http://www.diigo.com/annotated/967ddbbf2c2ad5936acba9d2e0134af4 as Diigo is HTML-centric, so we should not expect people to annotate (or paste from) Microsoft Word :)
All things considered, I should tend towards Kupu …
Best regards Graham
Postscripts:
* annotated link to the PYPI page includes a sticky note highlighting that the list of supported clients of Kupu (browsers) does include WebKit-based browsers
/ Diigo Community/ HTML edition in areas of Diigo: WYSIWYM (WMD), WYSIWYG (FCKeditor, Kupu, TinyMCE)
1. http://www.diigo.com/annotated/4fa5d97e971d1601410fac963dc8ad81
2. http://groups.diigo.com/Diigo_HQ/forum/topic/proper-paragraph-spacing-presented-in-tinymce-is-lost-when-submit-button-is-clicked-7332
3. http://www.diigo.com/annotated/15400ed58203bb04e9d6e3d31b46bffd
4. http://www.diigo.com/annotated/efed2dacc4daa2c8271351785bd4e997
5. http://www.diigo.com/annotated/94ba5a622f457d061aa1edd78720f337
The latter suggests that WebKit developers may be close to resolving or working around a significant issue. However: this is _not_ an issue that I should expect to affect a minimally-configured Kupu in UIs within Diigo.
= About versions and maintenance of Kupu =
Don't be misled by the 2006 version 1.3.5 of Kupu at http://kupu.oscom.org/download/
Focus instead on http://www.diigo.com/annotated/c1aff106c8eee19be3e16548a49fc9a0, http://plone.org/products/kupu/releases and http://dev.plone.org/plone/query?component=Visual+Editor+%28Kupu%29&order=status all of which demonstrate that (as Kupu for Plone is a product that is within 'Plone core') Kupu is highly and regularly maintained. (Many of the references to changesets etc. are to changesets within the Kupu code base, not the Plone code base. Open source done well.)
= Merits of Kupu, FCKeditor and TinyMCE =
It's often said that FCKeditor excels at dealing with the monstrosity that is Microsoft HTML. However, re http://www.diigo.com/annotated/967ddbbf2c2ad5936acba9d2e0134af4 as Diigo is HTML-centric, so we should not expect people to annotate (or paste from) Microsoft Word :)
All things considered, I should tend towards Kupu …
Best regards
Graham
Postscripts:
* annotated link to the PYPI page includes a sticky note highlighting that the list of supported clients of Kupu (browsers) does include WebKit-based browsers
* annotated link to the WebKit bugzilla may fail in some browsers, if so then aim directly for https://bugs.webkit.org/show_bug.cgi?id=13490#c16.
http://groups.diigo.com/Diigo_HQ/forum/topic/allowing-minimal-html-in-the-forum-text-412
> … html in the forum …
This exemplifies the difference between:
a) rich highlights from an original
- one of three highlights includes a link that can be clicked
and
b) poorer, text/plain Diigo annotation
- stuck to one of the highlights, text authored by a Diigo user includes two links, _neither_ of which can be clicked.
I'm certain that for some users, WYSIWYG would encourage greater/richer use of annotations.
Whilst I still wish for WYSIWYG edition of rich text in these areas, there's a side of me that prefers plain text:
* partly for aesthetic/visual reasons - it's often easier to read plain text, especially in 'busy' environments;
* partly for technical reasons - I think vaguely of APIs, http://groups.diigo.com/Diigo_HQ/forum/topic/diigo-api-rdf-semantic-web-45812 and the like.
In the meantime, it would be neat if we could preview things before posting.
Confirmed:
http://www.diigo.com/user/grahamperrin/WMD
Reportedly good for Chinese text, too:
http://www.diigo.com/user/grahamperrin/WMD+Chinese