Code Monkey home page Code Monkey logo

eczar's Introduction

Eczar

Eczar is an open-source type family published by Rosetta with generous financial support from Google. The fonts support over 45+3 languages in Latin and Devanagari scripts in 5 weights. It was designed by Vaibhav Singh (@errorsinc), code and production is by David Březina (@MrBrezina).

Eczar started as a student project in 2010–11 during Vaibhav’s MA studies in Typeface Design at the University of Reading. Eczar was designed to bring liveliness and vigor to multi-script typesetting in Latin and Devanagari – with the intention of providing an alternative to existing designs by imparting a strong mix of personality and performance, both at text sizes and in display settings. The family offers a wide expressive range and the display qualities of the design intensify with corresponding increase in weight, making the heaviest weights best suited for headlines and display purposes.

Eczar specimen 1

Download

You can download the compiled fonts from Releases section of this repo or from the Google Fonts directory. Download the latest release

Building the fonts from source

If you want to compile the fonts from sources, read the production README.

Rosetta – world typography specialists

Rosetta addresses the needs of global typography. Together with our collaborators we create original fonts for a polyphonic world. Our work has been featured and awarded. But most importantly it has enabled people to read better in their native language.

So far our retail library supports pan-European Latin, Arabic, Armenian, Greek, Cyrillic (besides Slavic languages we also support many Asian languages), Inuktitut, and Indic scripts like Gujarati and Devanagari. In total, the library covers more than 200 languages.

For more information see the website at rosettatype.com.

You can contact us at [email protected].

License

The fonts and related code are licensed under Open Font License. See LICENSE.txt for licensing information.

Feedback & progress

This version is now considered final. Let us know if you spot any problem (via issues).

Eczar specimen 2

eczar's People

Contributors

davelab6 avatar mrbrezina avatar rosawagner avatar sergiolmartins avatar yanone avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

errorsinc davelab6 moyogo sergiolmartins yanone pcm8081

eczar's Issues

Eczar weights in oft-format have wrong "weight class" in OS/2

Related to issue #17, I really like this font so I decided to try fontforge to find out why all weight in the oft format are regular in my linux desktop enviroment. I found the issue:
screenshot_20170419_114134

I compare this the ttf format:
screenshot_20170419_114920
Furthermore I change the weight class value to bold in the odt file and the issue was resolved.

I don't how you would solve this if you use a different editor.

Issue with Devanagari in Word

This was submitted via email. Requesting more information to be posted here.

word having error given below
Language -Hindi-Devanagari
कर्तब्य
कार्य
अर्पण
दुर्ब्यापार
दुर्ब्यवहार
पार्टी

Please Find error and correct
you can choose other font such as (nirmla ui,Halant,sakal bharti,Laila ,Hind,yantramanav,yatraone ..etc)
and look difference between eczar and other font

@RosaWagner : if you could look into this

Dot should be centred in ' ां '

I don't know if it's a stylistic choice but the font renders the 'bindi' in words like चांद, पांव, हां to the slight left of the 'aa maatra'. It should be centred to the last stroke of the letter or the aa maatra touching the upper line.
Screenshot_20220913-232038_Edge

Scaling of glyphs to UPM?

The scaling of Eczar compared to other Devanagari fonts seems very small:

screen shot 2015-01-27 at 8 08 31 pm

I believe that the UPM was changed to 2048 while the glyphs themselves were not rescaled; a UPM of 1000 is preferable for web fonts as it reduces the filesize.

$ fontbakery-fix-vertical-metrics.py Eczar-*.ttf 
Parameter              Eczar-Bold.ttf    Eczar-Extrabold.ttf    Eczar-Medium.ttf    Eczar-Regular.ttf    Eczar-Semibold.ttf    
ymax                   1110              1143                   1046                1016                 1078                  
hhea.ascent            1288              1288                   1288                1288                 1288                  
OS/2.sTypoAscender     1188              1188                   1188                1188                 1188                  
OS/2.usWinAscent       1288              1288                   1288                1288                 1288                  
ymin                   -594              -634                   -513                -473                 -554                  
hhea.descent           -960              -960                   -960                -960                 -960                  
OS/2.sTypoDescender    -860              -860                   -860                -860                 -860                  
OS/2.usWinDescent      960               960                    960                 960                  960                   
hhea.lineGap           0                 0                      0                   0                    0                     
OS/2.sTypoLineGap      200               200                    200                 200                  200                   
hhea total             2248              2248                   2248                2248                 2248                  
typo total             2248              2248                   2248                2248                 2248                  
win total              2248              2248                   2248                2248                 2248                  
UPM:Heights            2048:1704         2048:1777              2048:1559           2048:1489            2048:1632             
UPM:Heights %          83 %              86 %                   76 %                72 %                 79 %       
$

IAST glyphs

This is a feature request, not a bug report.

It would be nice to have glyphs for the characters used by the IAST scheme, such as the Latin letters with dots under them, e.g., ḍ, ṇ, ṛ, ṣ, etc. I believe the relevant Unicode block is Latin Extended Additional, 1E00 through 1EFF, but only a few of those are needed for IAST.

Having those glyphs would permit the use of Eczar in combined Sanskrit-IAST-English documents that are common in some scholarly work, for instance. (If I'm not mistaken, this font has some origins in multi-script typesetting.) Of course, those glyphs can be produced in other ways by a typesetting system, but I think having the glyphs included in the font itself would be nicer.

In any case, thanks for all the work on this very nice font!

Interpolation problems in `Eczar[wght].ttf`

Hello!

This is an automatically-generated report about possible interpolation problems in Eczar[wght].ttf, as found in the Google Fonts catalog.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph Chi was not compatible:
  Masters: '', 'wght=800.0':
    Contour order differs: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10] in '', [0, 1, 2, 3, 4, 6, 5, 7, 8, 9, 10] in 'wght=800.0'
Glyph Kappa was not compatible:
  Masters: '', 'wght=800.0':
    Contour order differs: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] in '', [0, 1, 2, 3, 6, 5, 4, 7, 8, 9] in 'wght=800.0'
Glyph Mu was not compatible:
  Masters: '', 'wght=800.0':
    Contour order differs: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] in '', [0, 1, 2, 3, 4, 5, 7, 6, 8, 9] in 'wght=800.0'
Glyph Upsilon was not compatible:
  Masters: '', 'wght=800.0':
    Contour order differs: [0, 1, 2, 3, 4] in '', [0, 1, 3, 2, 4] in 'wght=800.0'
Glyph asterisk was not compatible:
  Masters: '', 'wght=800.0':
    Contour order differs: [0, 1, 2, 3, 4] in '', [2, 0, 1, 3, 4] in 'wght=800.0'
    Contour 3 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
    Contour 4 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph dvDGRa was not compatible:
  Masters: '', 'wght=800.0':
    Contour order differs: [0, 1, 2, 3, 4, 5, 6, 7] in '', [0, 1, 3, 2, 4, 5, 6, 7] in 'wght=800.0'
Glyph dvKSDda was not compatible:
  Masters: '', 'wght=800.0':
    Contour 11 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph dvKSTa was not compatible:
  Masters: '', 'wght=800.0':
    Contour 8 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph dvKSTta was not compatible:
  Masters: '', 'wght=800.0':
    Contour 8 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph dvNSMYa was not compatible:
  Masters: '', 'wght=800.0':
    Contour 11 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph dvNgMa was not compatible:
  Masters: '', 'wght=800.0':
    Contour 7 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph dvNyJYa was not compatible:
  Masters: '', 'wght=800.0':
    Contour 2 start point differs: 0 in '', 2 in 'wght=800.0'; reversed: False
Glyph dvNyJa was not compatible:
  Masters: '', 'wght=800.0':
    Contour 2 start point differs: 0 in '', 2 in 'wght=800.0'; reversed: False
Glyph dvSTRa was not compatible:
  Masters: '', 'wght=800.0':
    Contour 1 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph multiply was not compatible:
  Masters: '', 'wght=800.0':
    Contour 0 start point differs: 0 in '', 2 in 'wght=800.0'; reversed: False
Glyph uni090B.ss06 was not compatible:
  Masters: '', 'wght=800.0':
    Contour 2 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph uni0937094D was not compatible:
  Masters: '', 'wght=800.0':
    Contour 1 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False
Glyph uni0938094D was not compatible:
  Masters: '', 'wght=800.0':
    Contour 1 start point differs: 0 in '', 1 in 'wght=800.0'; reversed: False

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please apologize and ignore & close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

all the .otf files labelled as regular.

I am unable to the .otf as all use the label "regualr", installing one prevents installing the other. The ttf don't demonstrate this problem.
screenshot_20170328_103930

I am using KDE under linux, if thats significant.

ँ after ै and ौ rendered incorrectly

The combination of ै + ँ is rendered as if it were a combination of ‍ै + ं . Similarly for ौ + ँ . These two combinations are different at least for Nepali(नेपाली) language.

Minor changes

  • Copyright notice in the files is Copyright (c) 2014, Vaibhav Singh (design) and Rosetta Type Foundry s.r.o. (post-production). but in the LICENSE is Copyright (c) 2014, Rosetta Type Foundry s.r.o. (http://rosettatype.com), so update LICENSE file to match
  • NAME table IDs with platformID=1 can be removed
  • ttfautohint settings should be recorded in the NAME table ID 5
  • NAME table IDs 18 are not needed
  • The license text and URL in NAME table ID 13 and 14 should be
    <namerecord nameID="13" platformID="3" platEncID="1" langID="0x409">
      This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL
    </namerecord>
    <namerecord nameID="14" platformID="3" platEncID="1" langID="0x409">
      http://scripts.sil.org/OFL
    </namerecord>
  • In Medium, NAME table id 1s are often Eczar Me should be Eczar Medium
  • In SemiBold, NAME table id 1s are often Eczar Sb and ids 4 are often Eczar Semibold, should always be Eczar SemiBold
  • In SemiBold, NAME table id 6 and 17s are Eczar Semibold, should be Eczar-SemiBold
  • In SemiBold, filename is Eczar-Semibold.ttf could be Eczar-SemiBold.ttf, but git and mac os x file system case (in)sensitivity means leave it as is
  • In Bold, NAME table ID 2s are Regular should be Bold
  • In Bold, NAME table ID 17s exist but should not
  • In ExtraBold, NAME table id 1s are often is Eczar Eb should be Eczar ExtraBold
  • In ExtraBold, NAME table id 17s are often Eczar Extrabold should be Eczar ExtraBold
  • In ExtraBold, filename is Eczar-Extrabold.ttf should be Eczar-ExtraBold.ttf, but git and mac os x file system case (in)sensitivity means leave it as is
  • the vertical metrics are:
Parameter              Eczar-Bold.ttf    Eczar-Extrabold.ttf    Eczar-Medium.ttf    Eczar-Regular.ttf    Eczar-Semibold.ttf    
ymax                   1110              1143                   1046                1016                 1078                  
hhea.ascent            1100              1100                   1100                1100                 1100                  
OS/2.sTypoAscender     1000              1000                   1000                1000                 1000                  
OS/2.usWinAscent       1100              1100                   1100                1100                 1100                  
ymin                   -594              -634                   -513                -473                 -554                  
hhea.descent           -500              -500                   -500                -500                 -500                  
OS/2.sTypoDescender    -400              -400                   -400                -400                 -400                  
OS/2.usWinDescent      500               500                    500                 500                  500                   
hhea.lineGap           0                 0                      0                   0                    0                     
OS/2.sTypoLineGap      200               200                    200                 200                  200                   
hhea total             1600              1600                   1600                1600                 1600                  
typo total             1600              1600                   1600                1600                 1600                  
win total              1600              1600                   1600                1600                 1600                  
UPM:Heights            1000:1704         1000:1777              1000:1559           1000:1489            1000:1632             
UPM:Heights %          170 %             177 %                  155 %               148 %                163 %                 

High Glyphs
Eczar-Bold.ttf: uni09480930094D0902 uni0948 uni094C uni09480930094D uni094C0930094D0902 u094C0930094D uni0914 uni09480902
Eczar-Extrabold.ttf: uni09480930094D0902 uni0948 uni094C uni09480930094D uni094C0930094D0902 u094C0930094D uni0914 uni09480902

Low Glyphs
Eczar-Bold.ttf: uni0926094D092C0943 uni094D09300941 uni094D09300942 uni0926094D09350943
Eczar-Extrabold.ttf: uni0919094D09180930 uni0926094D092C0943 uni094D09300941 uni094D09300942 uni0957 uni0921094D091F uni0977 uni0926094D09350943 uni0921094D0922 uni0919094D09170930 uni0919094D0915094D0930
Eczar-Medium.ttf: uni0926094D092C0943 uni0926094D09350943
Eczar-Semibold.ttf: uni0926094D092C0943 uni094D09300941 uni094D09300942 uni0926094D09350943

They should be

Parameter              Eczar-Bold.ttf    Eczar-Extrabold.ttf    Eczar-Medium.ttf    Eczar-Regular.ttf    Eczar-Semibold.ttf    
ymax                   1110              1143                   1046                1016                 1078                  
hhea.ascent            1143              1143                   1143                1143                 1143                  
OS/2.sTypoAscender     1143              1143                   1143                1143                 1143                  
OS/2.usWinAscent       1143              1143                   1143                1143                 1143                  
ymin                   -594              -634                   -513                -473                 -554                  
hhea.descent           -634              -634                   -634                -634                 -634                  
OS/2.sTypoDescender    -634              -634                   -634                -634                 -634                  
OS/2.usWinDescent      634               634                    634                 634                  634                   
hhea.lineGap           0                 0                      0                   0                    0                     
OS/2.sTypoLineGap      0                 0                      0                   0                    0                     
hhea total             1777              1777                   1777                1777                 1777                  
typo total             1777              1777                   1777                1777                 1777                  
win total              1777              1777                   1777                1777                 1777                  
UPM:Heights            1000:1704         1000:1777              1000:1559           1000:1489            1000:1632             
UPM:Heights %          170 %             177 %                  155 %               148 %                163 %

Uppercase Greek letters with leftside diacritics: diacritics outside container, diappearance of diacritics and of whitespace

Hi,

I found a bug related to display of almost all of uppercase Greek letters with leftside diacritics.

There are several related issues concerning display of these letters.

  1. Leftside diacritics of uppercase Greek letters are displayed outside container if they stand on the left side of the HTML container such as

    element.

  2. CSS rule 'overflow-y: scroll' applied to container forces leftside diacritics of uppercase letters to diappear.

  3. Leftside diacritics of uppercase Greek letters forces the space between words to disappear. In simple case the CSS rule "text-rendering: optimizelegibility" can solve this issue, but this rule does not help in other simple cases.

  4. Simple case when CSS rule "text-rendering: optimizelegibility" cannot solve diasappearance of whitespace is wrapping the word with tags.

Testcase HTML page attached (change the file extension).

Eczar is most beautiful and most readable font supporrting Greek extended char range. But unfortunately this issue makes it essentially unusable for Greek.

Thank you four your amazing achievement. Your work is really appreciated.

testcase.txt

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.