1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title> Dillo Web Browser ::
Frequently Asked Questions
</title>
<style type="text/css">
body {margin: 0}
.sidebar .items {background: #f8f8f8}
.sidebar h3 {font-size: 1em; margin: 0.4em 0 0.2em 0}
h1 {color: #67f; margin-top: 0.25em; margin-bottom: 0.25em}
h3 {color: #56f; background: #f0f0f0}
.section {background: #f8f8f8; border-color: #e8e8e8; border-style: solid; border-width: 1px; margin-bottom: 0.5em}
.section h3 {margin-top: 0; margin-bottom: 0.2em}
ul li {list-style-type: square}
</style>
</head>
<body text="black" link="blue" vlink="#403090" bgcolor="white"
style="line-height: 1.3">
<table width="100%" cellspacing="0" cellpadding="0"><tr>
<td><img src="db1.png" alt="The Dillo Web Browser">
<td width="100%">
<img src="db2.png" alt="The Dillo Web Browser" height="124" width="100%">
</table>
<table border="0" cellpadding="15" cellspacing="5" width="100%">
<tr valign="top">
<td class="sidebar">
<h3>Dillo</h3>
<div class="items">
<a href="index.html">Home</a><br>
<a href="screenshots/index.html">Screenshots</a><br>
<a href="download.html">Download</a><br>
<a href="FAQ.html" title="Frequently asked questions">FAQ</a><br>
<a href="Compatibility.html">Compatibility</a><br>
<a href="http://hg.dillo.org/dillo/raw-file/default/ChangeLog">
Changelog</a><br>
<a href="Plans.html">Current Plans</a><br>
<a href="MList.html">Mailing List</a><br>
<a href="conferences.html">Conferences</a><br>
<a href="donations.html">Donate</a><br>
</div>
<h3>Users</h3>
<div class="items">
<a href="dillo3-help.html">Help</a><br>
<a href="Icons/index.html">Icons</a><br>
<a href="help/bug_meter.html">Bug meter</a><br>
<br>
</div>
<h3>Bug Tracker</h3>
<div class="items">
<small>[currently broken]</small><br>
<!--
<a href="/bugtrack/Dbugtrack.html">Bug Track Intro</a><br>
<a href="/bugtrack/Dquery.html">View Entries</a><br>
<a href="/bugtrack/Dinsert.html">Bug Insertion</a><br>
<a href="/bugtrack/Dvolunteer.html">Volunteering</a><br>
-->
</div>
<h3>Developers</h3>
<div class="items">
<a href="developer.html">New Developer</a><br>
<a href="documentation.html">Documentation</a> *<br>
<a href="NC_design.html">Naming&Coding</a><br>
<a href="source.html">Source repository</a><br>
<a href="dpi1.html">Dpi1 Spec</a><br>
<a href="CSS.html">CSS Spec</a><br>
<a href="D_authors.html">Authors</a><br>
<a href="authors/jcid-email.html">Security contact</a><br>
</div>
<h3>Related</h3>
<div class="items">
<a href="press.html">Dillo in the Press!</a><br>
<a href="interview.html">Interview</a><br>
<a href="interview.es.html">Entrevista</a>
<img src="chile.png" alt="*"><br>
<a href="Links.html">Links</a><br>
<a href="logos/logos.html">Art</a><br>
</div>
<p>
<a href="authors/webmaster-email.html">Webmaster</a>
<p>
<a href="http://www.anybrowser.org/campaign/">
<img src="abblue.gif" width="80" height="15"
alt="anybrowser"></a>
<td valign="top" align="left" width="100%">
<div lang=en>
<h1>Frequently Asked Questions</h1>
<a href="FAQ.html#q20">Where is the user manual? </a>
<p>
<a href="FAQ.html#q21">What's the status of the dillo-3.x series ("dillo3")? </a> <br>
<a href="FAQ.html#q13">What's the status of the dillo-2.x series ("dillo2")? </a> <br>
<a href="FAQ.html#q9">What's the status of the dillo-0.8.x series ("dillo1")? </a>
<p>
<a href="FAQ.html#q23">What happened to the dillorc preferences for colors? </a> <br>
<a href="FAQ.html#q24">How do I force web pages to use my favourite fonts with CSS? </a> <br>
<a href="FAQ.html#q27">Why isn't Dillo3 finding the font that I set? </a> <br>
<a href="FAQ.html#q19">What libraries does dillo use? </a> <br>
<a href="FAQ.html#q22">Can I run dillo on directfb? </a> <br>
<p>
<a href="FAQ.html#q1">Internationalization and Localization (i18n & l10n) </a> <br>
<a href="FAQ.html#q7">Why do some pages look strange? </a> <br>
<a href="FAQ.html#q26">What does "bad font: variable" mean? </a> <br>
<a href="FAQ.html#q15">Dillo2's rendering is badly broken for me. What do I have to change? </a> <br>
<a href="FAQ.html#q28">Why doesn't Dillo display certain images? </a> <br>
<a href="FAQ.html#q8">How do I enable cookies? </a> <br>
<a href="FAQ.html#q16">How do I clear my cookies? </a> <br>
<a href="FAQ.html#q12">How do I enable the https (SSL) support plugin for dillo?</a><br>
<a href="FAQ.html#q17">How do I use a proxy with dillo?</a> <br>
<a href="FAQ.html#q18">Where is the history file?</a>
<p>
<a href="FAQ.html#q14">After upgrading, I get: <em>"ERROR: dpi.c: can't start dpi daemon"!</em> </a> <br>
<a href="FAQ.html#q3">How do I get started in developing Dillo plugins (dpis)? </a> <br>
<a href="FAQ.html#q10">I have sent an email/patch/question/etc. to Jorge, but still no answer. What's the deal? </a> <br>
<a href="FAQ.html#q11">I have an addition to the FAQ/website. Whom do I contact?</a>
<div class=section>
<a name="q20"></a>
<h3>Where is the user manual?</h3>
<small>(AKA How do I configure dillo/How do I change the settings/What are
the keybindings/Where do I change the
start page/home page/search engine/panel/etc...)</small>
<p>
Click on the '<b>?</b>' icon in dillo's control panel for the local
help file. If not installed, it should bring you
<a href="dillo3-help.html">here</a>.
</div>
<div class=section>
<a name="q21"></a>
<h3>What's the status of the dillo-3.x series ("dillo3")?</h3>
This is the active branch.<br> dillo3 uses the
<a href="http://www.fltk.org/software.php"> FLTK-1.3</a>
library.
</div>
<div class=section>
<a name="q13"></a>
<h3>What's the status of the dillo-2.x series ("dillo2")?</h3>
dillo2 used the unreleased FLTK-2.0 library and is no longer maintained.
</div>
<div class=section>
<a name="q9"></a>
<h3>What's the status of the dillo-0.8.x series ("dillo1")?</h3>
dillo1 used the obsolete GTK+-1.2 library and is no longer maintained.
</div>
<div class=section>
<a name="q23"></a>
<h3>What happened to the dillorc preferences for colors?</h3>
CSS happened! To set colors, make a <code>~/.dillo/style.css</code>
file and add CSS rules there.
<p>
<table border=1>
<tr> <th>old pref <th> new CSS rule
<tr> <td>bg_color=purple <td> body {background-color: purple}
<tr> <td>text_color=black <td> body {color: black}
<tr> <td>link_color=blue <td> :link {color: blue}
<tr> <td>visited_color=0x808080 <td> :visited {color: #808080}
</table>
<p>
To prevent web pages from overriding one of your CSS rules, add
"<code>!important</code>" to it.<br>
To replace the <code>force_my_colors</code> preference, you could use, e.g.:
<table border=1><tr><td>
<code>* {background-color: green !important; color:red
!important}</code><br>
<code>:link {color: orange !important}</code><br>
<code>:visited {color: brown !important}</code>
</table>
The asterisk means that this rule should be applied to all HTML elements
that are not otherwise specified.
</div>
<div class=section>
<a name="q24"></a>
<h3>How do I force web pages to use my favourite fonts with CSS?</h3>
In your <code>~/.dillo/style.css</code> file, add rules like:
<table border=1><tr><td>
<tt>code, tt, pre, samp, kbd {font-family: monospace
!important}</tt><br>
<tt>* {font-family: serif !important}</tt>
</table>
Specific fonts are associated with the serif, sans-serif, monospace,
fantasy, and cursive font families in the <tt>dillorc</tt> configuration
file.
</div>
<div class=section>
<a name="q27"></a>
<h3>Why isn't Dillo3 finding the font that I set?</h3>
fltk-1.3 is somewhat more restricted in its use of font names than fltk2
was. Please try the <kbd>fc-list</kbd> command as shown in the current
dillorc configuration file to find the right form of the fontname to use.
</div>
<div class=section>
<a name="q19"></a>
<h3>What libraries does dillo use?</h3>
Dillo itself: Required: libpthread, libiconv, zlib. Optional: openssl,
libpng, libjpeg.<br>
FLTK: At least on Unix, the minimum might be X11, Xext, plus the
default configuration also requiring Xft and fontconfig.
OpenGL, exceptions, and rtti can be disabled since dillo does not use them.
<p>
The FLTK library is normally statically linked into dillo, so you would
only need to get this library itself if you are building dillo for yourself.
<p>
Dillo3: fltk-1.3<br>
Dillo2: fltk-2.0 (make sure version is >= r6916 and <=r7513)
</div>
<!-- the search engine likes to send people to dillo's mail archive when they
want to know about browsers with directfb, so... -->
<div class=section>
<a name="q22"></a>
<h3>Can I run dillo on directfb?</h3>
No. (although Nikita Egorov did have fltk-1.1.9
<a href="http://www.mail-archive.com/fltk-dev@easysw.com/msg00762.html">working</a>
with directfb)
</div>
<div class=section>
<a name="q1"></a>
<h3>Internationalization and Localization (i18n & l10n)</h3>
dillo's internal character encoding is
<a href="http://en.wikipedia.org/wiki/UTF-8">UTF-8</a>.
It uses the iconv library to convert from/to other character encodings.
<p>
In recent releases, Dillo has improved line wrapping for Chinese and
Japanese text, and also handles zero-width spaces, which can help with
Thai, Lao, Cambodian, Burmese....
<p>
Scripts with right-to-left display (e.g., Arabic, Hebrew) or complex
rendering rules (e.g., Arabic, Indic scripts) are not displayed properly.
<p>
The current Dillo developers use Latin-1 languages, so i18n testing and
commentary would be particularly valued.
</div>
<div class=section>
<a name="q7"></a>
<h3>Why do some pages look strange?</h3>
In part because the CSS 'float' property is not implemented yet
(it is our top priority).
<p>
In the lower right corner of Dillo you'll see a bug-shaped icon.
This is Dillo's
<a href="help/bug_meter.html">bug meter</a>.
Click on it to see the HTML errors that have been detected.
<p>
Our policy is not to work around broken HTML. To learn why, see our
<a href="Links.html">links</a>,
and especially read
<a href="http://www.levien.com/free/decommoditizing.html">"The decommoditization of protocols"</a>
by Raph Levien.
<p>
Any HTML parsing patch should be backed up with information from the
<a href="http://www.w3.org/TR/html401/">HTML 4.01 spec</a>.
Note that previous HTML specs can be considered as well.
<p>
Unfortunately, despite our respect for standards, there're some
cases where it's impossible to change the Web's status quo; in those
cases we follow Firefox and HTML5.
</div>
<div class=section>
<a name="q26"></a>
<h3>What does "bad font: variable" mean?</h3>
When FLTK2 (used by Dillo2) is configured with XFT disabled, it expects
"variable" and "fixed" to be listed somewhere in your fonts.alias files
(and furthermore to be aliases for fonts that you <em>have</em>
<tt>:)</tt>.
(<a href="http://lists.dillo.org/pipermail/dillo-dev/2010-June/007519.html">an example</a>)
</div>
<div class=section>
<a name="q15"></a>
<h3>Dillo2's rendering is badly broken for me. What do I have to change?</h3>
You're getting blank regions in the window, and much of the text is being
drawn in the upper left corner?
<p>
If you configured FLTK2 with <tt>--enable-cairo</tt>, there's your problem.
Don't do that <tt>:)</tt>
<p>
OSX users: Dillo3 builds and runs native in it.
</div>
<div class=section>
<a name="q28"></a>
<h3>Why doesn't Dillo display certain images?</h3>
<ul>
<li>If a server sends a resource with content type
<code>image/png</code>, for instance, and it is not a PNG file,
Dillo will not display it.
<li>If Dillo requests an image and receives a response containing a
redirection (i.e., pointing to a different URL), the redirection
is not followed. These have a strong tendency to be advertisements.
<li>(versions 2.2.1-3.0.2)<br>
If you have <code>filter_auto_requests=same_domain</code> in your
dillorc, Dillo will not make automatic requests for third-party
resources. There are pros and cons to this due to the current
conditions of the web, as shown in the following example from running
dillo back in the <code>filter_auto_requests</code> days (with
<code>show_msg</code> enabled):
<pre style="font-size: x-small">
Nav_open_url: new url='http://en.wikipedia.org'
Connecting to 208.80.152.2
Nav_open_url: new url='http://en.wikipedia.org/wiki/Main_Page'
Connecting to 208.80.152.2
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'upload.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'bits.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'bits.wikimedia.org'
Capi_filters_test: deny from 'en.wikipedia.org' to 'bits.wikimedia.org'
Nav_open_url: new url='http://blogs.reuters.com/reuters-money/2011/10/11/
online-privacy-leaks-worsen-do-not-track-gains-steam/'
Capi_filters_test: deny from 'blogs.reuters.com' to 'ad.doubleclick.net'
Capi_filters_test: deny from 'blogs.reuters.com' to 'ad.doubleclick.net'
Capi_filters_test: deny from 'blogs.reuters.com' to 'statse.webtrendslive.com'
</pre>
<li>Beginning with version 3.0.3,
<code>~/.dillo/<a href='domainrc.html'>domainrc</a></code>
lets you specify whether to allow automatic requests between
individual domains, so you can, for instance, permit requests from
wikipedia and deny those for doubleclick.net.
</ul>
</div>
<div class=section>
<a name="q8"></a>
<h3>How do I enable cookies?</h3>
<small>(AKA Why can't I log into [some site]/Why can't I stay
logged into [some site]?)</small>
<p>
For privacy reasons, Dillo runs with cookies disabled by default.
<a href="Cookies.txt">Cookies.txt</a>
(also available in the tarball) explains why in more detail.
<p>
Configuring cookies in Dillo is easy. Something
like the following inside <code>~/.dillo/cookiesrc</code> could be
enough to get you started:
<p>
<code>
#domain action <br>
DEFAULT DENY <br>
fltk.org ACCEPT <br>
.host.com ACCEPT_SESSION <br>
</code>
</div>
<div class=section>
<a name="q16"></a>
<h3>How do I clear/remove/delete my cookies?</h3>
First, stop your plugins (<b>dpi</b>s) with the following command:
<p>
<code>dpidc stop</code>
<p>
The cookies dpi will write any permanent (ACCEPT) cookies to disk, and
temporary (ACCEPT_SESSION) cookies will be discarded as the dpi exits.
<p>
Second, get rid of the permanent cookies by removing or editing your
<code>~/.dillo/cookies.txt</code> file.
</div>
<div class=section>
<a name="q12"></a>
<h3>How do I enable the https (SSL) support plugin for dillo?</h3>
First of all, beware that this is a prototype in alpha state. It
will only provide for very basic web page retrievals, POST and GET.
There is no certificate caching and NO AUTHENTICATION performed.
<p>
<b>It's disabled by default</b>.
<p>
If you want to enable it (e.g. to read forums in https), then use<br>
<blockquote>
./configure <code>--enable-ssl</code>
</blockquote>
Then recompile and reinstall.
</div>
<div class=section>
<a name="q17"></a>
<h3>How do I use a proxy with dillo?</h3>
For <b>HTTP</b>, either set the proxy in your <tt>~/.dillo/dillorc</tt>
configuration file or set the <tt>http_proxy</tt> environment variable.
To use a proxy with <b>FTP</b> and <b>downloads</b>, you need to
<a href="http://www.gnu.org/software/wget/manual/html_node/Proxies.html">configure the <em>wget</em> program</a>
that they use.
</div>
<div class=section>
<a name="q18"></a>
<h3>Where is the history file?</h3>
Dillo does not have a file containing browsing history.
</div>
<div class=section>
<a name="q14"></a>
<h3>After upgrading, I get: <em>"ERROR: dpi.c: can't start dpi daemon"</em></h3>
The old <b>dpid</b> and some <b>dpi</b>s may still be running. Just:
<pre>
ps aux | grep dpid
dpidc stop
kill <dpid PID>
ps aux | grep dpi
kill <dpi PIDs>
</pre>
<p>
Also: If you built dillo from source yourself, did you configure it so
that 'make install' put dpid in a directory that's in your path?
</div>
<div class=section>
<a name="q3"></a>
<h3>How do I get started in developing Dillo plugins (dpis)?</h3>
First, read "doc/Dpid.txt" and then the
<a href="dpi1.html">Dpi1 spec</a>
for details.
The easy way to get started is to think of them as CGI programs
that don't need a web server, and that provide some handy
extensions. Dillo comes with several dpis. Play for a while
with the bookmarks in dillo (it's implemented with a dpi) to get
an idea of what can be done. The hello dpi provides a simpler
example ("dpi:/hello/world"). Downloads, FTP and view-source are also
dpi programs. Choose one of them and start to make some modifications.
Remember that a dpi is an independent process that communicates
with Dillo by using sockets. As an independent
program, it has all the power the underlying OS provides it.
For instance, it would be easy to modify the bookmarks dpi to
provide for a dillo-based GUI for data stored in a DB server.
</div>
<div class=section>
<a name="q10"></a>
<h3>I have sent an email/patch/question/etc. to Jorge, but still no answer.
What's the deal?</h3>
Jorge has much more work than he can cope with.
It's impossible to answer all the emails
that pour in. There'd be no time for development, design, patch
reviewing, patch integration, funding initiative, web site
maintenance, quality assurance, release management, ...
<p>
So what do I do?
<p>
Allow him a week for urgent messages and two for less pressing
matters. If he hasn't answered, send a reminder.
<p>
Search the <a href="MList.html">dillo-dev</a>
mailing list archive.
<p>
Subscribe to dillo-dev.
</div>
<div class=section>
<a name="q11"></a>
<h3>I have an addition to the FAQ/website. Whom do I contact?</h3>
Send all such additions, as well as general questions about the website,
to the
<a href="MList.html">mailing list</a>
(subscription required), or
<a href="authors/jcid-email.html">me</a>.
</div>
</div>
</td>
</tr>
</table>
</body>
</html>
|
