Project Notes for Developers

Plugins

  This is an idea that maybe could be better understood if stated
as  "simple  plugins".  The  fact  is  that our current rendering
system,  and  its  associated internal layers, is not ready for a
full  widget-integrated  interactive system, but (here's the good
part),  a simple plugin scheme, very similar to the way CGIs work
is running (read Dpi1 Spec for details).

  It  uses Unix domain sockets, for security reasons.

  Starting from 0.7.0 release dillo comes with the dpi framework.

Internationalization and Localization (i18n & l10n)

  This is covered in the new FAQ.

HTML parsing policy

  Our  policy  with  HTML  is  not to try to render badly written
HTML, ideally send a warning message, and not to crash!

  If  you want to understand why, please go to our site's [Links]
section, and read:

  Any  HTML parsing patch, should be backed-up with the HTML-4.01
spec.  (also  available  from  the  [Links]  section).  Note that
previous HTML specs could be considered too.

Authors page

  There's  not a deterministic algorithm for this yet, but beware
that  people credited for sending patches, start to appear at the
fourth  accepted  patch  (or  equivalent  work). OTOH patches are
always credited in the ChangeLog.

EBAY: Why some links on eBay doesn't work?

  Because  within the "A" element, the attribute value for "HREF"
instead of reading like this:

  <A HREF="http://<...>&item=4532234543<...>">

  has something like:

  <A HREF="http://<...>&item=[0x0D][0x0A]4532234543<...>">
                             ^^^^^^^^^^^^
                             -- Note these two characters.


  In fact, they are a carriage return/linefeed pair (CR/LF).

  The href value is of type CDATA, and SGML for HTML4 says:

  User agents should interpret attribute values as follows: 

     o Replace character entities with characters,
     o Ignore line feeds,
     o Replace each carriage return or tab with a single space.

  So, the LF is ignored, but the CR ends as a single space.

  BUT the value MUST be an URI, and white space is ILLEGAL inside
an  URI.  So  the  page  specifies  something  "like" an URI, but
ILLEGAL, and Dillo warns about it.

  Note that the interoperability of the WWW depends on the use of
standards. That's why Dillo refuses to "fix" broken HTML.

 (0x00-0x1F, 0x7F or space are all illegal inside an URI).

  * If someone can tell them, PLEASE DO SO.
  [screenshot]