-
Notifications
You must be signed in to change notification settings - Fork 51
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
Comments
If the font requires it, then, yes, of course we will acknowledge. |
This is the source page for the font: The readme states it as a free license and that:
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.
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.
|
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. |
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. |
Ah, C128-sized as in 80-column aspect ratio? |
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. |
Indeed. Or ask the guy who made the free 40 column one how hard it would be
to make an 80 column one.
…On Mon, 19 Nov 2018 at 13:38, Sausage Johnson ***@***.***> wrote:
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.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAonT0MookWqyaaHfd1kI2CKxR7DKHNbks5uwiDEgaJpZM4YnuVy>
.
|
I created a new font for the use in this manual and called it "mega.ttf". |
@Edilbert just wondering, do you make it from scratch or use another font as a base? We should probably acknowledge the source if so. |
But thanks for this. Fonts have been dogging me. |
@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. |
Ah that's awesome good job. I'll check it out with some of the listings. The asterisk was a headache for us before. |
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: |
Right. See that's the kind of LaTeX dark magic I just can't fathom. |
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.
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.
Need acknowledgements page?
The text was updated successfully, but these errors were encountered: