Sorry for the delay in getting back to you. We had some internal
discussions about this, and that takes time.
There are several issues that complicate your request. First, in
order to add new characters, we would need to have public-domain
versions of the glyphs for those characters, or create them
ourselves. None of the implementations I found for \oiint and \oiint
would match the other integrals in the MathJax fonts (so I didn't
check whether they were PD or not), which means we would have to
create them ourselves (not something we really want to get into).
Second, every character we add to the MathJax fonts requires
corresponding image font files and increases the size of the (already
large) image font installation. Third, some people (including you, as
I recall) have the MathJax fonts already installed locally, so if we
add characters to the fonts, there is a serious backward-compatibility
problem with people having old versions of the fonts. We are not
really interested in making new versions of the fonts for that
reason. On the other hand, it would be possible to make ADDITIONAL
font files with new characters, and that is a possibility for the
future (there are a number of characters I'd like to see as well),
though we would likely not include new image font versions of these.
You mention that you have been editing the extensions, fontdata.js and
other /font files. I would recommend against that, especially the /
font files, as these are generated programmatically from the fonts
themselves, so there is nothing you can add to those that would be
valuable, since every glyph in the fonts is already included (anything
you add would simply cause problems).
You could use \mathop{\unicode{x222F}}, for example, to get these
characters, but it will be difficult to get the different size for
displaystyle and textstyle this way.
Davide
Paul
Most such special-character needs can be handled through the \unicode
command, but this is not the case for stretchy characters, or for
"large operator" symbols like the ones Nageh is requesting. There are
a number of characters that it would be very useful to have in order
to handle more stretchy delimiters and stretchy arrows, and I do hope
to add these in this way at some point in the future. Nageh's
requests could be included at that point, along with other large
operators. That is, provided we can find or easily create the
required glyphs for them.
Davide
We get into trouble with backward compatibility if we change our
existing fonts, so adding new font(s) in the future is the way to go.
--Robert