- Dillo-dev - lists.mailman3.com

packed trie for hyphenation patterns in the main repository
by Johannes.Hofmann＠gmx.de Sept. 23, 2012

Sept. 23, 2012

Hi, I just pushed the packed trie implementation from http://flpsed.org/hgweb/dillo_hyphen_mem to the main repository. It considerably reduces the memory consumption of the hyphenator. The <lang>.pat files of the original implementation without any changes. However one can reduce memory consumption even further by precompressing the patterns using the new test/trie program: Usage: trie <pattern file> > <prefix>/lib/dillo/hyphenation/<lang>.pat.trie e.g: ./trie hyph-de-1996.pat > /usr/local/lib/dillo/hyphenation/de.pat.trie If the <lang>.pat.trie is found, dillo will use this precompressed trie instead of the <lang>.pat file. These changes should not have any effect on where the hyphenator breaks up words. If you find any regressions or changes, please report them. Cheers, Johannes

2 1

Hyphenation is in the main repository
by sgeerken＠dillo.org Sept. 15, 2012

Sept. 15, 2012

Hi all! The hyphenation, which has been developed in another repository, is now in the main repository at <http://hg.dillo.org/dillo>. The remaining bugs and glitches will hopefully fixed soon. Sebastian

4 8

Floats
by sgeerken＠dillo.org Sept. 14, 2012

Sept. 14, 2012

Hi! I've just merged the recent developments (including hyphenation) into the floats branch, which was originally at <http://flpsed.org/hgweb/dillo_floats/>, but is now at <http://flpsed.org/hgweb/dillo_floats_geerken>. Unfortunatey, floats do not work at all after the merge, since there were some incompatible changes for hyphenation (see comment at the beginning of calcAvailWidth). However, expect some work here in the next weeks. Sebastian

1 0

SimpleVector initAlloc parameter
by Johannes.Hofmann＠gmx.de Sept. 13, 2012

Sept. 13, 2012

Hi, I noticed that the initAlloc parameter of lout::SimpleVector() is ignored and we always start with a 1-element array (see SimpleVector::resize()). To avoid confusion I would either remove the initAlloc parameter altogether or use it and adjust the callers as appropriate. I'm fine either way, but the current solution is not good. Any opinions? Cheers, Johannes

1 0

next release of dillo?
by itsme_410＠yahoo.com Sept. 13, 2012

Sept. 13, 2012

On the Current Plans page of dillo, there are a number of issues that appear to have either items that are finished or have a prototype (eg handle javascript_. Just wondering whether there are any plans to release dillo soon? Thanks again for a great browser! Trotter

2 1

class attributes
by corvid＠lavabit.com Sept. 11, 2012

Sept. 11, 2012

Is there a reason why we don't parse entities when we get the class attr? (I was looking at how we use Html_get_attr2() in all cases for Html_parse_common_attrs(), and a_Html_get_attr() the rest of the time, and I haven't noticed anything yet in the html4 spec that makes it sound like we shouldn't parse entities for class.)

2 1

paragraphs
by Johannes.Hofmann＠gmx.de Sept. 6, 2012

Sept. 6, 2012

On Wed, Sep 05, 2012 at 10:43:42PM +0200, Johannes Hofmann wrote: > On Tue, Sep 04, 2012 at 09:57:59PM +0200, Johannes Hofmann wrote: > > On Tue, Sep 04, 2012 at 03:22:39PM +0000, corvid wrote: > > > > > > IIRC, the space between paragraphs went away when display was > > > implemented. Do you have an idea of what the problem was in the > > > code? (I'm so used to it now that I rarely remember that it > > > isn't supposed to be that way.) > > > > > > > I only know that things changed quite a bit due to paragraphs being > > textblocks now. > > I guess we need to make a testcase and compare the rendering to e.g. > > firefox and then see how to fix problems. > > I looked a bit at it and it's probabely just a missing line in the > user-agent style, e.g: > > diff -r 773b79919a0b src/styleengine.cc > --- a/src/styleengine.ccTue Sep 04 15:09:40 2012 +0000 > +++ b/src/styleengine.ccWed Sep 05 22:42:33 2012 +0200 > @@ -831,6 +831,7 @@ > "i, em, cite, address, var {font-style: italic}" > ":link img, :visited img {border: 1px solid}" > "frameset, ul, ol, dir {margin-left: 40px}" > + "p {margin: 1em 0}" > "h1 {font-size: 2em; margin-top: .67em; margin-bottom: 0}" > "h2 {font-size: 1.5em; margin-top: .75em; margin-bottom: 0}" > "h3 {font-size: 1.17em; margin-top: .83em; margin-bottom: 0}" > > > I'm still researching, why 1em seems to be a bit more in dillo than > in firefox. Ok I remember now. Adding "p {margin: 1em 0}" to our user agent style is correct. However we need to implement collapsing bottom-margin and top-margins for subsequent block level elements to make it look nice.

1 0

Fwd: Extending the CSS parser (was: hyphenation in dillo)
by sgeerken＠dillo.org Sept. 6, 2012

Sept. 6, 2012

Should go to the list ...

3 2

google translate and non-ascii characters
by andreas＠kemnade.info Aug. 26, 2012

Aug. 26, 2012

Hi, I tried to use translate.google.com with dillo and it does not work with non-ascii characters. I do not know http by heart so that I know what character set should be send in the post request but it seems not to be what google expects. Words with non-ascii characters are not translated and non-ascii characters are turned into questionmarks. Greetings Andreas Kemnade

2 3

Horizontal scrolling with mouse buttons
by jcid＠dillo.org Aug. 7, 2012

Aug. 7, 2012

On Mon, Aug 15, 2011 at 02:18:33PM -0400, saulgoode(a)flashingtwelve.brickfilms.com wrote: > Quoting Jorge Arellano Cid <jcid(a)dillo.org>: > > > Please try dillo-3.0-pre, following these directions [1]. > >Then report back how it goes. > > > > [1] http://www.dillo.org/source.html > > With that build, the horizontal scroll buttons are inactive. To my > mind this is satisfactory behavior as it does not interfere with the > vertical scrolling of the mouse wheel (previously the only way to > restore vertical wheel scrolling was to restart the program). Good! This looks like an issue with fltk-1.3. FWIW, inside fltk-1.3 src/Fl_x.cxx:1443, there's no code to handle those buttons. Having something like the following may be worth a try (if you're a coder): if (xevent.xbutton.button == Button4) { Fl::e_dy = -1; // Up event = FL_MOUSEWHEEL; } else if (xevent.xbutton.button == Button5) { Fl::e_dy = +1; // Down event = FL_MOUSEWHEEL; + } else if (xevent.xbutton.button == Button6) { + Fl::e_dx = -1; // Left + event = FL_MOUSEWHEEL; + } else if (xevent.xbutton.button == Button7) { + Fl::e_dx = +1; // Right + event = FL_MOUSEWHEEL; } else { Fl::e_state |= (FL_BUTTON1 << (xevent.xbutton.button-1)); event = FL_PUSH; checkdouble(); } > Thank you for your response. :) -- Cheers Jorge.-

3 2