(Note that it is only visible in IE9 and lower) It is due to be removed. While the default spell engine is Google spell which can be changed in Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor, this is no longer supported by Google and will not work. Instead you can use the enchant which is bundled by default in 5.3." To spell-check via your browser, type your word (which if incorrectly spelt will have red lines under it) and press right click + CTRL If you want to disable it and and rely on browser spell checker functionality instead, you can do this by disabling the legacy spellchecker plugin by clicking its eye in Administration > Site administration > Plugins > Text editors > TinyMCE HTML editor > General settings The legacy spell checker is visible in IE9 and lower only, but not in other browsers. If you have a global custom TeX filter, then disable this setting.Īccessed from Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>Insert emoticon, this allows you to enable or disable the emoticon filter in the editor context and thereby display the emoticon button. The TinyMCE editor plugins screen Insert equationĪccessed from Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>Edit equation, this allows you to enable or disable the TeX filter in the editor context and thereby display the Dragmath button. Additionally the equation, emoticon and spell check buttons have links to their Settings screens.Buttons for equations, emoticons,images, media, automatic linking, and legacy spell-checking may be enabled, disabled or uninstall here by clicking on their eye.The TinyMCE HTML editor has its own settings page Administration>Site administration>Plugins>Text editors>TinyMCE HTML editor>General settings with the following options: By default the TinyMCE HTML editor and plain text area are enabled. Site administration settings Manage editorsĪ site administrator can enable / disable text editors in Settings > Site administration > Plugins > Text editors > Manage editors. Click Save the Wiki page containing your table will then load displaying its borders.Click on its Advanced tab, set Border Color to black (for instance), then click Apply, and then click Update.Then right click (Macs: Command+click or Ctrl+Click) over any part of your selection to get a context menu from it select Cell > Table Cell Properties the cell properties dialog box then loads.Carefully select all the cells of the table.In the Wiki page containing your table, click its Edit tab.
If they aren’t showing already you can add them as follows: Ps My non-constructivist Moodle class, started 4 weeks ago, seemst to be making my rats work their goolies off outside of class, enablining me to have very constructivist classroom time.Cell borders are crucial for helping readers to follow the rows across the screen. I don't suppose that Joji can have that privelidge? His (?) cure of the double script error problem has been for me, a real blessing, but I can not keep asking him to cure the rte over again. Or, alternatively, what would I need to ask Joji to do so that the patches he makes are integrated with the ongoing Moodle source code? Some people seem to put things in the CVS. I would be very grateful for any ideas on what I should do to integrate.
Particularly in the latest there seems to be a call to rich_edit.php in weblib.php which means that rte from a month ago do not work at all. But both of these fixes are not in the latest moodle which I managed to upload last night (The new Moodle and in particularly the Glossary is BEAUTIIFUL). Alas the rte has changed so that I can not longer apply Joji's patch. Joji (My friendly neighbour hood information technology professor) has fixed the long standing rte double script area on load up problem (ah, such sublime relief), and using Janne's fix above he has implemented the style translation problem.
0 kommentar(er)
