bugUnifont - Bugs: bug #51672, Problems with Sharada

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #51672: Problems with Sharada

Submitter:  David Corbett <dscorbett>
Submitted:  Sun 06 Aug 2017 12:39:54 AM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  unifoundry
Open/Closed:  Closed

Tue 05 Jun 2018 10:40:46 PM UTC, comment #5: 

Changes made in Unifont 11.0.01.

Paul Hardy <unifoundry>
Group administrator
Wed 30 Aug 2017 04:13:57 AM UTC, comment #4: 

It was unintentional. I have re-opened it.


Paul Hardy

Paul Hardy <unifoundry>
Group administrator
Tue 29 Aug 2017 03:36:03 PM UTC, comment #3: 

Though this bug report is marked “Fixed” and the release notes for Unifont 10.0.06 mention Sharada, these changes are not in Unifont 10.0.06. Is that intentional?

David Corbett <dscorbett>
Sun 13 Aug 2017 01:46:15 AM UTC, comment #2: 

David,

I have incorporated your suggestions except for changing some of your original glyphs to these:

011182:0000000000000000000000000006000600000000000600060000000000000000
0111C1:0000000000000000000000F8010001000080004000400F800000000000000000
0111C5:0000000000000000080008000800080008000800080008000000000000000000
0111C6:0000000000000000090009000900090009000900090009000000000000000000
0111C7:0000000000000000100038001000000000000000000000000000000000000000
0111C8:0000000000000000000000000000000000000800080008000000000000000000
0111C9:0000000000000000FFFF00000000000000000000000001000200018000400380
0111DD:0000000000000400020002000200020004000200010000800040000000000000

I drew all the Indic glyphs using unibmp2hex, which hard codes the whole Sharada range to be double-width. I could modify that in the future, but for now I am hoping not to have to modify any more programs.

When Andrew Miller wrote the unipng2hex utility, he did not copy the hard-coding that I used in unibmp2hex. I have left unipng2hex as is for now, because nobody else was working on Indic glyphs. That does leave a void though.

I have not changed any of the combining characters, so for example the visarga is still a combining character (and I made its dots thicker from what I originally had).

Thank you,


Paul Hardy


Paul Hardy <unifoundry>
Group administrator
Sun 06 Aug 2017 03:43:22 PM UTC, comment #1: 

Apparently, Savane deletes non-BMP characters and everything after them. Let’s try this again.

U+111C4 SHARADA OM should look like U+1118F SHARADA LETTER O + U+11180 SHARADA SIGN CANDRABINDU.

U+111C5 SHARADA DANDA, U+111C6 SHARADA DOUBLE DANDA, and U+111C8 SHARADA SEPARATOR should not be so wide.

U+111C7 SHARADA ABBREVIATION SIGN should be higher and not so wide.

U+111C9 SHARADA SANDHI MARK should be lower, smaller, and not so wide. Its Unicode proposal shows that it is used between consonants without affecting their spacing, but it should not be a combining glyph, because it can be doubled. The glyph should have a headstroke to avoid breaking the headstroke between consonants, since Unifont uses a connected-headstroke style.

U+111CA SHARADA SIGN NUKTA and U+111CC SHARADA EXTRA SHORT VOWEL MARK should be shifted left to avoid overlapping vowel signs below.

Unlike U+A8FB DEVANAGARI HEADSTROKE, U+111DC SHARADA HEADSTROKE should join to adjacent headstrokes.

U+111DD SHARADA CONTINUATION SIGN should look more like it does in its Unicode proposal.

011181:0000000000200000000000000000000000000000000000000000000000000000
011182:00000000000010000000100000000000
011183:000000000000000007FF04101A10021007F00610001000300070001000000000
01118C:0000000000000000FFFF209421CC222020402180221021E00000000000000000
01118F:0000000000000000FFFF18201820144014E01210121011E00000000000000000
011193:0000000000000000FFFF0210021006100E100210001000100000000000000000
0111B6:0000000000000000000000000000000000000000000000000020006000E00020
0111B7:0000000000000000000000000000000000000000000000000020002007E00000
0111B8:00000000000000000000000000000000000000000000000000220022001C0000
0111B9:0000000000000000000000000000000000000000000000000049004900360000
0111BA:000000000000000000000000000000000000000000001FF804E0042004400470
0111BB:000000000000000000000000000000000000000000001FF80BB00890090009C0
0111BF:00000E7011881004000F00020002000000000000000000000000000000000000
0111C1:0000000000000000000C100804380000
0111C2:0780030005000300000000000000000000000000000000000000000000000000
0111C3:06C009200FE00000000000000000000000000000000000000000000000000000
0111C4:0380044005400000FFFF18201820144014E01210121011E00000000000000000
0111C5:00000000080808080808080800000000
0111C6:00000000242424242424242400000000
0111C7:00000000103810000000000000000000
0111C8:00000000000000000008080800000000
0111C9:00000000FF0000000000001020180438
0111CA:0000000000000000000000000000000000000000000000000000060006000000
0111CB:0020002000200000000000000000000000000000000000000000000000000000
0111CC:0000000000000000000000000000000000000000000000000000100008000400
0111DC:0000000000000000FFFF00000000000000000000000000000000000000000000
0111DD:00000020202020204020100804000000

David Corbett <dscorbett>
Sun 06 Aug 2017 12:39:54 AM UTC, original submission:  

U+11181 SHARADA SIGN ANUSVARA and U+111CB SHARADA VOWEL MODIFIER MARK should be more to the right, to be above the vertical stem of most letters.

U+11182 SHARADA SIGN VISARGA overlaps U+111B5 SHARADA VOWEL SIGN II, so it should have a non-combining 1-cell-wide glyph. A headstroke is not required.

The foot of U+11183 SHARADA LETTER A should be a small triangle. My suggested glyph uses the triangle of U+111B6: the triangle of U+111AB I found too large. The same goes for the left foot of U+11193 SHARADA LETTER GA.

U+1118C SHARADA LETTER VOCALIC LL can look more like U+1118B SHARADA LETTER VOCALIC L: there is plenty of room so it need not be squished.

The diagonal stroke of U+1118F SHARADA LETTER O should meet the headstroke at a steeper angle.

The below-base vowels U+111B6 through U+111B9 should be shifted right and up so they meet the vertical stem of most letters.

U+111BA SHARADA VOWEL SIGN VOCALIC L and U+111BB SHARADA VOWEL SIGN VOCALIC LL overlap the bottoms of consonants.

The headstroke of U+111BF SHARADA VOWEL SIGN AU is one pixel too high.

U+111C1 SHARADA SIGN AVAGRAHA should be lower and not so wide.

U+111C2 SHARADA SIGN JIHVAMULIYA and U+111C3 SHARADA SIGN UPADHMANIYA combine with the following consonant, so they should be combining characters with x-offsets of 0. They should be one pixel higher to avoid overlapping the headstroke. The jihvamuliya should be one pixel left so its stem is directly above U+11191 SHARADA LETTER KA’s.

U+111C4 SHARADA OM should look like ⟨

David Corbett <dscorbett>

 

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

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 unifoundry (Posted a comment)
  • -email is unavailable- added by dscorbett (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.

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-06-05 unifoundry StatusIn Progress Fixed
        Open/ClosedOpen Closed
    2017-08-30 unifoundry StatusFixed In Progress
        Open/ClosedClosed Open
    2017-08-27 unifoundry StatusIn Progress Fixed
        Open/ClosedOpen Closed
    2017-08-13 unifoundry StatusNone In Progress
        Assigned toNone unifoundry

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code