- Dillo-dev - lists.mailman3.com

hyphenation in dillo

by corvid＠lavabit.com

Sebastian wrote: > > I'm mostly finished with cleaning up the calculation of extremes (used > > for tables). This should already work now, please test it again. > > Just pushed some more changes; should be complete now. Please test > thoroughly. I'm noticing occasional overlapping of text with alt text (example from linuxquestions.org: http://www.dillo.org/test/alt_text.jpg ), and, when I load those images, I see that there's some clipping ( http://www.dillo.org/test/img_clipped.jpg ).

Sept. 4, 2012

hyphenation in dillo

by sgeerken＠dillo.org

On Tue, Sep 04, corvid wrote: > On http://www.dillo.org/stats/ , it breaks between the month and year. Fixed. Look at the change: it's simple. Unlike before, breaks are also prohibited for "white-space: pre-wrap"; this is how I interpret the CSS spec. Sebastian

Sept. 4, 2012

hyphenation in dillo

by corvid＠lavabit.com

Sebastian wrote: > Just pushed some more changes; should be complete now. Please test > thoroughly. On http://www.dillo.org/stats/ , it breaks between the month and year.

Sept. 4, 2012

hyphenation in dillo

by sgeerken＠dillo.org

> > Just pushed some more changes; should be complete now. Please test > > thoroughly. > > Nice! lwn.net and wikipedia look good for me now, but the text on the > splash screen seems a bit squeezed. I see no difference to the current main repository. I investigated this already some days ago, and found out that paragraphs are handled differenty. Defining a margin for paragraphs works, OTOH. So this is no reason to delay merging. :-) Sebastian

Sept. 4, 2012

hyphenation in dillo

by johannes.hofmann＠gmx.de

On Tue, Sep 04, 2012 at 02:36:29PM +0200, Sebastian Geerken wrote: > > I'm mostly finished with cleaning up the calculation of extremes (used > > for tables). This should already work now, please test it again. > > Just pushed some more changes; should be complete now. Please test > thoroughly. Nice! lwn.net and wikipedia look good for me now, but the text on the splash screen seems a bit squeezed. Johannes

Sept. 4, 2012

hyphenation in dillo

by sgeerken＠dillo.org

> I'm mostly finished with cleaning up the calculation of extremes (used > for tables). This should already work now, please test it again. Just pushed some more changes; should be complete now. Please test thoroughly. Sebastian

Sept. 4, 2012

hyphenation in dillo

by sgeerken＠dillo.org

On Wed, Aug 22, Jorge Arellano Cid wrote: > There're glitches, sure. Just in case you don't yet have a > reliable test case, lwn.net has problems with screen redraw. > Lefthand margin. I'm mostly finished with cleaning up the calculation of extremes (used for tables). This should already work now, please test it again. Sebastian

Aug. 31, 2012

google translate and non-ascii characters

by andreas＠kemnade.info

Hi, On Sat, 2012-08-25 at 20:10 +0000, corvid wrote: > Andreas wrote: > > 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. > > With our default http_user_agent setting, I see this problem as well. > With it set to a firefox string, translate.google.com seems to work fine. > setting it to a firefox string gives <meta content="text/html; charset=UTF-8" http-equiv="content-type"> instead of <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> but google seem to always want utf-8 from the html form. So it seems to be a clear google bug. Greetings Andreas Kemnade

Aug. 26, 2012

google translate and non-ascii characters

by andreas＠kemnade.info

Hi, On Sat, 25 Aug 2012 20:10:09 +0000 "corvid" <corvid at lavabit.com> wrote: > Andreas wrote: > > 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. > > With our default http_user_agent setting, I see this problem as well. > With it set to a firefox string, translate.google.com seems to work fine. > I captured a http request and recoded it to utf-8 and send it using netcat. The result was that google correctly translated that without changing user agent. So does google do a workaround for firefox problems, or is google broken and/or is dillo broken here? Greetings Andreas Kemnade

Aug. 26, 2012

google translate and non-ascii characters

by corvid＠lavabit.com

Andreas wrote: > 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. With our default http_user_agent setting, I see this problem as well. With it set to a firefox string, translate.google.com seems to work fine.

Aug. 25, 2012