Difference between revisions of "User:Thisoldman"

From ArchWiki
Jump to: navigation, search
(Reverting to old page)
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Console Fonts=
+
== How to write good ==
<!-- Introduction -->
+
# Correct spelling is esential.
The default font for consoles, that is, terminals with no ''X'' windows, uses the ASCII character set. This font and character set can easily be changed by the user.
+
# Verbs always has to agree with their subjects.
 
+
# Avoid run-on sentences they are hard to read.
 
+
# About those fragments.
Console fonts are found in {{Filename|/usr/share/kbd/consolefonts/}}. The console display is limited to either 256 characters and 16 available colors or 512 characters and 8 available colors. The "bright" terminal colors aren't available when using the larger set of characters.
+
# Remember to not ever split an infinitive.
 
+
# Parentheses are (usually) not necessary.
== Previewing and testing ==
+
# Do not end a sentence with a preposition. This is something the reader will not put up with.
 
+
# Use the apostrophe in it's proper place and omit it when its not needed.
No organized library of console font images is available. The user can, however, use {{Codeline|setfont}} to temporarily change the font. The user can then work as usual at the command line to determine if the font is suitable. A table of all the available ''glyphs'' or letters in the font can also be viewed with the command {{Codeline|showconsolefont}}.  
+
# The passive voice is to be avoided.
 
+
# Proofread your writing to see if you any words out.
If the font is not suitable, a return to the default font can then be made by issuing the command {{Codeline|setfont}}, without any arguments. If the console display is totally unreadable, this command will still work—the user just types in the command "blind."
+
 
+
Note that {{Codeline|setfont}} only works on the active console. Any other consoles, active or inactive, remain unaffected.
+
 
+
=== Examples ===
+
 
+
Change the font. This one is distinctive:
+
$ setfont gr737b-9x16-medieval.psfu.gz
+
 
+
Or change the font to one with 512 glyphs and the ISO 8859-3 character set:
+
$ setfont
+
 
+
Issue commands that send text to the display:
+
$ cat somefile
+
$ man man
+
 
+
View the table of glyphs:
+
$ showconsolefont
+
 
+
 
+
 
+
 
+
To use other fonts change the {{Codeline|CONSOLEFONT<nowiki>=</nowiki>}} and {{Codeline|CONSOLEMAP<nowiki>=</nowiki>}} settings in {{Filename|/etc/rc.conf}}. Different fonts can be found in {{Filename|/usr/share/kbd/consolefonts/}} directory and keymaps can be found in the subdirectories of {{Filename|/usr/share/kbd/keymaps/}}.
+
 
+
===Example===
+
For displaying characters such as ''č, ć, ž, đ, ''or ''š,'' use the font {{Filename|lat2-16.psfu.gz}}:
+
CONSOLEFONT="lat2-16.psfu.gz"
+
 
+
And set the proper keymap, in this case:
+
CONSOLEMAP="8859-2"
+
 
+
To use the specified font in early userspace (early in the bootup process), add the {{Codeline|keymap}} hook to {{Filename|/etc/mkinitcpio.conf}}:
+
HOOKS="base udev autodetect pata scsi sata filesystems '''keymap'''"
+
 
+
Then rebuild the image:
+
# mkinitcpio -p kernel26
+
 
+
{{Note| Repeat if you have more than one kernel package installed and want the same behavior for each kernel.}}
+
 
+
See: [[Mkinitcpio#Configuring the HOOKS|Mkinitcpio: Configuring the HOOKS]]
+

Revision as of 01:43, 28 October 2011

How to write good

  1. Correct spelling is esential.
  2. Verbs always has to agree with their subjects.
  3. Avoid run-on sentences they are hard to read.
  4. About those fragments.
  5. Remember to not ever split an infinitive.
  6. Parentheses are (usually) not necessary.
  7. Do not end a sentence with a preposition. This is something the reader will not put up with.
  8. Use the apostrophe in it's proper place and omit it when its not needed.
  9. The passive voice is to be avoided.
  10. Proofread your writing to see if you any words out.