Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acknowledge petme2y.tff font usage, or choose another font. #3

Closed
sausagejohnson opened this issue Nov 18, 2018 · 14 comments
Closed

Acknowledge petme2y.tff font usage, or choose another font. #3

sausagejohnson opened this issue Nov 18, 2018 · 14 comments

Comments

@sausagejohnson
Copy link
Collaborator

Need acknowledgements page?

@gardners
Copy link
Contributor

If the font requires it, then, yes, of course we will acknowledge.

@sausagejohnson
Copy link
Collaborator Author

This is the source page for the font:
https://www.kreativekorp.com/software/fonts/c64.shtml

The readme states it as a free license and that:

  1. The User may not sell copies of the Software for a fee.

1a. The User may give away copies of the Software free of charge provided this license and any documentation is included verbatim and credit is given to Kreative Korporation or Kreative Software.

  1. The User may not modify, reverse-engineer, or create any derivative works of the Software.

  2. Any Software carrying the following font names or variations thereof is not covered by this license and may not be used under the terms of this license: Jewel Hill, Miss Diode n Friends, This is Beckie's font!

3a. Any Software carrying a font name ending with the string "Pro CE" is not covered by this license and may not be used under the terms of this license.

  1. This license becomes null and void if any of the above conditions are not met.

  2. Kreative Software reserves the right to change this license at any time without notice.

@gardners
Copy link
Contributor

Hmm... That's all a bit complicated and restrictive. Of course, these limitations are different from limitations on the use of the font, but we really don't want to mess with a font with a seemingly potentially litigious or controlling approach. This one looks like it will be easier to work with:

http://style64.org/c64-truetype

I've sent a contact request to them.

Here is another that is self-proclaimed free-ware without restrictions:

https://www.dafont.com/commodore-64.font

Paul.

@sausagejohnson
Copy link
Collaborator Author

sausagejohnson commented Nov 19, 2018

Yes, and it's not clear what "the software" is in this case. Software carrying the font or the font itself.

I came across both the fonts you mentioned. The style64 one hints at c128 characters for the future, but it's not the case now.

And then there's Devin Cook's font you mentioned. This is C64 sized as well. No C128 font, which is pretty much (exactly?) like the C65.

@gardners
Copy link
Contributor

Ah, C128-sized as in 80-column aspect ratio?
Maybe there is a way to tell latex to change aspect ratio of fonts?

@sausagejohnson
Copy link
Collaborator Author

Yep 80 column. I'll see if the aspect can be changed on a font. If not, we'll keep this issue as a reminder to hunt for another Commodore 80 column font.

Alternatively we can get in touch with the KreativeKorp guys and get their advice on what is possible.

@gardners
Copy link
Contributor

gardners commented Nov 19, 2018 via email

@Edilbert
Copy link
Collaborator

I created a new font for the use in this manual and called it "mega.ttf".
So we don't need PetMe fonts anymore.
Furthermore I can expand it, e.g. make a narrower 80 column font or add more characters.
This first version is for the 95 ASCII characters only. PETSCII π is mapped to ~
so you have to insert the tilde character in your editor, to get a π in the
screen output.

@sausagejohnson
Copy link
Collaborator Author

@Edilbert just wondering, do you make it from scratch or use another font as a base? We should probably acknowledge the source if so.

@sausagejohnson
Copy link
Collaborator Author

But thanks for this. Fonts have been dogging me.

@Edilbert
Copy link
Collaborator

@sausagejohnson I wrote a C program, that reads the image of a C= character ROM, extracts the bitmaps for the characters and writes a fontfile for bitmap fonts. I chose the "bdf" format. This can be used directly in some UNIX/Linux applications or be converted to other font formats by several font converters, like bdftopcf and many more. Then I used the program FontForge to read my bdf file, vectorize it with the plugin "autotrace" and do all the necessary adjustments and by hand.
But I plan to expand my C program, so that it can produce a ttf file. Then I could add features, like visible scan lines or produce a whole font family with different strokes and attributes, like bold italic, etc.

@sausagejohnson
Copy link
Collaborator Author

Ah that's awesome good job. I'll check it out with some of the listings. The asterisk was a headache for us before.

@Edilbert
Copy link
Collaborator

Thanks. The asterisk issue was not caused by the font. The \lstnewenvironment has apparently some special handling for operators like * / - and also for blanks. I solved the issue with the defintion:
literate={*}{*}1{-}{-}1{/}{/}1{{\ }}{{ }}1
which tells the environment to print the characters instead of interpreting them.

@sausagejohnson
Copy link
Collaborator Author

Right. See that's the kind of LaTeX dark magic I just can't fathom.

dansanderson added a commit that referenced this issue Feb 3, 2023
dansanderson added a commit that referenced this issue Sep 15, 2023
This revises the User's Guide in preparation for the v0.96 release and new printing for batch #3 delivery.

Goals for this revision:
* Focus on the MEGA65 production model.
* Focus on new users.
* Update procedures and screenshots to represent the most recent best practices and v0.96 behaviors.
* Enhance information about upgrading the platform components, including how to register with Filehost and get the latest release package.
* Extend information about using disks and disk images.
* Give new users enough information to start finding and downloading software and loading it onto their computer.

This also includes an editing pass over the BASIC reference, mostly style consistency and minor factual corrections.

Still to-do: information on features still in progress, including slot 0 flashing, Ethernet file transfer, and M65Connect. LaTeX code style issues were identified in code review that will be addressed in separate commits, so they're not squashed with this one. In particular, I want to address line wrap style with an auto-format solution that needs testing to make sure it doesn't break our listing environments.
ki-bo pushed a commit to ki-bo/mega65-user-guide that referenced this issue Jan 16, 2024
This revises the User's Guide in preparation for the v0.96 release and new printing for batch MEGA65#3 delivery.

Goals for this revision:
* Focus on the MEGA65 production model.
* Focus on new users.
* Update procedures and screenshots to represent the most recent best practices and v0.96 behaviors.
* Enhance information about upgrading the platform components, including how to register with Filehost and get the latest release package.
* Extend information about using disks and disk images.
* Give new users enough information to start finding and downloading software and loading it onto their computer.

This also includes an editing pass over the BASIC reference, mostly style consistency and minor factual corrections.

Still to-do: information on features still in progress, including slot 0 flashing, Ethernet file transfer, and M65Connect. LaTeX code style issues were identified in code review that will be addressed in separate commits, so they're not squashed with this one. In particular, I want to address line wrap style with an auto-format solution that needs testing to make sure it doesn't break our listing environments.
dansanderson added a commit that referenced this issue Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants