Closed
Bug 72161
Opened 23 years ago
Closed 23 years ago
Back-end to extend the support of stretchy chars
Categories
(Core :: MathML, defect)
Core
MathML
Tracking
()
RESOLVED
FIXED
mozilla0.9
People
(Reporter: rbs, Assigned: rbs)
References
()
Details
Attachments
(3 files)
55.61 KB,
text/plain
|
Details | |
4.54 KB,
text/plain
|
Details | |
44.84 KB,
patch
|
Details | Diff | Splinter Review |
I will be attaching a patch that extends the handling of stretchy chars in accordance with the system that I described at the above URL. The patch allows the stretchy code to support mixed glyphs from different font families when these are specified with the 'code@font' notation in the MathFont Property File. The patch also allows using common code points in the Unicode' Pivate Use Area for glyphs of same rank but in different font famlies (this way, assignments to the PUA are kept minimum). To summarize, with this patch, the stretchy code now supports the system that I described in its entirety. Converting the mapping tables and property files to the new Unicode points published in MathML2 is the remaining piece of the puzzle (bug 71408). The patch only includes the conversion of the Symbol font.
Want to give me r/sr on this guys?
Target Milestone: --- → mozilla0.9
Also completed (in my tree) the migration of the entities & operator dictionary to the new MathML 2.0 unicode points (bug 30543), and completed the migration of the MathFont Property Files of Adobe' Symbol font and TeX fonts (CMR10, CMMI10, CMSY10, CMEX10) to agree with these code points and the stretching process. So the PUA stub has expanded quite a lot.
Comment 6•23 years ago
|
||
[s]r=waterson.
Checked-in. I will land the stretchy data later when they are ready (it is rather tedious to prepare so many of them in one go.)
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•