vtfontcvt is useful for end users to convert arbitrary bitmap fonts
for use by vt(4). It can also be used as a build tool so that we can
keep the source font data in share/vt/fonts, rather than uuencoded
binaries.
Details
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
usr.bin/vtfontcvt/vtfontcvt.8 | ||
---|---|---|
48 | This should use the .Pa (pathname) macro to make clear that the final dot is not part of the filename: HEX format files must have the file extension | |
54 | "It" is nonspecific. The default is 16. | |
55 | "It" is nonspecific. Font height is set automatically for HEX files with a | |
56 | Seems like this should have markup, but I don't know exactly what to use. .Li # Height: Ar height Untested, there's probably a better way. | |
62 | As above. The default is 8. | |
63 | As above. Font width is set... | |
64 | As above, if we can find the right markup. |
usr.bin/vtfontcvt/vtfontcvt.8 | ||
---|---|---|
51 | mandoc -Tlint points out that "-indent" is a fake parameter. I've been using just .Bl -tag -width "12345678" The 12345678 is just used for an indent width, the quotes are to help indicate it is an argument. | |
66 | mandoc -Tlint detected a missing .El before this line to end the list above. |
usr.bin/vtfontcvt/vtfontcvt.8 | ||
---|---|---|
56 | That looks right, but it seems odd within the paragraph then. This version looks "right", at least: ... have a -h height Set font height. The default is 16. Font height is set auto- matically for HEX files that have a # Height: height comment before any font data. |
The paragraph breaks are somewhat messy, and kind of defeat the intent of semantic markup (marking things for what they are and making the toolchain render them correctly).
There are two ways around this. Well, two that I tried.
- Make the example comment line a quoted literal (.Ql):
Font height is set automatically for HEX files that have a
.Ql # Height: Ar height
comment before any font data.
Renders as:
Font height is set automatically for HEX files that have a `# Height height' comment before any font data.
The single quotes added by .Ql delimit the comment line.
- Break the sentence up:
HEX files can have a comment describing the font height before any font data:
.Pp
.Li # Height Ar height
.Pp
Font height is set automatically for files with the comment.
Version 1 seems better and simpler to me.
For <> around height, replace the Ar above with Aq.
usr.bin/vtfontcvt/vtfontcvt.8 | ||
---|---|---|
56 | How about .Ql # Height: Ar height This renders it in `' quotes, with "height" underlined. Are the <> brackets actually present? |
Yes, version 1 looks good. The < > are not present in the file, that was just my earlier attempt at marking up a parameter.
-h height Set font height. The default is 16. Font height is set auto- matically for HEX files that have a `# Height: height' comment before any font data.
(height is underlined)