-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathrelease-early-release-often-version-numbers-for-typefaces.html
455 lines (306 loc) · 34.1 KB
/
release-early-release-often-version-numbers-for-typefaces.html
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
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=510">
<link rel="stylesheet" href="/and/style/in/reset.css" type="text/css" />
<link rel="stylesheet" href="/and/style/in/grid.css" type="text/css" />
<link rel="stylesheet" type="text/css" href="/and/style/in/tellyou.css" />
<link rel="start" href="/and/" title="Home" />
<link rel="alternate" type="application/atom+xml" title="Recent Entries" href="/and/feed/us/recent_entries.xml" />
<script type="text/javascript" src="/and/scripts/being/jquery-1.11.0.min.js"></script>
<script type="text/javascript" src="/and/scripts/being/scripts.js"></script>
<title>I like tight pants and release early release often version numbers for typefaces</title>
<meta property="og:title dc:title" content="I like tight pants and release early release often version numbers for typefaces"/>
<meta property="og:type" content="article"/>
<meta property="og:url" content="http://i.liketightpants.net/and/release-early-release-often-version-numbers-for-typefaces"/>
<meta property="og:image" content="http://127.0.0.1:7999/and/assets/called/openbaskerville_metadata.png"/>
<meta property="og:site_name" content="I like tight pants and mathematics"/>
<meta property="og:description dc:description"
content="I love the way version numbers are used in Open Source. Version 1.0 is not the first version released. Projects are well underway before they reach 1.00—if they even reach it. An open source maxim (by Linus Torvalds of Linux fame) is ‘release early, release often’. Get your code out there before it is perfect, because it can benefit from collaboration from the community. That is why we see version numbers like 0.15.2"/>
<meta name="description"
content="I love the way version numbers are used in Open Source. Version 1.0 is not the first version released. Projects are well underway before they reach 1.00—if they even reach it. An open source maxim (by Linus Torvalds of Linux fame) is ‘release early, release often’. Get your code out there before it is perfect, because it can benefit from collaboration from the community. That is why we see version numbers like 0.15.2"/>
<meta property="fb:admins" content="1488294875"/>
<meta property="mt:entry_basename" content="release-early-release-often-version-numbers-for-typefaces" />
<meta property="dc:modified" content="2013-11-11T12:13:43" />
</head>
<body>
<div id="header" class="container_7">
<div class="grid_2">
<h1><a href="/and/">i . like tight pants . net</a></h1>
</div>
<div class="grid_3">
<ul>
<li ><a href="/and/hybrid-publishing-back-to-the-future-publishing-theses-at-the-kabk">latest</a></li>
<li><a href="/and/about">about</a></li>
<li ><a href="/and/archives">index</a></li>
</ul>
</div>
<div class="grid_2">
<p class="byline" id="recent_entries">New entries published Monday and Thursday, 22:00 CET (<a href="/and/feed/us/recent_entries.xml">RSS</a>)</p>
</div>
</div>
<div id="content" class="container_7">
<div class="sidebar grid_1">
<img src="/and/assets/that/are/pictures/of/author/tellyou.png" style="width:100px;height:100px;" alt="" />
<h4 class="author" property="dc:created" content="2013-09-25T19:53:36">September 25, 2013</h4>
<h4 class="author">by <span property="dc:creator">tellyou</span></h4>
<p> </p>
<hr />
<h4>Other articles by tellyou</h4>
<dl>
<dt><a href="/and/hybrid-publishing-back-to-the-future-publishing-theses-at-the-kabk">Hybrid Publishing Back To The Future Publishing Theses at the KABK</a></dt>
<dd>May 10, 2018 10:07 AM</dd>
<dt><a href="/and/the-underwater-screen-or-lessons-from-wordperfect">The Underwater Screen Or Lessons From Wordperfect </a></dt>
<dd>June 10, 2014 6:21 PM</dd>
<dt><a href="/and/graphic-design-is-a-nostalgic-field"> Graphic Design Is A Nostalgic Field </a></dt>
<dd>February 19, 2014 7:02 PM</dd>
<dt><a href="/and/the-story-of-nokia-microsoft-and-a-1000-hearts-breaking">The Story of Nokia, Microsoft and a 1000 Hearts Breaking</a></dt>
<dd>September 4, 2013 8:02 PM</dd>
<dt><a href="/and/etherpad-or-the-textarea-is-a-lonely-place">Etherpad Or The Textarea Is A Lonely Place</a></dt>
<dd>April 22, 2013 7:59 PM</dd>
<dt><a href="/and/how-it-has-come-about-that-code-hosting-site-github-offers-visualisations-of-typeface-development">How it Has Come About That Code Hosting Site Github Offers Visualisations of Typeface Development</a></dt>
<dd>August 4, 2012 7:28 PM</dd>
<dt><a href="/and/figuring-out-fontforge-pythons-representation-of-postscript-curves">Figuring Out Fontforge-Python’s Representation of Postscript Curves</a></dt>
<dd>June 3, 2012 3:06 PM</dd>
<dt><a href="/and/my-favourite-wikipedia-user-user-rama">My Favourite Wikipedia User User:Rama</a></dt>
<dd>February 23, 2012 10:43 PM</dd>
<dt><a href="/and/making-unix-programs">Making unix programs</a></dt>
<dd>February 2, 2012 12:33 PM</dd>
<dt><a href="/and/installing-compilers">Installing compilers</a></dt>
<dd>December 1, 2011 2:13 PM</dd>
<dt><a href="/and/we-like-tight-pants-and-mathematics">We like tight pants and mathematics</a></dt>
<dd>November 23, 2011 9:27 AM</dd>
<dt><a href="/and/the-voice-of-the-shell">The voice of the shell</a></dt>
<dd>October 26, 2011 7:20 PM</dd>
<dt><a href="/and/learning-how-to-program">Learning how to program</a></dt>
<dd>August 11, 2011 9:04 AM</dd>
<dt><a href="/and/honest-artist-statements">Honest artist statements</a></dt>
<dd>July 9, 2010 4:15 PM</dd>
<dt><a href="/and/juxtapositions">Juxtapositions</a></dt>
<dd>March 14, 2010 8:32 PM</dd>
<dt><a href="/and/heroes">Heroes</a></dt>
<dd>March 8, 2010 7:06 PM</dd>
</dl>
<h4>tellyou’s comments</h4>
<ul>
<li>Hey Silvio, thanks for your comment. Coincidentally, Ned’s comment higher ... <a href="/and/hackers-culture-and-the-fear-of-wysiwyg#comment-319" title="full comment on: Hacker Culture and the Fear of WYSIWYG">read more</a></li>
<li>There is weird paradox here: When learning programming with Python, ... <a href="/and/48-hours-of-writing-stylesheets-with-etherpad-and-a-gong#comment-265" title="full comment on: 48 Hours of Writing Stylesheets with Etherpad and a Gong">read more</a></li>
<li>There is weird paradox here: When learning programming with Python, ... <a href="/and/48-hours-of-writing-stylesheets-with-etherpad-and-a-gong#comment-264" title="full comment on: 48 Hours of Writing Stylesheets with Etherpad and a Gong">read more</a></li>
<li>What do you do with that script? Where does it ... <a href="/and/48-hours-of-writing-stylesheets-with-etherpad-and-a-gong#comment-262" title="full comment on: 48 Hours of Writing Stylesheets with Etherpad and a Gong">read more</a></li>
<li>For the webfonts, ufo2otf will automatically perform a number of ... <a href="/and/ufo2otf-makes-otfs-webfonts-and-css-from-ufo#comment-260" title="full comment on: ufo2otf Makes OTF’s, Webfonts and CSS From UFO’s">read more</a></li>
<li>Isn’t one of the reasons for the small number of ... <a href="/and/no-one-starts-from-scratch-type-design-and-the-logic-of-the-fork#comment-249" title="full comment on: No-one Starts From Scratch: Type Design and the Logic of the Fork">read more</a></li>
<li>I like how Martin Majoor and Ben Archer use the ... <a href="/and/no-one-starts-from-scratch-type-design-and-the-logic-of-the-fork#comment-246" title="full comment on: No-one Starts From Scratch: Type Design and the Logic of the Fork">read more</a></li>
<li>You are on the trolly side of life today, bnf <a href="/and/i-need-my-generic-font-medicine#comment-244" title="full comment on: I Need My Generic Font Medicine">read more</a></li>
<li>And how did you make the video? <a href="/and/48-hours-of-writing-stylesheets-with-etherpad-and-a-gong#comment-224" title="full comment on: 48 Hours of Writing Stylesheets with Etherpad and a Gong">read more</a></li>
<li>So if you were all writing these styles on an ... <a href="/and/48-hours-of-writing-stylesheets-with-etherpad-and-a-gong#comment-222" title="full comment on: 48 Hours of Writing Stylesheets with Etherpad and a Gong">read more</a></li>
</ul>
<hr />
<h4>Other writers</h4>
<ul>
<li>glit</li>
<li>jenseits</li>
<li>habitus</li>
<li>tellyou</li>
<li>baseline</li>
<li>bnf</li>
</ul>
</div>
<div class="post grid_5">
<p class="byline">
<a href="/and/who-makes-standards">Previous</a>
/ <a href="/and/hybrid-publishing-back-to-the-future-publishing-theses-at-the-kabk">Next</a>
</p>
<div class="article grid_3 alpha omega suffix_2">
<h4 property="mt:entry_title">Release Early Release Often Version Numbers For Typefaces</h4>
<article property="mt:entry_id" content="81" class="entry" id="entry-81">
<p>I love the way version numbers are used in Open Source. Version 1.0 is not the first version released. Projects are well underway before they reach 1.00—if they even reach it. An open source maxim (by Linus Torvalds of Linux fame) is ‘release early, release often’. Get your code out there before it is perfect, because it can benefit from collaboration from the community. That is why we see version numbers like 0.15.2</p>
<p>Version 1.0 is reserved for the first version that sees the design intentions crystallised, the functionality in place, and all the first bugs accounted for. It’s what you would have wanted your first release to be like, except that it took all the releases in-between to get there:</p>
<blockquote>We are very pleased to announce the release of IPython 1.0, nearly twelve years after the first release of IPython 0.0.1.</blockquote>
<p>With the Open Baskerville project, we try to use this logic on a typeface. This is a screen shot showing the metadata of our most recently released font:</p>
<p>
<img style="height: 365px; width: 750px; position: relative; margin: 0px; resize: none; zoom: 1; display: inline-block; top: 0px; left: 0px;" src="/and/assets/called/openbaskerville_metadata.png" title="" class="">
</p>
<p class="byline">Version information for the latest Open Baskerville Release (generated from UFO by a script calling FontForge).</p>
<p style="">As you can see, we put the version number right in the font name. This has a practical reason: if there are going to be multiple versions, better make sure the user can tell them apart. But there is also a philosophical reason—we want to make it clear up front that our typeface is developed in an iterative way.</p>
<h4>Iterations in the industry</h4>
<p style="">Typefaces are not usually developed through release early, release often. When a designer or a foundry releases a typeface, it is usually considered finished: sometimes new technological developments warrant a new release, like when fonts first got released as OpenType, or now with the release of webfonts. The constant stream of updates as we know it from software teams is absent from type face development, even though most <a href="http://specimen.meteor.com/about#software" target="_self" style="" title="SPECIMEN">foundries refer to their work as software</a>.</p>
<p style="">There are cultural reasons for this. One is that the industry of type design has until now not really embraced the malleability of digital typography. <a href="http://ospublish.constantvzw.org/blog/typo/appropriation-and-type-before-and-today" style="" target="_self" title="Appropriation and Type – before and today">Ricardo Lafuente asks</a>: why are people who make and sell typefaces still referring to themselves as foundries, as if they are still producing shapes cast in lead?<br>There are also practical reasons: once one has made a layout with a typeface, one does not usually want it to change—especially in the width of the letters and their spacing—as it would change the layout in unpredictable ways.</p>
<p style="">But the ideas in the Free Software and open source movements have found their way into the larger field of culture. Libre fonts—typefaces released as open source—have been a large success in recent years, thanks in no small part to web typography, where for a long time most traditional fonts could not be used because of licensing restrictions. But in the way in which they have are made, the fonts offered on sites such as the Open Font Library and Google Web Fonts do not really offer any innovation over the existing foundry model. They are mostly released by individual authors as a finished package. Projects that think about setting up a framework for collaboration and iterative development are rare—what is telling is that it is often not clear how to contribute back a change to the font.</p>
<p style="">This means libre typography is in a hairy spot. Even if conventional type foundries celebrate a personality focused idea of type design, the actual production takes place in tightly coordinated teams: the type designer can count on other designers to help him flesh out the alphabet, and foundries often reach out to specialists when it comes to specific areas of type design such as kerning and hinting. Individual designers working with free licenses will not be able to match these teams on production quality if they work by themselves. </p>
<p style="">To me it is clear that if libre typography wants to distinguish itself from its traditional counterpart, it needs to embrace alternative conceptions of type design. This can be by focusing on the possibilities of appropriation, remixing and forking of existing typefaces. <a href="http://ospublish.constantvzw.org/workshop/write-me-a-shadow/" style="" target="_self" title="Write me a shadow. OSP @ ESAD Valence">Manipulating existing typefaces</a>, either manually or through <a href="/and/programmatically-manipulating-typefaces" style="" target="_self" title="I like tight pants and programmatically manipulating typefaces">scripts</a>, is only allowed only with libre fonts: the End User License Agreements of most typefaces explicitly forbid modification. Or it can be by embracing new collaboration methods and iterative processes, like we try to do with Open Baskerville.</p>
<h4>How we collaborate on Open Baskerville</h4>
<p style="">It is clear that the right tools for typographic collaboration <a href="/and/the-most-barebones-online-font-editor-possible" style="" target="_self" title="I like tight pants and the most barebones online font editor possible">still need to be built</a>. But like I explain in <a href="/and/how-it-has-come-about-that-code-hosting-site-github-offers-visualisations-of-typeface-development" style="" target="_self" title="I like tight pants and how it has come about that code hosting site github offers visualisations of typeface development">I like tight pants and how it has come about that code hosting site github offers visualisations of typeface development</a>, some elements of the underlying system are already showing up. The open <span style="font-size: 14px;">font format UFO and the versioning process Git are a solid basis to built on.</span></p>
<p style=""><span style="font-size: 14px;"></span>A collaborator on Open Baskerville needs to have an account on Github and the software <a href="http://git-scm.com/" style="" target="_self" title="Git">Git</a> installed on ones computer. She first ‘forks’ <a href="https://github.com/klepas/open-baskerville/" target="_self" style="" title="klepas/openbaskerville">our repository</a> to her Github account: she now has her own version of the revision history. This fork she ‘clones’ to her own computer, using git.</p>
<p style="">The clone consists of all the files of the project, plus the version history. She now goes and makes changes in the files. When she is happy with the changes, she ‘commits’ them, and ‘pushes’ them back up to her Github repository. She opens a ‘pull request’ where she asks for the changes to be merged into our repository.</p>
<p style="">This is a rather involved process. Outside of software developers, not many people have experience with Git. <span style="font-size: 14px;">The existing interfaces to Git are not intuitive to use, being geared to programmers directly editing source files rather than designers using a graphical tool. I think the complexity of this process is one of the barriers to contribution on our project.</span></p>
<p style=""><span style="font-size: 14px;">It will be much more easy to contribute to Open Baskerville once there exist more easy ways to handle the version control. Whether in the form of plugins for font-editors, or a new editor built around collaboration.</span></p>
<p style=""><span style="font-size: 14px;">What will stay the same in the future is the access we have to the revision history, as tracked in Git. In Open Baskerville, we use a set of scripts to be able to quickly generate a font package for each revision: <a href="https://github.com/fonts/skeleton" style="" target="_self" title="fonts/skeleton">we packaged them for other projects to use</a>.</span></p>
<h4>Formalising version numbers</h4>
<p>In computer software the <a href="http://semver.org/" target="_self" title="Semantic Versioning 2.0.0" style="font-size: 14px;">Semantic Versioning</a> standard is an attempt to formalise generally accepted practices for attributing version numbers.</p>
<p>It distinguishes between MAJOR, MINOR and PATCH versions, corresponding to three period separated numbers: MAJOR.MINOR.PATCH (i.e. version 1.5.4) What is the difference between these categories? From Semantic Versioning’s specification, the guideline as to when to augment the MAJOR, MINOR and PATCH versions:</p>
<blockquote>
<ol>
<li style="font-size: 14px;">MAJOR version when you make incompatible API changes,</li>
<li style="font-size: 14px;">MINOR version when you add functionality in a backwards-compatible manner, and</li>
<li style="">PATCH version when you make backwards-compatible bug fixes.<br style=""></li>
</ol>
</blockquote>
<p>This makes the distinction between how a program is used and how it works on the inside. Changes to the code implementation that don’t change how the program appears to the user, merit only a change in the PATCH version. Adding functionality that appears to the user, without changing existing functionality, merits a MINOR version. Finally, changing the way in which you as a user have to use the program, means updating the MAJOR version.</p>
<p>However, this model does not seem really applicable to type design. This is because every change in the code, influences the visual product with which the designer works. My poster design might break more spectacularly if the fonts metrics change, by messing with my line breaks: but if the axis by which the bar of the e is slanted changes, that does ‘break’, in a more subtle way, my design as well.</p>
<p></p>
<p>This means that for fonts, unlike in software, every version is functionally different. <span style="font-size: 14px;">Another reason why we chose to feature the version number prominently in the name of the typeface.</span></p>
<h4>What the version means</h4>
<p>Resuming the role of version numbers in Open Source, we have seen both the <span style="font-size: 14px;">way in which a version number talks about the mindsets and the aims of a project, and</span><span style="font-size: 14px;"> the more formalistic definition of Semantic Versioning.</span></p>
<p>It is the metaphor of the long road to the first version that I find the most easily applicable to design projects. Every project start with a set of goals, aspirations, challenges. In the context of design, I would then rephrase the different types of version numbers as such:</p>
<ol style="font-size:14px;line-height:18px;">
<li>MAJOR version constitutes a coherent set of design goals,</li>
<li>MINOR version constitutes a discrete goal obtained in pursuing these design goals and</li>
<li>PATCH version constitutes incremental progress toward design goals.</li>
</ol>
<p style="">For example, in Open Baskerville, the major design goal is to recreate Fry’s Baskerville in a way that is usable on the modern web (Version 1.0). As a sub-goal, we are first working to recreate a width faithful to Fry’s surviving specimen (version 0.1), with a system in place to create releases. We logged 83 incremental improvements towards this goal, but we are not there yet (thus, at version 0.0.83).</p>
<p style="">If we ever reach 1.0, what then? Can we think of a new major design goal for the project, or rephrase its design goal? We might want to re-inspire ourselves on other Baskerville variants, for example, and adjust are goals accordingly.<br style="">Where does it end? What is the final number? Is continuing working on one design project for years and years a desirable scenario, in a way that Windows now is at version 8 and Illustrator at version 16?</p>
<p style="">There are arguments against creating too many versions of a design. A design is a product of hopes, aspirations, goals and constraints that exist at a given point. The recent phenomenon of film directors revisiting their older movies and adding contemporary computer effects (not available at the time) has not at all been well received by fans. It shows that the constraints placed upon an artistic project shape it and create its character, and that authors might want to be reticent in revisiting their works.</p>
<p style="">Similar phenomenons exist in software too. People who use many subsequent versions of a software often feel like something gets lost along the way. The initial sense of purpose embodied in a program can give way to what is called ‘bloat’, by adding feature upon feature until it tries . In programmer’s circles, this is known as Zawinski’s law: ‘Every program attempts to expand until it can read e-mail.’ At the same time, using old versions of software is not very practical. They might contain security holes; they might even no longer run on your current operating system.</p>
<p style="">With typefaces we are in luck that they will in most occasions be usable for a longer time. As long as a description of its points exists somewhere—and mankind does not forget <a href="/and/seb-explaining-love-and-bezier-curves" style="" target="_self" title="I like tight pants and seb explaining love and bezier curves" class="aloha-link-text">the mathematics of Bézier curves</a>. So I think I will want for the 1.0 version to be the last. Anyone who has another vision on the design, is <a href="/and/no-one-starts-from-scratch-type-design-and-the-logic-of-the-fork" class="" style="" target="_self" title="I like tight pants and no-one starts from scratch: type design and the logic of the fork">free to fork</a>.</p>
</article>
<h4 class="comments-header">2 Comments</h4>
<div id="comments" class="comments">
<div class="comments-content">
<div property="mt:comment_id" content="232" id="comment-232" resource="/and/release-early-release-often-version-numbers-for-typefaces#comment-232" class="comment">
<div class="comment-editor" property="mt:comment_text">
<blockquote>
It’s what you would have wanted your first release to be like, except that it took all the releases in-between to get there.</blockquote><p>That is what Madonna means, I think, in Like a Virgin: it’s not the first time, yet it’s the first time it works like you want it to work. what the first time should have been like but necessarily could not.
</p>
</div>
<p class="byline" >
<img src="/and/assets/that/are/pictures/of/author/glit.png" width="18" height="18" />
by <a property="dc:creator" href="http://i.liketightpants.net/authors#glit">glit</a> - <a href="/and/release-early-release-often-version-numbers-for-typefaces#comment-232"><span property="dc:created" content="2013-09-05T07:33:51">September 5, 2013 7:33 AM</span></a><br />
<a title="Reply" href="javascript:void(0);" onclick="mtReplyCommentOnClick(232, 'glit')">Reply</a>
</p>
</div>
<div class="comments-parent-container" style="margin-left: 20px;">
<div property="mt:comment_id" content="338" id="comment-338" resource="/and/release-early-release-often-version-numbers-for-typefaces#comment-338" class="comment comment-reply">
<div class="comment-editor" property="mt:comment_text">
Keep it up
</div>
<p class="byline" >
by <a property="dc:creator" href="">Sujon Ahmad</a> - <a href="/and/release-early-release-often-version-numbers-for-typefaces#comment-338"><span property="dc:created" content="2016-11-07T13:25:05">November 7, 2016 1:25 PM</span></a><br />
<a title="Reply" href="javascript:void(0);" onclick="mtReplyCommentOnClick(338, 'Sujon Ahmad')">Reply</a>
</p>
</div>
<div class="comments-parent-container" style="margin-left: 20px;">
</div>
</div>
<a title="Reply" href="#reply">Reply</a>
</div>
<div class="comments-open" id="comments-open">
<h4 class="comments-open-header">Leave a comment</h4>
<div class="comments-open-content">
<div id="comment-greeting"></div>
<form method="post" action="/comments.cgi">
<input type='hidden' name='csrfmiddlewaretoken' value='2M2jHhVrKYN98VsVIJYsKeb1lShsP3v7' />
<input id="id_parent" name="parent" type="hidden" />
<input id="id_entry" name="entry" type="hidden" value="81" />
<div id="comments-open-data">
<div id="comment-form-name">
<div class="alpha grid_1"><label for="id_author" class="span-4">Name</label></div>
<div class="omega grid_2"><input id="id_author" maxlength="300" name="author" required="required" size="30" type="text" /></div>
</div>
<div id="comment-form-email">
<div class="alpha grid_1"><label for="id_email" class="span-4">Email address</label></div>
<div class="omega grid_2"><input id="id_email" maxlength="381" name="email" required="required" size="30" type="email" /></div>
</div>
<div id="comment-form-url">
<div class="alpha grid_1"><label for="id_url" class="span-4">URL</label></div>
<div class="omega grid_2"><input id="id_url" maxlength="765" name="url" size="30" type="url" /></div>
</div>
</div>
<div id="comment-form-reply" style="display:none">
<input type="checkbox" id="comment-reply" name="comment_reply" value="" onclick="mtSetCommentParentID()" />
<label for="comment-reply" id="comment-reply-label"></label>
</div>
<div id="comments-open-text">
<label for="id_text">Text:</label><br />
<p class="byline">For formatting your post, you can use html tags like <p> and <br />. Whitespace for now is eaten up, like in HTML. we are sorry—we will have a more friendly commenting option in place shortly!</p>
<textarea cols="40" id="id_text" name="text" required="required" rows="15" style="width:100%">
</textarea>
<!-- <textarea id="comment-text" name="text" rows="15" style="width:100%;" onfocus="mtCommentFormOnFocus()"></textarea> -->
</div>
<p class="byline" id="comments-open-license">By submitting your comment, you agree to license it under the <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution Share-Alike license</a>, the same license used for the text of the blog.</p>
<div id="comments-open-captcha">
<div class="alpha grid_1"><label for="id_captcha_code">Anti-spam: What is the last name of David?</label></div>
<div class="omega grid_2"><input id="id_captcha_code" name="captcha_code" required="required" size="30" type="text" /></div>
</div>
<div id="comments-open-footer">
<!-- <input type="submit" accesskey="v" name="preview_button" id="comment-preview" value="Preview" onclick="this.form.preview.value='1';" /> -->
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />
</div>
</form>
</form>
</div>
</div>
</div><!-- / comments -->
</div> <!-- / article grid_3 -->
<hr />
</div> <!-- / post grid_5-->
<div class="sidebar grid_1">
<h4>Latest articles</h4>
<dl>
<dt><a href="/and/hybrid-publishing-back-to-the-future-publishing-theses-at-the-kabk">Hybrid Publishing Back To The Future Publishing Theses at the KABK</a></dt>
<dd>May 10, 2018 10:07 AM</dd>
<dt><a href="/and/finding-red-letterboxes-in-belgium">Finding Red Letterboxes In Belgium</a></dt>
<dd>May 10, 2018 10:05 AM</dd>
<dt><a href="/and/the-underwater-screen-or-lessons-from-wordperfect">The Underwater Screen Or Lessons From Wordperfect </a></dt>
<dd>June 10, 2014 6:21 PM</dd>
<dt><a href="/and/hackers-culture-and-the-fear-of-wysiwyg">Hacker Culture and the Fear of WYSIWYG</a></dt>
<dd>May 22, 2014 11:40 PM</dd>
<dt><a href="/and/graphic-design-is-a-nostalgic-field"> Graphic Design Is A Nostalgic Field </a></dt>
<dd>February 19, 2014 7:02 PM</dd>
<dt><a href="/and/who-makes-standards">Who gets to write the web: the power struggles around the standards</a></dt>
<dd>November 20, 2013 9:08 PM</dd>
<dt><a href="/and/ufo2otf-makes-otfs-webfonts-and-css-from-ufo">ufo2otf Makes OTF’s, Webfonts and CSS From UFO’s</a></dt>
<dd>November 5, 2013 8:57 PM</dd>
<dt><a href="/and/no-one-starts-from-scratch-type-design-and-the-logic-of-the-fork">No-one Starts From Scratch: Type Design and the Logic of the Fork</a></dt>
<dd>October 9, 2013 8 PM</dd>
<dt><a href="/and/i-need-my-generic-font-medicine">I Need My Generic Font Medicine</a></dt>
<dd>October 9, 2013 7:55 PM</dd>
<dt><a href="/and/48-hours-of-writing-stylesheets-with-etherpad-and-a-gong">48 Hours of Writing Stylesheets with Etherpad and a Gong</a></dt>
<dd>October 8, 2013 8:06 PM</dd>
</dl>
<h4>Latest Comments</h4>
<ul>
<li><strong>Sujon Ahmad:</strong> Keep it up <a href="/and/release-early-release-often-version-numbers-for-typefaces#comment-338" title="full comment on: Release Early Release Often Version Numbers For Typefaces">read more</a></li>
<li><strong>Carly Durocher:</strong> I really like the stylized penrose triangle would you mind ... <a href="/and/illustration#comment-337" title="full comment on: Illustration">read more</a></li>
<li><strong>michaël:</strong> The recent evolution of MediaWiki is worth mentioning. One of ... <a href="/and/hackers-culture-and-the-fear-of-wysiwyg#comment-336" title="full comment on: Hacker Culture and the Fear of WYSIWYG">read more</a></li>
<li><strong>jaromil:</strong> Check the Linux Action Show on Tomb https://www.dyne.org/software/tomb there can ... <a href="/and/hackers-culture-and-the-fear-of-wysiwyg#comment-335" title="full comment on: Hacker Culture and the Fear of WYSIWYG">read more</a></li>
<li><strong>Ian Hickson:</strong> The member list is the one on the charter (it's ... <a href="/and/who-makes-standards#comment-334" title="full comment on: Who gets to write the web: the power struggles around the standards">read more</a></li>
<li><strong>habitus:</strong> Dear Ian, thank you for taking the time to respond. ... <a href="/and/who-makes-standards#comment-333" title="full comment on: Who gets to write the web: the power struggles around the standards">read more</a></li>
<li><strong>Ian Hickson:</strong> The part about the WHATWG membership is wrong. The WHATWG ... <a href="/and/who-makes-standards#comment-332" title="full comment on: Who gets to write the web: the power struggles around the standards">read more</a></li>
<li><strong>Erik:</strong> Good points. Also: writing UI is hard. <a href="/and/the-underwater-screen-or-lessons-from-wordperfect#comment-327" title="full comment on: The Underwater Screen Or Lessons From Wordperfect ">read more</a></li>
<li><strong>nike shox:</strong> do not want to be t basket vans femme pas ... <a href="/and/no-one-starts-from-scratch-type-design-and-the-logic-of-the-fork#comment-324" title="full comment on: No-one Starts From Scratch: Type Design and the Logic of the Fork">read more</a></li>
<li><strong>Tolan Blundell:</strong> As someone who's written a moderately complex CMS from scratch ... <a href="/and/hackers-culture-and-the-fear-of-wysiwyg#comment-323" title="full comment on: Hacker Culture and the Fear of WYSIWYG">read more</a></li>
</ul>
</div>
</div>
<div id="bar"> </div>
<!-- Piwik, Open Source Analytics,
let’s not give Google more data then necessary! Eric -->
<script type="text/javascript">
var pkBaseURL = (("https:" == document.location.protocol) ? "https://var.schr.fr/piwik/" : "http://var.schr.fr/piwik/");
document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
</script><script type="text/javascript">
try {
var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 2);
piwikTracker.trackPageView();
piwikTracker.enableLinkTracking();
} catch( err ) {}
</script><noscript><p><img src="http://var.schr.fr/piwik/piwik.php?idsite=2" style="border:0" alt="" /></p></noscript>
<!-- End Piwik Tracking Code -->
<!--[if !(lt IE 8)]><!-->
<script type="text/javascript">
(function(){var e=document.createElement("script");e.type="text/javascript";e.async=true;e.src=document.location.protocol+"//d1agz031tafz8n.cloudfront.net/thedaywefightback.js/widget.min.js";var t=document.getElementsByTagName("script")[0];t.parentNode.insertBefore(e,t)})()
</script>
<!--<![endif]-->
</body>
</html>