Frequently Asked Questions

Where is the user manual?

What’s the status of the dillo-3.x series (“dillo3”)?
What’s the status of the dillo-2.x series (“dillo2”)?
What’s the status of the dillo-0.8.x series (“dillo1”)?

What happened to the dillorc preferences for colors?
How do I force web pages to use my favourite fonts with CSS?
Why isn’t Dillo3 finding the font that I set?
What libraries does dillo use?
Can I run dillo on directfb?

Internationalization and Localization (i18n & l10n)
Why do some pages look strange?
What does “bad font: variable” mean?
Dillo2’s rendering is badly broken for me. What do I have to change?
Why doesn’t Dillo display certain images?
How do I enable cookies?
How do I clear my cookies?
How do I enable the https (SSL) support plugin for dillo?
How do I use a proxy with dillo?
Where is the history file?

After upgrading, I get: “ERROR: dpi.c: can’t start dpi daemon”!
How do I get started in developing Dillo plugins (dpis)?
I have sent an email/patch/question/etc. to Jorge, but still no answer. What’s the deal?
I have an addition to the FAQ/website. Whom do I contact?

Internationalization and Localization (i18n & l10n)

dillo’s internal character encoding is UTF-8. It uses the iconv library to convert from/to other character encodings.

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….

Scripts with right-to-left display (e.g., Arabic, Hebrew) or complex rendering rules (e.g., Arabic, Indic scripts) are not displayed properly.

The current Dillo developers use Latin-1 languages, so i18n testing and commentary would be particularly valued.

Why do some pages look strange?

In part because the CSS ‘float’ property is not implemented yet (it is our top priority).

In the lower right corner of Dillo you’ll see a bug-shaped icon. This is Dillo’s bug meter. Click on it to see the HTML errors that have been detected.

Our policy is not to work around broken HTML. To learn why, see our links, and especially read “The decommoditization of protocols” by Raph Levien.

Any HTML parsing patch should be backed up with information from the HTML 4.01 spec. Note that previous HTML specs can be considered as well.

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.

Why doesn’t Dillo display certain images?

How do I enable cookies?

(AKA Why can’t I log into [some site]/Why can’t I stay logged into [some site]?)

For privacy reasons, Dillo runs with cookies disabled by default. Cookies.txt (also available in the tarball) explains why in more detail.

Configuring cookies in Dillo is easy. Something like the following inside ~/.dillo/cookiesrc could be enough to get you started:

   #domain action

How do I get started in developing Dillo plugins (dpis)?

First, read “doc/Dpid.txt” and then the Dpi1 spec 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.