removes the ambiguity of using names - it's not case sensitive, it doesn't care if there
are spaces or not, and so on.
- You can generate picons yourself from existing images, or you can usually find sets
- pre-made on the Internet if you search for them. They're a good way to get large numbers
- of icons matched quickly, and usually in a similar style (such as square, x * y pixels, with
- a consistent highlight/reflection effect).</dd>
+ You can generate picons yourself from existing images, or you can usually find sets
+ pre-made on the Internet if you search for them. They're a good way to get large numbers
+ of icons matched quickly, and usually in a similar style (such as square, x * y pixels, with
+ a consistent highlight/reflection effect).</dd>
<dl>
<dt>Prefer picons over channel name:</dt>
<dt>Picon path</dt>
<dd>Path to a directory (folder) containing your picon collection. This can be named however
- you wish, as a local (file://) or remote (http://) location - however, remember that it's pointing
- to a directory as the picon names are automatically generated from the service parameters
- (frequency, orbital position, etc.).<br>
+ you wish, as a local (file://) or remote (http://) location - however, remember that it's pointing
+ to a directory as the picon names are automatically generated from the service parameters
+ frequency, orbital position, etc.).<br>
Example: file:///home/hts/picons</dd>
</dl>