The design discussion with Claude that produced the documents here, kept because the reasons for a decision matter as much as the decision. Tool calls, file edits and command output are left out; what remains is what was asked and what was answered. Session 8d97a797-a676-4df6-afff-e48c01df3ae4.
This is just a fun thread to take over the fonts and screen size form the main thread.
I'll look at the project notes and files to pick up where the fonts and screen size discussion stands.
I've picked up the fonts and screen size thread. Nothing has changed yet. Here is where it stands, from the design doc and the font folder.
Screen size - The design mode is 640 by 480 at 60 Hz at stock clock on the RP2350B. The monitor does the enlarging. - A text line can be 8 to 16 scan rows tall. That gives 80 columns by 30 to 60 lines. - 800 by 600 would need a mild overclock. 1024 by 768 and above need a voltage boost and are ruled out for a school build. - On the Pi Zero 2 W option, any HDMI resolution works, in a window or full screen. - A plain frame buffer mode is kept open alongside the text mode. A 320 by 240 doubled buffer fits easily, and so does a full 640 by 480 at 4 bits per pixel.
Fonts - The text mode uses a character map at 0xF000 and a rewritable 256-glyph table at 0xE800, in the BBC VDU 23 byte format. - There are two redrawn 8 by 8 fonts in the font folder. One is a light font with 1-pixel strokes. The other is bold, with 2-pixel strokes in Acorn proportions. - The font2tab.py script converts them to tables. The specimen page is at https://claude.ai/artifact/De36exdVjBvgdLVVaL71QE. - The genuine BBC glyphs are planned as an optional add-on, with the UK section 55 copyright note attached.
Possible next steps - Render both fonts at real size on a simulated 640 by 480 screen. This would show 30, 40 and 60 line layouts so you can judge what reads well from across a classroom. - Finish the glyphs above ASCII, such as box drawing and block graphics for bar charts. - Write the scanline renderer in C for both the Pico and Linux, so it can be tested on this machine before the board arrives.
Tell me which one to start, or give me something else to work on.
800 by 600 would need a mild overclock. 1024 by 768 and above need a voltage boost and are ruled out for a school build no - we will allow this. They've got to be able to handle a hot soldering iron, nothing is risk free
I'll update the design doc's resolution bullet and the memory note so the higher modes are allowed options.
I've updated the design doc and my project notes. The design now treats the overclocked display modes as allowed build options.
What the doc now says - The default stays at 640 by 480 at stock clock, because every monitor accepts it. - 800 by 600, 1024 by 768 and 1280 by 720 are selectable options. The last one runs the chip at 371 MHz with a core voltage boost. - Your reasoning is recorded as the decision: if a builder can handle a hot soldering iron, they can handle an overclocked chip.
What actually limits the bigger modes is memory, not clock speed. - Text mode needs no frame buffer, so the bigger modes work at any size. They give 100, 128 or 160 columns of characters. - A frame buffer has to fit in the Pico's memory alongside the CPU's 128 KB. At 1024 by 768 that allows 1 bit per pixel, or 4 bits per pixel with pixels doubled. At 1280 by 720 it allows 1 bit per pixel.
can I see https://github.com/ivop/8x8-fonts as minatges
I'll fetch that repo, render its fonts as images, and put them on a page for you.
The repo already ships about 2,000 preview images across thousands of fonts. I'll check how they're organised.
The repo already has one preview image per font, 2,061 in all and under 2 MB. I'll build a searchable gallery page from them, grouped by machine.
Most previews are dark ink on white, and 87 are inverted. I'll normalise them all to the same ink colour on a dark screen panel, then build the gallery.
The gallery is up: https://claude.ai/artifact/UGEAMwEnKREUgVauj6btfy
It shows all 2,061 font previews from ivop/8x8-fonts, grouped by machine.
The page is private until you share it. I also saved this conversation into the design folder with the stash script, as usual.
So the fonts that you've generated are very nice. Um, they are quite BBC-like, and that's a nod to um, the history around Cambridge, UK, um, and Raspberry Pi that obviously is um, all linked. So the choice is to either continue with the fonts that you've got and polish them a bit, or to look at that page you've just given me of all of the possible 8x8 fonts and pick some that are freely licensed and um, will work for us. So, are there any very close to the BBC fonts that have free licenses?
I'll check the licences on the BBC-style fonts we already found, and look for others in the gallery's sources.
The repo includes the real BBC MOS 1.20 ROM font. I'll measure every font against it pixel by pixel, then check licences for the closest ones. First I'll load the web tools.
Now I'll measure. First a look at the file formats.
Every close match turns out to be a copy of the Acorn font itself. I'll check which glyphs differ in the Unlicense copy, and the licence on Damien Guard's FontStruct version.
No freely licensed font is close to the BBC font unless it is actually a copy of it. I compared about 2,000 fonts pixel by pixel with the real BBC Micro ROM font, which the repo includes. Every close match turned out to be the Acorn font itself with a different label.
The free-labelled copies - coraxcorvidae's BBC fonts, under the Unlicense. Its default font is the Acorn font with only four symbols changed: the apostrophe, caret, backtick and vertical bar. The uploader collected it from public domain disks, but they never owned it. Their Unlicense cannot give away Acorn's rights. - Damien Guard's FontStruct "BBC Micro", under CC BY-SA. It is also a trace of the system font, so it has the same problem. It also requires attribution, and anything derived from it must use the same licence. - Other matches, such as an Atari copy, some ZX conversions and the Archimedes fonts, are copies with no licence at all.
So none of these is safer than the original. What lets us use the BBC look is still the UK rule from earlier. Section 55 of the Copyright, Designs and Patents Act allows a typeface to be copied 25 years after it was first sold.
What this means for our own fonts - Our light font is fully our own. It shares no glyph exactly with the BBC font. - Our bold font is not an independent design. It matches the BBC font exactly on 54 of the 94 printable characters, including most of the lowercase. Some overlap is unavoidable at 8 by 8 pixels with 2-pixel strokes. Even so, it is far more than any other design in the collection. The closest independent font, Lander Bold from Damien Guard's ZX Origins set, matches on 36.
My recommendation - Keep our light font as the clean default and polish it. If you want a bold default too, redraw the bold font so it shares far fewer glyphs with the Acorn one. - Offer the BBC look as the optional add-on, as planned. Use the coraxcorvidae copy of the Acorn font for it, because it is a convenient public domain-labelled file. Attach the section 55 explanation, not the Unlicense, as the reason it is allowed.
I've added these findings to my project notes and saved this conversation into the design folder.
Let's see how both of these go. Um, that is, we will keep both the bold and the light and we'll change them and we will see whether the bold we keep or whether we just have the light. The main thing on the light is the width. The bold one, I think, has two pixels always gap between characters and um, the light one doesn't. It has one pixel. It looks very crowded. I think that although we will offer zero padding gaps, um, I've lost your page now, um, but you gave me a different number of padding gaps from instead of having eight, we could have nine, ten, twelve. Um, so we probably won't go for eight in its um, display format, um, and that sorts the vertical direction out, but in the horizontal direction, um, it's still too crowded, the light one. So can we um, trim one from the width of all of the light ones?
I'll look at the light font, narrow every glyph by one column so there's a 2-pixel gap like the bold one, then show you the result.
I'll rebuild that page with four faces: Acorn, bold, the old light and the new narrowed light. The narrowed light will be the screen's default, at 10 rows per line.
The source is in the main session's scratchpad. I'll copy it here so the main thread's file stays untouched, then patch the copy.
I've narrowed the light font by one column. It now has the same 2-pixel gap between characters as the bold one.
The font page has been updated at the same link: https://claude.ai/artifact/De36exdVjBvgdLVVaL71QE
It shows the Acorn font, bold, the old light and the new light side by side. The 80-column screen now opens on the new light font at 10 rows per line. You can still switch it to 8, 9 or 12.
What changed in the light font
- Most glyphs lost their centre column automatically. That covers the round letters, most digits and most lowercase, and it keeps their shape.
- Glyphs with a centre stroke, such as T, I, Y, +, ! and the vertical bar, can't be symmetric in 6 columns. They are now 5 wide, centred on column 2.
- About 40 glyphs were redrawn by hand because removing a column broke them. These were mainly the diagonals and the wide letters: / \ 0 4 7 < > M N V W X Z v w x z, plus some punctuation.
- M and W now use a two-pixel centre, which reads well at 6 wide.
- The old 7-column version is kept in the font folder as blink8x8-7col.txt for comparison. The bold font is unchanged.
What to look at on the page: check whether the centre-stroke letters, T, I and Y, look slightly off-centre or too narrow in running text. That is the main compromise of an even width.
The narrowed light is a big improvement and it's probably the right thing to go for, as you say, um, because we can just switch in the bold one from the BBC if that's what people really want. But otherwise, it's got enough of a nod to the um, 8 bit days as it stands. Um, a few things though. Um, modern fonts have the normal apostrophe as a straight vertical and not as a forward tick. So you have a straight vertical and a back tick characters on normal fonts as you've drawn in the box underneath. Um, other things are I think we can make the semicolon full stop lighter. Um, I think that would look um, less um, less solid, and perhaps uh, what else? Um, we can also get away from the BBC a bit. In the one two seven doesn't need to have anything at all. In fact, we can make that remappable, so it doesn't need to be a a a very BBC like black box. Um, and then uh, yeah let's leave that let's see what that looks like
I'll make the apostrophe straight, lighten the full stop, comma, colon and semicolon to single-pixel dots, and blank character 127. Then I'll republish the page.
I've made all three changes to the narrowed light font and updated the font page at the same link: https://claude.ai/artifact/De36exdVjBvgdLVVaL71QE
The bold font and the old 7-column copy are unchanged. On the page, check whether the single-pixel dots are still easy to see from a distance, especially at the larger line heights.
Let's remove the um, first light version from the comparison when you redraw the page because the second light version is so much better. Oh yes, the bottom of the T, um, what happens if we make the very last pixel one lower down, so more like an inverted F.
I'll move the end of the lowercase t's hook down a row so its foot is flat, and take the old light font off the page.
I've updated the font page at the same link: https://claude.ai/artifact/De36exdVjBvgdLVVaL71QE
The old light version is off the page. The page now compares three fonts: Acorn, bold and the new light, which is the default on the screen view.
I read "the T" as the lowercase t, since that is the one with a hook at the bottom. The pixel at the end of its hook has moved down one row, so the tail now ends in a flat foot on the baseline. With the crossbar above, it reads like an upside-down F:
..#...
..#...
.###..
..#...
..#...
..#...
...##.
If you meant the capital T, say so and I'll change that one instead.
That's really good - we may polish it later when somethign is really working and I can see it in a classroom like envireonment, but our light font should be the main one and the BBC and optional one (just for fun).
I'll record that decision in the design doc and my project notes.
The design doc is updated. My notes say the public site gets rebuilt and deployed after doc changes, so I'll check how that's done.
Blink light is now the official default font. The BBC font is an optional switch-in, just for fun.
What I recorded - The design doc's display section names Blink light as the default from 15 November. It says why: one-pixel strokes, a 2-pixel gap, and no glyph copied from Acorn. It also lists the tweaks you asked for, and says polish waits until you can see it in a classroom-like setting. - The BBC font is described as an optional switch-in. The doc notes that our bold redrawing matches Acorn on 54 of 94 characters, which is why it isn't the default. - The copyright paragraph now includes the licence survey. No free BBC-like font turned up that isn't a copy of Acorn's, so the UK section 55 argument stays the basis for the optional download. - My project notes and the stashed conversation are updated too.
The public site isn't updated yet. I rebuilt it, but the copy onto the web server was blocked by the permission system. To deploy it yourself, run:
! sudo -n cp /tmp/claude-1000/-srv-nvme-blinking/8d97a797-a676-4df6-afff-e48c01df3ae4/scratchpad/site/*.html /net/www/var/www/html/blinkingcomputer.org/ && sudo -n cp /tmp/claude-1000/-srv-nvme-blinking/8d97a797-a676-4df6-afff-e48c01df3ae4/scratchpad/site/conversations/*.html /net/www/var/www/html/blinkingcomputer.org/conversations/ && sudo -n chmod 644 /net/www/var/www/html/blinkingcomputer.org/*.html /net/www/var/www/html/blinkingcomputer.org/conversations/*.html
Alternatively, add a permission rule for that copy so I can deploy it next time.
what does lower case m look like if the top left and the top right are filled? maybe it's more solid
Here is the word "summer mum" with the lowercase m as it is now, and with the top-left and top-right corners filled. Only the top row of the m changes.
now
##### # # # # # # #### # ### # # # # # #
# # # # # # # # # # # # # # # # # # # # #
#### # # # # # # # # ###### # # # # # # # # #
# # ## # # # # # # # # # # # # ## # # #
##### ### # # # # # # # #### # # # # ### # # # #
corners filled
##### # # ## ## ## ## #### # ### ## ## # # ## ##
# # # # # # # # # # # # # # # # # # # # #
#### # # # # # # # # ###### # # # # # # # # #
# # ## # # # # # # # # # # # # ## # # #
##### ### # # # # # # # #### # # # # ### # # # #
The filled version is more solid. It also matches the n, whose top is already a full bar with square shoulders. The current m has rounded shoulders, so it looks lighter and slightly out of family next to the n.
I haven't changed the font file yet. Tell me if you want the filled version, and I'll update the font and the page.
let's drop our bold version and have BBC, our baseline lite as it is at the moment, and some candidates for changes, like the m, as the third option.
I'll rebuild the page with three fonts: the BBC font, our light font as it is, and a candidate light font. The candidate starts with the filled m. I'll also add one more change worth judging, a plainer lowercase r. In the current r the stem sits one column in from the left edge, which looks odd beside n and m.
The font page now shows three fonts: the BBC font, our light font as it stands, and a candidate light font. It's at the same link: https://claude.ai/artifact/De36exdVjBvgdLVVaL71QE
What's on the page - Our bold version is gone from every part of the page. The font file is still in the font folder, but nothing uses it. - The character grid shows BBC, light and candidate in each cell. Cells with a candidate change are outlined. - The 80-column screen can switch between all three fonts. - A new candidate changes section shows each change in a word, with the current font above the candidate.
The candidate changes so far - Lowercase m with the corners filled, as you suggested. It gets square shoulders that match the n. - Lowercase r with its stem on the left edge, like n and m. I added this one myself. The current r has its stem one column in from the left edge, and it looked odd next to n and m in the earlier test. Reject it if you prefer the current r.
current r candidate r
#.###. #.###.
.#...# ##...#
.#.... #.....
.#.... #.....
.#.... #.....
The candidates are kept in a new file, design/font/candidates.txt, so the main font file stays as it is. When you accept a change, I'll copy it into the main font and remove it from the candidates.
let's make the change to r and m. This is too much fun and I should be doing it later.
But whilst I am thinking, the screen sizes are 640x480 and 800×600 (mild overclock when on Waveshare Pico). That's 80 or 100 characters across, more than enough. It's 60 or 80 deep with ten rows per line, again more than enough.
I'll move the new r and m into the main font, empty the candidates file and update the page.
The new r and m are now in the main font. The candidates file is empty, and the font page is updated: https://claude.ai/artifact/De36exdVjBvgdLVVaL71QE
One correction on the screen sizes. At ten rows per line the screens are 48 and 60 lines deep, not 60 and 80. Your figures are what you get at eight rows per line, the BBC spacing.
| Screen | Characters across | Lines at 10 rows | Lines at 8 rows |
|---|---|---|---|
| 640 by 480, stock clock | 80 | 48 | 60 |
| 800 by 600, mild overclock | 100 | 60 | 75 |
Either way there is plenty of room. I've recorded these two as the working modes in the design doc.
The public site still needs the deploy command from earlier before it shows any of today's doc changes.