Difference between revisions of "User:Thisoldman"

From ArchWiki
Jump to: navigation, search
(Reverting to old page)
(39 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Java (Sun) Fonts=
+
== How to write good ==
 
+
# Correct spelling is esential.
 
+
# Verbs always has to agree with their subjects.
Users may find the default Java fonts and their display in Java applications unpleasant. Several methods to improve font display in the '''Sun Java Runtime Environment (JRE)'''[http://java.sun.com/javase/6/docs/technotes/guides/index.html#jre-jdk] are available. The methods may be used separately, but many users will find better results by combining them.
+
# Avoid run-on sentences they are hard to read.
 
+
# About those fragments.
== Anti-aliasing ==
+
# Remember to not ever split an infinitive.
 
+
# Parentheses are (usually) not necessary.
'''Anti-aliasing'''[http://en.wikipedia.org/wiki/Anti-aliasing] of fonts is available with Sun Java 1.6 on Linux. To do this on a per user basis, add the following line to the user's {{Codeline|~/.bashrc}}.
+
# Do not end a sentence with a preposition. This is something the reader will not put up with.
export _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=''{setting}'''
+
# Use the apostrophe in it's proper place and omit it when its not needed.
Replace {{Codeline|''{setting}''}} with one of these seven values:[http://java.sun.com/javase/6/docs/technotes/guides/2d/flags.html] {{sn|'''TrueType'''[http://en.wikipedia.org/wiki/TrueType] fonts contain a '''G'''rid-fitting '''A'''nd '''S'''can-conversion '''P'''rocedure '''(GASP)'''[http://www.microsoft.com/typography/otspec/gasp.htm] table with the font creator's recommendations for font display at different point sizes.  Some sizes are recommended to be fully anti-aliased, others are to be hinted, and some sizes are recommended to be displayed as bitmaps. Combinations are sometimes used for font display at certain point sizes.}}
+
# The passive voice is to be avoided.
 
+
# Proofread your writing to see if you any words out.
*No anti-aliasing -- {{Codeline|off}} or {{Codeline|false}} or {{Codeline|default}}
+
*Full anti-aliasing -- {{Codeline|on}}
+
*Use the font's built-in hinting instructions -- {{Codeline|gasp}}
+
*Setting useful for many popular LCD monitors -- {{Codeline|lcd}} or {{Codeline|lcd_hrgb}}
+
*Alternative LCD monitor setting -- {{Codeline|lcd_hbgr}}
+
*Alternative LCD monitor setting -- {{Codeline|lcd_vrgb}}
+
*Alternative LCD monitor setting -- {{Codeline|lcd_vbgr}}
+
 
+
The {{Codeline|gasp}} and {{Codeline|lcd}} settings work well in many instances.
+
 
+
For the above change to take effect, {{Codeline|~/.bashrc}} must be ''sourced'' as the normal user.
+
$ source ~/.bashrc
+
Open a new instance of a Java application to test the changes made.
+
 
+
== Font Selection ==
+
 
+
 
+
=== Enable TrueType Fonts ===
+
TrueType fonts appear to be the best supported format in Java. Java applications that are coded to use a specific TrueType font must be given the ''path'' to that font. TrueType fonts are located in the directory {{Codeline|/usr/share/fonts/TTF}}. Add the following line to {{Codeline|~/.bashrc}} to enable these fonts.
+
export JAVA_FONTS=/usr/share/fonts/TTF
+
 
+
''Source'' {{Codeline|~/.bashrc}} as the normal user for the change to take effect.
+
$ source ~/.bashrc
+
 
+
=== Change the Default Fonts ===
+
The '''Lucida'''[http://en.wikipedia.org/wiki/Lucida] fonts distributed along with the Sun JRE are the default for Java applications that do not specify a different font's use. The Lucida fonts were designed for low resolution  displays and printers[http://www.tug.org/store/lucida/designnotes.html], many users will wish to use other fonts. This default Java font can be changed on a system-wide basis by the creation or editing of a file named {{Codeline|fontconfig.properties}}.
+
 
+
As root, change directory to {{Codeline|/opt/java/jre/lib}}. Copy {{Codeline|fontconfig.properties.src}} to {{Codeline|fontconfig.properties}}. Then, as root, open the new {{Codeline|fontconfig.properties}} in an editor.
+
# cd /opt/java/jre/lib
+
# cp fontconfig.properties.src fontconfig.properties
+
# nano fontconfig.properties      ## Editor is the user's choice.
+
{|
+
|{{Note|Encodings other than '''Latin-1,''' or '''ISO 8859-1,'''[http://en.wikipedia.org/wiki/ISO/IEC_8859-1] are shown in other {{Codeline|fontconfig.properties.*.src}} files in {{Codeline|/opt/java/jre/lib}}. Some users will find these files to be better sources to use for editing. In all cases the edited file should be saved as {{Codeline|fontconfig.properties}}.}}
+
|}
+
The Java font names in this configuration file are in the form of ''genericFontName.style.subset'', for example,{{Codeline|serif.plain.latin}}. These generic fonts are mapped to the installed fonts using '''X Logical Font Description (XLFD)'''[http://en.wikipedia.org/wiki/X_logical_font_description] names. The {{Codeline|%d}}, in the example below, is used as a placeholder in the XLFD name for the point size. The Java application will replace {{Codeline|%d}} at runtime.
+
serif.plain.latin-1=-b&h-lucidabright-medium-r-normal--*-%d-*-*-p-*-iso8859-1
+
 
+
{{Tip|The utility, '''xfontsel''', may be used to display fonts and to discover their XLFD name. Xfontsel is part of the '''xorg-utils''' package.}}
+
 
+
Below is an excerpt of a {{Codeline|fontconfig.properties}} file after modifications have been made. The Lucida fonts have been replaced by variations of the '''DejaVu'''[http://en.wikipedia.org/wiki/DejaVu_fonts] fonts.
+
# Version -- a version number is required.
+
# IMPORTANT -- Do not delete the next line. Ever.
+
version=1
+
+
# Component Font Mappings
+
# gen_name.style.subset=
+
#      -fndry-fmly-wght-slant-sWdth-adstyle-pxlsz-ptSz-resx-resy-spc-avgWdth-rgstry-encdng
+
+
serif.plain.latin-1=-misc-dejavu serif-medium-r-normal-*-*-%d-*-*-p-*-iso8859-1
+
serif.bold.latin-1=-misc-dejavu serif-bold-r-normal-*-*-%d-*-*-p-*-iso8859-1
+
serif.italic.latin-1=-misc-dejavu serif-medium-i-normal-*-*-%d-*-*-p-*-iso8859-1
+
 
+
After the changes have been saved to {{Codeline|fontconfig.properties}}, the editor may be closed and the user should drop root privileges. Open a new instance of a Java application to test the changes.
+

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.