November 2012 - Dillo-dev - lists.mailman3.com

Extensions for hyphenation
by sgeerken＠dillo.org Dec. 23, 2012

Dec. 23, 2012

Hi! At http://flpsed.org/hgweb/dillo_hyphen, you'll find some extensions for hyphenation I've not yet merged into the main repository. Still needs some documentation, but here is an overview: There are now configuration variables for dillorc (see source): penalties for hyphens, as well as the left and right side of an em-dash. The suffix "_2" means that this value is used for lines following a line which ends already with a hyphen. When this value is larger, two adjacent lines ending with a hyphen are avoided. For values, see the definition of the "badness". Typical values: 0 = Penalty used for normal spaces. 1 = A justified line with spaces having 150% or 67% of the ideal space width has this as badness. 8 = A justified line with spaces twice as wide as ideally has this as badness. "inf" may be used (preventing a break in any case); also "-inf" (forcing a break), although the latter makes no sense and may lead to strange results. There is a text page, test/hyphens-etc.html, to play around. Sebastian

4 21

Tooltip bugs revisited
by jcid＠dillo.org Dec. 17, 2012

Dec. 17, 2012

Hi there, These days I've devoted some more effort to the tooltips bug [1] and its workaround patch [2]. The motivation is that the current workaround involves a full UI and viewport expose (i.e. a full erase/redraw) that produces annoying flickering when the mouse is in the UI but outside the viewport (e.g. over the panel). Over time I've learnt to move the mouse pointer outside the panel and into the viewport to scroll without flickering (but probably I'm among the few that know this trick). So far (and despite the warning inside FLTK), I've experimented with a custom tooltip handling class, and a couple custom UI widgets, that seem to work well together (i.e. solve the problem without the workaround :) ). Testing revealed the workaround concealed another problem, which I don't remember whether it was detected before, and this is that viewport mouse events get "through" the panel UI!. How?, placing the mouse pointer over the panel (e.g. to the right of the Tools button, or even inside the Location), and scrolling a page full of links under it, will make the mouse pointer change to a hand, and the destination link appear in the status bar area. This bug is revealed by disabling the workaround: just apply the small attached patch. Clearly there's a viewport offset problem somewhere. Correcting it may save us lots of headaches in the future. Does anybody know or has a clue of where this may be happening? TIA. [1] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-July/008494.html [2] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-July/008515.html -- Cheers Jorge.-

2 6

ideographic, zero-width space
by corvid＠lavabit.com Dec. 6, 2012

Dec. 6, 2012

Would it make the most sense for the handling of ideographic characters and zero-width space to go somewhere in textblock these days instead of html.cc?

2 1

Patch: improve window titles for the downloads DPI
by onepoint＠starurchin.org Dec. 1, 2012

Dec. 1, 2012

Comments on this tiny patch? http://starurchin.org/dillo/patch/dpi-downloads_window_titles.html I thought it looked a little unprofessional to have default dialog titles like "Unnamed". Any objections to me pushing this? Regards, Jeremy Henty

2 2

hyphenation in dillo
by sgeerken＠dillo.org Nov. 28, 2012

Nov. 28, 2012

Hi! At <http://flpsed.org/hgweb/dillo_hyphen/>, you'll find a version of dillo which automatically hyphenates words, using the algorith by Frank Liang (which is also used by TeX). It is still quite messy, but works already rather stable. Some manual work is neccessary (from dillo_hyphen): mkdir /usr/local/lib/dillo/hyphenation cp test/hyph-de-1996.pat /usr/local/lib/dillo/hyphenation/de.pat cp test/hyph-en-us.pat /usr/local/lib/dillo/hyphenation/en.pat For other language, the files in the CTAN should be converted. For playing around, try this one: <http://de.wikisource.org/wiki/Spezial:Zuf%C3%A4llige_Seite> :-) Sebastian

6 38

soft hyphen and hyphenation
by Johannes.Hofmann＠gmx.de Nov. 28, 2012

Nov. 28, 2012

Hi, is it correct that we use a soft hyphen (0xc2 0xad) to draw the hyphen when breaking words? It seems to draw ok with fltk/X11, but wouldn't an unconditional hyphen 0xE2 0x80 0x90 be more correct? I'm asking because e.g the Apple drawing library doesn't seem to draw the soft hyphen if it thinks there should be no line break. Cheers, Johannes

3 9

valgrind complaints when running datauri
by corvid＠lavabit.com Nov. 25, 2012

Nov. 25, 2012

Jeremy's valgrind logs have had a couple of these recently, e.g., http://starurchin.org/dillo/valgrind/5b601af9ce7facc17690b88c4323c194fded01… I found that - after dpidc stop - valgrind --leak-check=full --trace-children=yes dillo - going to http://jimbojw.com/wiki/index.php?title=Data_URI_Explained - and pasting in the second example (the percent-encoded one, not the base64 one) gets me: ==20817== Invalid read of size 4 ==20817== at 0x804AED5: dStr_insert_l (dlib.c:287) ==20817== by 0x804AFB5: dStr_append_l (dlib.c:308) ==20817== by 0x8049317: main (datauri.c:332) ==20817== Address 0x41cbbb0 is 0 bytes after a block of size 664 alloc'd ==20817== at 0x402AE29: realloc (vg_replace_malloc.c:662) ==20817== by 0x804A736: dRealloc (dlib.c:53) ==20817== by 0x804918B: datauri_get_data (datauri.c:273) ==20817== by 0x80492E1: main (datauri.c:324) ==20817== ==20817== ==20817== Process terminating with default action of signal 11 (SIGSEGV): dumping core Valgrind has options for debugging, but I haven't had any luck with getting them to work so far. I'm imagining that this might have to do with only being able to send part of the data at a time when everything's sluggish due to valgrind, but I don't know datauri/dpip well enough to go straight for the most likely spots... PS I don't trust the "by 0x8049317: main (datauri.c:332)" line because I have -O0, and sometimes it's had some 0x40... address instead that it describes as being below main. PPS I find myself wishing that we could have the dpis back in dillo.

2 2

missing redraw?
by corvid＠lavabit.com Nov. 18, 2012

Nov. 18, 2012

I was looking at the source for http://omicsomics.blogspot.com/ , and there was a little bit of first-column background color visible in the second column. Switching to another tab and back shows that the first column is really a little wider than what is initially seen. This problem appears to pre-date the inclusion of hyphenation.

2 1

Handling preferences
by sgeerken＠dillo.org Nov. 16, 2012

Nov. 16, 2012

Hi! I'm just working on making some values related to hyphenation configurable via dillorc. A long time ago (before the Fltk port), Dw directy accessed the prefs module for the value limit_text_width. When Dw was ported to Fltk (which was largely a rewrite), it was seperated, so it does not depend on prefs anymore. However, this made it necessary to pass the value of prefs.limit_text_width to dw::Textblock in the constructor. Now, I do not want to extend dw::Textblock::Textblock() by a couple of new parameters. Instead, I though of storing the values directly in Dw (initialized by feasable standard values), and the prefs parser must store them there. This way, Dw is still independent. This could be adapted in other modules. Currenty, my code is this: 1. The new values are still stored in DilloPrefs. 2. There is a static method dw::Textblock::init, which called in main, after the prefs parser: @@ -50,6 +50,7 @@ #include "auth.h" #include "dw/fltkcore.hh" +#include "dw/textblock.hh" /* * Command line options structure @@ -359,6 +360,8 @@ a_Cookies_init(); a_Auth_init(); + dw::Textblock::init (prefs.penalty_hyphen, prefs.penalty_hyphen_2); + /* command line options override preferences */ if (options_got & DILLO_CLI_FULLWINDOW) prefs.fullwindow_start = TRUE; Any thoughts/comments? Sebastian

3 5

fill in that little square that the scrollbars form
by corvid＠lavabit.com Nov. 14, 2012

Nov. 14, 2012

I don't know this drawing/damage code well enough to know whether this is the best way to go about it, but it appears to work.

2 1