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
|
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>2025 december adventure — aaoth.xyz</title>
<link href="style.css" rel="stylesheet">
</head>
<body>
<nav>
<ul>
<li><a href="/">home</a></li>
</ul>
</nav>
<h1>la ninpre's december adventure 2025</h1>
<div class="win">
<p><a href="https://eli.li/december-adventure">december adventure</a>
is a <b>low key</b> thingy by eli oat. the goal is to choose a project
and work on it in a relaxed pace.</p>
<p>in this year's decadv i want to work on a project that
i've been postponing for too long now. i'm fascinated
by scripts and writing aystems, both natural and
constructed. over the years i've accumulated a few
writing systems of my own. sadly, i haven't found the
time to document them, but this year i want to try to
change this.</p>
<p>in particular, i want not only to document each writing
system, but to make a computer font for each one.</p>
<p>this log is an <a href="https://journal.miso.town">html journal</a>. here is an <a href="/decadv-2025-atom.xml">atom feed</a> of the log.
</div>
<!--newlog
<article>
<h2 id="2025-12-xx">2025-12-xx</h2>
<div class="win">
<p>
</p>
</div>
</article>
-->
<article>
<h2 id="2025-12-25">2025-12-25</h2>
<div class="win">
<p>
today i didn't do much about the font.
played with sqlite at work. i think it is a very useful little tool.
</p>
</div>
</article>
<article>
<h2 id="2025-12-24">2025-12-24</h2>
<div class="win">
<p>
tweaked some letter shapes today. although, much more needs to be done about that.
i don't quite like the shape of 'y', thinking of making it a bit smaller.
</p><p>
this is actually weird, but i never used the half-horizontal
glyph variants anywhere. i needed them for some reasson
in test version, but for real one i don't think i'll need them.
</p>
</div>
</article>
<article>
<h2 id="2025-12-23">2025-12-23</h2>
<div class="win">
<p>
i've written all the opentype-feature logic, it's <a href="ukarpanghooth.html#playground">live</a>!
see the font repo for all the spicy details.
but seriously, i need now to do the boring part. test, test, test and tweak.
</p><p>
also i want to create a version of the font that is rotated 90 degrees to the left,
because then it'll behave correctly like it should. right now the letter blocks are placed
left-to-right, but they should stack top-to-bottom instead.
since computing is western-oriented (latin-oriented), vertical scripts aren't well supported,
i might have to do this rotation manually for it to work.
</p>
</div>
</article>
<article>
<h2 id="2025-12-22">2025-12-22</h2>
<div class="win">
<p>
added the remaining character variants to the fontforge file!
yesterday before wrapping up for the day i created encoding slots
in fontforge for character variants, but i didn't know
that if these encoding slots have nothing inside, fontforge
won't save them and their names!
so i've written a script to append empty char defininitions to the sfd file.
</p><p>
this means i'm moving to step 5, yay!
</p>
</div>
</article>
<article>
<h2 id="2025-12-21">2025-12-21</h2>
<div class="win">
<p>
i skipped a week or so, because of some sickness (idk what exactly,
flu-like symptoms).
but this day i started working on a font for my first writing system.
i've drawn all the main glyphs, except for numbers.
i had to do four versions of each glyph because of
how the script is going to work.
i've set up <a href="https://git.aaoth.xyz/lipi">a repo</a>
for all fonts to live in.
right now i'm on stages 3 and 4 of <a href="#2025-12-01">the scheme</a>.
initially, i wasted a lot of time because i didn't set up
the units correcly in inkscape.
now i think of making a template for drawing the glyphs.
</p>
</div>
</article>
<article>
<h2 id="2025-12-10">2025-12-10</h2>
<div class="win">
<p>
i've seen some posts on the fediverse that reminded me of something.
i refactored the html of this log so that it conforms to
the <a href="https://journal.miso.town/">journal</a> spec
by m15o. this means we can get atom feed for free!
i've also written a library for parsing html journals. why? i don't know, felt like it.
there is already original implementation, and i won't say it's inferior or something,
but i noticed that it behaves a bit differently than is
specified in the format.
i wrote a little <a href="https://git.aaoth.xyz/html-journal">tool</a> that can be used to make a feed from
html journal file. i've added it to my build script.
my library recognizes a subset of html journal formats,
i've tested it on some other people's journals, some of them don't work.
but i think that if it works with my library, it'll work
with the original as well.
anyway, it was fun.
</p>
</div>
</article>
<article>
<h2 id="2025-12-09">2025-12-09</h2>
<div class="win">
<p>
today is a little meta-day.
i've added a little script to compose new log entries.
see how i said no automation and here i am, writing ed scripts.
oh, btw, i wrote this using ed(1). on workdays i can't use my home pc with a comfy acme.
as i once said, ed(1) is the best text editor for a phone.
no jokes. also it kinda forces you to think what you type and slow down a bit.
every line entered could not be edited with backspace.
once i wanted to write my own ed, but with more powerful regexes and with some features borrowed from sam(1),
like, for example, ability to forget that line terminators exist and treat text as a one-dimensional array of bytes.
but that's for another day maybe.
</p>
</div>
</article>
<article>
<h2 id="2025-12-08">2025-12-08</h2>
<div class="win">
<p>
this was a busy day at work, like all mondays are.
day before i started automatic reconstruction in colmap,
because i figured it would take some time.
actually, it died a few times, there wasn't enough
memory.
i stopped all daemons and closed display server so it could have all power it needs.
and it finished! but the results are quite roughh and noisy. and it took whooping 46GiB of space!
didn't even get close to gaussian splatting. will try that on a lighter dataset.
</p>
</div>
</article>
<article>
<h2 id="2025-12-07">2025-12-07</h2>
<div class="win">
<p>
another one that i've spent with friends.
also i've learned about <a href="https://en.wikipedia.org/wiki/Gaussian_splatting">gaussian splatting</a> and it got me attracted.
i've tried to make a structure from motion in <a href="https://colmap.github.io">colmap</a>, but tinkered with it for a long time without any good results.
it is quite heavy and needs a lot of storage and computing power.
we also tried to do our first linocuts. we've figured out how to cut,
but not so much how to print, that's a thing to learn.
in the evening we went to the swimming pool. i try to add something physical to my life,
otherwise it's just computers and work.
</p>
</div>
</article>
<article>
<h2 id="2025-12-06">2025-12-06</h2>
<div class="win">
<p>
this day i spent time with friends.
we went to a flower market (or a festival, i am not sure how these things are named, flower event).
plants were nice, but the place they choose to host such event wasn't fit for it.
there were narrow spaces between stands, and there were quite a lot of vizitors,
so to see anything or even go through one had to
push through people.
</p>
</div>
</article>
<article>
<h2 id="2025-12-05">2025-12-05</h2>
<div class="win">
<p>i found the thing!
uploaded the picture of it, as well as inscription of what's been cut there.
been a pretty busy day at work, so that's all for today i guess.
</p>
</div>
</article>
<article>
<h2 id="2025-12-04">2025-12-04</h2>
<div class="win">
<p>no writing systems related stuff today, alas.
but i've worked on improving my websiting experience.</p>
<p>i wanted to rebuild this website without any automation
(yeah, this is third time i redo this, but now i literally
write html by hand).
although, i thought, that maybe having cross-links displayed
at the bottom of pages is not that bad. so i added some
shell stuff so these lists could be generated.
i try not to worry too much about how well does it do.</p>
<p>initially, i went with straightforward O(n²) approach
(for each file, for each link, search each file for that link).
but then it occured to me that basically outgoing links,
which are much easier to find can be set as incoming links
to targeting pages.</p>
<p>oh, by the way, the repo is available on my git:
<a href="https://git.aaoth.xyz/aaothxyz-decadv">site sources</a>.</p>
</div>
</article>
<article>
<h2 id="2025-12-03">2025-12-03</h2>
<div class="win">
<p>added pictures for <a href="ukarpanghooth.html">ukarpanghooth</a> script.
i planned to do another one, but didn't manage to find this little trinket i've cut writings on.
</p>
</div>
</article>
<article>
<h2 id="2025-12-02">2025-12-02</h2>
<div class="win">
<p>today i mostly tweaked the website. decided to make it look
like <a href="http://acme.cat-v.org">acme</a> window in which i'm currently writing this sentence :D</p>
<p>css is a bit questionable, but i'll tweak it more as i go.</p>
<p>as a sidenote, it's a bit challenging to work on something while also having
to go to a $dayjob...</p>
</div>
</article>
<article>
<h2 id="2025-12-01">2025-12-01</h2>
<div class="win">
<p>started working on <a href="ukarpanghooth.html">ukarpanghooth</a> description. couldn't do images today, sorry...</p>
<p>also came up with a rough scheme on how to make each font:</p>
<ol>
<li>draw each glyph and glyph variant (inkscape)</li>
<li>save glyphs as individual svg files</li>
<li>load glyphs (fontforge)</li>
<li>tweak position and size (fontforge)</li>
<li>export as ufo (fontforge)</li>
<li>add opentype fea</li>
<li>compile (fontmake/fontc)</li>
<li>test (browser, libreoffice, harfbuzz, pango), looping back to 1-7 as needed</li>
<li>verify metadata and upload</li>
</ol>
</div>
</article>
</body>
</html>
|
