bugFree UCS Outline Fonts - Bugs: bug #35130, Extend support for math operators...

 
 

bug #35130: Extend support for math operators in FreeSans

Submitter:  Pander <pander>
Submitted:  Tue 20 Dec 2011 04:35:56 PM UTC
   
 
Category:  character range Severity:  3 - Normal
Item Group:  glyph(s) missing Status:  Fix posted
Privacy:  Public Assigned to:  Stevan_White
Open/Closed:  Open Release:  * development
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 20 Sep 2017 06:41:11 PM UTC, comment #8: 

fixed.

Steve White <Stevan_White>
Group administrator
Wed 20 Sep 2017 04:20:34 PM UTC, comment #7: 

Revision 3636 added a glyph called “NameMe.8622” but did not associate it with U+21AE.

David Corbett <dscorbett>
Wed 20 Sep 2017 01:07:24 PM UTC, comment #6: 

No worries. Hope to see a new release of this font family, if possible this year. If I can help, let me know.

Pander <pander>
Wed 20 Sep 2017 01:01:33 PM UTC, comment #5: 

Pardon the many-year wait.  I just forgot.

Steve White <Stevan_White>
Group administrator
Thu 22 Dec 2011 03:53:54 PM UTC, comment #4: 

Agreed. What is in Unicode has already consensus amongst a group of experts. By the way, and to close this off-topic dialogue, is was nice to go through the process at the Unicode Consortium for requestion a code for double barred capital b for https://en.bitcoin.it/wiki/Bitcoin_symbol (the request is still pending at this moment).

Pander <pander>
Thu 22 Dec 2011 03:39:52 PM UTC, comment #3: 

We're all mathematicians here, and I've seen strange symbols too, and I think there ought to be a law.  Complicated symbols often strike me as a failure in communications skills.

But anyway, the standard is what it is, and the aim of the project is to follow that.

Steve White <Stevan_White>
Group administrator
Thu 22 Dec 2011 02:53:03 PM UTC, comment #2: 

My field is information technology (computer science, electronics and mathematics) and I've seen stranger symbols. ;)

Pander <pander>
Tue 20 Dec 2011 06:09:13 PM UTC, comment #1: 

Hi Pander,

I take it that this is a list for which you see special need.

I don't follow how extending these in FreeSans will extend the support for math in FreeSerif.

If you're feeling artistic, please don't hesitate to send me a diff from a recent SVN update.  (But write to me for guidelines first.)

I'm not sure I follow your suggestions about scaling.  I don't like the sounds of it.

U+219A, U+219B, U+21AE (Arrows)
  The intent is to give Sans and Mono a similar subset of most common arrows (NOT to make all the sets the same).

U+2274, U+2275, U+2278, U+2279 (various slashed inequalitites)

U+22AC, U+22AD, U+22AE, U+22AF (slashed logic signs)

U+22EC, U+22ED (slashed triangle inequalities)
   Wow -- I don't even know what field these are used in...
   Curious: what is your field Pander?

Steve White <Stevan_White>
Group administrator
Tue 20 Dec 2011 04:35:56 PM UTC, original submission:  

Please extend support for math operators in FreeSans. It concerns the following ranges:
-  U+219A, U+219B
-  U+21AE
-  U+2274, U+2275
-  U+2278, U+2279
-  U+22AC, U+22AD
-  U+22AE, U+22AF
-  U+22EC, U+22ED

These are already implemented for FreeSerif and FreeMono. These can be used by scaling conform other math operators in between these ranges which are already available in all three fonts. Also, the components or other glyphs from which these math operators are composed from are already available as glyphs in FreeSans. Preferably these can also be used in order to construct the missing ghyphs which are listed above.

Implementing this will extend the support of math operators in FreeSerif.

Pander <pander>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by Stevan_White (Posted a comment)
  • -email is unavailable- added by pander (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-09-20 Stevan_White StatusProceeding Fix posted
    2011-12-20 Stevan_White StatusNone Proceeding
        Assigned toNone Stevan_White

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code