Hello, sorry for not replying earlier; with the public holiday in germany and a number of other issues this mail got sort of lost.
> So, assuming that neither delaying the release nor fixing the Kupu > integration are valid options, which course of action should we take? Some > suggestions (not mutually exclusive): > > 1. Just release, add the known issues to the release notes. Document the issues: yes; just release: no. -1 > 2. Move Kupu to the contributions area, release without Kupu. -1 > 3. Move Kupu to the last position in the "Edit" menu. 0 > 4. Promote FCKEditor (menu item with link to the install instructions) +1 > 5. Promote TinyMCE (menu item with link to the install instructions) +1 > 6. … (?) Improve the TinyMCE integration by making tiny_valid_elements.js and the RelaxNG schema compatible (if possible). This might break some features of TinyMCE, but would avoid the extremely annoying and difficult to understand error messages you sometimes get when you click on TinyMCE's Save button. Of course, I'm most interested in TinyMCE since I recommended it to my users. I can prepare a stripped down copy of tiny_valid_elements.js; I have already started doing it on a case by case basis. As for FireDocs, I haven't been able to get it to work out of the box (had a frozen firefox browser and no time to look into it), so I'm not very much in favour of it. On the other hand, it looks like a promising editor for the future. Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org For additional commands, e-mail: user-h...@lenya.apache.org
