- Dillo-dev - lists.mailman3.com

[Thank you very much.]

by jcid＠dillo.org

On Fri, Aug 06, 2010 at 11:14:55AM +0200, Johannes Hofmann wrote: > On Fri, Aug 06, 2010 at 11:00:05AM +0200, Johannes Hofmann wrote: > > Hi, > > > > > > > > I'm an Ubuntu user. My connection speed is just 5kbps. > > > Dillo is just amazing!! It opens the web pages in seconds. > > > > That's good to hear. > > > > > > > > When i right click on a web page, it automatically chooses previous > > > option. Thank you very much. > > > > Yeah, that's a nice feature of the fltk toolkit. It does this > > automatically. > > > > > > > > But I'm not be able to view 'TAMIL' language sites. Is there anyway to > > > view tamil sites? > > > > What exactly does not work? Are you seeing little square instead of > > tamil characters? > > In that case you can try to install FreeSans and FreeSerif, which > > are part of the freefont package. > > Then change the fonts in your dillorc to: > > > > font_sans_serif="FreeSerif" > > font_sans_serif="FreeSans" > > Argh, that should of course read: > > font_serif="FreeSerif" > font_sans_serif="FreeSans" Just forwarded a corrected version to the guy, and suggested a dillo-dev subscription if he wants to follow the thread. -- Cheers Jorge.-

Aug. 6, 2010

[Thank you very much.]

by Johannes.Hofmann＠gmx.de

On Fri, Aug 06, 2010 at 11:00:05AM +0200, Johannes Hofmann wrote: > Hi, > > > > > I'm an Ubuntu user. My connection speed is just 5kbps. > > Dillo is just amazing!! It opens the web pages in seconds. > > That's good to hear. > > > > > When i right click on a web page, it automatically chooses previous > > option. Thank you very much. > > Yeah, that's a nice feature of the fltk toolkit. It does this > automatically. > > > > > But I'm not be able to view 'TAMIL' language sites. Is there anyway to > > view tamil sites? > > What exactly does not work? Are you seeing little square instead of > tamil characters? > In that case you can try to install FreeSans and FreeSerif, which > are part of the freefont package. > Then change the fonts in your dillorc to: > > font_sans_serif="FreeSerif" > font_sans_serif="FreeSans" Argh, that should of course read: font_serif="FreeSerif" font_sans_serif="FreeSans" Cheers, Johannes

Aug. 6, 2010

[Thank you very much.]

by Johannes.Hofmann＠gmx.de

Hi, > > I'm an Ubuntu user. My connection speed is just 5kbps. > Dillo is just amazing!! It opens the web pages in seconds. That's good to hear. > > When i right click on a web page, it automatically chooses previous > option. Thank you very much. Yeah, that's a nice feature of the fltk toolkit. It does this automatically. > > But I'm not be able to view 'TAMIL' language sites. Is there anyway to > view tamil sites? What exactly does not work? Are you seeing little square instead of tamil characters? In that case you can try to install FreeSans and FreeSerif, which are part of the freefont package. Then change the fonts in your dillorc to: font_sans_serif="FreeSerif" font_sans_serif="FreeSans" Note however, that you might also need to force the use of these new default fonts in case the webpage chooses a different font explicitely. To do that add e.g. * {font-family: sans-serif !important} to your ~/.dillo/style.css file. Hope that helps, Johannes

Aug. 6, 2010

[sethupathy3e@gmail.com: Thank you very much.]

by jcid＠dillo.org

-- Cheers Jorge.-

Aug. 5, 2010

[patch]: do not let '>' terminate a quoted attribute value

by onepoint＠starurchin.org

If you point dillo at http://www.reddit.com/ you will see many javascript fragments. These come from div elements with an onclick="$(this).vote('<$>votehash</$>', null, event)" attribute. Dillo thinks that the '>' looks suspiciously like an end tag character. It looks ahead, sees the '<' character and decides that its suspicions are correct, so it terminates the tag at the '>', warns of a missing attribute close quote and renders the rest as HTML. This algorithm may have been effective in the early days of the web but I think it clearly does not work well today. I can't think of a better way of doing the job so I suggest removing it and instead just finding the matching close quote in all cases. Patch attached. After applying this patch dillo reports 0 HTML errors from http://www.reddit.com/! Regards, Jeremy Henty

Aug. 1, 2010

[patch]: fix .hgignore

by onepoint＠starurchin.org

corvid wrote: > Jeremy wrote: > > The problem was that .hgignore contains a line "dillo", which > > ignores every file with the string "dillo" anywhere in its path. > > Many other lines in .hgignore are similarly inappropriate. It > > looks as though these lines were written to be interpreted as > > glob-style patterns, but in fact mercurial interprets every line > > as a regexp. > > Looking in http://www.selenic.com/mercurial/hgignore.5.html it seems > that specifying "syntax: glob" is also a possibility. Yes, glob syntax might well be better, but either way the current .hgignore is not working as it should and could do with fixing. Regards, Jeremy Henty

July 31, 2010

[patch]: fix .hgignore

by corvid＠lavabit.com

Jeremy wrote: > I was freaking out a bit for a while there because I had created some > files with names like dillo_hg_* and "hg status" was not reporting > them as untracked, even though I had not "hg add"-ed them. > > The problem was that .hgignore contains a line "dillo", which ignores > every file with the string "dillo" anywhere in its path. Many other > lines in .hgignore are similarly inappropriate. It looks as though > these lines were written to be interpreted as glob-style patterns, but > in fact mercurial interprets every line as a regexp. Looking in http://www.selenic.com/mercurial/hgignore.5.html it seems that specifying "syntax: glob" is also a possibility.

July 31, 2010

[patch]: fix .hgignore

by onepoint＠starurchin.org

I was freaking out a bit for a while there because I had created some files with names like dillo_hg_* and "hg status" was not reporting them as untracked, even though I had not "hg add"-ed them. The problem was that .hgignore contains a line "dillo", which ignores every file with the string "dillo" anywhere in its path. Many other lines in .hgignore are similarly inappropriate. It looks as though these lines were written to be interpreted as glob-style patterns, but in fact mercurial interprets every line as a regexp. So here's patch to make .hgignore a little more sensible. Regards, Jeremy Henty

July 30, 2010

[patch]: Capi_filters_allow(): improve the logging

by corvid＠lavabit.com

Jeremy wrote: > Another skirmish in my eternal war against uninformative log messages! > :-) Patch attached. Rearranged slightly and committed. > BTW, dillo's loging is quite a mischmasch of different formats. Would > there be any interest in patches to make things more consistent: > eg. by always having the function name at the beginning of MSG calls? > That would help debugging, I think. I, for one, would at least be open to the idea. I see that compiling png.c gives me warnings now. I'll have to see what that's all about...

July 30, 2010

[patch]: Capi_filters_allow(): improve the logging

by onepoint＠starurchin.org

Another skirmish in my eternal war against uninformative log messages! :-) Patch attached. BTW, dillo's loging is quite a mischmasch of different formats. Would there be any interest in patches to make things more consistent: eg. by always having the function name at the beginning of MSG calls? That would help debugging, I think. Regards, Jeremy Henty

July 30, 2010