-
Notifications
You must be signed in to change notification settings - Fork 0
/
feed.rss
3070 lines (2378 loc) · 381 KB
/
feed.rss
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
<id>tag:old.rosettatype.com,2005:/feed</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com"/>
<link rel="self" type="application/atom+xml" href="https://old.rosettatype.com/feed"/>
<title>ROSETTA TYPE BLOG</title>
<updated>2014-07-24T00:00:00+02:00</updated>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2021/01/11/Ten-years-of-Rosetta</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2021/01/11/Ten-years-of-Rosetta"/>
<title>Ten years of Rosetta</title>
<content type="html"><style>
h4 {
margin: 2em 0 17px 0;
}
.simpletable {
width: 940px;
border: 0;
padding: 0;
margin: 1em 0;
border-collapse: collapse;
border: 1px solid black;
}
.simpletable td, .simpletable th {
border: 0;
margin: 0;
padding: 0.75em;
text-align: left;
vertical-align: top;
font-size: 14px;
}
.simpletable th {
margin: 0;
font-weight: bold;
background: #000;
color: #fff;
}
.simpletable tr:nth-child(even) {
background-color: #eee;
}
</style>
<p>It has been ten years since we launched the first Rosetta website on 11 January 2011 at 11:11 CET and started making it our business selling fonts for multiple scripts of the world. This anniversary prompted a reminiscence of our past efforts, so here’s a personal look back at what those ten years brought to our corner of the industry.</p>
<p><div class='image'><img src='/blog/assets/2021-Ten-years-of-Rosetta/2021-Ten-years-of-Rosetta_old-webite_big.png' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> This is how the original Rosetta website looked like. Snapshot from 30 June 2012. We were excited about the new possibilities of non-system webfonts. Reproduced here for readers’ amusement.</div></div></p>
<h4>(The motivation)</h4>
<p>The market for digital fonts was quite different ten years ago and we did not have any certainty whether our new venture was going to pan out. We simply felt that more fonts for more scripts ought to be made, and that they should be made well.</p>
<p>Every Czech designer understands the need for high-quality diacritics in fonts. They know first-hand that many of the hip and renowned Western foundries do a poor job when it comes to accents, and that a strong brand is not a guarantee of quality across the full range of languages they claim to support. We extrapolated from this experience and committed to quality in every script we would tackle.</p>
<h4>(The inspiration)</h4>
<p>Obviously, we were not the first to focus on language and script support that goes beyond European languages. Besides vernacular foundries typically providing fonts for a single script, some were providing Cyrillic-Greek-Latin (LCG or pan-European or PE) or Chinese-Japanese-Korean (CJK) support.</p>
<p>While we could not compare to the big players like Adobe, Morisawa, or Monotype,* there were a few smaller foundries that diversified towards multiple scripts. Some of them became an inspiration and indication of what could be achieved. Russian Paratype had been offering fonts for languages and scripts of the former Soviet republics for some time. Then there was the rigorous Canadian duo Tiro Typeworks, with whom I collaborated on two projects before Rosetta. Slovak-Dutch Typotheque had already tapped into designing for Arabic, Cyrillic, and Greek and their Peter Biľak had just founded the new Indian Type Foundry together with Satya Rajpurohit. London-based Dalton Maag started speed-growing from a relatively small studio into a mid-sized company while developing custom multi-script projects for global clients such as Nokia, Intel, and others.</p>
<h4>(The model)</h4>
<p>There has been a lot of talent coming out of type design programmes in the past few years. Many of these designers have enthusiastically embraced working in various world scripts, including those unfamiliar to them when they started studying. I thought that a platform where such projects could be released without the pressures of vicious commercial deadlines would allow people to develop knowledge, expertise, and eventually confidence to design for scripts of their choosing rather than only those they were born into. At the same time, this could also help solve the apparent lack of quality fonts for typographically less-represented scripts by expanding relevant knowledge in the type design community. In turn, it would also benefit readers.</p>
<p>The business model was similar to other font publishers. Our collaborators would work on their own time and we would pay them shares from future sales of their fonts through our e-shop. And importantly, the designers would retain ownership of their designs. We would help manage the design progress – by providing art direction, quality control, production, post-production, legal support, marketing, library maintenance, promotion, and customer service – to free our collaborators to focus on design.</p>
<p>This plan turned into Rosetta.</p>
<p>Every now and then we hear how multilingual communication is a novel thing, or that multi-cultural societies are the new challenge. We chose the name Rosetta, in reference to the famous Rosetta Stone, to remind people that multi-script documents have been with us for millennia. We’re just helping the newcomer, digital typography, play catch up.</p>
<p>I did not want to do this alone, so I teamed up with Veronika Burian and José Scaglione of Type Together because of their experience running a successful independent type foundry. And although this collaboration lasted only two years, their initial wisdom and guidance were a great help in the early days.</p>
<h4>(The ignorance)</h4>
<p>Developing design knowledge about the visual system of a particular world script takes time. Familiarity or the ability to read the script give one only so much head start and by itself are not a guarantee of quality. We believe that with patience and commitment, one can learn to read or design for any script.</p>
<p>But how do we, as a foundry, guarantee quality in all the scripts we want to design for? We acknowledged our limits and worked with consultants such as Fiona Ross, Irene Vlachou, Maria Doreuli, or Meir Sadan (to name a few) in cases where the designer was less experienced in their project’s script. Beta testers and informal reviewers have been a great help too.</p>
<p><div class='image'><img src='/blog/assets/2021-Ten-years-of-Rosetta/2021-Ten-years-of-Rosetta_people2_big.jpg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> People looking at pictures of things</div></div></p>
<h4>(The job of a designer)</h4>
<p>Working on a retail typeface takes months. It means choosing the harder way over a steady paid job, possibly working late nights and weekends to squeeze the passion project around a daily job that pays the bills. Developing a multi-script typeface takes even more time. The challenges of one script multiply when they meet those of the other script. When designing for a previously unfamiliar script, one also faces uncertainties every step of the way.</p>
<p>Type designers face all of these challenges with unclear prospects in an unpredictable market driven by fashion. Every single designer who has released with us deserves applause here for their skills and for their commitment. </p>
<p>Sadly, for every two projects that get released, there is one that doesn’t make it. There are moments when a foundry has to cut ties on projects that stop moving ahead, whatever the reason. But there are also times when we have to acknowledge our own limits; every now and then, I still have mild coding nightmares about the Burmese medial forms.</p>
<h4>(The start)</h4>
<p>When we launched, there were two type families in our library: Skolar and Aisha. By the end of the year, there were five, and they were supporting five scripts. Each of these early releases tells a different story about multi-scriptuality.</p>
<p>I started Skolar during my MA at the University of Reading as a Latin-script typeface, but developed it anticipating stylistic requirements of other scripts, particularly Indian ones. In 2009, Skolar Latin was released with Type Together. By the time Rosetta published it in 2011, it supported Cyrillic and Greek, but the Indian scripts were to come year later.</p>
<p>In contrast to Skolar’s origin, Titus Nemeth’s Aisha started as a revival of a Maghrebi Arabic fount. The Latin was developed afterwards.</p>
<p>The next release was Nassim, also designed by Titus during his MA at Reading. It was also designed as Arabic first, and Latin second. Thanks to the BBC selecting it for their Arabic and Persian news services online, Nassim has been served to over 10 million readers monthly for the past ten years, and it helped improve the quality of Arabic web typography immensely. Note that when all this started, it was still the relatively early days of both webfonts and the BBC Online. We never counted, but Nassim must have been among the most used non-system webfonts at the time. Its illegal copies are now serving many users in Iran and they have been used by local news there to replicate the look of the BBC Persian website. Needless to say, we cannot easily/legally sell the fonts in Iran due to international embargoes, so Iranian users have had to get their hands on Nassim in other ways. It’s a good typeface, so can we really blame them?</p>
<p>Neacademia by Sergei Egorov ended up in our library by mere coincidence. I was asking Sergei, a graduate of the Moscow Institute of Physics and Technology living in the USA, for high-resolution images of one of his mathematical experiments with Aldine italics. With his response, he dropped me a line humbly offering his pet project. Released slowly over the years, Neacademia has become one of the most comprehensive revivals of the Aldine types: the Latin is the true revival, while the added Cyrillic comes from an alternative universe where Aldus Manutius printed in Russian.</p>
<p>The last release of 2011 was Sutturah by Octavio Pardo. It shows the challenges achieving equal illegibility across scripts. Awesomely intricate, admired by many, used by few. Some projects are released because you simply have to get them out there, not because they pay off.</p>
<p>Looking back, the first year looks like one crazy release frenzy. Eventually, we had to slow down and make tough decisions between pace, multitude, and quality. And although behind each project there’s a lot to talk about, there is no space to indulge in a lengthy discussion of each. Here is a table at least.</p>
<table class="simpletable">
<tr><th>Release date</th><th>Type family</th><th>Author(s)</th><th>Script(s)</th></tr>
<tr><td>2011–2016</td><td>Aisha Arabic</td><td>Titus Nemeth</td><td>Arabic</td></tr>
<tr><td>2011–2016</td><td>Aisha Latin</td><td>Titus Nemeth</td><td>Latin</td></tr>
<tr><td>2011</td><td>Skolar PE</td><td>David Březina</td><td>Cyrillic, Greek,, Latin</td></tr>
<tr><td>2011</td><td>Nassim Arabic</td><td>Titus Nemeth</td><td>Arabic</td></tr>
<tr><td>2011</td><td>Nassim Latin</td><td>Titus Nemeth</td><td>Latin</td></tr>
<tr><td>2011–2016</td><td>Neacademia</td><td>Sergei Egorov</td><td>Cyrillic, Latin</td></tr>
<tr><td>2011</td><td>Sutturah</td><td>Octavio Pardo</td><td>Cyrillic, Latin</td></tr>
<tr><td>2012</td><td>Skolar Devanagari</td><td>Vaibhav Singh</td><td>Devanagari</td></tr>
<tr><td>2012</td><td>Skolar Gujarati</td><td>David Březina</td><td>Gujarati</td></tr>
<tr><td>2012</td><td>Arek Armenian</td><td>Khajag Apelian</td><td>Armenian</td></tr>
<tr><td>2012</td><td>Arek Latin</td><td>Khajag Apelian</td><td>Latin</td></tr>
<tr><td>2013</td><td>Eskorte Arabic</td><td>Elena Scheider</td><td>Arabic</td></tr>
<tr><td>2013</td><td>Eskorte Latin</td><td>Elena Scheider</td><td>Latin</td></tr>
<tr><td>2014–2016</td><td>Skolar Sans PE</td><td>David Březina, Sláva Jevčinová, and Rafael Saraiva</td><td>Cyrillic, Greek, Latin</td></tr>
<tr><td>2015</td><td>Clone Rounded PE</td><td>Lasko Dzurovski</td><td>Cyrillic, Greek, Latin</td></tr>
<tr><td>2016</td><td>Gitan Latin</td><td>Florian Runge</td><td>Latin</td></tr>
<tr><td>2016</td><td>Skolar Sans Arabic</td><td>Titus Nemeth</td><td>Arabic</td></tr>
<tr><td>2016</td><td>Yrsa & Rasa</td><td>Anna Giedryś and David Březina (open-source)</td><td>Latin</td></tr>
<tr><td>2016</td><td>Eczar</td><td>Vaibhav Singh (open-source)</td><td>Devanagari, Latin</td></tr>
<tr><td>2017</td><td>Avory PE</td><td>Sláva Jevčinová</td><td>Cyrillic, Greek, Latin</td></tr>
<tr><td>2017</td><td>Corsair PE</td><td>Ksenya Samarskaya and associates</td><td>Cyrillic, Greek, Latin</td></tr>
<tr><td>2018</td><td>Marlik</td><td>Borna Izadpanah</td><td>Arabic</td></tr>
<tr><td>2018–2020</td><td>Handjet (open-source)</td><td>David Březina</td><td>Arabic, Armenian, Cyrillic, Greek, Hebrew, Latin</td></tr>
<tr><td>2019</td><td>Adapter PE</td><td>William Montrose, Sláva Jevčinová, David Březina</td><td>Cyrillic, Greek, Latin</td></tr>
<tr><td>2019</td><td>Adelphi PE</td><td>Nick Job</td><td>Cyrillic, Greek, Latin</td></tr>
<tr><td>2019</td><td>Adapter Hebrew</td><td>Sláva Jevčinová</td><td>Hebrew</td></tr>
<tr><td>2020</td><td>Adapter Arabic</td><td>Borna Izadpanah</td><td>Arabic</td></tr>
<tr><td>2020</td><td>Gridlite PE</td><td>David Březina</td><td>Cyrillic, Greek, Latin</td></tr>
</table>
<h4>(The production)</h4>
<p>The production job, i.e. making fonts actually work, has changed dramatically. Ten years ago, OpenType support for Indian and South-East Asian scripts was not mature in many applications. Adobe did not yet have any Indian fonts in their library, and their pre-Cloud Creative Suite came with less reliable support. The main font editor back then, FontLab 4, could only be tricked into supporting the right-to-left kerning required for Arabic. It was also unable to compile the more advanced OpenType feature code required for Indian scripts; one had to use other tools, such as MS VOLT or the latest Adobe Font Development Kit for OpenType (AFDKO), which had just introduced this option. We chose AFDKO and thanks to people like Miguel Sousa and Paul Hunt, both working for Adobe, we developed our first custom production tools. Finally, we could compile fonts for Arabic and Indian scripts on a Mac! It took months to figure things out.</p>
<p>The new font editors (Glyphs and Robofont) were just around the corner. Over time, they have picked up a few tricks and they now support and often automate the OpenType features required. And thanks to Google Fonts, many of those feature layouts are now open-sourced and widely available as examples to follow. Things are being documented way better, too.</p>
<p>However, the most significant change has been the development and adoption of HarfBuzz, an open-source rendering engine that supports a majority of the world scripts. Started by Behdad Esfahbod, HarfBuzz brought unprecedented script support to browsers and operating systems. The open-source world thus leapt ahead of proprietary solutions by Adobe and Microsoft. (The story of Apple’s solutions would take longer to unpack.)</p>
<p>All of this is to say that developing Arabic and Indian scripts in the past ten years has been exciting, but also difficult and ever-changing, and thankfully it is much easier now. The amount of support we needed to provide meant that it would not have been possible to start Rosetta in London or New York and maintain the same quality standards. The financial pressures would have been too high for a mostly retail-based venture. Luckily, living expenses in Czechia were low and allowed us the freedom of idealists.</p>
<p><div class='image'><img src='/blog/assets/2021-Ten-years-of-Rosetta/2021-Ten-years-of-Rosetta_people1_big.jpg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> We organized two meetups over the years Rosetta Camp in South Moravia (2012, top left photo) and Rosetta Cruise in Croatia (2013, bottom right photo). Several colleagues from other foundries joined us for the latter.</div></div></p>
<h4>(The grand total)</h4>
<p>It is hard to say how many people work at Rosetta today. We do not function like a typical company for numerous reasons. At the core is me (management, type design) and Anna Giedryś (type design, marketing), with our part-time font engineer Johannes Neumeier. There are our frequent collaborators, often working on custom or in-house projects; the following worked on multiple projects with us in the past: Borna Izadpanah, Sláva Jevčinová, Ben Mitchell, William Montrose, Titus Nemeth, Florian Runge, and Vaibhav Singh. And there are further seven designers who released their fonts with us.</p>
<p>Since launching, we’ve worked with 40–50 esteemed colleagues including collaborating designers, consultants, studio managers, font engineers, interns, and others. Thank you all for helping Rosetta to make it this far!</p>
<p><div class='image'><img src='/blog/assets/2021-Ten-years-of-Rosetta/2021-Ten-years-of-Rosetta_people3_big.jpg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Some of the people that contributed to the success of Rosetta over the years, in no particular order (top to bottom, left to right): Nick Job, Florian Runge, Lasko Dzurovski, Khajag Apelian, Fiona Ross, Mathieu Réguer, Ross Mills, Sláva Jevčinová, Johannes Neumeier, David Březina, Elena Schneider, Ben Mitchell, Maria Doreuli, Filip Dědic, William Montrose, Borna Izadpanah, Anna Giedryś, Titus Nemeth, Irene Vlachou, Kamil Kurzajewski, Sasikarn Vongin, Vaibhav Singh, Ksenya Samarskaya, Sergei Egorov, Octavio Pardo, Maxim Zhukov, Meir Sadan, and Viktoriya Grabowska-Gadomska.</div></div></p>
<p>Over the past ten years, we have released 28 type families supporting 8 scripts and over 440 languages in total. Three of the type families are open-sourced. And a few custom projects. Although the retail fonts differ in their degree of commercial success, nearly every release has been recognized by one or more design awards or featured in influential favourites lists. Not to mention all the love given by our amazing customers!</p>
<p>All these successes give only part of the picture, as we’ve also fallen short many times and in many ways. One shortcoming bothers me the most: we aimed to build knowledge, but we failed to share it. I was always “too busy”. Besides our open-source fonts, conference talks, and two TypeTalks conferences we organized, we only managed to publish a handful of blog posts about multi-script typography. In the past year, we have been working hard to change that. Last year, we managed to release the Universal Specimen which now allows everyone to test their own fonts in 333 languages of the world simultaneously. And we are almost ready to show you what else we’ve been working on. I can’t tell you what they are yet, but to build suspense I’ll leave you with a cliffhanger by sharing their names: Hyperglot and Design Regression.</p>
<p>In large part thanks to Johannes, we have also updated most of our library to include variable fonts and we will roll them out in the following months together with new PDF specimens. And if I find the time, there will also be limited-edition posters… and more fonts!</p>
<h4>(The new competition)</h4>
<p>Today in the type design community, in addition to those already mentioned, we have amazing competition in Mota Italic, Black Foundry, Ek Type, Fontpad, Typotheque Arabic, Typeland, Bold Monday, Commercial Type, and the up-and-coming Universal Thirst, each with their own take on designing for multiple scripts. And there’s also many other exciting foundries focused on individual scripts. All this activity is thrilling but also enough to give even experienced practitioners some degree of stage fright! But whenever I panic and question whether we still have something to contribute, I try to remember that more fonts for more scripts ought to be made, and I believe that this is a task best tackled by many.</p>
<p>—</p>
<p>* Note that Google Fonts and their open-source efforts were yet to come and change the game of scripts dramatically.</p>
<p>—</p>
<p><em>Edited by Andrea Churchill Wong.</em></p></content>
<updated>2021-01-11T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2020/04/28/14-tips-for-ruling-the-work-from-home-game</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2020/04/28/14-tips-for-ruling-the-work-from-home-game"/>
<title>14 tips for ruling the work-from-home game</title>
<content type="html"><p>Contrary to popular beliefs about productivity, it is ok to mix your work and personal lives. They are your lives, after all! Mixing things up can help you achieve unexpected efficiency and a deepened sense of fulfillment. Independent type designers are masters of this discipline. Here are some ground rules from the best. </p>
<ol>
<li>Work a bit before breakfast. That will make the rest of the workday shorter.</li>
<li>Mornings are not for catching up on new episodes of the latest mystery thriller. Studies by Czech researchers show a 32% higher chance of binge watching if you turn Netflix on in the morning.</li>
<li>Work in pyjamas (or naked!) for as long as you can. It makes for better blood flow, which is good for all kinds of mental processes.</li>
<li>If you are emphatically against pyjamas, invest in some comfortable loungewear. Whatever you do, say no to smart casual!</li>
<li>Avoid socks at all costs. Slippers are okay. The fluffier the better.</li>
<li>There is definitely no need for a suit. Unless you are having a conference call with a client. In that case, it is sufficient to wear only the top bits – and shorts. Do <em>not</em> stand up during a call. That’s why office chairs have wheels.</li>
<li>Be creative with your working places and positions. You can work virtually anywhere! Use your kitchen desk, use your sofa, sit on the floor, lie on the floor. It is better than any of the fancy startup offices and it is only yours. You can also work on a bed with the computer on the floor. Thoroughly tested.</li>
<li>Go out for lunch. Make the mid-day break longer. Enjoy the outside. It is ok to work outside too, btw. it is ok to work when you have just finished lunch and there is a small beer next to your laptop. Post a picture on social media to make the office workers’ lives miserable.</li>
<li>Work out when everyone else is working. The gym will still have some fresh air, and the swimming pool will be emptier and cleaner. Worst case, it might be packed with retired people, but they are usually easy to lunge past or swim around (though beware, some of them might present surprisingly fierce competition). Post all your achievements online. Collegial envy is the new love.</li>
<li>Complain about your commute. Why not!</li>
<li>Remember to go outside. But if you do not, it is ok too. Just play some music and it will do. Human contact is overrated.</li>
<li>You probably do not want to work full eight hours. No one does.</li>
<li>Make use of the post-napping guilt. If you’re tired, take a nap. The guilt you feel afterwards will fuel your most productive hours yet, and you’ll catch up on lost working minutes in no time.</li>
<li>Make use of your bedtime. It is ideal for catching up on emails, tweets and the like. The trick is simple: if you read something upsetting, go to sleep! Immediately. No replies. Chances are, someone else will get upset instead of you. Or you will forget. Either way, you’ll have started a new day before it can get to you.</li>
</ol>
<p>This article was written around midnight when everyone else was asleep. As a result there was more time for a slow breakfast with pancakes, forest fruits, and maple syrup, sprinkled with chia seeds for a healthy kick.</p>
<p>—</p>
<p><em>Edited by Andrea Churchill Wong.</em></p>
</content>
<updated>2020-04-28T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2020/03/11/Adapter-World-programme</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2020/03/11/Adapter-World-programme"/>
<title>Adapter™ World design programme</title>
<content type="html"><p>Adapter™ World is a design programme involving an international team of designers and consultants who work with Rosetta type foundry to provide a modern, coherent, and reliable design for a wide range of the world’s languages.</p>
<p><a href="https://rosettatype.com/Adapter">Adapter</a> follows a number of successful multi-script font releases including <a href="https://www.rosettatype.com/Skolar">Skolar™</a>, <a href="https://www.rosettatype.com/SkolarSans">Skolar Sans</a>, and <a href="https://www.rosettatype.com/Nassim">Nassim</a> and collaborations with global clients such as the <a href="https://www.rosettatype.com/custom-fonts/BBC-Nassim">BBC</a>, <a href="https://www.rosettatype.com/custom-fonts/LG-WebOS">LG</a>, and <a href="https://www.rosettatype.com/custom-fonts/Yrsa-Rasa">Google</a>. Adapter already supports languages using Latin, Cyrillic, Hebrew, and Greek scripts. Adapter’s language skills keep on growing with the new Arabic script extension released today. This will amount to over 330 languages used by approximately 3.54 billion speakers* around the globe. Rosetta’s long-term goal is to extend Adapter to support languages of Africa, Georgia, Armenia, Thailand, as well as the many Indian languages.</p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_1_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_2_big.svg' title='' width='940'></div></p>
<p>Providing typefaces that are visually harmonized across diverse language contexts is no small feat as different languages and cultural environments pose many design challenges. For example, the aesthetics of the Latin script may not easily be translated to Arabic or Hebrew environments. This is a challenge that lies far beyond the abilities of an individual designer. Thus, Rosetta always works collaboratively, employing specialized consultants. The goal is to deliver fonts that are both visually pleasing and culturally valid. The quality of Adapter Cyrillic has already been recognized in the respected <a href="https://moderncyrillic.org/en/">Modern Cyrillic 2019</a> competition.</p>
<p>Adapter’s type system can be adjusted freely across three dimensions to modify weight, italic slant, and optical size between text and display variants. Adapter Text delivers a good reading experience even in low-resolution and small type sizes thanks to generous spacing, overall openness, and slightly squarish counters. Adapter Display is tightly spaced for a striking impact in headlines across a wider range of weight styles, from thin to black.</p>
<p>Utilizing the new OpenType Variable font technology, Rosetta managed to pack all of this potential into a single font with a tiny data footprint. Dramatically increased stylistic and linguistic options with little extra file size mean that websites and apps can easily provide fast service to a larger number of customers reading in a range of the world’s languages.</p>
<p><br><a class="solidButton red" style="font-weight:normal;font-size: 16px;" href="https://rosettatype.com/Adapter">
<span class="ico page"></span><span class="innerText">See Adapter microsite</span></a></p>
<p><a class="solidButton black" style="font-weight:normal;font-size: 16px;" href="https://rosettatypefoundry.cmail19.com/t/r-i-jhikiyz-l-i/">
<span class="ico bag"></span><span class="innerText">Get free trial fonts</span></a></p>
<p><a class="solidButton black" style="font-weight:normal;font-size: 16px;" href="https://rosettatype.com/merchandise#merch-21">
<span class="ico bag"></span><span class="innerText">Order Adapter poster</span></a><br><br></p>
<p>(*) This estimate is based on a sum of the native speakers of the languages.</p>
<p>P.S. If you want to know more about the details of Adapter design, find us on <a href="https://twitter.com/rosettatype">Twitter</a> or <a href="https://www.instagram.com/rosettatypefoundry/">Instagram</a> where we have already posted numerous previews. You can also read our previous post about <a href="https://www.rosettatype.com/blog/2019/05/21/The-making-of-Adapter">the making of Adapter</a></p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_3_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_4_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_5_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_6_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2020-Adapter-World-design-programme/Adapter-World-design-programme_7_big.svg' title='' width='940'></div></p></content>
<updated>2020-03-11T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2019/05/21/The-making-of-Adapter</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2019/05/21/The-making-of-Adapter"/>
<title>The making of Adapter</title>
<content type="html"><p>For many years now, we have felt a gap in our library. The missing piece was a simple, no-frills sans serif that would appeal to contemporary modernist and post-modernist aesthetics. A straightforward, universal typeface easy to use for a wide range of design genres. We set out to develop this missing piece about three years ago in a pub in London’s Bloomsbury and today we release it to the world hoping it will serve you well. Below are a few notes about our thoughts and the process.</p>
<p><div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_1_big.svg' title='' width='940'></div></p>
<h1>Neutralizer</h1>
<p>As we were working on the concept, we realized we needed to decide on a language to describe our design direction. The typeface we had in mind could be categorized as a neo-grotesque, but such a classification merely describes appearance. We were more interested in describing the ideas and motivations behind the design and linking them with a particular style and utility.</p>
<p>At first, “neutral sans-serifs” seemed to be the term we were looking for. It often refers to typefaces that are supposed to show as little personality of their designers as possible. This is usually presented as a modernist attempt to focus on the function and the content of a message that is being typeset. However, neutrality in design in general is a questionable construct. And <a href="https://2x4.org/ideas/2009/fuck-content/">many</a> <a href="https://articles.c-a-s-t.com/lussu-file-2-wines-and-goblets-2ac327e8f416">have</a> <a href="https://practicaltypography.com/drowning-the-crystal-goblet.html">argued</a> that before us. For better or worse, designers are always contributing to the message readers ultimately perceive. A choice of colour, font, illustration, or layout – they all have their meaning. In this way, typographers and typeface designers are always co-authors of the message. The presence of the designers’ opinions is inescapable and it would be pretentious to say and act otherwise. It would be a disservice to typeface design and its contribution to society if we subscribed to this notion of neutrality.</p>
<h1>Universalizer</h1>
<p>Keith Tam, a colleague from the University of Reading, once told me that instead of “neutral”, he prefers the term “universal”. Although still somewhat vague, the term better indicates how it might be possible to pragmatically judge whether a typeface lives up to it. In my mind, a universal typeface is suited for as wide a range of messages as possible. And, importantly, it does not need to be voiceless! It just needs to be suitable.</p>
<p>Although a truly universal typeface in this sense is clearly an impossibility, the more pragmatic perspective helped orient our design direction. It also helped us realize that even though the neo-grotesques (Helvetica, Neue Hass Grotesque, Arial, and others) seem to form a single, coherent category of typefaces when judged by their appearance, they are frequently used in two very different ways.</p>
<p>Neo-grotesques are an unobtrusive, basic, or even default choice when used for continuous texts. Yet, they can also be selected intentionally to make a strong stylistic statement suggesting minimalism or unaesthetics when used in posters, magazines, or book covers. These differences become obvious when looking at post-modern design, from unrestrained art books to down-to-earth navigation systems.</p>
<p>Typeface publishers sometimes claim to have achieved both good readability in small sizes and interesting appearance in big sizes, but the challenge is more complex. We found it is nearly impossible to have a single sans-serif font that satisfies both requirements equally well. Text sizes require stronger articulation of features which tends to look out of place in larger sizes. On the other hand, display sizes favour finer details and spatial economy which would inconvenience readers when used for continuous text. Not one, but two or more typefaces might be needed.</p>
<h1>Adapter!</h1>
<p>Thus, we set out to design two variants of the same sans-serif: Adapter Text and Adapter Display. To maintain the distinction between the two objectives, both functionally as well as stylistically, we thought of the two Adapters as being designed by two different designers. The Text designer was a typographer who focused on the ergonomics of reading, thus the rhythm and clarity of forms were his utmost concern. He would acknowledge the influence of production technology and shape the characters to comply with it. The Display designer, on the other hand, was a graphic designer or an architect with a sweet spot for smooth curves, symmetries, and alignments. She would not be eccentric, but would want to demonstrate her appreciation for form and introduce some statement details here and there while keeping an economy of expression.</p>
<p><div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_3_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Adapter Text</div></div></p>
<p>As a result, Adapter Text has more squarish, solid forms that don’t easily get distorted by the pixel grid or the raster of printers and presses. Apertures are open and junctions are pinched in order to better articulate these features. You might notice some ink traps in action, too. The vertical proportions are generous to allow for distinct ascenders and descenders and well-differentiated diacritical marks. The inter-letter spacing and kerning were set with a preference for even rhythm. Compare Adapter Text to Helvetica and Arial and you might think it’s a bit loose, but once you start reading you will notice how much more comfortable it is and how cramped Helvetica and Arial seem. The weights of Adapter Text range from Extralight to Extrabold, but not further, as weights beyond this range would simply look sub-par in text sizes. Thin would disappear. Black would be too dark and have uneven counters.</p>
<p><div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_2_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Adapter Display</div></div></p>
<p><div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_4_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Adapter Text and Display</div></div></p>
<p>Adapter Display has rounder and narrower forms. Unlike in the Text, most of the terminals are aligned horizontally, which turns the aperture shapes into cleanly defined cut-outs. The curves flow smoothly, the corners are sharp; the letters “a, y, R” and their relatives in Cyrillic and Greek speak for themselves. The overall appearance is more condensed and the vertical proportions are a tiny bit more compact too. The spacing strategy is different from that of the Text, too. The letters are closer together as the focus was on keeping the inter-letter spaces small and equal. The spaces within the letters (the counters) become bigger than the inter-letter spaces which results in a less even rhythm, but a greater economy. The weights stretch across a wider spectrum, from Thin to Black.</p>
<p>Our goal was to design a no-nonsense type system that is easy to use, with the defaults just right. There is nothing you could do without: no ligatures, no small caps, and no old-style figures. A handful of alternates made it in for the sake of DIN 1450 compliance, which should make our wayfinding colleagues happy. This includes the seriffed “I”, the hooked “l”, and the slashed zero. Otherwise, Adapter’s only indulgence is a single-storey alternate of the letter “a”, which makes the typeface soft and fluffy, and an alternative “J” for better spacing in all-caps settings.</p>
<p>As with most of our fonts, with Adapter we provide wide-ranging and well-considered language support for over 160 languages using Latin, Cyrillic, and Greek scripts. And we have already started exploring similar ideas in the contexts of Arabic and Hebrew and their contemporary aesthetics. We hope to release equally interesting fonts for these scripts later this year.</p>
<p><div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_5_big.svg' title='' width='940'></div>
<div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_6_big.svg' title='' width='940'></div>
<div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_7_big.svg' title='' width='940'></div>
<div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_8_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Adapter supports over 160 languages using Latin, Cyrillic, and Greek scripts</div></div></p>
<h1>Variable Adapter</h1>
<p>It would be an opportunity missed if we thought about a universal system that adapts to all kinds of environments, and did not manage to make it into a variable font.</p>
<p>Variable fonts are useful in two major ways. First of all, they allow users to customize the font’s appearance using design parameters that are typically represented by axes or sliders. Each of these corresponds to a continuous change in the design. For example, instead of choosing from a pre-set collection of weights, in Adapter Display, a user can pick any weight on the scale from Thin to Black. If the predefined Semibold weight is too light for their design, they can simply move a slider and get a darker weight.</p>
<p>We did not stop at weight only. In fact, we packed all of the variants and styles into a single font! You can move seamlessly between the Text and Display, adjusting the design to a specific size or to your taste, or change the slant from upright to a 10-degree angle. The italic letters have the same width as the corresponding upright letters. This is super useful as the text will not reflow when you set a word in italics or when you decide to change the italic angle late in your design process.</p>
<p>The second advantage of variable fonts is their small file size. This is particularly useful on the web. The variable version of Adapter contains text and display variants, its full range of weights, and italics. And yet, the result is a single webfont with a lightweight 334 KB footprint that supports over 160 languages using the Latin, Cyrillic, and Greek scripts. It shrinks to a dainty 230 KB when supporting only the Latin-script languages. When trying to cover the same stylistic and linguistic scope with single-style fonts, it would be 2400 KB (for the three scripts) or 1600 KB (for Latin). See the chart below.</p>
<p><div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_9_big.svg' title='' width='940'></div>
<div class='image'><img src='/blog/assets/2019-The-making-of-Adapter/The-making-of-Adapter_images_10_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Adapter Variable provides the stylistic potential of Adapter Text and Display with a significantly smaller file size</div></div></p>
<p>—</p>
<p>Adapter is the brainchild of William Montrose and David Březina. William created the shapes, and David developed the concept. William worked on the drawings with our frequent collaborator Sláva Jevčinová. Once he set up the basic Latin, Sláva took over, refined the shapes and expanded Adapter to its current scope. She also designed the Cyrillic and Greek with consultants Maria Doreuli and Irene Vlachou. Kerning was done by Jitka Janečková. Production by Johannes Neumeier and David. And finally, big thanks to Anna Giedryś for making Adapter presentable and to Andrea Churchill Wong for making all of the texts about Adapter clearer. All these people played a part in releasing Adapter into the world. We hope you will like it! Download the free trial fonts and take it for a spin.</p>
<p><br><a class="solidButton red" style="font-weight:normal;font-size: 16px;" href="https://rosettatype.com/Adapter">
<span class="ico page"></span><span class="innerText">See Adapter microsite</span></a></p>
<p><a class="solidButton black" style="font-weight:normal;font-size: 16px;" href="https://rosettatype.com/merchandise#merch-21">
<span class="ico bag"></span><span class="innerText">Order Adapter poster</span></a><br><br></p>
<p>P.S. If you want to know more about the details of Adapter design, find us on <a href="https://twitter.com/rosettatype">Twitter</a> or <a href="https://www.instagram.com/rosettatypefoundry/">Instagram</a> where we have already posted numerous sneak peeks.</p></content>
<updated>2019-05-21T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2018/07/20/Rosetta-Loft</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2018/07/20/Rosetta-Loft"/>
<title>Rosetta Loft</title>
<content type="html"><p>We’ve moved into a shiny new workspace, and you’re invited to join us!</p>
<p>After a couple of years of nomadic, office-less life, we have decided to settle again. However, we didn’t want to set up a studio just for ourselves. We wanted a space we could share. A space where our collaborators and friends could visit us, and where we could work on projects together – but also a space into which we could invite type-friendly local designers and students to attend workshops and release parties.</p>
<p>So, for the past two months Anna has been busy kitting out the new Rosetta Loft. It’s located in the centre of beautiful Brno, a city known for its modern architecture, biennial of graphic design, controversial statues, and too many cafés per capita. One third of the Loft is dedicated to the Rosetta HQ. Another third is for other designers: there is a small co-working space, and a couple of available offices. The remaining third is a common area for workshopping, hanging out, and of course having parties. We have two balconies with great views, a small typographic library, and way too many bathrooms.</p>
<p><div class='image'><img src='/blog/assets/2018-Rosetta-Loft/Rosetta-Loft_07.jpg' title='' width='610'></div></p>
<p>Interested in joining us? We are currently renting desk and office space. If you’re looking for a new work environment, get in touch and come over for coffee or tea and a tour.</p>
<p>Even if you’re based elsewhere, we might have something for you. We are reserving desk space in our studio to offer free for up to one month to visiting designers we know personally. Come visit us to focus on a project or get a new perspective on your work. Send us an email to enquire about availability.</p>
<p>We are already planning some events and a type design residency programme for recent graduates. Stay tuned to our social networks for more information.</p>
<p><em>For enquiries, contact Anna Giedryś at <a href="mailto:anna@rosettatype.com">anna@rosettatype.com</a>.</em></p>
<p><div class='image'><img src='/blog/assets/2018-Rosetta-Loft/Rosetta-Loft_01.jpg' title='' width='610'></div>
<div class='image'><img src='/blog/assets/2018-Rosetta-Loft/Rosetta-Loft_06.jpg' title='' width='610'></div>
<div class='image'><img src='/blog/assets/2018-Rosetta-Loft/Rosetta-Loft_02.jpg' title='' width='610'></div>
<div class='image'><img src='/blog/assets/2018-Rosetta-Loft/Rosetta-Loft_04.jpg' title='' width='610'></div>
<div class='image'><img src='/blog/assets/2018-Rosetta-Loft/Rosetta-Loft_08.jpg' title='' width='610'></div></p></content>
<updated>2018-07-20T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2017/05/22/Jaroslav-Benda</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2017/05/22/Jaroslav-Benda"/>
<title>Jaroslav Benda: nouveau, cubiste, moderne</title>
<content type="html"><p><em>To accompany our upcoming release, Avory by Sláva Jevčinová, we asked art historian Lucie Urbánková to write a brief introduction about Jaroslav Benda whose typographic work served as a starting point for the creation of the typeface. The internationally lesser known Czech designer-explorer was born in the Austrian-Hungarian Empire, lived through both World Wars, and embraced stylistic change with enthusiasm and vigour.</em></p>
<p>Jaroslav Benda influenced numerous areas of the fine arts in the first half of the twentieth century. Showing impressive versatility, his work spans from monumental decorative works, mosaics, etched glass, typography, and posters, to precious metal objects. He is best known though for his book designs, book covers, lettering, and typeface design. His work with leading publishers contributed to the foundations of the modern Czech book style. </p>
<p>Benda’s graphics and book typography cover a broad range of expressions, often following prevailing art trends or demands of publishing houses. However, there are principles common to all of his work: a professional exactitude, connecting his understanding of an overall concept with interesting artistic and typographic solutions, and his original use of typefaces.</p>
<h3>Book design and stylistic twists</h3>
<p>In the first decade of the 20th century, Jaroslav Benda and several other artists stood at the beginning of a revival in the artistic quality of Czech books. He did not view books as a rarity or custom-made, stand-alone opuses. Rather, he relied on conventional printing presses and remained faithful to the original purpose of the book, which is to disseminate knowledge.</p>
<p><div class='image'><img src='/blog/assets/2017-Jaroslav-Benda/Benda_01.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Jaroslav Benda’s early work, book covers designed between 1906 and 1909.</div></div></p>
<p>Aesthetically, the early work of Benda was strongly influenced by the Arts and Crafts movement and the ideas of William Morris. This movement later led Benda to his art nouveau period. The indulgence in floral and geometric ornament so typical for this style, echoed even in his later, cubist designs, typically based on a geometrical arrangement of grid patterns and fractured lines.
The establishment of the Wiener Werkstätte (Vienna’s Workshops), Bauhaus in Germany, and a similar art group Artěl in Czechoslovakia brought up a gradual shift to modernism in Czechoslovakia and by extension in Benda’s work. He was a founding member of Artěl for which he also designed the logo and stationery.</p>
<p><div class='image'><img src='/blog/assets/2017-Jaroslav-Benda/Benda_02.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Book cover for: Stanislav K. Neumann, Kniha lesů, vod a strání, Básně 1907 – 1913, vyd. Spolek výtv. umělců Mánes, Praha 1914.</div></div></p>
<p>His simple linear, sometimes ornamental work stood opposite to the book designs spearheaded by contemporary avant-garde artists, like <a href="https://en.wikipedia.org/wiki/Josef_%C4%8Capek">Josef Čapek</a>, who either used new means of expression (e.g., collage, montage) or designed individualised covers and bindings. In contrast, Benda’s work can appear conservative, repeating the same elements over and over again.
Yet, in the late 1920s and early 1930s, following another stylistic change, Benda created several book covers that were inspired by constructivist typography. He embraced alignment grids, asymmetrical composition, as well as dramatic diagonal arrangements. However, his book cover design work truly peaked in the 1940s and 1950s when he replaced conventional woodcut illustrations with distinctive, idiosyncratic lettering, calligraphy, and colour gradients.</p>
<p><div class='image'><img src='/blog/assets/2017-Jaroslav-Benda/Benda_03.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> His distinctive lettering style was employed on various book covers throughout the years. The covers are from 1936 (left) and and 1946 (right).</div></div></p>
<p>Over the course of his career, Benda also focused on other branches of the applied arts that were closely related to the visual language of the newly-established Czechoslovakia. These included designs for stamps, banknotes, tapestries, cut glass. In the late 1930s, fascinated by the new opportunities, he also contributed to the very beginnings of Czech animated film.</p>
<p><div class='image'><img src='/blog/assets/2017-Jaroslav-Benda/Benda_04.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Bank note for five Czech korunas, 1921. Originally planned as a bank note for the first Czechoslovak release with the date 15. 4. 1919, Tiskárna Česká grafická unie, Praha, circulation: 25. 9. 1922 – 31. 12. 1926.</div></div></p>
<h3>Typeface design</h3>
<p>In the 1930s, Benda attempted to develop his first, “typically Czech” typeface. He sent his drawings to the Monotype Corporation for casting, but the design never made it into production.<sup><a href="#footnote1" name="reference1">1</a></sup> As Benda believed the drawings had been destroyed, he continued revising his own version until the 1960s. In 1962, at the age of 80, he and his daughter Jarka Tupá published Betu (Benda-Tupá), an evolutionary conclusion of the designs supplied to Monotype.</p>
<p><div class='image'><img src='/blog/assets/2017-Jaroslav-Benda/Benda_05.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Typeface specimen from: Písmo a nápis [Typeface and lettering], Heintze & Blanckertz, Berlín 1931.</div></div></p>
<p><em>Following is David Březina’s analysis of the version Benda sent to Monotype.</em></p>
<p>The typeface is a rather strange collage of unconventional elements and stroke treatments. It is hard not to be judgemental at first, but there is a lot to discover if one resists such temptation. The bars in ‘a, e, f, t’ are surprisingly dark; the stroke contrast seems unresolved and inconsistent; leaf-like terminals that reference art nouveau aesthetics contrast with sharp serifs in unexpected combinations. The diagonals in letters like ‘k, v, w, y’ are connected with a bar, a signature trick of many of Benda’s letterings. The individual letterforms further add to the the frenzied collection of shapes: the bowl of ‘a’ is angular, the ‘b’ is spurless, ‘l’ has a tail-like out-stroke similar to the one in ‘t’ instead of a typical bottom serif, ‘y’ has a vertical descender, the bottom of ‘z’ is lifted above baseline in order to engage in an impatient swashiness. The letter ‘s’ looks unfinished. It must be an awkward early attempt because the ‘§, &amp;’ – much more challenging letterforms – are executed with confidence. Or were they possibly added by someone else? The figures, on the other hand, radically refuse any attempt at coherent treatment. A coherence-sensitive reader might prefer to look the other way.</p>
<p><div class='image'><img src='/blog/assets/2017-Jaroslav-Benda/Benda_06.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Unreleased seriffed typeface with diacritics and punctuation, Monotype Corporation, Surrey, 1935.</div></div></p>
<p>The diacritical marks are a remarkable representative of a blind evolutionary branch of accent design, yet they make for an interesting study. Benda clearly tries to establish a system that associates carons with acutes. This allows him to resolve the placement of caron on letters with ascenders such as ‘ď, ť’ where the vertical part of the caron merges with the ascender (today this is solved by adding a vertical stroke or a teardrop accent next to the ascender). Dot accents are merely flat rectangles which makes them a bit feeble. The inclusion of the Hungarian double acute and german umlaut (dieresis) is a statement of its own. Perhaps Benda, being born in the Austrian-Hungarian empire, could not not include them.</p>
<p>Although this version of Benda’s typeface might cause a headache for many of today’s type designers, it also presents a wealth of striking ideas. Three beasts in one skin, each pulling in a different direction. We are bound to see more, new typefaces inspired by this work soon.</p>
<h3>Conclusion</h3>
<p>Benda’s book designs and typography can be viewed from two different angles. On one hand, there is a tendency to conform to ideals of a certain period, and along with that, publishers’ demands, on the other is his loyalty to usefulness and simplicity, and an emphasis on typography. In addition to his body of work, on which he actively worked up until his final years, there is also the sheer quantity of his professional texts and essays. Some of them were published as books during his lifetime, while others remain in archives. Either way, they remain an impressive account of his creative spirit.</p>
<p>This year marks the 135th anniversary of Jaroslav Benda’s birth, yet a complete study of his work is sorely missing. A monograph providing a concentrated overview of his life’s work in typography is currently in the making. The authors Lucie Urbánková and Petra Dočekalová will introduce the publication “Jaroslav Benda 1882–1970” at the exhibition of the same name, which will open on 6 June, 2017 at the UM gallery of the School of Applied Arts in Prague.</p>
<p>—</p>
<h3>Footnotes</h3>
<p><a href="#reference1" name="footnote1">1</a>. These drawings were considered lost, until recently recovered thanks to the help of Dan Rhatigan, type director at Monotype Inc. at that time.</p></content>
<updated>2017-05-22T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/11/15/Skolar-Sans-Arabic</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/11/15/Skolar-Sans-Arabic"/>
<title>Skolar Sans Arabic</title>
<content type="html"><p>The design brief for <a href="https://rosettatype.com/SkolarSans#arabic">Skolar Sans Arabic</a> sounded fairly straightforward. Extend an existing design, wherein a significant part of the conceptual work had been done. The whole family can be described as a system with ‘universal’ aspirations, made to look good on the web but ultimately serving a broad purpose. A sans-serif conceived for continuous reading, developed to cater for complex typography, as the name suggests. According to David Březina, who initiated the project, it was ‘nothing deep really’.</p>
<p><a href="https://rosettatype.com/SkolarSans#arabic" class="button" style="margin: 2em 0;">
<span class="innerText">Visit the Skolar Sans microsite »</span>
</a></p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Arabic/Skolar-Sans-Arabic_preview.svg' title='' width='610'></div></p>
<p>While one may differ about this assessment for the Skolar Sans family as released in 2014 – by most standards a typeface of exceptional complexity – translating its characteristics to an Arabic design proved to be challenging. Here, the notion of a sans-serif is everything but straightforward. In the Latin script, the sans-serif genre has been solidly established for more than a hundred years and had ample time for evolution, design movements, counter-movements and even plentiful revivals. In Arabic typography, however, sans-serifs are an utmost novelty, seriously pursued only since the last ten years. While the model of the Latin sans-serif towers above any Arabic attempts at the genre, and is bound to influence its inception, the definition of an Arabic sans-serif is a work in progress with open outcomes. Recently many Arabic typefaces conceived as companions or extensions to established Latin sans-serif designs have fallen into the so-called <a href="https://www.rosettatype.com/blog/2016/05/24/Arabic-calligraphic-styles#kufi">Kufi</a> strand, defined by geometric, strongly modular, and often static type forms. </p>
<p>To me, however, it is all but certain that the Kufi approach is suitable for typefaces that are used for continuous text, rather than headlines. A contemporary Arabic design might as well be based on a (typographic) Naskh structure, and for Skolar Sans with its explicit text orientation, it was my direction of choice. The fundamental nature of the decisions and design approaches that are only emerging for contemporary Arabic typeface design is also apparent in the terminology: in the absence of serifs a ‘sans’ companion makes little sense, and it is more useful to refer to such Arabic type as ‘low-contrast’ designs until a better term has been found.</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Arabic/Skolar-Sans-Arabic_waterfall.svg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Skolar Sans Arabic comprises of nine weights, ranging from Thin to Black.</div></div></p>
<p>It comes as no surprise then, that finding the right amount of typographic contrast was one of the first issues that I encountered in the development of Skolar Sans Arabic, and the answer didn’t provide itself immediately. Many of the most frequent and important Arabic letterforms – alif, lam, and bah, for example – could easily have a completely monolinear design because of their simple skeletons. Yet, some of the most frequent and character-defining Latin letters – think of n, e, and a – by their very nature require a significant amount of contrast. If the goal is to match the Arabic extension to the Latin model, should then the key letterforms be drawn with (unnecessarily) pronounced contrast? Or in other words, should contrast be consistent within a script or between multiple scripts? Or should individual type forms be allowed to diverge from general principles if it contributes to the overall appearance of words and sentences?</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Arabic/Skolar-Sans-Arabic_blindspots.svg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> The structure of certain letters diverges in darker weights. Note the blinded counters in Extrabold and Black.</div></div></p>
<p>In the design of Skolar Sans Arabic I began with fairly geometric letterforms. Alif and lam, for example, were initially based on straight rectangles – following the simple stems of the Latin letters I and l – with minimal adjustments for the joining glyphs. My initial tests, however, weren’t convincing. The frequent pairing of alif and lam was too rigid in comparison to the joined horizontal letterforms, breaking the flow of the line.</p>
<p>Similarly, the design of the diacritical dots required extensive testing and frequent revisions. Since it was going to be a companion to a sans-serif, I wondered if the traditional rhombic dot would be suitable and assumed that a different configuration would work better. As the dots in Skolar Sans are round, I began with rounded, but slightly more squat dots for the Arabic too. This seemed to work reasonably well, but neither David nor I were fully convinced. Because of the high frequency of Arabic diacritics, the round design felt somewhat too jovial. Every possible variation was considered, half-rounded, at different angles, rectangular. Even if a drawing was successful as a single dot, its repetition in double and triple dots was usually not. Especially if the angle was half-way between the conventional rhombic dot and the square, the nesting of the three dot combinations did not work well. After weeks of testing and revising, I resorted to a much more classical configuration. Seeing the effect of something more akin to the rhombic dot across the typeface, it became clear that this was the way to go. Sometimes the simplest answer to a problem is correct after all.</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Arabic/Skolar-Sans-Arabic_dots.svg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Three different approaches to designing diacritical dots, shown in a Persian sample text.</div></div></p>
<p>Many more questions and design challenges such as these made this a particularly exciting and interesting project to work on. In this process David was an ideal partner, as his confidence in my work never descended into uncritical reliance, asking pertinent questions and raising relevant observations. In all the design decisions that were eventually taken, the ultimate goal was always to arrive at an authentic, original and functional interpretation of Skolar’s design for the Arabic script, extending the reach of its voice to many more countries and languages.</p>
<p>—</p>
<p>You can read more about the development of the Latin and pan-European versions <a href="https://www.rosettatype.com/blog/2014/11/26/On-Skolar-Sans">here</a> and <a href="https://www.rosettatype.com/blog/2016/02/02/Skolar-Sans-Pan-European">here</a>.</p></content>
<updated>2016-11-15T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/11/02/Adobe-Typekit-Marketplace</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/11/02/Adobe-Typekit-Marketplace"/>
<title>Adobe Typekit Marketplace</title>
<content type="html"><p>Today, <a href="https://typekit.com/marketplace">Adobe Typekit Marketplace</a> has been announced as a next, logical step in the Typekit story. When Typekit started, it brought the software-as-service approach to fonts while tackling the technical challenges of webfonts at the same time. Licencing and managing fonts on the web had finally become user-friendly. It helped webfonts to become a thing.</p>
<p>Once acquired by Adobe, it also developed into a font-hub for all their applications, for both web and desktop fonts. All fonts were pre-licenced by Adobe for the convenience of their users. While convenient, it naturally limited the selection.</p>
<p><div class='image'><img src='/blog/assets/2016-Adobe-Typekit-Marketplace/Adobe-Typekit-Marketplace.svg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Most of Rosetta’s Latin, Cyrillic, Greek, and Armenian fonts are now available on Adobe Typekit Marketplace</div></div></p>
<p>Typekit Marketplace is removing these limitations by allowing users to licence fonts directly from type publishers (like Rosetta). All of this with transparent terms that are fairly standardised across the publishers. The fonts can be synced with desktop or mobile applications in the Adobe Creative Cloud. An unprecedented ease of use. The fonts designers want, built into the tools they use. Security and fair treatment for the type publishers. This could become a complete game-changer. An App Store for fonts.</p>
<p>At Rosetta, we believe in independent fonts and independent foundries. We see Adobe’s efforts as complementary to this – rethinking what fonts could be, an essential part of typographic tools. Plugins of typographic style so to speak. These are exciting times for the type industry and we are happy to sit in the first row.</p>
<p>You can find nearly all of our Latin, Cyrillic, Greek, and Armenian fonts on Typekit Marketplace today. Arabic and Indic fonts will come in the future.</p></content>
<updated>2016-11-02T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/09/20/The-development-of-Neacademia</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/09/20/The-development-of-Neacademia"/>
<title>The development of Neacademia</title>
<content type="html"><h3>Another Aldine revival?</h3>
<p><a href="https://www.rosettatype.com/Neacademia">Neacademia</a> is a typeface with a past. Like other fonts that are inspired by a historical model, it conveys a feeling from a bygone era and transports it into a modern format. Where it differs to many others however, is its approach to be historically sensitive, rather than historically accurate.</p>
<p><a href="https://rosettatype.com/neacademia" class="button" style="margin: 2em 0;">
<span class="innerText">Visit the Neacademia microsite »</span>
</a></p>
<p>The typeface that served as an example for the development of Neacademia is Francesco Griffo’s type, found in Aldus Manutius’ 1499 edition of Hypnerotomachia Poliphili (further abbreviated as HP). Its lower case is a direct descendant of Griffo’s De Aetna typeface (commonly known as “Bembo”), but its capitals are significantly different. <a href="https://en.wikipedia.org/wiki/Stanley_Morison">Stanley Morison</a> had a low opinion of them, because they are ascender-high (in reality they aren’t). He preferred the lower and darker De Aetna capitals. </p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_HP.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Detail of the Hypnerotomachia Poliphili.</div></div></p>
<p>The capitals of De Aetna were taken from a much older set of Greek capitals, and were only used in combination with the De Aetna lowercase for three years until a new set of HP capitals replaced them in Aldus Manutius print shop. Morison’s preference however stuck – Griffo revivals such as Morison’s own Monotype Bembo, John Downer’s Iowan Old Style, or Matthew Carter’s Yale all look back at De Aetna capitals, not their HP counterparts which seem to be closer to Griffo’s intentions.</p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_DA.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> A close-up of De Aetna taken at the Plantin-Moretus Museum in Antwerp.</div></div></p>
<p>This is where Neacademia and most other Aldines part ways – it deliberately draws its inspiration from Griffo’s post-Bembo typefaces; from the freshly invented italics used in 1501 octavo series, as well as from type used in Leoniceno’s De Epidemia of 1497 and books printed after 1502 by Gershom Soncino in Fano. Neacademia brings Griffo’s italics and italic capitals into its fold and harmonizes them with the romans, while staying true to the calligraphic style of Griffo’s Venetian contemporary, Giovannantonio Tagliente.</p>
<h3>Lost &amp; fount</h3>
<p>The admiration towards a historical typeface, however strong, is rarely in itself a good enough reason to make a revival of it. For such an idea to make sense, it should fit into a modern typographic environment, fill a need not currently served by any of the existing fonts, and express something that does not have a typographic expression yet.</p>
<p>Neacademia’s historical sources are by no means original. The novelty lies in its approach to revivalism. At a time when mainstream typography shifts to digital media, it takes a step in the opposite direction, assisting the book-as-an-object community in its struggle to keep the art of making physical books alive. This relatively small group of retrogrades can hardly be considered a “market”, but they are very determined and capable of making things of exceptional beauty. In the not-so-recent past they had all tools of the trade at their disposal. Nowadays, hand-set type is disappearing at an alarming rate, with high-quality book paper and printing equipment following the same path. Thankfully, some losses are offset by technological advances; the arrival of relatively inexpensive photopolymer plates, which can be processed in small print shops, helped bring new life to letterpress printing. The process of typesetting can now be fully digital, and involve digital fonts.</p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_photopolymer.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Neacademia on a photopolymer plate with the ink being applied.</div></div></p>
<p>Digital descendants of highly esteemed metal typefaces first made an appearance in the 1980s. The main concern of those involved in the process of digitization was first and foremost commercial. If you could make similar looking books to the ones deemed acceptable by readers at a much lower price, compromises in visual quality were justified. The original authors of the metal typefaces were mere spectators of that process, so simplifications of all sorts were commonplace. Shapes were copied over from letter to letter, curves got straightened up, inflections disappeared. There was also a feeling that metal fonts were crude results of inferior technology – with the new tools, everything can be cleaned up and harmonized. Little was thought of the fact that excessive harmonization (e.g. repetition of details) could hinder legibility, especially in combination with printing processes involving high-contrast inks, and bright, smooth paper. Only a handful of printing establishments entered the new era of photo- and then digital printing with a clear understanding of what made the books of the past such a pleasure to read.</p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_gasperau.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Neacademia in use: Someone somewhere by Dana Mills (designed by Andrew Steeves from Gaspereau Press) was awarded in the 32nd edition of The Alcuin Awards, Canada’s national competition for excellence in book design.</div></div></p>
<h3>A fantasy metal revival</h3>
<p>The point of Neacademia’s departure begins in 1998, when I first encountered ITC Founder’s Caslon by Justin Howes. Its appearance pointed to a whole new range of possibilities. Designing a digital type family with optical sizes had been possible since the days of Prof. Donald Knuth’s Metafont, but Howes’ Caslon demonstrated that it could be done in a way that is faithful to the punchcutter’s hand. The approach would produce enough variation on the page to give it a natural, man-made character. On the other hand, by that time, the “harmonization” movement was in full swing, every new font was “cleaner” than the previous one. When taken to the extreme, they looked as childish as a poem with perfect one-syllable rhymes.</p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_itc-caslon.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> ITC Founder’s Caslon at different sizes.</div></div></p>
<p>Since no punches or matrices had survived from the Renaissance, you had to imagine how they were made, and examine printed examples from that period carefully in order to produce a “fantasy metal revival”. Harvard college’s Haughton library hosts an extensive collection of Renaissance manuscripts for close inspection, Peter Burnhill’s Type Spaces could serve as an invaluable reference for printing methods of the time, and Giovanny Mardersteig’s &amp; Charles Malin’s Griffo typeface, as well as Monotype Poliphilus provided some insight into what metal revivals may look like.</p>
<h3>Hurry slowly</h3>
<p>The original plan for Neacademia envisaged six optical sizes, which later was adjusted to four, to keep the scope realistic and not to overtax the user. All styles should be suitably different, as required by the intended use, sticking to the basic set of roman capitals, small caps, lower case, italic capitals and lower case. A Cyrillic counterpart already saw the light of day, with a Greek version to follow eventually. In keeping with the initial idea of a “fantasy metal revival”, all optical sizes were designed separately, so they ended up looking quite different when magnified to the same size. The effect on the page is exactly opposite; when each typeface is set at, or close to its design size, they look more “the same” than if they had a common frame.</p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_optical.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Two different approaches to developing optical sizes in comparison – Neacademia (left) and Adobe Jenson (right).</div></div></p>
<p>The idea of making the glyphs look like they were traced from printed samples, with their wobbling contours and wart-like features, had been rejected. If the new typeface is designed to be used for letterpress printing, the physical processes of etching the photopolymer plate, inking it, and pressing a sheet of paper on it, would provide enough fine-grain variety to make any form of artificial irregularity unnecessary, as well as highly suspect from a philosophical standpoint.</p>
<p>Alternate shapes were however still considered an essential part of Neacademia’s character. Since each letter was created from scratch, there were no shared parts that were exactly identical, resulting in each letter having its own unique shape. Furthermore, the frequently-used letters, such as ‘e’ or ‘a’, also received several alternative variants which change depending on their surrounding context. This allows the letters to fit their context better, by creating ligature-like combinations, as well as reduce the need for kerning in many cases.</p>
<p>The actual styling of individual Neacademia variants exceed the needs of optical adjustment. The Small Text variant is simplified and rounded, with more effort spent on making shapes easily recognizable than on their detailing. The Text variant is closest to its historical typographical prototype, owing much to the punchcutter’s graver, as it worked its way through the steel, making short curves and leaving sharp details in tight corners. The Display variant is more “calligraphic”, clearly influenced by Tagliente’s hand and “constructed” initials of Luca Pacioli and his contemporaries, which, had Griffo to design a typeface to be used at 24 points and higher, would most likely serve as sources of inspiration. Unlike Text and Small Text that were ‘cut’, Display evokes a more “drawn” expression, imitating the effect of a variable-width pen on stems and curves. And finally, Subhead is a child of two worlds in that aspect, nestled between Display and Text, it takes cues from both approaches.</p>
<p><div class='image'><img src='/blog/assets/2016-The-development-of-Neacademia/Neacademia_styles.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> An overview of all styles of Neacademia.</div></div></p>
<p>Neacademia started out in 2009 as an investigation into the working methods of Francesco Griffo. Since then, I have been developing and releasing not more than one style per year. This is very much in the spirit with Aldus Manutius’ favourite saying: &quot;Festina Lente&quot; (hurry slowly). It allowed enough time for new ideas to find their way into the design to make the variants even more different than they would be if they had been all drawn at once.</p></content>
<updated>2016-09-20T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/08/23/Introducing-the-new-licencing</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/08/23/Introducing-the-new-licencing"/>
<title>Introducing our new pricing & licencing</title>
<content type="html"><p><div class='image'><img src='/blog/assets/2016-Introducing-the-new-licencing/Introducing-the-new-licencing.png' title='' width='610'></div></p>
<h3>A note on licencing fonts</h3>
<p>Licencing fonts is a two sided matter. Just like music, typefaces are an intellectual property – an immaterial commodity, that once created can be reproduced indefinitely and distributed at virtually no additional cost. What the customer is really paying for is the blood, sweat, and tears (and doughnuts) that went into its development.</p>
<p>For people licencing fonts, it is important that things go smoothly and the rules of the game are clear – no hidden costs, no constant monitoring of usage, in short: no legal squabbles. For designers, it is important that they will be compensated in relation to the extent their design is used. A foundry’s licencing structure and costs are the result of balancing these two interests.</p>
<p>With our new website two years ago, we have introduced (maybe as the first on the market?) bundled licences aimed towards our typical retail customers. Importantly, it made the licencing an integral part of the shopping experience. While well received, it also raised some questions. So a few months ago we went back to the drawing board to make it clearer, more compatible, simpler, and … more relaxed. Thanks to everyone who took part in our surveys and polls. You helped a lot.</p>
<h3>So what exactly changed?</h3>
<ul>
<li>We have eliminated the strange price tags that looked like charm pricing in some instances. We are not selling air fresheners after all.</li>
<li>While individual fonts are slightly pricier, bundles are more heavily discounted, up to 40 % on selected families.</li>
<li>No limits for PDF embedding or use in logos, no distinction between small- and large-scale projects. We were silly to do that.</li>
<li>All of our licences (except Test licenses) now allow <strong>e-book embedding as a standard</strong>. The distinction between printed and digital belongs to the 20th century. A book is a book is a book.</li>
<li>The Web licence is now web-only. You will need a Single or Studio licence if you want to use the fonts on desktop. It is significantly cheaper though. And! It is for an unlimited number of domains, and does not require any kind of tracking (we love and trust our customers). The only limitation is the total monthly pageviews.</li>
<li>There is a new <strong>App licence</strong>, finally! Intended for mobile and tablet apps. Up to three titles, unlimited extension packs and updates, any platform.</li>
<li>There is a new <strong>Universal licence</strong>. It covers installation of the fonts for up to 20 users, use on the web (the limit is 5 million pageviews/month), and in-app embedding for an unlimited number of apps.</li>
<li>We discontinued the Publisher licence.</li>
</ul>
<h3>If you previously purchased fonts from us:</h3>
<ul>
<li>Studio and Freelancer licence owners will be transferred to the new, more generous Studio and Single licences respectively.</li>
<li>If you purchased a Publisher licence you will continue to receive updates, and can use the fonts according to the old licence.</li>
<li>If you purchased a Web licence your will continue to receive updates for the WOFF+EOT fonts, and can use the fonts according to the old licence. If you wish to switch to a combo of the new Single and Web licences instead, we can do that for you, for free. Just send us an email.</li>
</ul>
<p>We hope that new and existing customers alike will appreciate the revised, and in our opinion, more transparent pricing and licencing.</p></content>
<updated>2016-08-23T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/05/24/Arabic-calligraphic-styles</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/05/24/Arabic-calligraphic-styles"/>
<title>A brief overview of the various Arabic calligraphic styles</title>
<content type="html"><p>There are many different calligraphic styles used for writing the Arabic script, styles that developed over the span of many years and in different regions. This article will explain the characteristics of the major styles and styles that were influential on future typographic developments, and give readers the ability to visually distinguish between them.</p>
<p>The basic Arabic alphabet consists of 28 letters, and because these letters are all consonants, the alphabet is classified as an abjad. Abjads represent consonants, or consonants plus some vowels. However, Arabic is an impure Abjad; the long vowels are represented in the alphabet by the letters alif, yā and wāw (ا - ی - و), and the short vowels only exist in the form of diacritic marks that are usually absent from texts, as context largely helps to avoid the drawback of misreading a word.
Another important feature of the script is the lack of distinction between uppercase and lowercase letters. In both printed and written Arabic, words are constructed in a cursive style; this means that characters are written through the continuous movement of the pen, and dots are usually added in once a single word has been fully written. Additionally, the same letter can take on a different appearance, depending on where it appears in a given word. This is because in Arabic, letters have contextual forms, and can appear in initial, medial, final and isolated positions.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_table.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> The table shows how the rendering of characters is affected, depending on where they appear in a sequence. They can be divided into four groups; isolated, initial, medial and final forms. Most Arabic fonts rely on OpenType technology, since their shaping is contextual.</div></div></p>
<p>Other noteworthy features of the script include numerals being written from left to right despite words being written from right to left, the copious amount of dots used to characterize letters that share a basic form, and achieving justification by means of extending <a name="kufi"></a>certain letters (this is referred to as a kashida).</p>
<h3>Kufi</h3>
<p>At first, localized variants of the Jazm script were used to record the Quran, and each of these scripts carried the name of the region they were created in – Makki from Mecca, Madani from Medina and Kufi, which ultimately became the general term used to describe this style, from Kufa <sup><a href="#footnote1" name="reference1">1</a></sup>. Features of Early Kufi include horizontal strokes that are either extremely elongated or very compact, the crescent shaped curve on the lower right side of the alif, and noticeably round characters that have extremely small counters. Towards the end of the seventh century, vowels were introduced into the text in the form of red dots placed above or below characters to show proper pronunciation <sup><a href="#footnote2" name="reference2">2</a></sup>.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_earlykufi.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Example of the Early Kufi style, used to write the Quran. Notice the small counters of characters such as feh and waw, the elongated kaf and the curved alif.</div></div></p>
<p>In the tenth century, Persian calligraphers developed a new variation of Kufi called Eastern Kufi <sup><a href="#footnote3" name="reference3">3</a></sup>. There are many noticeable similarities between this style and Early Kufi in the character shapes and geometric structure. However, when looking at Eastern Kufi and scripts such as Avestan and Pahlavi <sup><a href="#footnote4" name="reference4">4</a></sup>, distinct influences of the national scripts can be observed. The contrast between the long ascenders and shorter slanted strokes, curved letterforms, strokes that are more slender than in Early Kufi, and the tendency to employ a slight slanting to the left when writing, are some of these characteristics.
These features give the style an overall highly vertical and upright appearance, and a dynamic forward movement when reading. Eastern Kufi was used to transcribe the Quran for some time before it was replaced with the Naskh style, but continued to be used for decorative purposes such as chapter headings.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_easternkufi.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> (Above) The beginning of Vīdēvdād, a law book containing the rules for dealing with pollution and crime. It is one of the oldest existing Zoroastrian manuscripts, copied in 1323 in Nawsari, Gujarat, by the scribe Mihraban Kaykhusraw. The Avestan (Old Iranian) script is in red, and the Pahlavi (Middle Persian) is in black. (Below) 11th-Century Qur’an in Persin-style (Eastern) Kufic. When comparing the two, similarities in strokes and shapes can be seen in many places.</div></div></p>
<p>Around the same time as Eastern Kufi was being developed, its Western counterpart called the Maghribi Kufi was evolving. Maghribi (which translates to western) originated from the Western Islamic world of North Africa and South Spain, and was highly influential on the future scripts of North and West Africa, as well as Andalusia. Characteristics of this style includes descending strokes that have large bowls, sweeping curves that encircle the next few letters, flat vowel signs that are often added in with red ink, and the general use of uniform strokes with a toothpaste quality.</p>
<p>By the twelfth century, these three styles of Kufi were slowly replaced as the main style for transcribing the Quran and book calligraphy. Instead, they were used for ornamentation on objects such as coins, seals, pottery and on monuments, and many of the newer Kufi styles began to emphasize visual aesthetics over legibility.
Today this style is still widely used in design and for decorative purposes. It is also commonly referred to as the source of inspiration when describing very low-contrast typefaces that have become ubiquitous in recent years in attempts to harmonize Latin and Arabic. However, a comparison of these styles and Kufi calligraphy shows great dissimilarities in the letterforms and their proportions.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_maqribi.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Example page of the Quran written in the Maghribi Kufi style.</div></div></p>
<h3>Naskh</h3>
<p>The Early Naskh style originated in the cities of Mecca and Medina around the seventh century. However, it was truly refined in the early tenth century through the endeavors of Ibn Muqlah <sup><a href="#footnote5" name="reference5">5</a></sup>, who transformed it into an elegant cursive script. Naskh quickly became the preferred calligraphic style for manuscripts and transcribing the Quran; a replacement that was doubtless due to features like high legibility and the fact that it is quick to write. To this day, it is the most commonly used style in the publication of the Quran.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_naskh.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Example of the Naskh style in a hand written Quran. The Fatihah panel is signed by a certain ‘Alireza’ and is dated 1241 AH (1825 AD). Balance is obtained by equal distribution of flat and circular forms.</div></div></p>
<p>The harmonious proportions of Naskh render it extremely legible. This combined with the way in which most characters rest on a visible connecting middle stroke has appointed it as the style most adaptable to the limitations presented by metal. Today, most newspapers, publications and periodicals are printed with typefaces based on Naskh, making it the most widely used style for setting text in Arabic.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_nassim.png' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Nassim Arabic is based on the Naskh style. Justification is achieved through swashes, rather than flat elongated kashidas that can be observed in most other Arabic typefaces.</div></div></p>
<h3>Thuluth</h3>
<p>In Arabic, the word Thuluth translates to ‘one third’. There are different theories as to what this is referring to, such as the observation that one-third of each letter slopes, or that it relates to the pen size that is used to write this particular style. The most acceptable reason is most probably that of Ibn Muqlah himself, who has been quoted to say that in Thuluth, one-third of the letters are straight, and two-thirds, round <sup><a href="#footnote6" name="reference6">6</a></sup>.
Thuluth is closely linked with religion and often finds its application in the decoration of mosques and writing holy names. Notable features of this style are the inclusion of vowel signs and ornamental frills that are used to beautify the script, and a combination of sharp, hair-thin out-strokes that curve slightly upward in a small loop. The letters are usually large but very compact, high ascenders are written with a slight tilt towards the left, and round shapes predominate the texture.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_thuluth.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> The Thuluth style being used in the tile work of Yeni Cami (the New Mosque) in Istanbul, Turkey.</div></div></p>
<h3>Ruq’ah</h3>
<p>An invention of the Ottoman Empire Government offices in Istanbul, Ruq’ah was created by combining elements from two styles; Ta’liq and Dīwanī. Many similarities such as diagonal word structures and connecting strokes that were devised to increase the speed of writing can be seen between Ruq’ah and that of its parent styles. The main feature however, is the exclusion of elongations, decorations, or the need to lift the pen off paper. These attributes made Ruq’ah fast to write and efficient for the use of government scribes <sup><a href="#footnote7" name="reference7">7</a></sup>. Other characteristics include clipped letters composed of short, straight lines and simple curves, as well as its even lines of text. Another important and distinct feature is the connecting of the diacritical dots to the final and isolated letters in the form of short strokes.</p>
<p><div class='image'><img src='/blog/assets/2016-Arabic-calligraphic-styles/acs_ruqah.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> The Hayat al-Qiddis Mar Afram al-Surani (The Life of Saint Ephrem the Syrian), an anonymous text translated from Syriac into Arabic by Butrus Rizq al-Andari in Lebanon (The School of the Monastery of Mar Yuhanna Marun), dated 17 January, 1895. Written in clear Ruq’ah style, in purplish ink.</div></div></p>
<h3>Conclusion</h3>
<p>These are only a few of the many calligraphic styles used to write the Arabic script, and while it is easy to detect the unique features of each, other styles are not so easily distinguishable. Sometimes it is only through details, like the size of the alif that styles visually differentiate. Today, calligraphy is mainly practiced as an art form, and even when looking at the most widely employed styles, there is a noticeable decline in use from the early 19th century, when printing technology appointed Naskh as the most adaptable variant. However, the importance of studying these various calligraphic styles is in the fact that some, (most notably Naskh, Maghribi, Ruq’ah and Kufi) were imitated in the typographic reproduction of the Arabic script, and the success of these types was dependent on how close they could get to replicating handwritten manuscripts. Calligraphic traditions like the relationship between stroke width and counter size, or the fitting of letters and words still remain relevant to the design of typefaces used in printing.</p>
<p>—</p>
<h3>Footnotes &amp; further reading:</h3>
<p><a href="#reference1" name="footnote1">1</a>. Safadi, Yasin Hamid, <em>Islamic calligraphy</em>, 1979.<br>
<a href="#reference2" name="footnote2">2</a>. By the eighth century, these developed into the familiar short black diagonal strokes that are commonly used today. Baker, Colin F, <em>Qur‘an manuscripts: Calligraphy, Illumination, Design</em>, 2007.<br>
<a href="#reference3" name="footnote3">3</a>. Schimmel, Annemarie, <em>Calligraphy and Islamic culture</em>, 1984.<br>
<a href="#reference4" name="footnote4">4</a>. The scripts were used in Iran before the country adopted the Arabic script.<br>
<a href="#reference5" name="footnote5">5</a>. Abbott, Nabia, <em>Studies in Arabic Literary Papyri, Vol. I</em>, 1972.<br>
<a href="#reference6" name="footnote6">6</a>. Yūsofī, Gholam Hoseyn, <em>“Calligraphy” Encyclopedia Iranica, Vol. IV</em>, 1990. http:iranicaonline.org/articles/calligraphy (state as of 5. 3. 2016.)<br>
<a href="#reference7" name="footnote7">7</a>. Vilhjálmsson, Gunnar, <em>“Ruq’ah – the new style” The Recorder, Issue 1</em>, 2014.</p></content>
<updated>2016-05-24T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/05/17/A-work-in-progress-Nassim-v2</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/05/17/A-work-in-progress-Nassim-v2"/>
<title>A work in progress – Nassim 2.0</title>
<content type="html"><p>On May 17, 2006, I was in the process of defining Arabic mark positions for <a href="http://rosettatype.com/Nassim">Nassim</a> in a roundabout process involving a dummy FontLab MultipleMaster file, custom export scripts and Microsoft’s beloved Visual OpenType Layout Tool – VOLT. I was a Master’s student at the Department of Typography and Graphic Communication at the University of Reading and in the final third of the practical programme, adding finishing (or so I thought) touches to the regular design, and completing the family’s scope. Ten years on, Nassim has established itself as a key exponent of a new generation of Arabic typeface design, a feat I would not have dreamed of back in my student days. Today, I am excited to announce the release of an updated and improved version of the typeface, Nassim 2.0. The new version of Nassim is a major update, reflecting its use, technical changes and my learning.</p>
<p><div class='image'><img src='/blog/assets/2016-A-work-in-progress-Nassim-v2/Nassim_banner.svg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Extended language support, new features, a Medium weight, and a new Italic companion.</div></div></p>
<p>Even though Nassim won several prestigious awards, I was not eager to publish it immediately. As I studied Arabic in Syria in 2007, I pursued other projects and left the type to rest. Not only did it provide me with some distance, refreshing my critical eye, but also allowed my appreciation of Arabic type forms to mature further. In 2008 an opportunity arose to reconsider the design and concept of Nassim, as DecoType and WinSoft sought new designs for their jointly developed Tasmeem software. I had the interesting and sometimes challenging task to revise parts of the Arabic design to take advantage of DecoType’s Arabic Calligraphic Engine (ACE), an approach to Arabic type with fundamentally different concepts to those found in the OpenType world. For example, ligatures are unnecessary in ACE fonts, as the changing letterforms of different contexts are built dynamically from component parts – a more elegant and efficient approach to the typographic rendering of the Arabic script. Nassim was released with Tasmeem in the Middle Eastern version of Adobe InDesign extending the original design with numerous features and language support.</p>
<p>By 2010, technological changes and an entirely new area of typography opened up with the advent of web fonts. Coincidentally, Nassim became a protagonist in its early days, as it was selected by the BBC World Service for its Arabic-script news websites. In the process of adapting it to the client’s specific requirements – technical for screen rendering and stylistic for culturally distinct audiences – Nassim evolved further. Drawing from the approach I had learnt in the collaboration with DecoType, I rendered ligatures as contextual alternates, to reduce the number of glyphs needed, and thus the size of the fonts. Working with the teams of the BBC’s language services – Arabic, Persian, Pashto and Urdu – provided insights into the various cultural typographic preferences, contributing to the continued improvements of the design. This tailoring to specific audiences worked so well, that it also resulted in a rampant pirating of the Persian BBC Nassim version for websites in Iran. The following year, the retail version of Nassim was released as an OpenType font with Rosetta Type Foundry. It was based on the fonts I had developed for the four BBC language services, incorporating their core, localised glyph sets.</p>
<p><div class='image'><img src='/blog/assets/2016-A-work-in-progress-Nassim-v2/Nassim_BBC.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Nassim in use for the BBC World Service.</div></div> </p>
<p>In the meantime I had begun my PhD research in Reading and embarked on other projects, leaving little time for further extensions of my retail type. But ideas for Nassim’s continuous development were aplenty, and just waiting for the right opportunity – which did not take long to present itself. In 2012 I became involved in the the Murty Classical Library project, published by Harvard University Press and designed by Rathna Ramanathan. My contribution consisted in consultation and design of the Arabic script typography of the series (in Persian, Sindhi and Urdu languages), and the typesetting of the first volumes. Rathna and Fiona Ross – consultant and designer of the Indian typefaces – suggested to include Nassim in our tests. Initially I was hesitant – I did not see the design as a particularly literary type – but agreed to see how it suited the overall concept and how it sat with the types for the Indian and Latin scripts. Against my preconceived idea, Nassim actually worked well in the approach to the design of the series typography. Rathna wanted the books to be accessible and not to have an academic air, so she favoured contemporary, low contrast typefaces. Having part of the series printed in India in unpredictable conditions also required a certain robustness. Eventually, we all agreed that Nassim worked best, when paired with the choice for the English texts – Henrik Kubel’s Antwerp.</p>
<p><div class='image'><img src='/blog/assets/2016-A-work-in-progress-Nassim-v2/Nassim_Murty.jpg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Detail of Nassim in the Murty Classical Library of India series.</div></div></p>
<p>So here was the occasion to extend the typeface further – in terms of language support as well as in terms of typographic features. Swash characters were high on my list, since the books were going to be justified and I wanted to have a better means of justification than flat Kashidas. Not only do swashes look better and make the text more lively, they are also a more authentic tool than the typewriter-style elongation.
Another element that I wanted, were drawn Arabic superior figures. I had already designed superiors that matched DecoType’s Naskh in my work for Brill – a key feature for scholarly typography – but not for my own Nassim. The Murty series was going to keep the academic apparatus to a minimum, yet there were going to be footnotes, and they should look right. And when you have superiors, it makes of course sense to also provide Arabic script fractions. My guess is that probably neither feature is found in any other current Arabic typeface.</p>
<p>Among the more obvious additions were numerous contextual alternates (instead of ligatures), for a selection of letter combinations, as well as stylistic variants for a few specific letters. While most retail fonts provide their ligatures and other features only for Arabic (and sometimes Persian) language support, it was a concern for me to make sure that the same functionality was offered for all languages the fonts support, so they still ended up with a fair few glyphs. Among the more subtle, but technically challenging features are the so-called raised teeth glyphs, specialised typeforms that help to increase the distinctiveness of letters where the repetition of similar shapes can lead to ambiguity. Here, the correct letter patterns had to be identified, and then translated into OpenType code that would produce the right results. After a lengthy process of trial and error, I hope to have arrived at a satisfying implementation.</p>
<p><div class='image'><img src='/blog/assets/2016-A-work-in-progress-Nassim-v2/Nassim_teeth.gif' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> Raised teeth alternates increase the distinctiveness of letters and improve legibility.</div></div></p>
<p>Since 2014, a Nassim beta version that incorporates these improvements has been in use for the Murty Library for the first three volumes of the Persian epic Akbarnama, the history of Akbar. But when doing an update, it is hard to stop, and thus I kept adding elements and features to the family that went beyond the immediate needs of this series.</p>
<p>Whereas many of the above features are deeply rooted in Islamic manuscript culture, I also added some more unconventional ideas to the design. Drawing on my experiences with the setting of substantial quantities of text, I came to the conclusion, that ranging figures would be an excellent feature that Arabic typography could derive from the Latin script tradition. As the figures are of Indian origin, their proportions are not quite in sync with the letters of the Arabic abjad which use the vertical dimension very differently. As no figure descends below the baseline, and all but one have the full height of the Alif, they tend to look too big and are exceedingly prominent in a block of text. The Arabic figures that found their way into the Latin script remain – despite their far-reaching adaptation – difficult to blend in with the shape repertoire that derives from the Carolingian Minuscule and the Roman Capitals. But since numerals travelled wide and far and were adopted for these fundamentally different writing systems, it only seemed fitting to make the cultural influence go full-circle, and bring ranging figures to Arabic typography. After Aisha, Nassim is thus the second Arabic typeface to feature them, and I hope that more are going to follow.</p>
<p>On the level of language support, the typesetting for Harvard University Press called only for Sindhi (Urdu and Pashto had already been designed for the BBC), but I decided to extend the coverage to Maghrebi orthographies, Malay in the Jawi script, and Uyghur. In this glyphset enlargement, care was taken to enable all typographic features for all supported languages.
Although the Murty series did not employ Nassim for the English texts, this update provided the opportunity to revise also the Latin part of the family. Here, other typographic tools like small capitals with matching figures, the typical four figure sets, superiors, fractions and some other features were added. We finally used the occasion to release the Italic companion of Nassim. Although conceived as part of the original design, the Italics had never been published because of the focus on the Arabic. Now, the revised and updated design is in line with the upright fonts’ glyphset, bringing the family to a new level of completeness.</p>
<p><div class='image'><img src='/blog/assets/2016-A-work-in-progress-Nassim-v2/Nassim_italics.svg' title='' width='610'><div class='imageDescription'><strong>Figure:</strong> The Italic allows Nassim to be employed for a wide range of applications.</div></div></p>
<p>Ten years of experience, research and use in a range of diverse applications have thus shaped and influenced the evolution of Nassim. Today, the family is better, more complete than ever, and available for licensing. Existing users have a heavily discounted upgrade option, that I would recommend wholeheartedly. Many thanks to all the users who have given their trust to Nassim for their inspiring work, I am looking forward to seeing more of it in the future.</p></content>
<updated>2016-05-17T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/04/26/Introducing-Gitan</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/04/26/Introducing-Gitan"/>
<title>Introducing Gitan</title>
<content type="html"><p><a href="http://rosettatype.com/Gitan">Gitan</a> is Florian Runge’s debut release – a flared sans serif, reminiscent of engraving and stone carving. Sturdy and informal, the design features a moderate contrast with distinct terminals.</p>
<p>The idea of a raw typeface was explored by Rudolf Koch and Berthold Wolpe, as early as the 1920s. Experiments with shapes that negotiate boundaries between the exactness of mechanical production and the imperfection of human condition led to the development of designs like Neuland and the ubiquitous Albertus. Nonetheless, they were limited to display typography, namely book jackets, and are not suitable for continuous reading.</p>
<p>Gitan takes expressive forms derived from chiseling and engraving and places them comfortably on the crossroads of editorial and package design. A contemporary typeface with a wide range of applications, that doesn’t fall into the anachronistic traps, set by similar genres.</p>
<p>The genre-less-ness turned out to be the ultimate design challenge. Balancing functionality and expression leads to questions of categorization. Is it really a serif or a sans? Is it a display or text typeface? Strong features like the cuneiform head serif on characters like <em>n</em> and <em>m</em>, or the deeply cut wedge terminals on <em>c</em>, <em>r</em>, and <em>s</em> give Gitan a sculptural appeal – a quality that is desired for all things display. A rhythmic pattern and a classic construction make it sparkle in text. You will have to decide, we clearly could not.</p>
<p>Gitan’s versatility is underpinned by a huge typographic repertoire. Apart from supporting over 120 languages, the fonts contain small caps, six sets of numerals, including case-sensitive figures, and a vast array of Open-Type features.</p>
<p><div class='image'><img src='/blog/assets/2016-The-Journey-Of-Sherpa-Sans/SherpaSans-previews_big.svg' title='' width='940'></div></p></content>
<updated>2016-04-26T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/03/16/Yrsa-Rasa-released</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/03/16/Yrsa-Rasa-released"/>
<title>Yrsa & Rasa released</title>
<content type="html"><p>Yrsa and Rasa are open-source type families published by <a href="http://rosettatype.com">Rosetta</a> with generous financial support from Google. The fonts support over 92 languages in Latin script and 2 languages in Gujarati script. The family currently has 5 weights. They were designed and produced by Anna Giedryś and me and they are now released and ready for download.</p>
<p>I wrote two articles about the project development where we discussed what we <a href="https://www.rosettatype.com/blog/2015/09/01/Introducing-Yrsa">meant by remixing</a> and how we approached <a href="https://www.rosettatype.com/blog/2016/01/20/Harmonizing-Rasa-Gujarati-and-Yrsa-Latin">harmonization of two different scripts</a> such as Latin and Gujarati. Today, as we release the fonts out into the wild I will explain what we learned from this six-month-long exercise.</p>
<p>But first, we need to clarify who did what. Anna was the main draughtswoman. I was merely a supervisor, occasional stern critic, main revisionist of the Gujarati, and a coder. Briefly put, if there is anything to like, it is Anna’s. If there is anything wrong, it is mine.</p>
<p><div class='image'><img src='/blog/assets/2015-Introducing-Yrsa/Yrsa-corrections_big.jpg' title='' width='940'></div></p>
<h3>Design as redesign</h3>
<p>Is it useful to start from an existing design? We believed it would be faster to change Merriweather than draw a new design from scratch. And it was faster, but not as much as we expected. We wanted to change more than we had originally planned. As we worked, we found that the version of Merriweather we started from had some inconsistencies: stems with different thicknesses, serifs that were a bit different from each other in unexpected ways*, and some shapes that we simply would have done differently.</p>
<p>Some of these were deliberate design decisions to make the texture more lively. Others were differences of opinion. Some small, some large (we hereby disapprove of Merriweather’s sterling symbol). A lot of the corrections Anna felt needed to be done, were beyond what initially seemed like a straightforward restyling. In contrast, converting Skolar Gujarati to Rasa was much more effortless. Only the bold weight required more creativity, when harmonising with Yrsa’s contrast and weight (see our previous post for details). A matter of less different opinions?</p>
<h3>Design as testing</h3>
<p>On the other hand, and on a more positive note, Anna got to design with real texts in no time. When starting from scratch, type designers typically have a handful of letters which cannot provide real-life testing environment. Even a–z is insufficient, as capitals and punctuation are missing. This setup makes going from the big picture of typography and layout to the micro-level of type design really tricky. One might easily miss the intended niche for their fonts. Imagine digging a tunnel from both sides of a hill, but without navigation. Fortunately, in our case we had a complete set of characters to test and proportions we were fairly happy with. This allowed us to make critical judgements about what works and what does not, and make informed design decisions.</p>
<p>In Gujarati that applies even more. Seeing the whole, large character set and how it is set up provides a comfortable safety hammock.</p>
<h3>Design as dialogue</h3>
<p>It is enlightening to have a conversation among curves and forms with a fellow type designer and uncover their thoughts and misdemeanours in great detail. But it should be a dialogue, not just listening or parroting. There is a point where an opinion ought to be voiced and that can take some energy. We previously stated that every design is redesign, now we can safely say that with an opinion of one’s own, every redesign quickly turns into design.</p>
<h3>Design as service</h3>
<p>Now, take the fonts and make something nice with them! Every font remains incomplete until someone uses it. We both hope you will like to use them.</p>
<p>Yrsa &amp; Rasa are released under the Open Font Licence and free to use. They are available from the <a href="https://fonts.google.com/specimen/Yrsa">Google</a> <a href="https://fonts.google.com/specimen/Rasa">Fonts</a> directory and <a href="https://typekit.com/fonts/yrsa">Adobe Typekit</a>.</p>
<p>Their main purpose is continuous reading on the web (think Medium), British visual style (now with a decent looking sterling symbol), Gujarati visual style (several kinds of rupee symbols which change, depending on their appearance within Latin or Gujarati text), or printed matter (think books). Extra care was taken to make all the supported European languages shine – not just English, but also Polish, Dutch, Czech, Catalan, Slovenian, Romanian, and others. The are a few ligatures, capital German ß, and tabular figures for both Latin as well as Gujarati.</p>
<p><a href="http://github.rosettatype.com/yrsa-rasa/" class="button" style="margin: 2em 0;">
<span class="innerText">Download the fonts from Y &amp; R microsite</span>
</a></p>
<p>FYI, we would love to add italics at some point, so if you want to stay in the loop for future extensions, <a href="http://rosettatype.com/contact">subscribe to our newsletter</a> or <a href="http://github.com/rosettatype/yrsa-rasa">follow/star the repo on GitHub</a>.</p>
<p>* I am not referring to classic type design tricks.</p>
<p><div class='image'><img src='/blog/assets/2016-Yrsa-Rasa-released/Yrsa-Rasa-previews_1_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2016-Yrsa-Rasa-released/Yrsa-Rasa-previews_2_big.svg' title='' width='940'></div></p></content>
<updated>2016-03-16T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/02/02/Skolar-Sans-Pan-European</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/02/02/Skolar-Sans-Pan-European"/>
<title>Skolar Sans Pan-European</title>
<content type="html"><h3>Expanding the design space</h3>
<p>Skolar Sans is Rosetta’s biggest type system so far, and as such, a good study in a design expansion. The family consists of 72 styles and addresses the needs of modern responsive design. It is able to adapt to a wide range of devices and formats, from the biggest desktop screen to the smallest printed booklet. Last year, Sláva Jevčinová and me started extending Skolar Sans to full pan-European standard so it would cover not just Latin but also Greek and Cyrillic scripts. After going from serif to sans, and to a great number of widths, weights, and styles, there was still room for another parameter – language.</p>
<p><a href="https://rosettatype.com/SkolarSans" class="button" style="margin: 2em 0;">
<span class="innerText">Visit the Skolar Sans microsite »</span>
</a></p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Design-parameters_big.svg' title='' width='940'></div></p>
<h3>A truly European project</h3>
<p>The advanced language support was commissioned by <a href="http://www.rferl.mobi">Radio Free Europe/Radio Liberty</a> with the goal to carry their content through all of their newly developed websites (together with our Skolar PE and Merriweather by Eben Sorkin). The project, one of very few to support this many languages on the same CMS platform, was headed by Kim Conger, Design Director at RFE/RL and Karel Knop, who brought it to life in his role as the Senior Designer. The platform, <a href="http://www.pangea-cms.com">Pangea</a>, supports RFE/RL websites as well as Voice of America, Middle East Broadcasting and Cuban Broadcasting. Every day, 95 responsive sites are accessed by 1.3 million users (on average) from 200 countries and territories. RFE/RL has launched the mobile and tablet versions (see <a href="http://www.ozodi.mobi">Radio Ozodi</a> in Tajik for example) and yesterday they started rolling out the desktop versions as well (see <a href="http://www.evropaelire.org/">Radio Evropa e Lirë</a> in Albanian for example).</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Ozodi-web.jpg' title='' width='610'></div></p>
<p>The plans to include more scripts in Skolar Sans existed before but sometimes it takes a pressing need and a visionary client to get things going. We were happy to work with Irene Vlachou and Maxim Zhukov on this project, assisting us with Greek and Cyrillic, respectively. The resulting linguistic scope, together with the number of styles, is largely unprecedented and we would not have achieved this quality without our consultants.</p>
<p>Although we constantly strive to release large multilingual projects, putting this much work and effort into a single product presents a challenge for a small business like us, as great risk comes with designing for an unpredictable market. The fact that additional language and script support is now increasingly requested by clients, might tell us something about the changing demands in delivering content today. Consequently, briefs like this allow us to do our work in the best possible environment.</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Preview_big.svg' title='' width='940'></div></p>
<h3>The unwritten laws of language extension</h3>
<p>Extending Skolar Sans to include Cyrillic and Greek meant adding extra 1000 glyphs to each font. The Cyrillic supports many Slavic and Asian languages, but also comes equipped with language-sensitive character variants for Macedonian, Serbian, and Bulgarian. The Greek offers support for monotonic as well as polytonic orthography. Monotonic Greek is used in everyday communication and is the successor of polytonic Greek, which is necessary for academic publications and a variety of conservative texts. Altogether, the type system will effortlessly provide support for at least 140 languages. We also added 300 more glyphs that are used in linguistics and for various Latin transliterations of Asian scripts (e.g. Chinese, Indian languages including Sanskrit, Arabic, Hebrew). That brings Skolar Sans PE on a par with our popular text type family Skolar PE, which has only a slightly bigger glyph repertoire which we hope to match eventually.</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Bulgarian-Serbian-Cyrillic_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Comparison of the default, International Cyrillic and Bulgarian letterforms in uprights (top, Bulgarian in Green) and default and Serbian/Macedonian forms in uprights and italics (bottom, Serbo-macedonian in Green)</div></div></p>
<h3>A multiverse design approach</h3>
<p>A type system is designed to function in a universal way, although in this case the design itself cannot follow a single recipe. Like with culture, what works for the Latin might not be the best solution for other scripts. The cursive Greek is a good example for that. Greek has a very fluid motion, and is not as rigid as Latin or Cyrillic. Hence, the distinction between upright and italic styles would not be as strong if they followed the same construction, so we decided to use more of the significantly different forms for the cursive Greek and introduce various shape subtleties to distinguish the two. That way, the cursive maintains similar degree of typographic versatility as Latin and Cyrillic, while following a different design approach.</p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Italics-comparison_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Comparison of Latin and Greek and their corresponding italics. Marked green are characters that change their construction beyond mere sloping.</div></div></p>
<h3>Font size matters</h3>
<p>If you care about your users’ experience, you care about your website performance. And with RFE/RL’s mission to broadcast to millions of users in so many countries with slow or censored internet this becomes even more of an issue. Keeping the loading speed high (and the size of the websites small) sets a strict limit on fonts. Rosetta’s designers were facing a double challenge: supporting a large number of languages in three different scripts that are bound to result in large fonts, while reducing the size of those fonts drastically, so that they can be used on the web. In short, we went from around 268KB fonts to 33–40KB subsetted webfonts, and it was not very easy. Elaborating on the nitty-gritty would require another article.</p>
<h3>Skolar Sans in Numbers</h3>
<p>171 396 glyphs, 3600+ hours of drawing and engineering, 2370–2391 glyphs per font, 143+ languages covered, 72 styles, 10 months development time, sanity lost and recovered: more than three times, all of that with Daft Punk’s Tron Legacy soundtrack on repeat with <a href="https://soundcloud.com/bordelloaparigi/flemming-dalum-hot-girls-of">Stella Carnacina and Daniela Poggi</a> to lift up the spirits on a particularly rainy English day.</p>
<p><em>Having been born in communist Czechoslovakia where RFE was one of the beacons of uncensored news, it has been real honour to contribute back to RFE/RL with our fonts. And now that they are widely available we hope they will serve our retail customers equally well.</em></p>
<p><br></p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Glyphs-and-languages_big.svg' title='' width='940'></div></p>
<p><br></p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Commits_big.svg' title='' width='940'></div></p>
<p><br></p>
<p><div class='image'><img src='/blog/assets/2016-Skolar-Sans-Pan-European/Email-estimates_big.svg' title='' width='940'></div></p></content>
<updated>2016-02-02T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/01/20/Harmonizing-Rasa-Gujarati-and-Yrsa-Latin</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/01/20/Harmonizing-Rasa-Gujarati-and-Yrsa-Latin"/>
<title>Harmonizing Rasa Gujarati and Yrsa Latin</title>
<content type="html"><p>This is the second post in a series about our open-source project Yrsa/Rasa – a contemporary typeface for continuous text setting in Latin and Gujarati, for both web and print designed by Anna Giedryś and me. The project is subsidised by Google and you can follow the ongoing development on <a href="http://rosettatype.github.io">GitHub</a>. You can also get in touch via <a href="mailto:ask@rosettatype.com">email</a> if you want to give the finished Latin part a test drive before all scripts are officially released in February.</p>
<p>Let me elaborate on the naming first. Yrsa is used for Latin and any other European script, Rasa is for Gujarati and any other Indic script. The original reason for this change was a technical requirement of the Google Fonts system, but it is also quite nice that the Indic fonts get an Indic name while the Latin fonts keep the European moniker.</p>
<p>In this article, I would like to write a little bit about the challenges of peaceful coexistence between Latin and Gujarati in one typographic environment. What does it mean and can type designers control this kind of coexistence at all? I think not, certainly not to the full extent. But they can prepare tools, i.e., multi-script fonts, which would be convenient for typographers: easy-to-use fonts with predictable and practical defaults. In this regard, an <em>equal importance</em> of each script in multi-script fonts is of essence. This allows typographers to control the relationship between the scripts well. They might, of course, eventually decide to emphasize one of the scripts depending on the content and genre they are designing for.</p>
<p>When it comes to a harmonization strategy, there is a scale that ranges from no changes at all to radical uniformity. “Harmony“, “uniformity”, and “matchmaking” are some of the words people would use to refer to various points on this spectrum. Rosetta is subscribed to the concept of <em>loose harmonization</em> which crudely put means: make scripts look equally important, harmonize what you can, and don’t touch the rest. Of course the tricky bit is knowing what you can or cannot change. It takes experience with each script to recognize the areas that can share a similar treatment. It depends on a particular genre of documents one is designing for. To make it even more complex, there are also cultural differences to consider. Different shapes have different connotations in different environments. What looks modern in Latin, may look dated in Gujarati etc. The only recommendation for navigating through this minefield is intensive exposure to corresponding scripts and study of their history and technological developments. Alternatively, a knowledgeable consultant might be of help.</p>
<p>As I mentioned in the <a href="https://www.rosettatype.com/blog/2015/09/01/Introducing-Yrsa">previous post</a> the Gujarati is based closely on Skolar Gujarati, so there is no point in explaining how we draw each and every character. They were drafted already when we started. We <em>only</em> had to make sure the Latin and Gujarati are equally important typographically and that both have a natural style that resonates well with the other.</p>
<p><div class='image'><img src='/blog/assets/2016-Harmonizing-Rasa-Gujarati-and-Yrsa-Latin/Latin-Gujarati-proportion-comparison_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Comparison of potential Latin and Gujarati proportions in a font: the first line shows the Gujarati too small when aligned with the Latin x-height, the second line shows the Gujarati too big when aligned with the Latin cap-height, and the last line shows the proportions we used, with both scripts equally important.</div></div></p>
<p>Specifically, we had to make sure the relative scaling and weights of each script was right. Aligning the Gujarati to the proportional grid of the Latin or vice versa would clearly produce unequal sizing (see the figure above). One script appearing smaller than the other would be an issue of course. Therefore, their relative sizes have been based on comfortable reading experience and typical size expectations of each script.</p>
<p><div class='image'><img src='/blog/assets/2016-Harmonizing-Rasa-Gujarati-and-Yrsa-Latin/Latin-Gujarati-weight-comparison_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Comparison of weight between the two scripts: the first line shows the Gujarati too light compared to the Latin, in the second line the Gujarati is too dark. The third line shows harmonized weight.</div></div></p>
<p>Similarly for the weight, an overly bold typeface will look more important. Once the size was set, Anna corrected the weight of the Gujarati to match with the Latin (see the figure above). At the same time, in order to bring the two styles closer together, she increased the contrast between thick and thin bits in the Gujarati (see number 5 in the last figure). It is important to note that the stress in Indic scripts goes in the opposite direction to that of Latin (see the figure below) and increasing contrast or boldening has to respect this.</p>
<p><div class='image'><img src='/blog/assets/2016-Harmonizing-Rasa-Gujarati-and-Yrsa-Latin/Latin-Gujarati-stress-comparison_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Stress axis in Latin is transitional with a variety of angles while Gujarati maintains the same angle.</div></div></p>
<p>Yrsa Latin is a transitional design, so some letters have oblique and some have vertical stress. This is not very common in Gujarati which usually follows a fairly consistent oblique angle. Transitional contrast would be alien to this script, so we decided to stick with a solution typical to Gujarati. In the end, we are designing a typeface for continuous reading, not an experimental display type family.</p>
<p><div class='image'><img src='/blog/assets/2016-Harmonizing-Rasa-Gujarati-and-Yrsa-Latin/Skolar-Gujarati-Rasa-Gujarati-comparison_big.svg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Smaller stylistic changes between Skolar Gujarati (top) and Rasa Gujarati (bottom)</div></div></p>
<p>After the important bits were out of the way, we could play with stylistic details. These might not matter much in small sizes on screen, but we wanted the fonts to look great even in print and in headlines. Here are some of the smaller stylistic changes (see the figure above): the softer endings of Skolar were removed (1), the typical Gujarati foot (aka flick or vanaak) has changed (2) as well as the short in-strokes in ‘pa’ and ‘ma’, both are simpler and relate better to the other endings (3), and the knots are more triangular if ever so slightly (4).</p>
<p>To conclude, one needs to know very well how to shape a script to make it resonate with another. When done wrong, it creates something that looks harmonised to a Latin-script designer, but comes across as a clunky pastiche to Gujarati readers (and vice versa!). Let’s hope, we are on the right track.</p>
</content>
<updated>2016-01-20T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2016/01/11/Rosetta-turns-five</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2016/01/11/Rosetta-turns-five"/>
<title>Rosetta turns five</title>
<content type="html"><p>It is five years today since we started Rosetta and I would like to take the opportunity to thank all our supporters, the moral ones who encouraged us with their kind words and of course our loyal customers who have been buying every font we release. We do not take that for granted!</p>
<p>In these five years, we have been working with over 16 designers to produce their fonts for over ten different world scripts. Broken down by scripts, we released an impressive number of 21 type families for retail and there is more to come. Add some exciting custom work we have done, but cannot talk about, and two open-source projects which you can see on <a href="http://rosettatype.github.io">GitHub</a>. That is not too bad at all.</p>
<p>But it was never about churning out fonts. Although we refer to Rosetta as a publisher, we think of it as a platform. The notion is tied with a sense of design community and expanding knowledge. Our designers get extensive support in sometimes endless, and almost always painful, iterations that lead to a release of their typeface. And that typeface remains their property! The fonts are almost exclusively produced in-house and there are easier things than engineering complex Asian scripts. This way, slowly and carefully, an expertise has been developed, both ours and that of the associated designers. Thanks to that we can manage major custom projects together, and teach others. It is these largely unseen operations and explorations, expanding our knowledge base, what becomes the most rewarding in the end. And it is a great honour to see this recognized in the wider type community.</p>
<p><div class='image'><img src='/blog/assets/2016-Rosetta-turns-five/Rosetta-turns-five_big.jpg' title='' width='940'><div class='imageDescription'><strong>Figure:</strong> Some of the people of Rosetta (left to right, only those facing the camera): Anna Giedryś, Sláva Jevčinová, Vaibhav Singh, Titus Nemeth, David Březina</div></div></p>
<p>In an <a href="https://www.myfonts.com/newsletters/cc/201306.html">interview with Titus, Vaibhav, and me</a> for MyFonts in 2013, Jan Middendorp asked us a very simple and obvious question:</p>
<blockquote>
<p>The Rosetta collection comprises fonts for Arabic, Armenian, Cyrillic, Devanagari, Greek, Gujarati and of course the Latin script. Is there a viable market for each of those scripts — at least enough to earn back costs — or are some of your choices purely idealistic?</p>
</blockquote>
<p>The question took me by surprise. Oddly enough, I have never seriously thought of viability and markets. Business plan, what is that?! I just hoped it will work out somehow!</p>
<p>Of course, I had a very good idea of what we <em>should</em> be doing. The idea of a digital foundry focused on more than Latin fonts was with me since I became interested in Indic scripts (Fiona Ross and Jo de Baerdemaeker shall be forever blamed for sparking that interest). We mused about it with friends – namely with Rob who runs the one-and-only <a href="http://motaitalic.com">Mota Italic</a> from India now and <a href="http://www.typojo.com">Jo</a> first-class researcher into Tibetan and Mongolian, and <a href="http://uk.linkedin.com/in/fermello78/">Fernando</a>, who works for FontSmith during the day, but is also an excellent designer of Tamil and Malayalam fonts. And I should not forget Veronika and José from <a href="http://type-together.com">Type Together</a> who helped starting the foundry and are now pursuing their own non-European fonts.</p>
<p>The idea was to have a place where we could release our work in the highest standard we could achieve, where it would be well presented with as little skewed marketing as possible, where no idiotic managers would take advantage of our labour of love, and where informed people would hold the steering wheel. Or in other words, where producing new fonts for typographically underserved languages was not a checkbox to be ticked, a means to a higher stock value, or a cheesy charitable mission, but a solid work and passion in the first place. No objection to making money along the way, of course.</p>
<p>To what extent we managed to do that is up to others to judge. Back in 2013, in the interview, I replied to Jan honestly. I simply did not know what else to say:</p>
<blockquote>
<p>Our choices are always idealistic. And sometimes it does feel we arrived too early for a party, but that’s part of the game, isn’t it?</p>
</blockquote>
<p>And Jan <a href="https://www.myfonts.com/newsletters/cc/201306.html">generously concluded</a> the whole interview and my systematic naivety in particular.</p>
<p>Nonetheless, looking at it now, when we have much better idea of what we want and where we are going, I think I cannot do better than just stick with the answer. In the next five years we hope to learn a bit more, share a bit more, and keep arriving early for world-script parties.</p>
<p><em>Please, do let us know if you have any suggestions as of what party that should be and what music shall be played.</em></p>
</content>
<updated>2016-01-11T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2015/11/25/Holiday-giveaway</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2015/11/25/Holiday-giveaway"/>
<title>Holiday giveaway</title>
<content type="html"><p>At Rosetta we are not exclusively subscribed to just one spiritual concept, but as the festive season is approaching we would like to continue our tradition and share some of our nicely designed material gifts with you.</p>
<p><div class='image'><img src='/blog/assets/2015-Holiday-giveaway/Holiday-giveaway.png' title='' width='610'></div></p>
<p>We will give away <strong>two pieces of merchandise of your choice</strong> with every standard font license purchased before December 25th. You can keep them both or share them with a loved one, and if they live far away, just let us know and we’ll arrange separate shipments. Once you make the order, we will be in touch via email to settle the details.</p>
<p>btw. you can win a set of Nassim and Huronia posters, one of the last copies of the Specimen of text typefaces, and our sketchbook specimen every week if you share this promo on Twitter, Facebook or from our newly launched Instagram page. Just click one of the buttons below. Make sure that you use the hashtag <strong>#rsttgoodies</strong>!</p>
<p><br>
<div class="socialMediaLinks">
<a href="https://twitter.com/share?url=http%3A%2F%2Frosettatype.com%2Fblog%2F2015%2F11%2F25%2FHoliday-giveaway&text=Happy%20typographic%20holidays!%20Get%20free%20merchandise%20with%20any%20font%20order%20from%20%40rosettatype%0A%20%23rsttgoodies" class="twitter button">Share on Twitter</a>
<a href="https://www.facebook.com/sharer/sharer.php?u=http%3A%2F%2Frosettatype.com%2Fblog%2F2015%2F11%2F25%2FHoliday-giveaway" class="facebook button">Share on Facebook</a>
<a href="https://www.instagram.com/p/-ga_IAwiZA/?taken-by=rosettatypefoundry" class="button">Share on Instagram</a>
</div>
<br>
<br></p>
<h3>Rules</h3>
<p>The competion starts on Wednesday, November 25th and ends Friday, December 25th 2015. Eligible to enter is everyone who is a person (I’m looking at you twitter bots). Shares on the above mentioned platforms enter the competition, winners will be picked and notified each Wednesday and the last week on Friday.</p>
<p><div class='image'><img src='/blog/assets/2015-Holiday-giveaway/Holiday-giveaway_merchandise.jpg' title='' width='610'></div></p>
</content>
<updated>2015-11-25T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2015/10/07/Clone-Rounded</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2015/10/07/Clone-Rounded"/>
<title>Clone Rounded</title>
<content type="html"><p>Clone is a type family by Lasko Dzurovski from Macedonia. The lovechild of cyber-culture and genetic font modification takes inspiration from coding, technology and architecture. A quasi-monospaced typeface that gives a nod to the quirkiness of engineered fonts without sacrificing a natural reading experience. Biomechanical future meets CAD blueprints. The first generation of Clone has rounded forms, the next one is already in the making. Stay tuned.</p>
<p>Clone is currently offered in two versions: Clone Latin and Clone PE. <strong>Discounted presale of Clone PE</strong> supports Latin and Cyrillic only, with the Greek coming soon as a free update. All fonts include a healthy dose of typographic extras!</p>
<p><a href="https://rosettatype.com/Clone" class="button" style="margin: 2em 0;">
<span class="innerText">Visit the Clone microsite »</span>
</a></p>
<p><div class='image'><img src='/blog/assets/2015-Clone-Rounded/Clone_previews_1_big.svg' title='' width='940'></div></p>
<p><div class='image'><img src='/blog/assets/2015-Clone-Rounded/Clone_previews_2_big.svg' title='' width='940'></div></p>
</content>
<updated>2015-10-07T00:00:00Z</updated>
<author>
<name>David Březina</name>
</author>
</entry>
<entry>
<id>tag:old.rosettatype.com,2005:BlogPost//2015/09/01/Introducing-Yrsa</id>
<link rel="alternate" type="text/html" href="https://old.rosettatype.com/blog/2015/09/01/Introducing-Yrsa"/>
<title>Introducing Yrsa</title>
<content type="html"><p>Yrsa is an open-source/libre project we have just started with generous financial support from Google Fonts. The typeface is going to support some 92+2 languages in Latin and Gujarati scripts and will be freely available from the Google Fonts directory, once it is ready. Design and production are done in-house at Rosetta, by Anna Giedryś and me (David Březina).</p>
<p><div class='image'><img src='/blog/assets/2015-Introducing-Yrsa/Yrsa-corrections_big.jpg' title='' width='940'></div></p>
<p>What makes Yrsa different is the design approach. It is a deliberate experiment in remixing existing typefaces to produce a new one. As such, we find it fascinating and… honest.</p>
<p>Let me explain what I mean by that. It is not uncommon in our profession to use previous typefaces as a starting point for something new. Stanley Morison took Monotype’s Plantin as the basis for Times New Roman (1986), Gerard Unger speaks openly of reusing drawings of his former designs, and I suspect there are many others. And it does make sense. Type design is a time consuming activity and there is no need to reinvent the wheel over and over again. However, using someone else’s outlines is not a concept that appeals to everyone. Besides legal issues, personal integrity and the strive for originality seem to be the most common concerns. But maybe it is not all black and white.</p>
<p>Gerrit Noordzij (1991) points out that “writing is a convention. […] unconventional writing is no writing at all.” This also applies to fonts. In order to decode a message set in a particular typeface, the letters need to resemble the ones we already know, either from handwriting or from existing typefaces. In this sense every typeface is a revival. It cannot not be. Every type designer knows that, most have probably encountered it, yet very few seem to acknowledge that in their work. Would it affect anyone’s personal integrity if the sources of inspiration were more discernible? Is it possible to do that at all? Would such a typeface be perceived as less original by the customers? Would it reduce the sales? I do not know. What I know is that the design process is too often portrayed as if it was plucked out of thin air. It was not.</p>
<p>Just to be clear, this is not a manifesto for plagiarism. A truly creative person will always find their own voice, sufficiently distanced from everyone else&#39;s. It is a matter of common decency to not benefit from other people&#39;s work without their consent. Regardless if this is permitted by law or if it is an improvement of the corresponding work.</p>
<p>In his excellent article, Jan Michl elaborates on this issue and suggests that we should try to <a href="http://janmichl.com/eng.redesign.html">see design as redesign</a>. I could not agree more. Yrsa is an opportunity to play with that idea in practise. It is a redesign of contemporary typefaces.</p>
<p>The Latin part of Yrsa will be based on <a href="http://sorkintype.com/fonts.html#mw">Merriweather</a> by Eben Sorkin. It has been released under <a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;id=OFL">SIL Open Font License</a> which allows us to modify and release the design under a new name. The Gujarati will be based on my own <a href="https://www.rosettatype.com/Skolar#gujarati">Skolar Gujarati</a>.</p>
<p><div class='image'><img src='/blog/assets/2015-Introducing-Yrsa/Merriweather-Yrsa-comparison_big.svg' title='' width='940'></div></p>
<p>The illustration shows Merriweather (top) compared to an initial sketch of Yrsa (bottom). The ascenders will be taller (1), the serifs will be bracketed (2 &amp; 5), the head serifs will be less dominant while the outstroke in the ‘u’ (and consequently in the ‘a’) will become more prominent (2). We will also make the terminal in the ‘r’ a bit stronger (4) and simplify the ‘j’ (3). And finally, the counters will be more squarish with a bit ‘less dynamic’ modulation (6).</p>
<p>Our hope is that we will not step on anyone’s toes, i.e. into the uncomfortably immediate vicinity of other designs, while redesigning from Merriweather. We are aware of typefaces with a similar spirit (e.g. Milo Serif or Guardian Egyptian) and are making sure we keep a respectful distance. This is less of a problem with Gujarati where the stylistic space is much less populated.</p>
<p>Wish us luck. That is it for now. You can find the project on <a href="http://rosettatype.github.io">GitHub</a> already.</p>
<p>We intend to write a little series to document the progress. In the next article, we will present the Gujarati sketches together with some considerations regarding the harmonization of both scripts.</p>
<h3>References</h3>
<p>Michl, Jan. 2002. On Seeing Design as Redesign : An Exploration of a Neglected Problem in Design Education. <a href="http://janmichl.com/eng.redesign.html">http://janmichl.com/eng.redesign.html</a>.</p>