- Dillo-dev - lists.mailman3.com

hyphenation in dillo

by corvid＠lavabit.com

The borders on the "Search results" and "Nutrient values" boxes are overlapping on http://www.bitelog.com/mega-food-search.htm?q=masa

Sept. 27, 2012

hyphenation in dillo

by sgeerken＠dillo.org

On Wed, Sep 26, Jorge Arellano Cid wrote: > On Fri, Sep 14, 2012 at 12:38:46PM +0200, Sebastian Geerken wrote: > > On Thu, Sep 13, Alexander Voigt wrote: > > > On Mon, Sep 10, 2012 at 08:45:22PM +0200, Sebastian Geerken wrote: > > > > No, not yet. BTW: I haven't understood whether "xml:" is a normal > > > > namespace prefix (for which namespace?) or is specialy reserved (and > > > > may so not be used as namespace prefix). In the latter case, support > > > > would be rather simple. > > > > > > As written in [1], the "xml:" prefix is bound to the namespace > > > http://www.w3.org/XML/1998/namespace , which is reseved for the W3C. > > > This means that the nobody, except the W3C, can reuse this prefix for > > > their own namespace. > > > > > > So, as long as the meaning of "xml:lang" does not change (which is > > > very unlikely), it can be interpreted in the same way as the "lang" > > > attribute. > > > > So, this simple patch (or similar): > > > > ---------------------------------------------------------------------- > > [...] > > ---------------------------------------------------------------------- > > > > would work, without bothering about XML namespaces (in the near > > future). What do the other developers think? > > Yes, it looks OK to me. > > I'd go with the attached patch (a bit more explicit, +comments) > > Feel free to commit. Done. Sebastian

Sept. 27, 2012

hyphenation in dillo

by jcid＠dillo.org

Hi Sebastian, On Fri, Sep 14, 2012 at 12:38:46PM +0200, Sebastian Geerken wrote: > On Thu, Sep 13, Alexander Voigt wrote: > > On Mon, Sep 10, 2012 at 08:45:22PM +0200, Sebastian Geerken wrote: > > > No, not yet. BTW: I haven't understood whether "xml:" is a normal > > > namespace prefix (for which namespace?) or is specialy reserved (and > > > may so not be used as namespace prefix). In the latter case, support > > > would be rather simple. > > > > As written in [1], the "xml:" prefix is bound to the namespace > > http://www.w3.org/XML/1998/namespace , which is reseved for the W3C. > > This means that the nobody, except the W3C, can reuse this prefix for > > their own namespace. > > > > So, as long as the meaning of "xml:lang" does not change (which is > > very unlikely), it can be interpreted in the same way as the "lang" > > attribute. > > So, this simple patch (or similar): > > ---------------------------------------------------------------------- > diff -r d0a8d2a5ede3 src/html.cc > --- a/src/html.cc Thu Sep 13 12:35:54 2012 +0200 > +++ b/src/html.cc Fri Sep 14 12:35:38 2012 +0200 > @@ -3448,6 +3448,15 @@ > html->styleEngine->setNonCssHint(PROPERTY_X_LANG, > CSS_TYPE_STRING, > attrbuf); > } > + > + if (tagsize >= 14) { /* TODO prefs.hyphenate? */ > + /* length of "<t xml:lang=i>" */ > + attrbuf = Html_get_attr2(html, tag, tagsize, "xml:lang", > + HTML_LeftTrim | HTML_RightTrim); > + if (attrbuf) > + html->styleEngine->setNonCssHint(PROPERTY_X_LANG, > CSS_TYPE_STRING, > + attrbuf); > + } > } > > static void Html_display_block(DilloHtml *html) > ---------------------------------------------------------------------- > > would work, without bothering about XML namespaces (in the near > future). What do the other developers think? Yes, it looks OK to me. I'd go with the attached patch (a bit more explicit, +comments) Feel free to commit. -- Cheers Jorge.-

Sept. 26, 2012

Doxyfile

by sgeerken＠dillo.org

On Sun, May 27, 123 wrote: > By the way new Doxygen supports Markdown[1] and it is enabled by > default. It is easier to read and write than HTML. index.doc rewritten > using markdown is attached. Existing documentation (especially .txt > files) can be converted to markdown too. > > [1] http://daringfireball.net/projects/markdown/ Yes, this looks interesting, and I've started new documentation using Markdown (in the floats repository). Although I do not plan to convert the existing documentations, at least as long as there are different repositories to merge. Thank you for the hint. Sebastian

Sept. 26, 2012

Key binding for viewing page source

by Hole.destructor＠gmx.de

Hi. Jeremy Henty wrote: > Jorge Arellano Cid wrote: > > > BTW, as you use viewsource very often, what do you like best for > > displayed HTML lines, one long scrollable line or wrapping? > > Pardon me for butting in here, but I use view source quite a lot and I > would definitely prefer wrapping. (Is wrapping supported at the > moment?) Many Web sites ship HTML with absurdly long lines which > makes viewing their source practically impossible - horizontal > scrolling is very little help when the line is around 50 screen widths > long (sadly this is not an exaggeration). I also like line wrapping more than scrolling horizontally. When you want to read the HTML code with long lines, it is more convenient to have only one scrolling direction (vertically) instead of two (vertically + horizontally). Best, Alex

Sept. 23, 2012

Key binding for viewing page source

by corvid＠lavabit.com

Jeremy wrote: > Jorge Arellano Cid wrote: > > BTW, as you use viewsource very often, what do you like best for > > displayed HTML lines, one long scrollable line or wrapping? > > Pardon me for butting in here, but I use view source quite a lot and I > would definitely prefer wrapping. (Is wrapping supported at the > moment?) Many Web sites ship HTML with absurdly long lines which > makes viewing their source practically impossible - horizontal > scrolling is very little help when the line is around 50 screen widths > long (sadly this is not an exaggeration). I strongly prefer wrapping as well.

Sept. 23, 2012

[awards@nerdydata.com: Dillo.org Has Entered The Domain Hall Of Fame]

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > FYI, I received this email. After following the link, the map data > looks quite interesting, but it turns to be the same for lwn.net, > and other sites... > > Comments? I am very skeptical. How can they know how much traffic our domain gets? It sounds to me like they would like to sell us some useless service by kidding us that it matters how their site ranks us. I would ignore it. Regards, Jeremy Henty

Sept. 23, 2012

Key binding for viewing page source

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > BTW, as you use viewsource very often, what do you like best for > displayed HTML lines, one long scrollable line or wrapping? Pardon me for butting in here, but I use view source quite a lot and I would definitely prefer wrapping. (Is wrapping supported at the moment?) Many Web sites ship HTML with absurdly long lines which makes viewing their source practically impossible - horizontal scrolling is very little help when the line is around 50 screen widths long (sadly this is not an exaggeration). Regards, Jeremy Henty

Sept. 23, 2012

[awards@nerdydata.com: Dillo.org Has Entered The Domain Hall Of Fame]

by jcid＠dillo.org

Hi there, FYI, I received this email. After following the link, the map data looks quite interesting, but it turns to be the same for lwn.net, and other sites... Comments? -- Cheers Jorge.-

Sept. 23, 2012

packed trie for hyphenation patterns in the main repository

by jcid＠dillo.org

On Thu, Sep 20, 2012 at 10:21:14PM +0200, Johannes Hofmann wrote: > 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. OK, now I'm using the *trie files. BTW, they're bigger than the original *pat files; I assume this is OK. -- Cheers Jorge.-

Sept. 23, 2012