We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 5882 - Add super- and subscript functionality to TinyMCE
Add super- and subscript functionality to TinyMCE
Status: NEW
Product: OJS
Classification: Unclassified
Component: Plug-ins
3.0
PC Mac OS X 10.6
: P5 enhancement
Assigned To: PKP Support
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-09-03 15:14 PDT by James MacGregor
Modified: 2013-05-29 16:01 PDT (History)
3 users (show)

See Also:
Version Reported In:
Also Affects: OCS 2.3.4, OMP 1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2010-09-03 15:14:46 PDT
It should be possible to enable superscript and subscript functionality in TinyMCE. Jay on the forums (http://pkp.sfu.ca/support/forum/viewtopic.php?f=9&t=6527&p=25115#p25115) has pointed out that there's often a need, in biology journals, to super- or subscript items. 

I've posted this against 2.3.3; I'm assuming it's not a huge fix. Any thoughts (probably Matt in particular)?
Comment 1 Matthew Crider 2010-09-03 15:26:08 PDT
James, this should be as easy as adding 'sup' and 'sub' to the list of plugins in plugins/generic/tinymce/TinyMCEPlugin.inc.php::callback().  Could you test that out?
Comment 2 James MacGregor 2010-09-03 15:54:52 PDT
Yeah, that works great! Do we have any policy on how we make changes like this, eg. should I just tell Jay how to do this, or do you think it's worth adding?
Comment 3 Matthew Crider 2010-09-03 15:56:41 PDT
My only concern was that the button bar was already full--Are you sure adding those two doesn't conceal any of the other plugins (i.e., does it resize the whole tinyMCE editor to fit the new buttons)?  If not, then we might as well commit it.
Comment 4 James MacGregor 2010-09-03 16:13:28 PDT
Hrm ... it definitely does stretch the field wider than it was, in some cases at least. I'm a little leery on how this might affect fields here and there that might not have the room to spare, at least at this late a date -- I'll move this to 2.3.4, and will respond on the forum as to how to otherwise fix.
Comment 5 Alec Smecher 2012-12-28 12:45:10 PST
Low priority and has cosmetic implications; deferring to post-UI overhaul.