Jump to content

Photo

Bird's nest...


44 replies to this topic

#26 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Thu Jul 13, 2017 5:39 AM

I suggest Mattel's Keyboard Component character set.

#27 Lathe26 OFFLINE  

Lathe26

    River Patroller

  • 2,810 posts

Posted Thu Jul 13, 2017 12:31 PM

I suggest supporting every character in the Unicode 10.0 standard. There are only 136690 characters to support, including emojis. :-P

#28 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Thu Jul 13, 2017 6:01 PM

Those C64 fonts are definitely something I can work with. I've been looking at arcade fonts but it helps to draw from more sources.

 

Is there a bitmap available somewhere that contains the entire Keyboard Component character set? I agree that including it is a must.



#29 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Thu Jul 13, 2017 8:29 PM

Keyboard Component character set:

The exclamation mark is character 33 and 32 is a space.

Attached Thumbnails

  • kc_chars.png


#30 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Fri Jul 14, 2017 12:24 AM

It's a bit blurry but I think I can work with it. Does it include everything from 0..255?

 

This is what I get after some resizing:

 

 

Attached Thumbnails

  • kbc.png


#31 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Fri Jul 14, 2017 1:32 AM

Current state of the bitmap. I' m concerned about the lack of characters in the Keyboard component font before the space character. After drawing the blocks I now understand what's going on there: they're following a simple binary pattern from 0 to 63, once with solid areas and once with dots.

Attached Files


Edited by JohnPCAE, Fri Jul 14, 2017 1:35 AM.


#32 carlsson OFFLINE  

carlsson

    River Patroller

  • 4,398 posts
  • Location:Västerås, Sweden

Posted Fri Jul 14, 2017 2:51 AM

Yeah, it looks like 2x3 semi graphics as used by various Teletext, Videotex etc systems which suggests the Keyboard Component might've been meant to be Videotex compatible. The development of such services begun in 1978-ish, so it fits in the time frame. The other dot patterns I presume are Braille, meant for blind people whose TV sets would emit enough static electricity for every "on" pixel that they could use their fingers to read on the screen. :-)



#33 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Fri Jul 14, 2017 5:55 AM

Yes, the Intellivision was originally planned for Videotex bringing data into the home; ie. news, sports scores, and weather.  North America was behind Europe with this stuff in the early 1980s.  I never thought of braille but it could be.  I'm pretty sure the stock market program that wasn't released used those "braille" characters to plot graphs.

 

edit:  The Keyboard Component has 256 characters including ASCII control codes.  In ASCII the first 32 characters are control codes.

 

Here's another view of the characters not including the control codes.  There are another 32 characters, you can see them in the KC "Owners's Book".  But I'm not sure how to access them in basic.

Attached Thumbnails

  • kc_chars2.png

Edited by mr_me, Fri Jul 14, 2017 6:44 AM.


#34 carlsson OFFLINE  

carlsson

    River Patroller

  • 4,398 posts
  • Location:Västerås, Sweden

Posted Fri Jul 14, 2017 6:13 AM

On second thought, it probably isn't meant to be Braille as it would display the glyphs in a very odd order: A n/a C n/a B I F n/a E n/a D n/a H J G ... etc



#35 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Fri Jul 14, 2017 7:20 AM

Here are the other 32 using a code ie. "chr$(27);chr$(16);chr$(64+x)"

Attached Thumbnails

  • kc_chars3.png


#36 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Fri Jul 14, 2017 9:54 AM

The blocks and dots are following the same binary pattern from 0 to 63, with the bits arranged like this:

 

0   1

2   3

4   5

 

Are those extra 32 characters the control characters from 0 to 31?



#37 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Fri Jul 14, 2017 10:02 AM

No they're not. In fact ascii code 31 generates an accent grave character seen in the first image.

#38 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Fri Jul 14, 2017 10:07 AM

Hmm. Which codes do they represent? If space is 32 then the last dot pattern should be 255. Another question I have revolves around character alignment. I have to be able to accurately place each glyph in the 8x8 box. That's pretty easy with the block and dot patterns, but it's hard with the letters. The letter patterns in the large image seem to have a different alignment than the box patterns, for instance: the letters on the right side seem to span bounding box boundaries.



#39 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Fri Jul 14, 2017 10:17 AM

The large image is actually two images spliced together. They don't line up.

Edit: 255 should be that last 2x3 dot pattern.

Edited by mr_me, Fri Jul 14, 2017 10:27 AM.


#40 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Fri Jul 14, 2017 10:30 AM

Ok. I placed the extra 32 characters after the dot patterns. I'm guessing they're special escape codes that lie outside the 0-255 range. Last question: do the 0-31 control characters have glyphs?



#41 Lathe26 OFFLINE  

Lathe26

    River Patroller

  • 2,810 posts

Posted Fri Jul 14, 2017 10:32 AM

The dot pattern is a superset of Braille.  There are some dot patterns that are not assigned in Braille.  Still, it's pretty cool that they added that.



#42 mr_me OFFLINE  

mr_me

    Stargunner

  • 1,665 posts
  • Location:Ontario

Posted Fri Jul 14, 2017 10:38 AM

The first image was generated by printing chr$(x) starting with x=1 without any spacing. Only chr$(31) left a character.

#43 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Fri Jul 14, 2017 12:03 PM

This is where I am now. I made some small tweaks to the earlier glyphs (e.g. I had missed a lowercase Greek letter) and made certain glyphs look a little better. I also added a few glyphs before the KC font that allow for drawing rounded boxes, and a pointer glyph for drawing rounded balloon windows.

 

Any thoughts on what else we want included? A futuristic font? A western font? A stencil font? If we limit t to 0-9, A-Z, and a-z, there is room for all three with room to spare.

Attached Files


Edited by JohnPCAE, Fri Jul 14, 2017 12:03 PM.


#44 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Sun Jul 16, 2017 1:52 PM

As promised, here are my current Eagle files and Arduino code for my video overlay project. It only has the first half of the CGA font as I haven't implemented anything else yet. It's just proof-of-concept code that outputs the static pattern in the screenshots, but it works. As for the board, I've done a lot of validating and I'm pretty confident that it will give a clean crisp signal (at least, it does when using the included Arduino code).

Attached Files



#45 JohnPCAE OFFLINE  

JohnPCAE

    Moonsweeper

  • Topic Starter
  • 367 posts

Posted Mon Jul 17, 2017 8:22 AM

Dammit. I missed a change to my schematic that I had on my breadboard. It would affect how video would look when the intensity bit was off. Attached is the corrected schematic and board...

Attached Files






0 user(s) are browsing this forum

0 members, 0 guests, 0 anonymous users