You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
(33) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(17) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(6) |
Jul
(4) |
Aug
(2) |
Sep
(5) |
Oct
(2) |
Nov
(2) |
Dec
|
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
(1) |
2014 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
(1) |
17
(2) |
18
(2) |
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
|
From: Vincent M. <vi...@ma...> - 2017-05-18 07:14:01
|
Hi David, > On 17 May 2017, at 20:54, David Schweinsberg <dav...@gm...> wrote: > > Hi Vincent, > > As Ronald says, cssparser would have to work in conjunction with other code to apply the style to the DOM. I've not used it myself, but would something like CSSelly (http://jodd.org/doc/csselly/) do the job? Thanks for the link to csselly which I didn’t know. I’m adding it to my list of things to explore! TBH ATM it seems a bit complex to move away from CSS4J to CSSParser + something else bit if we get too many problems in the near future we may have to go down that route. Thanks -Vincent > > Best regards, > David > > On 17 May 2017 at 12:24, Ronald Brill <rb...@rb...> wrote: > Hi Vincent, > > thanks for considering CSSParser as alternative solution. > CSSParser is a smaller/more focused solution; only parsing the css into some tree sturcture is the current focus of the project. There is no support to parse (X)Html and also no > help for mixing the two trees into one. > As far as i know there are two main use cases for CSSParser at the moment: > * parsing a css for error detection or optimization and optional writing back the optimized version (The cleanup/optimization is not part of CSSParser) > * parsing a css to support html processing > > The second case is what is done by HtmlUnit (i'm also involved with this project). HtmlUnit uses NekoHtml to parse (X)Html and CSSParser for css. Then HtmlUnit uses both > informations to simulate real browser behavior. > If you like i can think a bit if your use case is someting that can be done with HtmlUnit - give me a sign and i will have a look ;-) > > Outside of this i'm a bit curious about your case. Usually the css is separated from the Html by idea. Why you like to merge this? > > RBRi > > On Tue, 16 May 2017 18:18:56 +0200 Vincent Massol wrote: > > > >Hi guys, > > > >On the XWiki project (http://xwiki.org) we're currently using CSS4J but it's painful (several bugs, no issue tracker, no mailing list) so we're considering migrating to another > library and we're looking at CSSParser. > > > >We use CSS4J to do the following: apply some CSS content to XHTML. > > > >For example: > > > >CSS: > >"span { color:red; }" > > > >XHTML: > >... > ><div id="xwikicontent"> > > <p><span style="background: white;">Hello</span></p> > ></div> > > > > > >Result: > >... > ><div id="xwikicontent"> > > <p><span style="background: white; color: red;">Hello</span></p> > ></div> > > > > > >Is that possible to do with CSSParser? > > > >FTR this is our code where we use CSS4J: > >* > https://github.com/xwiki/xwiki-platform/blob/30d27eb8ec23f7c5a28ca505a75f1c73f8fe0073/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xw > iki/pdf/impl/PdfExportImpl.java#L460-L460 > >* > https://github.com/xwiki/xwiki-platform/blob/30d27eb8ec23f7c5a28ca505a75f1c73f8fe0073/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xw > iki/pdf/impl/PdfExportImpl.java#L506 > > > >Thanks > >-Vincent > >------------------------------------------------------------------------------ > >Check out the vibrant tech community on one of the world's most > >engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >_______________________________________________ > >cssparser-developers mailing list > >css...@li... > >https://lists.sourceforge.net/lists/listinfo/cssparser-developers > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > cssparser-developers mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/cssparser-developers > > > > -- > David > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > cssparser-developers mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/cssparser-developers |
From: Vincent M. <vi...@ma...> - 2017-05-18 07:11:05
|
Hi Ronald, > On 17 May 2017, at 21:24, Ronald Brill <rb...@rb...> wrote: > > Hi Vincent, > > thanks for considering CSSParser as alternative solution. > CSSParser is a smaller/more focused solution; only parsing the css into some tree sturcture is the current focus of the project. There is no support to parse (X)Html and also no > help for mixing the two trees into one. > As far as i know there are two main use cases for CSSParser at the moment: > * parsing a css for error detection or optimization and optional writing back the optimized version (The cleanup/optimization is not part of CSSParser) > * parsing a css to support html processing > > The second case is what is done by HtmlUnit (i'm also involved with this project). HtmlUnit uses NekoHtml to parse (X)Html and CSSParser for css. Then HtmlUnit uses both > informations to simulate real browser behavior. > If you like i can think a bit if your use case is someting that can be done with HtmlUnit - give me a sign and i will have a look ;-) > > Outside of this i'm a bit curious about your case. Usually the css is separated from the Html by idea. Why you like to merge this? Thanks for your reply. Yes I agree that the use case may look weird from the outside :) So let me explain. This is for the XWiki PDF export. The big steps are (better explained here: http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration#HCustomizingthePDFexportLook26Feel): * Render a wiki page into XHTML * Apply CSS4J to merge the pdf.css and user-customized CSS for PDF export into the generated XHTML * Apply a xhtml2fo.xsl XSL stylesheet to generate XSL-FO * Use Apache FOP to convert from XSL-FO to PDF The problem is probably because XSL-FO doesn’t support defining the styles into CSS so in any case there’s a need to convert the CSS into something usable by XSL-FO processors such as Apache FOP. I did a quick search and found http://stackoverflow.com/questions/17495152/using-external-css-in-xsl-fo but that is far from simple and requires to convert CSS into some XSL. Thanks -Vincent > RBRi > > On Tue, 16 May 2017 18:18:56 +0200 Vincent Massol wrote: >> >> Hi guys, >> >> On the XWiki project (http://xwiki.org) we're currently using CSS4J but it's painful (several bugs, no issue tracker, no mailing list) so we're considering migrating to another > library and we're looking at CSSParser. >> >> We use CSS4J to do the following: apply some CSS content to XHTML. >> >> For example: >> >> CSS: >> "span { color:red; }" >> >> XHTML: >> ... >> <div id="xwikicontent"> >> <p><span style="background: white;">Hello</span></p> >> </div> >> >> >> Result: >> ... >> <div id="xwikicontent"> >> <p><span style="background: white; color: red;">Hello</span></p> >> </div> >> >> >> Is that possible to do with CSSParser? >> >> FTR this is our code where we use CSS4J: >> * > https://github.com/xwiki/xwiki-platform/blob/30d27eb8ec23f7c5a28ca505a75f1c73f8fe0073/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xw > iki/pdf/impl/PdfExportImpl.java#L460-L460 >> * > https://github.com/xwiki/xwiki-platform/blob/30d27eb8ec23f7c5a28ca505a75f1c73f8fe0073/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xw > iki/pdf/impl/PdfExportImpl.java#L506 >> >> Thanks >> -Vincent >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> cssparser-developers mailing list >> css...@li... >> https://lists.sourceforge.net/lists/listinfo/cssparser-developers >> > |